![]() so I don't want to jump to conclusions yet but for thus far it seems like S1 is just not accurate enough to handle midi note off messages flawless. ![]() different routings and midi settings and stil no positive result.Īlso did a test with Ableton lite and i couldn't even replicate the hanging / freezing notes problem there. (sorry to be negative, just frustrated.Haven't found any solution yet. Opening up MIDI editor gives strange zoom behavior, recording MIDI gives stuck notes, notes get cut off when recording from project start, looping while recording gives several strange behaviors, MIDI notes get stretched through the entire clip, quantization don't work as expected etc etc. Right now, MIDI on Reaper is a "i have to assume this might not going to work as expected, but lets try anyway" feeling. Just as i expect predictable audio playback to be the basics of any DAW. Not when these kinds of bugs exist.Įffortless and predictable recording and playback of MIDI without bugs, issues or hangups is just the very basics of a MIDI-compatible DAW. This is why i never recommend Reaper to people who use a lot of MIDI or virtual instruments - no matter the endless eclectic possibilities through workarounds and scripting, the fundamentals are simply not there. That is a good way to solve the stuck notes issue, but it means Sonar has to analyze the entire MIDI file before playing it (which shouldn't be too much of a problem), and also it cannot do that whith live recording since you don't know in advance the duration of a note while recording it. That way it is technically impossible copy "Note ON" separately." Interestingly, I've read in the Cakewalk forum that "While that is true about Note ON/OFF, Sonar internally does not store Notes that way. The MIDI spec is unclear what to do in that case, so implementers are left guessing what to do in those cases, so it's best to avoid overlapping events altogether. What I've read though leads me to think that overlapping events is a widespread problem that isn't unique to Reaper, and that some VSTi don't deal correctly with overlapping events too. I don't know if Reaper also deals with the case ON ON OFF OFF. If it is, either it doesn't do a good work at it, or it is relatively new, because when I had the problem, it clearly wasn't doing it. Once I removed the overlapping notes, it solved the issue in my case.Īccording to a post I read, Reaper automatically merges overlapping events. In particular, I've had files downloaded from popular sites that had them and these files would lead to stuck notes (sometimes, one MIDI event could hide completely another one, leading to the sequence ON ON OFF OFF in the MIDI editor, though, you see only one note, as the other one is hidden under it). Nothing prevents MIDI files to contain overlapping events. ![]() Just FYI, I had (a long time ago) stuck notes with malformed MIDI files, in particular when several MIDI events were overlapping, aka when, on the same note, there was a MIDI event that was starting when the previous one wasn't finished. It makes Reaper almost unusable for music involving MIDI/VSTis. Are developers aware of these issues? For anyone working on complex midi arrangements this is extremely frustrating.Ĭan looking into this be a priority for the next update?
0 Comments
Leave a Reply. |