196,182 users have contributed to 43,014 threads and 258,396 posts.
In the past 24 hours, we have 0 new thread(s), 8 new post(s) and 168 new user(s).
I'm having problems now with Export Audio Mixdown using Vienna Ensemble Pro. If I export in real time, everything is OK but if I export normally, the VEP tracks start several seconds into the song. This is the same with both VEP vst3 and vst2 plugins however if I roll back to 4.0.5436, everything is fine. Has anyone else found this?
Also, I find version 4.0.5436 much quicker to "release" VEP when closing a Cubase project.
@beatpete said:
Has noone else found this export problem?
Yes, I noticed this exact problem. I ended up exporting 30 tracks one at a time at real time. Just left the station until it was done. I suppose it was introduced in Cubase 5.5, but I'm not rolling back. Hopefully, Vienna can sort this out on their end.
On the VEPro server I have 4 instances of Kontakt loaded, one with pianos and three with orchestral instruments. In Cubase 5.5, I have one instance of VEPro VST3 in the instrument rack being fed by 4 sets of 16 midi channels. In this particular case, I only had a piano playing but I tested in three different projects with orchestral stuff going on. I just tried recording a short piece from the beginning and all was well (in VEP 4.0.5436). I then re-installed VEP 4.0.6150 and recorded the same short piece and, alas, no piano. I hope this helps...(I'll be glad to send you the 2 short clips if you like)
I use two systems, one with Win7 64 and one with Vista 64. My Cubase project uses an instance of VEP locally and one on the remote system. It all works fine when composing and playing back even with 6150 and Cubase 5.5. If I export at real time it doesn't lose anything off of the front of the song. If I export faster than real time it loses the first 3-5 seconds of each track.
In my case I use MEAP to export one track at a time have this problem, so I know it's not too much data or anything. The export starts from the beginning of the midi track but you can see there is no meter movement in Cubase or the VE Pro mixer until it is part way into the export. At real time, the meters begin immediately and you don't lose anything.
I even tried just exporting one of my tracks manually and moving the midi data farther down but still starting the export area at the front of the timeline so as to give it a few seconds to start up -- but it still loses the first part of the music. I just assumed this was a Cuase 5.5 issue. But now beatpete makes me think it was introduced in the new VEP pro. For me it's just an inconvenience now.
@Karel said:
Do you experience this also without Kontakt in the VE Pro instance? Thanks.
Karel,
Just tested it. You may be onto something. With only the Vienna Instrument it exports properly. But with only a Kontakt 4 instrument, it misses almost the first nine seconds of the audio data.
@beatpete said:
CSTeam, are you using Kontakt 4.1?
Yes, I am. The test Karel suggested seems to narrow it down to Kontakt. And you may be right about the quickload feature.
@beatpete said:
did you try rolling VEP to 4.0.5436?
No if I may if I have the chance.
Karel, my happens when I don't have any Vienna Instruments in the VE Pro instance, just Kontakt 4.1.
@Karel said:
So having a Vienna Instruments in the VE Pro instance actually fixes the behavior?
It seems.
Karel, I was finally brave enough to migrate from v4686 which has been working well for ages, due to the lure of PLAY compatibility (I try not to update if everything is working!).
However, I've just encountered the same problem as the original poster. The severe delay while bouncing seems only to affect those instances of VEpro that have K4.1 loaded. I haven't discovered a fix and so am going to have to roll back to 4686.
Unlike the OP I'm on Cubase 4.5 in XP64. I'd love a solution or an update if you have one.
Regards
fwiw I took the OPs advice and rolled back to 5436 (rather than my old fave 4686!) and so far so good. Export Audio (bounce) is working again and even PLAY seems to be behaving. Seems to be an issue with the new release and K4.1. Hopefully PLAY 2.018 behaves with 5436.
Disclaimer - I've only been working 20 min or so. I'll post back if I get probs with either exporting or PLAY.
Brett
So far so good. 5436 is working better than 6150. PLAY is behaving, and audio export is fine. fwiw (and this prob belongs in another thread) but I noticed that 6150 would take a while to "let go" of Cubase once Cubase was shut down. 6150 also wouldn't let the computer shut down without force quitting on occasion. 5436 is fine in both regards.
Brett
@brett said:
So far so good. 5436 is working better than 6150. PLAY is behaving, and audio export is fine. fwiw (and this prob belongs in another thread) but I noticed that 6150 would take a while to "let go" of Cubase once Cubase was shut down. 6150 also wouldn't let the computer shut down without force quitting on occasion. 5436 is fine in both regards.
Brett
Exactly! Not only does 5436 export properly but it's much quicker to "let go" (as you said) of the VEPro plugin. Fortunately this is an acceptable workaround but a workaround none the less.