I finally got things sorted on the Windows side (thanks Nick B!) but now Logic is giving me "Out of memory" errors. I have a few plug-ins loaded on my Windows machine, and I am trying to use them from the Mac machine. I've restarted, trashed my preferences and started from an empty project, but Logic 9.1 still gives an "Out of memory!" error if I add more than one instance of the VE Pro plug-in. I'm running OSX 10.6.2 on my Mac Pro 8-core (Nehelam) with 6GB of RAM. Logic was showing ~256MB of RAM use at the time. Perhaps this is a Logic 9.1 bug with VE Pro 4.0.4881? I'm running in 32-bit mode and VE Pro Server was not running on the Mac, only on the Windows machine. I might try downgrading to Logic 9.0.2 if the problem persists.
-
VE Pro "Out of memory" errors with Logic plug-in
-
I've been working with it all day. I got the same errors in Logic 9.0.2 as I did in 9.1. I haven't seen as many "Out of Memory" errors today, but I have seen a lot of slowdowns and spinning beachballs. Deleting a MIDI track has taken as long as 20 seconds sometimes. Are there any VE Pro files that might have become corrupted?
-
The 32 bit version of Vienna Ensemble PRO can only allocate 4GB of RAM (2 ^ 32 = 4 294 967 296 bytes = > 4GB) minus approx. 1 GB for libraries and frameworks, which means that you can load a maximum of 2.8 GB of samples. When this limit is exceeded the application will crash easily – you can check this in your <Activity monitor> application.
Best,
Maya
-
I'm running less than that. I'm also using the Kontakt 3.5 memory server, which uses an outside memory space for sample memory. And VE Pro is not crashing, Logic is just running very slowly: 30 seconds to save a project, 60 seconds to delete a MIDI track, etc. If the AU plug-in is 64-bit, then I will be able to run Logic 9.1 in 64-bit mode which may help. (Even though Logic itself shouldn't need a lot of memory -- all I'm running at this point is ~9 instances of VE Pro plug-ins.)
-
@synthetic said:
I'm running less than that. I'm also using the Kontakt 3.5 memory server, which uses an outside memory space for sample memory. And VE Pro is not crashing, Logic is just running very slowly: 30 seconds to save a project, 60 seconds to delete a MIDI track, etc. If the AU plug-in is 64-bit, then I will be able to run Logic 9.1 in 64-bit mode which may help. (Even though Logic itself shouldn't need a lot of memory -- all I'm running at this point is ~9 instances of VE Pro plug-ins.)
Are you running VE Pro decoupled? If not, this could be the causes of your long save times.
Have you checked exactly how much memory 9 instances uses (with no samples loaded)?
DG
-
I can't tell if it's decoupled! The UI shows all-red, and it's still there when I quit Logic, which makes me think it's decoupled. But when I save the Logic program, I see a little "Project Saved" message on each VE Pro instance, which seems more like coupled. I'll look at the RAM usage tonight. I have new RAM getting here Wednesday and I really hope that helps.
-
I upgraded my Mac to 24GB of RAM today. This seems to have solved the “Out of Memory” errors but I’m still seeing slowdowns. My system specs are:
Mac Pro 8-core (early 2009 Nehelam) 2.26GHz, 24GB RAM
Mac OS X 10.6.2
Logic 9.1
VE Pro build 4881
I did three tests using a Logic 9.1 project I built with nothing but 7 instances of VE Pro plug-ins:
1. No VE Servers running
In Activity monitor, Logic Pro shows 320MB physical memory/420MB virtual memory loaded, 5% CPU when idle
Opening the project with no servers running took 10 minutes!
Making a new track, deleting that track, and then saving took 1-2 seconds per task.
2. VE Pro Server (32-bit) running on Mac Only
I opened VE Pro Server on the Mac and opened my MFrame project, four instances of Kontakt 3.5. For each of these steps I quit Logic, opened VE Pro then opened Logic and the Logic project again.
Logic Pro now shows 276MB/376MB RAM use, less than when no servers were running for some reason. The Logic project opened very fast, about 1 second.
Making a new track, deleting that track, and saving again takes 1-2 sec per task.
3. VE Pro server running on Mac and x64 (both 32-bit)
I again quit Logic and opened VE Pro Server on Windows x64 SP1 (4 instances of GVI, 1 instance Kontakt 3.5. The 2.5GB RAM template took 10 min to open.
Logic Pro now shows 370/480MB RAM use, 17% CPU in Activity monitor
Opening a project and making a new track go instantly.
Deleting a track takes forever with this setup: 30 seconds of spinning beachball, then the track goes away, another 30 seconds of beachball = 60 seconds total
Saving the Logic project takes 30 seconds of spinning beachball.
So there seems to be a problem when using VE Pro Server on the Windows machine. I suppose I can upgrade to Windows 7 if you think this will help, but it seems like Logic is unhappy with something happening with the plug-in when connected to Windows.
I also found that the VE Pro plug-in doesn’t remember connections if you open when a server is not connected and then save the Logic project. If I did this I had to open each plug-in, connect, and choose the instance name.
I hope this is helpful, -jl
-
Is anybody working with Logic as host and Windows 7 as slave? Is this working better? I got a Mac Pro with Logic and want to buy VE Pro to use on a PC. Now I am a little bit confused when reading this messages.