MOTUnation.com

I'm in the process of recording an album project for a client and I'm doing the entire 11 song project tape style. All songs are in the same sequence/project. There have been no issues, but as I was doing my normal backups, I noticed the file is a little over 6 gigs.

By the time we add the BGVs and just a few more parts I'll probably be pushing 8+.

I have an 8 gig MacPro (see sig) and was just wondering if when it comes to mix time if I might have any performance issues with a file this large when I start adding plugins, etc. I don't anticipate using any VIs. (If I do, I'd freeze the tracks and de-instantiate the VI.)

I haven't deleted any unused soundbites yet or cleared the undo history which I know would probably chop off maybe a gig.

Should I make a copy and split this file in two, or am I needlessly concerned?

I looked through the manual and didn't see any obvious references to file size limits.

Thanks!

Buzzy

Hi
I don't think you have to worry, but I think that when
DP loads a file it just loads the project info so to speak
and reads the audio off the disk. If you open the
activity monitor you can check how much ram is being used.
Hope this helps.
Rick

Are you saying the project file itself (without audio files) has expanded to 6G? And might go to 8G or more?

The manual does say that the project files are loaded into RAM. If it's size goes beyond the RAM available, you might expect OS X to start page swapping RAM to virtual memory. I don't know if that would cause noticeable performance problems, but wouldn't be surprised.

I have MenuMeters installed so I can watch my RAM as I record. Having done some 2 hour, 24track recording sessions on my MBP, I can attest that the project can eats away RAM over time. By the end of the recording the GUI gets sluggish and I have to be patient with my mouse clicks, saving constantly just in case. Keep in mind the meager specs of my laptop though. If I could stick 4gigs in my MBP I would and I probably wouldn't have to worry as much. It has done the job so far either way.

Some of the main things I think of when I do a live recording:

Disable plugins in DP, close all other apps, open Terminal and type "purge" to free up even more RAM.

Keep spinning hard discs away from extreme bass vibrations.

Be prepared to lift the A/C ground on your setup because those laptop power supplies can pick up interference pretty easily, but only lift grounds as a last resort.

Save, save, etc....

Mostly obvious stuff that you probably know, but I even have to talk myself through the same steps every time just in case.

-Ian

I did a 72-minute concert the same way--all one long sequence. I didn't have the horsepower you have in your machine and I got it done, but I doubt I would do it again. It makes things very difficult. If I had to do it over again now, I would chop it up into different sequences or even different projects but keep the continuous feel of it. But at that time, I wanted the challenge of doing it and to say I did it. Hard-headed.

c-ya,

Dan Worley

bayswater wrote:Are you saying the project file itself (without audio files) has expanded to 6G? And might go to 8G or more?

The manual does say that the project files are loaded into RAM. If it's size goes beyond the RAM available, you might expect OS X to start page swapping RAM to virtual memory. I don't know if that would cause noticeable performance problems, but wouldn't be surprised.

No, the project size includes the audio.

The actual file size (not in front of studio Mac) is probably about 1.25 megs or so.

Looks like from the comments that I appear to be "safe".

Thanks...

Buzzy

You'll be fine. I normally run sessions for a tour I just finished with 50+ full song chunks on 8 core machines with no problems. I'm not using many plugins, just some occasional MW eq's and limiters but the processor meter never goes beyond 20% usage. The session folder is 175 TB's and the project file is about 58 megs. The only issue which is an understandable one is load time. (about 4-5 min using a Solid State HD)