Okay, I have noticed this recently as my sets have been getting larger and larger.
So I write, and then bounce to audio once I like a particular part. I may even bounce just the straight audio coming from the VST and then use effects so that I can change them as I wish.
But, I keep the MIDI track, unarmed and with all the VSTs and effects off, just so that if I want to create another part, be it rhythmic or melodic, I can....
But, when LIVE loads all these different tracks, my RAM goes through the roof. One of my tracks must have about 10 tracks with VSTs off, but still in their MIDI track, with bounced audio, but my RAM usage is extremly high, maxing out my 1 gig of RAM.....
Now, I know that 1 gig is almost a minimum at this time, and that I could delete the unarmed VSTs, but if I want to go back and re-write a certain part...
that would create a whole new conundrum...
Just a thought....
I have started having RAM issues....and this, I believe is a large part of what a lot of people are seeing with LIVE5. Check task manager if you are using PC...see what your REM usage is....it may be much higher than you think...
And this may be effecting LIVE very badly...
I know it is for me...
Cheers,
AB
LIVE and RAM usage
-
anti-banausic
- Posts: 1609
- Joined: Fri Jun 11, 2004 9:15 pm
- Location: NYC
LIVE and RAM usage
Macbook c2d 2.0, 2G RAM, 160G HD 5400 RPM, OSX(10.5.5), XP Home, LIVE6, BCR 2000, UC33e, Yamaha P-200, Logic Studio, KRK V6 II
-
Casual Beats
- Posts: 279
- Joined: Mon Dec 12, 2005 9:15 am
- Location: Austin, Texas
there's no doubt that there Live is a bit resource intensive (and from what I am seeing with my projects) very much so when using vsts and vstis. I had a project with just a few tracks, plus an instance of Virus Control (the TI's gui interface) and instance of Stylus RMX and a few VST effects and my ram usage was at 1.5gigs plus another gig in use by the swap file. This is on 3 ghz P4 machine with 2 gigs of ram. Hopefully with future bugfix releases (and updates) we will get some optimizations, but ultimately it looks like I will be going the dual core route fairly soon.