Hi,
does anyone have any experience yet how Vienna's software is working with OS X Mavericks?
190,293 users have contributed to 42,730 threads and 257,094 posts.
In the past 24 hours, we have 5 new thread(s), 25 new post(s) and 40 new user(s).
Hi,
does anyone have any experience yet how Vienna's software is working with OS X Mavericks?
i just installed (i'm to curious for my own good).
in cubase, when i try to connect to the (64 bit) server, everything crashes..
i'm on an 2008 mac pro. vienna instruments works fine.
the mir pro plugin loads, but does not load the differen rooms (hangs).
standalone everything seems to work just fine - seems to be a server problem. or a cubase/vst prolem.. or just my problem? time (and other users) willt ell.
i'd definitly wait ;)
take care,
gernot
Thank you very much for your feedback. I'm itching to get to try Mavericks, but I'll try to hold myself back a bit longer.
Logic Pro X with VE Pro 5seems more CPU efficient under Mavericks!
At first, I thought it was my imagination but it is running like butter. I wonder if the new "Compressed Memory" feature is doing this or if there has been improvement in hyper threading?
On my website in the Listen page, there is a piece called "Diabolique". It is using a bunch of Hollywood series Play 4 stuff on my slave PC in VE Pro and Kontakt stuff in VE Pro on my Mac.
In the past when I opened it, it would take a couple of play thoughs to settle in and even then I would occasionally at the biggest section get a system overload message. Not a lot, but occasionally. Now, first play through and subsequent replays, perfect!
As you can probably tell, I am pretty excited.
ok - addendum:
i can open cubase porjects with existing ve pro instances - everything works.
however, in new projects the server interface doesn't see existing instances nor does it offer me to create a new one..
this is strange. can anyone confirm a server problem here or is it just me?
or was no one... brave enough to upgrade ;)
This may be important: for audio peeps:
http://stockoto.com/final-cut-pro-x-stops-rendering-app-nap-osx-mavericks-background-processing/
I can confirm this, although not with total confidence. I just installed 10.9 and fired up Logix X and VEpro. Everything seemed fine until I held a chord on an Ivory patch which resides in a 64-bit VEPro server. The chord played but after a second or so it cut off abruptly. I saw your post, disabled "napping" for VEPro, relaunched VEPro, and now all is well.
Also, when I first experienced the problem i switched over the the VEPro app to see what was going on. Everthing was fine. Of course VEPro then became the frontmost app, and therefore not "napping" . WHen I switched back to Logic everything was normal for a few seconds, and then the bad behavior returned.
So... turn off the napping!
Hope you are well, Jay!
Steve
One thing I'd be interested in seeing in action is the compressed memory. Apple say that you can fit up to 50% more into RAM using this.
So if I had a VEPro slave Mac with 16gb RAM - could I load 24GB of samples without the system paging out to disk? Apparently the compression and decompression happens in a few millionths of a second and is low CPU. Has anyone at VSL tried this scenario?
hi bobulusbillman,
just gave it a try, to be sure, and now i can say:
nope - that's not how it works.
mavericks uses A LOT of ram unless you're using it. after booting up 6 gig of my 16 are used.
once you start loading samples into vienna ensamble, os x looses a lot of that and assigns space for ve. some of the memory of background tasks / not active apps seems to be compressed in that process instead of deleted from ram.
so i tried to load as many samples as i could, but at 14 gig samples my computer stoped responding and i had to restart (by the way - could anybody at vsl maybe program in a security limit to loading samples? it's not the first time that my computer crashed on me after i failed to realize i was loading too many samples).
long story short: the vsl data is not being compressed - only that of other inactive apps/processes to make more space for the active app.
or at least that's what it looks like on my system.
cheers
gernot
Everything seems to be working well here in Mavericks. I have no measurements to confirm it, but it feels like there's more overhead, as if I have a 10% faster CPU in big projects. This might be something to do with the compressed memory trick removing virtual memory use. So, it's not like my 2012 MBP is suddenly running like a 12 core new Mac Pro, but it does seem to be a real and noticeable improvement.
A couple of plugins seems to be having trouble running in VEPRO with OSX 10.9 - SWAM plugins from Sample Modeling, and Steven Slate Drums 4 seem to be having trouble, but as a workaround running SWAM plugins in the host software instead of VEP, and switching off Disk Streaming in SSD4 seems to have resolved those problems.
As people say, you need to switch off App Nap for VE PRO.
I find all VSL Plugins not working at Garageband 10 eLicenser Control - Error
This is the error massage
eLicenser Control - Error
Application 'ViennaFX' has caused the following error:
Application 'Synsopos.app' could not be started. Probably the file is corrupted or incompatible, or file access permissions are set incorrectly.
Please download and install the latest version of the eLicenser Control software from
<http://www.eLicenser.net>
@kohlhtor said:
I find all VSL Plugins not working at Garageband 10 eLicenser Control - Error
This is the error massage
eLicenser Control - Error
Application 'ViennaFX' has caused the following error:
Application 'Synsopos.app' could not be started. Probably the file is corrupted or incompatible, or file access permissions are set incorrectly.
This happens sometimes when eLicenser check for multiple licences at the same times. It's not specific to Maverick.
The problem is solved by restarting the computer or by (force-)quitting the DAW and other VSL apps and killing the synsopos task in the activity monitor utility (found in your utilities folder).
I have also encountered this issue in GarageBand 10.0 in OSX Mavericks.
I have updated to the latest eLisencer, updated Vienna Software, and tried several restarts, to no avail.
Most AU instruments loaded without issue, but several required re-entering license information, as Kohlhtor found.
So far I have not experienced issues inside of Cubase Elements 6/7 or Notion 4 (VST). I do not own Logic X.