Vienna Symphonic Library Forum
Forum Statistics

181,993 users have contributed to 42,199 threads and 254,645 posts.

In the past 24 hours, we have 4 new thread(s), 9 new post(s) and 49 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. Odd Error Message After VE Pro Update

  • Odd Error Message After VE Pro Update

    A
    A

    Last week I was successfully running VE Pro as a standalone, plug-in and server but after upgrading to the latest version, I am now unable to run either the 32-bit or 64-bit version at all.  Once I start VE Pro in stand-alone or as an instance in the server, I get the following message:  Cannot start audio (Couldn't change sample rate/buffer size).  VI and VE 2 both still run as intended.  The interface comes up but the "Vienna Ensemble Pro" menu is grayed out and the "Options" menu is blank.  

    I am running the latest Mac Pro (2.66, 16 GB ram) with OSX 10.5.7 and an Apogee Duet with the latest version of the firmware

    Any ideas?
  • C
    C

    I see this happen to me quite often in OS X.  Open the standalone, then go into audio preferences and change the sample rate to something other then 44100 (48000), then close the audio preferences window.  Re-open it up and select 44100 sample rate.  Then close that window and hit the start engine button in the top left of VE Pro.

    Maestro2be
  • K
    K
    Default samplerate/blocksize doesn't seem to function any longer on Mac. Checking now if this can't be improved.
  • A
    A

    Unfortunately the "Preferences" option in the drop down menu of VE Pro was grayed out, as the VE Pro audio engine would not start without initializing the interface.  Changing the sample rate in the audio interface's software did not work either except that it allowed the VE Pro engine to start.  Once this happened, the Preferences in VE Pro were available and I had to manually set the sample rate to ultimately get VE Pro to work.  Thanks for the help!
  • K
    K
    Default samplerate/latency problem on Mac is fixed for next release.
  • C
    C

    You're welcome!  It's a real goofy thing that has been around for a while on OS X.  It will be nice to have this fixed finally.  glad i was able to help though.

    Maestro2be