Vienna Symphonic Library Forum
Forum Statistics

201,387 users have contributed to 43,245 threads and 259,264 posts.

In the past 24 hours, we have 5 new thread(s), 18 new post(s) and 46 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE Pro and DP 8, is the long awaited future of recording finally here?

  • VE Pro and DP 8, is the long awaited future of recording finally here?

    T
    T
    The post below was submitted to motunation. I’d appreciate it if any VE Pro experts or staff could respond to this and let me know if I am understanding the benefits of VE Pro correctly?. Thanks, The post: I think the holy grail of VI handling is upon us, I hope I am not wrong. Initial testing using VE Pro 5 with DP 8 has shown me something incredibly exciting. We have always wanted to be able to INPUT at 128 while having previously recorded VI parts run at higher buffers. Well, VE Pro 5 can now do that and DP can run at 128 low latency without breaking a sweat. IN DP 7, something was goofy in DP’s latency reporting to VE Pro, and this meant a HUGE aspect of VE was NOT usable. That aspect? The ability to run VE Pro at buffers 4 times as high as DPs audio engine. With DP 8, the latency is being reported properly by DP, so one can run VE Pro at 4x buffers which means ALL the VIs in VE Pro are only taxing the computer at 640 samples while DP runs at 128. What does this mean? It means you can record drums, etc,with 128 sample low latency while the previously recorded drums and VIs are only taxing the computer at 640. So, here I am ,loading up VE Pro with VIs, and running DP 8 at 128 buffers. I have very fast throughout, (128 going through DP into VE Pro), and DP’s memory meter is barely up above 10%. All the work is being done by VE Pro, but, with VE set at 4x buffers, it responds immediately, (128 buffer), but runs at 640. If I run the same VI’s in DP, the memory meter is spiking and very high. Why, because running the VIs in DP means ALL the VIs are using that same 128 buffer power drain. With VE Pro, it is 640 buffer power drain=lower computer strain. So, though I have not tested DPs efficiency with VIs, one for one, I don;t need to because only VE Pro can offset the buffer strain of previously recorded VIs by 4x. I am working at 128 buffers, VE Pro is set to 4x that, taking all the strain and the long awaited fast throughout, low VI strain appears to be upon us. This is totally important and a huge reason for every VI user to get VE Pro if you ask me. It really puts DAW sequencing into the future..finally. I will let you all know if I discover any drawbacks. The only ones I have found thus far are: 1) You get the beach ball a bit using VE Pro each time DP saves VE’s setting every minute or so, this is a tiny bit annoying. 2) You have to switch between 2 programs to work which, I must admit, I don’t like VE’s interface 1/2 as well as DPs. but I’ll get used to it for this kind of nirvana. 3) I am not sure this translates to audio power savings such as running guitars through gtr amp sims etc., vocals through effects in VE Pro, etc, But I will experiment with this more as time goes on. This is exciting.
  • K
    K

    As far as 1) goes, that's why Decouple was introduced in VE Pro, which allows you to disable saving/loading of the VE Pro instance data with the plugin. The usual way people work is to enable Decouple All while working and disable it again when purposely saving. See the manual for more info on that.
  • T
    T
    Great, I will try that. I am still a bit confused as to VE’s style of saving and have been letting DP save it. That finally got me into a bit of trouble the other day when something crashed in DP and VE wouldn't load right thereafter. I had to go back to a previous save to get VE to load. What is the best method for just saving everything in the VE file to each clients song? I get a bit confused with the various save options. Sorry to be a bit dense here.