181,978 users have contributed to 42,198 threads and 254,643 posts.
In the past 24 hours, we have 4 new thread(s), 8 new post(s) and 45 new user(s).
Hello everybody,
all internal tests with this latest version, 2.1.5132, went very well - please give this new 64-bit version a spin and challenge your RAM!
As always, this update is available in your USER AREA.
If something doesn´t work as expected, please let us know. The functionality is exactly the same as in previous versions.
Best,
Paul
Finally!!
Works great so far in Logic 9.1 /64 bit mode.
The only thing that slows down the workflow is still the VI window that has to be opened by clicking on the "show window" button in the server interface plug in window.
It would be so helpful to integrate the VI window directly to the plug in interface, or even to have it opened as floating window, like all other plug in's do...
... it always jumps into the background when you click somewhere else...this could be improved.
Anyway, ALL VSL products 64 bit for the Mac!!Congratulations!
christof
@Christof Unterberger said:
The only thing that slows down the workflow is still the VI window that has to be opened by clicking on the "show window" button in the server interface plug in window.
It would be so helpful to integrate the VI window directly to the plug in interface, or even to have it opened as floating window, like all other plug in's do...
christof
I don't think this can be changed until there is no longer a memory server connected to VI. If VI used the memory within the host, then this could be changed.
DG
Sorry to ask a silly question but I just want to be sure.
In order to use the the 64bit version of vienna instruments will I need to upgrade to Logic 9? Or will it work in Logic 8 since the vienna instruments use memory outside of logic?
I'm going to upgrade to OS X 10.6 soon. I'm just not doing it yet as I have a deadline and I think it would be unwise to upgrade in the middle of a project.
Thanks in advance.
Edwin.
Hello! The release of 64-bit VI is really wonderful news. Thank you VSL-team. Like edwinsykes I'm also an ignorant user wondering do I have to have the 64-bit Logic 9 to get access to all of my 16GB of RAM or will the 64-bit VI manage to do that in Logic 8 too?
If I'm not mistaken, your whole system (4 elements) has to be 64 bit; the system (10.6), the DAW (Logic 9.1), the plugs (VI 64 bit), and your sound card drivers (Apogee is already there, SSL in beta, not sure about others).
Thanks VSL [B]
@MS said:
Vienna Instruments will run at 64-bit even in a 32-bit Logic version, only the VI connector plugin (with the infamous "show window" button) will then run in 32-bit, while the VSL-Server process, hosting the VI's itself, will run in 64-bit.
So (sorry again for my ignorance) will this cause problems when loading over 4Gb of sample data into one project?
@MS said:
Vienna Instruments will run at 64-bit even in a 32-bit Logic version, only the VI connector plugin (with the infamous "show window" button) will then run in 32-bit, while the VSL-Server process, hosting the VI's itself, will run in 64-bit.
Thank you. That's great news.
That sounds like you can load as many samples as you like (within the constraints of your physical memory of course).
As soon as I have finished my project I'm upgrading to snow leopard and firing up the 64 bit version of vienna instruments.
@jammusique said:
If I'm not mistaken, your whole system (4 elements) has to be 64 bit; the system (10.6), the DAW (Logic 9.1), the plugs (VI 64 bit), and your sound card drivers (Apogee is already there, SSL in beta, not sure about others).
That's true about the OS and app, but you don't need 64 bit sound card drivers to run the app and plugins in 64 bit.
Ok, so also the OS and app has to be 64-bit to gain access to larger amounts of RAM? This is a bit confusing with all the different answers. Does someone have a solid knowledge on this matter?
@Paul said:
Hello everybody,
all internal tests with this latest version, 2.1.5132, went very well - please give this new 64-bit version a spin and challenge your RAM!
As always, this update is available in your USER AREA.
If something doesn´t work as expected, please let us know. The functionality is exactly the same as in previous versions.
Best,
Paul
Hi Paul,
Just installed the beta and a strange thing is happening - when I open Vienna Instruments stand alone I get a Mac security dialogue box saying "Type your password to allow osascript to make changes" it doesn't appear to make any difference whether I put the password in or not the standalone will still open and function - though it appears in activity monitor as a 64 bit app. If I insert Vienna Instruments as a plug-in in Logic havng not previously launched the stand-alone there is no security dialogue box - it just launches and works. If I then open the standalone (with an active Vienna Plug-in open in Logic) I still get the dialogue box and it still opens with or without the password!
All the usual bases covered dongle plugged in the front of the mac, latest versions of e-licensor and database. Running Logic 9.1 in 64 bit mode on 64 bit MacPro in Snow Leopard 10.6.2 and permissions repaired.
Another thing to get Vienna Ensemble stable (it had been working fine) I had to re-install following installing Vienna instruments 64 bit. Also I notice that the size of the directory manager app is 21.9MB in the Ensemble Applications folder but only 819k in the Vienna Instruments Applications folder is that correct?
Any thoughts?
Thanks
Julian
@Karel said:
Don't be alarmed, this is normal behavior and is required in order to enable VI to use all of your memory properly during execution. It might be nicer to have a warning there to explain this however. We'll look into putting that in for clarity.
Hi Karel,
Thanks for the heads-up. No password required for plug-in use (only stand alone) so how does that allow the VI to use all the memory in Logic? Standalone does not show up as a 64 bit app is this correct? and finally? could you explain the difference in size of the 2 directory manager apps noted earlier!
Thanks
Julian
Heya,
So here something i found out. When i load a project with VI on it and then close it, the VSL serveur is still on the monitor activity and will still use the ram. For can get back the ram i need force close the VSL server.
Julian if you check in your monitor activity you can see that the VSL server is in 64Bits.
Best Gilles
