Hard drive optimization & Page file

  • Thread starter Thread starter R_Spaulding
  • Start date Start date
R

R_Spaulding

New member
I do audio recording AND video editing. I have a freshly formatted internal system/program drive and I have a 500gb eSATA external drive to dedicate to project files. I've done all of the optimization techniques listed HERE

-Is it OK to have all my audio projects and all my video projects on the same unpartitioned external drive? Or should I create a separate partition for each?

-I run programs like BFD2 and Colossus which have very large sample libraries. Should I put the libraries on the external dedicated project drive, or leave them with the program on the system drive?

-I've read that you want your min & max page file set to 1.5 times your physical ram. I have done this to my system drive, but should I also do this to the external data drive?
 
Yes you can have audio and video projects on the same drive. The computer doesn't care and dont bother partitioning.

Some samplers load all the samples into memory ONCE and dont hit the disk again, but very large sample libraries or ones that stream from disk should have their own dedicated drive. Even a USB2 drive is OK.

Leave the page files alone. Thats a tweak from 1998 that really isnt valid anymore now that we have more than 1Gb of ram.... (and you should max your ram out, too)
 
Well, I have a 2.6 ghz dual core processor and 4gb of RAM (even though 32-bit xp will only recognize 3.5gb of it). When I try to load the ram intensive 'Steinway B' piano sample in Colossus I get "low memory" errors. And try running that sample while using Colossus as a VST in CubaseSX3 to record it... it won't even finish loading!! So my ram is in fact maxed out, but i'm still having issues.
 
I would go over to Cubase.net and search for other Colossus posts.... maybe someone over there has some solutions.
 
Thats not actually a RAM issue, its a SX3 multiprocessor issue.
 
Disable multiprocessing in the Kompakt/Kontakt player for Colossus then open it in Cubase and see what happens. I havent used the KP for Colossus in a long time, but I know this was a Kontakt2/3 thing and I'm guessing it rolls over to the player too.
 
So the multiprocessing problem is in SX3 or in Colossus kompact player? And I want to DISABLE multiprocessing? isn't multiprocessing a good thing?
 
IT generally is a good thing, but in those early programs it caused issues like you're seeing there. It has since been addressed more in newer versions of the programs. But its a workaround for back then. Try it and see how it responds. Its certainly not going to blow up your system.
 
I don't see anywhere in Colossus to alter multiprocessing. The options menu is very small. I can post a screen-shot later.
 
You must log in or register to reply here.
Back
Top