Edirol Orchestra - Hanging notes after render

Hope someone can help me out. This is the last thing I want to iron out before I commit to buying. Using Edirol Orchestra, everything is set up properly, with one vst instance routing to four tracks inside a folder. It sounds great playing the project inside reaper, but when I render the entire project to a wav file I get hanging notes on a few of the midi tracks, sounds like a train wreck. I've searched the forum but couldn't find an answer, even in this thread: I can get around it by "save live output to disk" and it works. Anyone know if you get the same quality when doing this you get when rendering to a wav? Is there a way of converting a midi file to a wav file inside reaper, which takes the vst you're using with it? Better yet is there a way of eliminating these hanging notes from the rendered wav file? I'd really appreciate some help, it's probably something simple or a problem with the vst? PS. When I close down a project and open it up later, ReaVerb, ReaEQ, ReaComp and the JS limiter revert back to default and all the changes I've made to each disappear. So a decent mix becomes a bad mix! Again probably something simple but can't figure it out. Thanks.

Strange. I find the same thing happening with the Edirol Super Quartet, which is the same vintage and a similar kind of design as the Orchestral. This is the DXi version. I didn't try the "save live output to disk" option but I tried various other render options and it was always the same. But it played back inside Reaper OK. Only renders have the problem.

Have you tried the setting in the Audio Preferences to limit FX rendering to real time? I had problems rendering a few VSTs to .wav (don't have Edirol)and this solved them, though of course the process goes more slowly.

hmm.. to render the midi plus ur fx to a wav file... just choose "apply fx as new take" when right clicking the region... did u save ur project before exiting.. i have never encountered that.. and cant help with that. ^^

Can you post the RPP file?

Hello ajfm, I had the same problem a while back when I was writing a piece but I later realized that it only happened with the dxi version of the plugin, I switched to the vsti version and everything was cool. One thing I noticed is that reaper doesn't read dx plugins 100% (it does a good job but not a great job), but most daws have some problems reading one or the other. Try using the vsti version to see if that makes a difference.

Hi jonespnice. I just tried switching to the VST version of the Edirol Super Quartet and I got the same thing happening at the same points of the render, basically two points about 2/3 into the 3 min song. It sounds like some notes -- the same ones every time -- are not reciving their notes off, or a sus pedal up command. But when I look at the MIDI data itself, it's all clean. (No pedals in any case.) And it plays back ok realtime in R. It's just a render thing. Rendering with 1x settings doesn't fix it... but then I don't think I've successfully done a 1x... even with that setting it's rendering much faster than that. Oh well. I'll experiment some more next time I render. But it's not a big problem, I'm just using the Edirol as a temporary sound source for sketching out a song and getting more familiar with Reaper.

You could always mixdown to an external deck, if real time playback is working well- as a temporary work around. In fact, some prefer this over ITB renders. Dan

I have this same type of problem with other vsti plugins like ones from EastWest that use the kontakt player or kompakt... Plays fine in real-time but the render results in hanging and cut-off notes, and large sections of nothing. I've been told it's the vst's fault or my computer's fault for not having enough ram - but surely the playback would also NOT work? I thought "rendering" ensures the best possible quality. well... I guess not! Please try the same thing in other daws if you have them, or can get a demo. So far I've tried ACID and it does not have this issue. If we can confirm that other daws don't have this problem, then maybe the developers of reaper would look into it and see where a fix or work-around might be possible.

Thanks for all the tips. Still can't get it sorted though. It was the VST version I've been using, I guess I can live with rendering it in real time.