Midibox 2nd loop Hesitation.
I'm nearing the end of 7 nights of work and decided to play Unify before I left for work. I was going through my Rex Patch Drum Loops. I was creating a new one, and noticed that on the second time through it always hesitates before looping. Always plays right the first time, hesitates 2nd time. It was not doing this before. And it's now doing it on every single one of them. I know John says you optimized Midibox. So?
I need more to go on, Kendall. Please post a patch that illustrates the problem? As I've advised before, pare it down to the absolute simplest form before posting.
Sorry was running late to leave but wanted to a post to remember the issue. I’ll get it Thursday afternoon when I wake up. After thinking about it it’s more like it’s chopping the end of the measure off. And these are the midi files that are created by Recycle when I export the wav file.
I figured I'd just send my T-Rex library completely, most of the issues are with these Patches. Before one of the latest beta it wouldn't do this. As far as I can remember. Just don't remember which one. I also included a video showing the issue. I had played every patch, before I sent these to John, so I was sure they were playing correctly. A few didn't show it doing it but I figured they were simple and spread out enough where there wasn't data near the end of the midi file. But I've only been noticing it on a majority of my Rx2 drum patches using Midibox.
Here's the Video
I emailed the Library to you since I didn't mark this one private
I can work with these, thank you. There is definitely an issue with notes getting dropped at the end of the sequence. I'll dig in and see what I can find.
What I've found so far is that all four MIDI files have the final note-off at the exact end of the sequence, and this is throwing off MIDIBox somehow. Probably an easy fix, and I'm super-glad to have found this issue.
In the meantime, if you bring the files into a MIDI editor and shorten the last note by even one tick, they'll play correctly.
I've attached a zip file with the four MIDI files edited in this way using MidiEditor, a free Windows MIDI editor.
I've looked at them in MidiEditor, but they all look the same to me. I've even compared ones you've "fixed" with the ones I was originally using and they look the same to me. Maybe if you create another app for those of us who can't seem to get them basic enough and call it "Midi Morons". It would probably outsell Unify. Ok here's a head scratcher. Everything I've done so far is in the standalone version on my PC. I just now played it inside Unify on a track in Reason and it played right with the original midi file. Every time. They're all playing right.
The one thing that frustrates me the most, why is Recycle putting out some midi files that work fine and some are giving me the problem they are?
ReCycle is working just fine. It's MIDIBox that is wrong, and your files have helped me find the bug. I'll get a fix out as soon as I can, but that will probably be at least a week from now because I'm slammed with other stuff. So for the meantime, I've tried to explain how to tweak the MIDI files that ReCycle makes, so they don't trigger the MIDIBox bug. They look the same because all I did was shorten the final notes by one tick.
None of this reflects badly on you. You're perfectly right to expect it to just work and it doesn't right now. Furthermore, the fix is really intricate, and a pain in the butt to do manually. I'm sorry about that.
Email me a zip of ALL your MIDI files and I'll fix them for you and send them back. I'm happy to do so.
Two of the midi files were still skipping. The original clone and the Syncopated Jazz Drums. I went ahead and opened it in reason and shortened them both by 1/256th note and they're both working now. The odd part was when I opened each of them to edit, they opened with an extra 1/4 measure added on. So if I find any I'll save you some time and edit them but I appreciate the offer. But does this mean they'll play short with the Bug fix?
does this mean they'll play short with the Bug fix?
I don't know until I actually fix the bug, but I would hope not.
Sorry it's been so long. I wanted to let you know I've made some progress on this issue, and I hope to have a beta out soon, that you can test with.
Was wondering also if you had ever got a chance to talk to Reason Studios and their plugin about the issue there and/or heard back from them?
I'll take a look at the beta here in a bit. Gotta take a nap before I work tonight.
I can't reproduce the Reason issue on either my Win10 PC or my Mac. No point contacting them until I can tell them how to reproduce the problem.