Isn't it easier to freeze a VI if it's hosted in DP? The VEPro alternative, I'm assuming, would be a real time recording of a VEPro aux track coming into DP.Īlso, how about automating VI parameters? I do need to up the buffer though towards the end of a project and that's where the latency becomes an issue.
I'm often automating my VI's and want to see everything in context. One is being able to see a MIDI track alongside it's corresponding VI track. It's sometimes cumbersome, but there are some benefits. I don't use VEPro, but do host a ton of VI's in DP.
VIENNA ENSEMBLE PRO5 PRO
Why would someone who uses VIs heavily not use VE Pro with DP? It's a breeze to manage all your VE Pro templates and sessions via DP's Chunks window.Īctually, my question would be the other way around. Stems, OTOH, will be identical to your final mix.Īudio stems or bounced individual tracks would last at least until the WAV format becomes obsolete.Īlso, it's really neat to have all your VIs under a single powerful environment. and if they have gain compensation that makes it even worse). Personally, I stick with sets of wet audio stems as I think bouncing every individual track is a bit overkill, and doing it has its huge issues too (i.e., you would't really be able to make this sound identical to your final mix anyway, especially if you used master bus plugins or stem/subgroup compressors or multiband dynamics processors. I soon learnt that the most I can do reliably for the foreseeable future for solid future proofing are audio stems (6-10 are a good compromise), and if you really want instant mix recall even with missing audio plugins (which have the same problem of uncertainty), you must freeze or bounce your tracks separately. It was energy-draining and totally out of my control. If VSL suddenly disappeared, and if you have all the required synths (which you needed anyway), you can still open your project and load them outside of VE Pro normally and work as usual, so future proofing wouldn't be a reason to not use VE Pro anymore than not using DP.īut I agree having all that functionality in DP's chunks as a new feature would be even better.
Just missing one VI can ruin the future proof aspect of a project. So what you said applies to every single VI you own in your arsenal, not just VE Pro. I don't think there's such a thing as "future proofing" the MIDI stage.There are too many variables, and companies that are hot today and get mismanaged and die later happen all the time, tech and protocols change, etc. If V-Rack did what ever it is that VEP does, that would be optimal. It'd be better if everything was in one DP document. DP projects that use VEP will need to remain compatible with VEP and have access to the VEP server document in perpetuity.