Vienna Symphonic Library Forum
Forum Statistics

200,222 users have contributed to 43,194 threads and 259,061 posts.

In the past 24 hours, we have 0 new thread(s), 2 new post(s) and 70 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VE Pro 5 Audio/Event Input in DP
  • K
    K

    It's unlikely that this bounce issue (which, I emphasise, only happens when using the Event/Audio Input plugins) will be fixed anytime soon. However VE Pro 5 works just the same way as VE Pro 4. You don't have to use the Event/Audio Input plugins if you don't want to and your projects will just open as before. Everything works just as well (and better) than with VE Pro 4. Just to make clear that VE Pro 5 is not worse than VE Pro 4 in DP in any way.
  • B
    B
    I've set the number of ports to 16, restarted VE PRO5 I can see them set plugin to receive to them but when I go to DP8 and add the event plugin it shows only 8 ports. Then I go back to VE PRO and it shows 8 ports only! I go back in the pref and still says 6 ports. Is that a DP limitation or bug?
  • A
    A

    Hi Karel, I'm late to this conversation but am all too familiar with the issue. I had a similar experience as you with Bounce to Disk where when I tested DP8 with a large template using the Event Processor - and it worked fine, then it stopped working correctly - notes would bunch together in odd ways - and then it stopped working entirely.

    I know I can freeze and bounce, but my template is 150 or more midi tracks, and my music can be as long as 5 minutes. Freeze/bounce takes too long under a tight television deadline, and I have resorted to bussing the VEPro plugin to an audio track.

    I am on the latest releases of DP and VEPro and it won't Bounce to Disk. Is there any hope for a fix? 

    Thanks,

    Robert
  • A
    A
    last edited
    last edited

    @Anthropy said:

    Hi Karel, I'm late to this conversation but am all too familiar with the issue. I had a similar experience as you with Bounce to Disk where when I tested DP8 with a large template using the Event Processor - and it worked fine, then it stopped working correctly - notes would bunch together in odd ways - and then it stopped working entirely.

    I know I can freeze and bounce, but my template is 150 or more midi tracks, and my music can be as long as 5 minutes. Freeze/bounce takes too long under a tight television deadline, and I have resorted to bussing the VEPro plugin to an audio track.

    I am on the latest releases of DP and VEPro and it won't Bounce to Disk. Is there any hope for a fix? 

    Thanks,

    Robert

    +1

    Hi Karel, the Release Notes for the new DP update (8.0.5) clarly states:

    "Improved compatibility with Vienna Symphonic Library (VSL) and Vienna Ensemble Pro (VEP)."

    So, is there a chance that Event Plugin/Bounce to Disk issues has been addressed?

    TIA

    Arceo
  • A
    A

    It is not working correctly -

    I can confirm that on my system, only midi that is sent through the server plugin will bounce, no Event Processor midi gets bounced. Just before I updated VEPro to 5.2.12800 (Oct. 8, 2013) I was able to bounce to disk using the same template as today's test. After downloading and installing the latest VEPro, I could no longer bounce tracks that use the Event Processor.

    Here is my system:

    MacPro 2 x 2.26 Quad Xeon, Snow Leopard 10.6.8, 16GB RAM

    Digital Performer 8.05 in 64bit mode, VEPro 5.2.12800 in 64bit mode, Kontakt 4, Vienna Instruments 5.3.11859

    Incidentally, freezing tracks is not an option as my VEPro/Event plugins are on a V-Rack.

    Regards,

    Robert
  • A
    A

    Karel?
  • K
    K

    There have been no changes to the VE Pro plugins and their network protocol for quite some time. The Audio/Event Input plugin not being able to bounce is an inherent limitation from the way the DP audio engine works, so the feature should be used at own risk, knowing that offline bouncing is impossible. This is something we cannot change on our side, and we can't expect the DP developers to change the way their engine works either, as it is most likely a non-trivial exception to make.
  • A
    A

    Sounds like the U.S. Congress.

    It worked beautifully for a while - then I upgraded something - pretty sure it was VEPro, but it may have been something else - and it broke.

    Motu's user base is made up largely of film composers like me, so maybe they'll address the issue. If it all gets working it would be an unbeatable combination - DP/VEPro.

    Has any more thought been given to an MAS version?
  • K
    K

    We've checked out the MAS SDK a bit, but it is a rather huge undertaking to support it. Perhaps something for a future version, but no promises...
  • A
    A

    Karel, thanks a lot for being so clear on the subject, I do apreciate it!

    Now let's hope that you can find the time to deepen the MAS protocol development. As has already been stated, the DP user base is quite crowded by musicians that work with video; hence we have big tracks count, and a DP/VEPRO setup perfectly running would be a bless!

    Thanks again for your time

    Arceo