Vienna Symphonic Library Forum
Forum Statistics

200,456 users have contributed to 43,198 threads and 259,085 posts.

In the past 24 hours, we have 1 new thread(s), 7 new post(s) and 83 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. VEP Problems after install of full version

  • VEP Problems after install of full version

    H
    H

    Hi,

    We have just purchased Vienna Ensemble Pro after downloading and using the demo with no problems.  However, after registering the product there are multiple problems which make the application unusable.  We were using the demo version as below:

    • We have two Mac's, one running OS X 10.4.11 and the other 10.5.8.

    • We run Logic 8 on the 10.4 machine and send MIDI data over the network using MusicLab's Midi Over LAN app.

    • We open an instance of VEP (not using the VEP Server app, just opening the specific VEP 32/64 bit application)

    • In VEP we set the MIDI preferences to receive data from Midi Over LAN Ports 1-4.

    • The audio from VEP is sent out via an M-Audio ProFire Lightbridge by ADAT, which is then sent into a Pro Tools HD 192 interface back into an audio channel in Logic.

    This system was working perfectly when running the demo version of Vienna Ensemble Pro.

    Now that we have installed the full version of VEP there are a number of problems:

    • VEP will not see the MIDI being received over the network, even though we still have the preferences set to receive MIDI using MIDI Over LAN ports 1-4.

    • When we load a virtual instrument in VEP it doesn't react/play samples even when we click the piano GUI on screen (e.g. The keys at the bottom of a Vienna Instruments screen)

    • In the Audio Routing preferences panel, when we click on an output the drop down menu just lists 'ADAT Output 2' 32 times (we have set the number of outputs to 32).  In the demo version the drop down list would say 'ADAT Output 1', 'ADAT Output 2', 'ADAT Output 3' etc......

    • VEP often crashes the entire computer when loading - it gets stuck on 'Scanning Content...' will eventually stop responding and then the finder will also stop responding.

    I have uninstalled VEP and reinstalled using the CD we purchased and then updated to the latest version from the VSL website.

    I have noticed that if I set VEP to output audio using the Mac's built in output the plug ins will start responding when I click on the onscreen piano rolls.  When I set the audio back to using the M-Audio interface the plug ins stop working.

    Just wondering in anyone had come across any of these problems?  I'm not sure if they are all related, (I have seen some other posters run into the 'Scanning content' crashes)

    Thanks

    Jack
  • K
    K

    There is no difference between the demo version and the full version apart from the license on the eLicenser. Could you tell me which version of VE Pro you were using with a demo license?

    Your setup seems to defeat the purpose of VE Pro by the way. You'll be a lot better off using the VE Pro Server Interface plugin and the VE Pro Server. This approach allows you to bounce/render from Logic. Also, audio and MIDI will be sample accurate and jitter free, which is rather impossible to achieve with your approach. It allows you to run without an audio interface on the slave(s) as well. Only a stable gigabit network is required. So this approach is not only a lot more cost effective, but comes with several additional benefits as well.
  • H
    H

    Hi Karel,

    Thanks for the speedy reply.  I was using the latest version of VE Pro with the demo license (can't remember the version number off the top of my head)

    I understand what you mean about using the VE Pro Server Interface but the problem is we are still on OS X 10.4 on our main computer which runs Logic, so are unable to install VEPro on that Mac.  The reason we want to use VEPro is because of the 64 bit capabilities and the fact we can run multiple instances of VEPro, therefore helping us get round the RAM issues we were having previously running all our plug ins in Digital Performer.

    In the long term we will upgrade to OS X 10.5, but that is going to bring up issues with compatibility and costs of upgrading our Pro Tools set up, so for now we'd like to use VEPro as I described (and as it worked before registering the full version)

    Best

    Jack