Unfortunately it seems that this issue is unlikely to be solved due to the way DP handles bouncing, so when using Audio/Event Input plugins in DP, freezing first is the only option at this point. I'll have a look at the viability of a MAS version of the VE Pro 5 Server Interface, which will at least circumvent the single MIDI input port limitation of AU without breaking bounce to disk functionality.
-
I for one am EXTREMELY excited to have the new VE Pro 5 functionality in DP!!!
Kudos to the VSL team for really listening to their users who have lobbied for a solution to the midi port issue for years now.
Bounce to disk is a non issue for me as I always submix everything down to a final stereo track (and stems) and run a print in real time anyway. The freezing tracks is also an acceptable workaround as I can freeze all my VI's in one pass if need be.
You guys are awesome and I just wanted to land some positive feedback as we often only comment in forums when things are exibiting problems.
cheers!
-
I'm a very happy DP7 user working with VEP5.
I don't use bounce though - I bus the inputs directly to stems in real time which is something DP can do which Logic and Cubase can't. I go from up to 90 or so VEP inputs to 12 mix stems then down to 3 delivery stems all in a single pass. I found that when I bounced mixes, too often there were glitches so Id have to review the mix anyway so I decided at least mixing to stems in real time, I know the whole mix is clean and it doesn't take any longer than checking the mixes. I still freeze things from VEP and that works fine but I wouldn't do that with each line of a mix unless I was going to prepare prerecords for a protools sessions when working with live players and mixing in an outside studio. Freezing works really well for that.
I'm far more frustrated by DP's lack of 64bit which is causing daily problems. (sigh)
-
Really can Cubase do that? I never found a way of doing that, but I will go and have another look. I know Logic can't (unless you use Apogee Symphony and VBus). I have to say I'm really impressed with Cubase overall and if I moved off DP then I think Cubase would be a safer bet than Logic at the moment.
-
@flashman said:
Really can Cubase do that? I never found a way of doing that, but I will go and have another look. I know Logic can't (unless you use Apogee Symphony and VBus). I have to say I'm really impressed with Cubase overall and if I moved off DP then I think Cubase would be a safer bet than Logic at the moment.
Cubase can record directly to an audio track from a Group track or an output (real, or dummy), so recording stems in real time is easy. . Let me know if you want to try it, and I'll talk you through it.
Cubase can also do a quick bounce of stems as well, for those people who don't want to listen to their music as it goes down.
DG
-
While I'm not using VEP 5 yet, I am able to get around the no Bounce feature by printing live into my session. I then disconnect Instances of VEP with a single click and am able to bounce to disk (which I do instead of exporting because I apply a mastering plugin). One of these days I will print in real time through the mastering plugin and just export as needed.
-
Hi Flashman,
I'm a DP 7 user and I've put this out in the forums and even tech support, but no one has addressed it. I love VE Pro 5, but what I miss about multiple instances is being able to freeze multiple midi tracks into their own separate audio tracks for mixing in one pass. Can you tell me how to do this with VE Pro 5? Is there even a way to do this, or do I have to freeze each midi track separately, one by one.
Thanks!
-
... never mind, i figured it out. it astounds me how clueless i can be at times :)
-
Karel, I don't know which - or what combination of the two - it might be? But tonight, using the newest VEPro5 (11548) and the newest Digital Performer (8), I *was* able to bounce a midi track to audio in DP! Did this get recently fixed?
-
Willie, just to clarify, we've always been able to bounce normal MIDI tracks going to the first 16 channels of a VEP instance. The question is whether we can bounce MIDI tracks using VEP Event Input to more than the first 16. Can you confirm whether that's what you did? I was holding off on buying DP* as I normally wait for the .1 update of any software, but if you're bouncing Event Input tracks, I'll order today!
-
Randin, yes I can confirm that I did this successfully a couple of days ago with DP8 & VEP5. I had an empty DP8 seq., with a single instance of VEP5 containing a single Kontakt5 instrument, and a single instance of VEP5Event routed to that K5 instrument. I selected the midi info in DP8 and "bounced to wav" and success! I've got the wav to prove it!@didger said:
The question is whether we can bounce MIDI tracks using VEP Event Input to more than the first 16. Can you confirm whether that's what you did?**BUT**, I haven't been able to replicate it! The only thing that I've changed is that, at the time, I'm pretty sure I was still on VEP5 "11262". And now, I've upgraded to VEP5 "11548". And now, when I try and bounce the midi track, I either get an empty wav, or one with broken notes.
So, not sure where it all is yet, I'll be most anxious to hear what Karel's tests indicate?
-
So far I haven't found any problems with VE Pro 5 and DP8. And indeed, bouncing with the Audio/Event Input plugin seems to work flawlessly. Mind that all affected tracks (VE Pro Server Interface plugin track, its assigned VE Pro Audio/Event Input plugin tracks and their respective audio/MIDI tracks) need to be selected or bouncing will indeed just result in silence. It is still required to set the Audio Plug-ins preferences to All Plug-ins in Real-time for proper functionality, much like with DP7. All in all a rather major improvement.
EDIT: I was a bit premature in my conclusions about bouncing. It only happened to work in my one test session, but I can't get it to work again now. Apologies.
-
Karel, this is excellent news! But please, just to be clear?
On 11/01/2012, you were saying, "..this issue is unlikely to be solved due to the way DP handles bouncing,..."
And then no further word on the matter,
And now, you are saying, " indeed, bouncing with the Audio/Event Input plugin seems to work flawlessly."
Would you think it was the changes in VEP5 and/or the changes in DP(8) that made the difference?
thanks for following up on this