Midi Files in Midibox
So I'm working on patches for the collective library which will include a lot of original loops from audio I created, then edited in Reason Recycle to create RX2 files, then I export them into the "Wave Parts" which spits out a Midi file to go with them. As in the past it will play the whole file then when repeating it skips the end. I'll do a video and attach to show.
Does John have any issues at all? I do most of my editing with PC cause it's got the largest screen. I thought about trying to put it out on my Mac but Recycle just crashes as soon as I touch the Recycle window. Well I did actually get it to export the midi file, but was still doing the same thing.
So it was playing correctly the 1st, 5th, 9th, etc. But even then, it's not doing that every time. It's not doing it with the Bodhran Rx2 patches i made?!?! The midi files were created the same way with Recycle.
I'll include the midi files and Video. With all that being said, This only happens when I include in a BPM SPLIT. So when creating a BPM SPLIT, adding other UNIFY layers is when this is occurring. When I play the patch by itself it's not happening. But it was doing the Bodhran Patch correctly within the BPM SPLIT. I'm trying my best to try every possible scenario I can think of. I know I ramble.
I also re-edited the midi file in Reason and at a specific Tempo lined each part where they fell exactly on the lines but still did it.
File link in case it didn't attach here:
I've asked John if he can help. The one MIDI file I looked at (1.2) seems OK and plays OK for me. Can you please give more details about how you set up a "BPM SPLIT" patch, in particular, where is the MIDIBox instance?
The best thing would be if you can create a simplest-possible Unify patch (using only resources in the Unify Standard Library plus your MIDI file) that illustrates the problem, zip and post here. Otherwise I can't tell what you might be doing, that could be causing the issue.
One thought: double-check that you have MIDIBox's speed control set to exactly 100%.
That is a very weird conundrum! I have not experienced anything like that in a while now - I just recycled a number of grooves for the update for Cutting Edge: RAD Waves. They play solid, no lost notes 32 times in a row.
One question - is there a chance either a) there are 2 MIDI events on the same note or b) this is highly unlikely but could the sample map have 2 samples on that last note layered from the .sfz creation?
Very odd situation you have - I'm replying to your email to me on round robins shortly.
Life is Sound / Sound is Divine
I checked for the doubled notes using several methods, but the odd thing is it plays fine until I add other parts to it to create a BPM SPLIT. But even then it doesn't do it every time. Hey I sent an email to you about Round Robin notes. I was wanting to round robin the Irish Bodhran notes, just 3 notes RR, but wanted to be able to get a variation, wasn't sure how to set that up in the SFZ files. You happen to have a sample file I could compare to? Thanks
the odd thing is it plays fine until I add other parts to it to create a BPM SPLIT.
So you create a patch with one MIDIBox driving one instrument plug-in, then you add... what, another INST layer, an embedded Unify layer, ... ?
It would help if you could give a step-by-step example so I can try to reproduce the issue here. Preferably using the MIDI file(s) you already shared.
@getdunne Im going to finish up the patches today for the collective library and will hope to properly create the installable guru file and hopefully it will work when yall get it, im thinking that its just that my PC is 16 years old now. it takes so long to open patches anymore. ill notate the one BPM SPLIT i made that is showing the issue. i tried creating another complicated patch as so far it wasnt doing it but i ran out of time cause i went to play at a bar last night.
@pbeprod +10 for the gigging musician! Hopefully I can help get to the bottom of this for you.
@pbeprod, I have responded already by email.
For everyone else who may be following along, here's what happened. Kendall had set up BPM layers with a key-range set to B2 and below, but had set the key-range for the Unify Transport to B2 and up. As a result, when playing e.g. C1, the Transport would not start. The BPM layers would still play, but with the MIDIBox instances "free running", i.e., setting their own tempo to match the Transport's BPM setting. As it turns out, this isn't quite accurate enough, so the timing would deviate a bit.
As soon as I set the Transport's key-range to match that of the layers, the Transport would start and run as it should, and all the layers synced up correctly.
This was an easy mistake to make, and points out a bit of weakness in the Unify GUI. I'll write up something about it for the Unify manual, and ask John to demonstrate the issue on YouTube.
What Kendall has been cooking up is very impressive. Let's all look forward to checking out his patches in the Guru Nation Collective library!