Vienna Symphonic Library Forum
Forum Statistics

181,942 users have contributed to 42,195 threads and 254,636 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Pro Tools & VEP5

  • Pro Tools & VEP5

    T
    T

    Hi,

    I am now trying out Pro Tools 11 HD with VEP5. Using Logic Pro X and VEP5 logics CPU meter is constantly down all the way, no matter how many midi tracks is playing via VEP5. In Pro Tools 11 HD however, in the exact same load (imported the midi from LPX) the CPU meter is up to 75% in Pro Tools. Also, when using Pro Tools, VEP5 is much heavier on the CPU (up to 70-99%) and the GUI in VEP is lagging when playing the project. In LPX, VEP is around 50% CPU usage and the GUI of VEP is not laggy.

    I donĀ“t understand why? Pro Tools is only dealing with midi, there should be like there is in LPX, 0% CPU load, right? In both senarios I of course have the same settings in Pro Tools and Logic Pro X, which is 512 buffer, 44.1khz, 24 bit, and adding 1 buffer in VEP5, so 1024. IĀ“m using 2 VEP instances with only one stereo return each in the sequenser. No plugins.

    The reason why I just donĀ“t stay with LPX is because of the multiport layer bug (random midi note drops).

    Can anyone explain this to me? This is a big concern for me. I love Pro Tools so far, but this CPU load for no reason makes me lean towards Cubase 8 instead (which IĀ“m still waiting for a trial version to try out with VEP5).

     

    Also, maybe Pro Tools is not the right choice for heavy orchestral libraries templates? Is Cubase 8 a better choise for this?

    Image

    Image
  • M
    M
    last edited
    last edited

    @Sirthoms said:

    The reason why I just donĀ“t stay with LPX is because of the multiport layer bug (random midi note drops).

    I just posted in another thread, that Apple has fixed this in the 10.1 update for Logic.
  • T
    T

    Wow are you kidding me, thatĀ“s amazing and almost unbelievable, since apple havenĀ“t done anything about this in years. Almost never thought they would. But still, the questions about Pro Tools remains.

     

    Thanks!

    ---------------------------------------------------------------------------

    What made you think that the midi problem in LPX 10.1.0 was fixed? Well itĀ“s not. ItĀ“s exactly the same as in 10.0.7. Thanks very much. Now I have installed Yosemite and LPX 10.1.0 for nothing. DonĀ“t you think you should test something before telling people that something has been fixed?

    PROBLEM REMAINS in Logic Pro X 10.1.0
  • S
    S
    last edited
    last edited

    Hi

    The way PT 11 handles VI's are much different from Logic and Cubase. I have been testing all 3 - and DP8 + Studio One - for a very long time. No question I think that Logic X is a master in economizing with the resources, so you can get the smallest buffer and latency. But as you mentioned Logic X is not the choice if you want to use VEPro on another Mac or PC, because the routing is chaotic.

    I have gone with Cubase 8 although there for the moment are some problems with the Asio Guard feature when you are using VEPro - I think! I think the possibilities in Cubase are very good and you can have all the extra stuff, like VCA faders, compression showing in the mixer, soloing effect tracks and the best midi-editor.

    Even with buffer size on 128 samples my project runs fine with Asio Guard 2 turned on in the small position.

    The only drawback for me is that Cubase doesn't fully support the Eucon, so my to Avid Artist controllers is only used for volume. šŸ˜”

    Now you write that PT11 only deals with the Midi, don't you stream the audio back into PT11?

    If you ask wich DAW is best, I think you will get a lot of different answers, but take a look at http://www.vi-control.net, I think it can help you.
  • T
    T

    Hi,

    thank you for your answer!

    Are you saying that, if I keep using LPX, and later buy a PC slave, there is no way of connecting to the slave using the multiport layer in LPX? This is extremely bad news. I donĀ“t understand why apple doesnt upgrade their stoneage midi handling, so it is equal or the same as Cubase, Pro Tools, DP and well maybe every other DAWS out there? 

    I think Cubase is the best choise for midi handling too. CanĀ“t wait to try the Cubase 8 trial whenever they release it.

     

    ""Now you write that PT11 only deals with the Midi, don't you stream the audio back into PT11?""   -   Yes I have one stereo/VEP instance in Pro Tools. Same as in Logic. But I can have as many Stereo returns as I want in logic, and the cpu is still 0% (in logic).
  • S
    S

    Hi

    It has been a while since I worked a lot in Logic, and I will not guess about how Apple will develop their DAW. But I decided a year ago to try to find the right DAW for me. Building a template is crucial for my work, I simply have to concentrate about composing instead of dealing with technical stuff. The way that Logic X interact with a host like VEPro makes it so limitting.

    But as I said it has been some times since I used Logic for that kind of things. I installed the Logic X 10.1 this morning but to me there are still the same small annoyancies.

    I think definitely Cubase 8 is a much more inspiring DAW.

    Take a look - be prepared to spend some time - at this:

    Regards Stig

    ps. PT11 has to use some cpu to manage the incomming audio from VEPro, but I imagine that Logic X and Cubase 8 will prove better also in this field.
  • K
    K

    VE Pro will not perform well with an odd amount of latency buffers set on the plugin in Pro Tools. Try setting it to 2 buffers and the numbers should be better for you.