You are converting which tells me you are Rendering from within Vegas Pro. Yes?

Rendering takes PC power and hard drive real estate to do it. From the little you have provided us with, I'm also guessing you are using the C system drive to hold, render and render back to. Meaning you ONLY have one drive - Yes?

Can you tell us what size that drive is and how much free space you have available. Yes?

Without these vital bits of information we are shooting blind. But with this data we could maybe offer a further solution.

All up to you.

Regards

G

What format are the clips? If they are QuickTime, this can certainly happen.

~jr

I have multiple drives with 32 gig of RAM and have had this message appear as well, which, with over 16 gig of free memory available, is a Windows software joke. I usually just reboot and all is well.

Also, as suggested, another drive helps your system processing tremendously since it cuts down on the amount of simultaneous read-write states your system must perform in order to render to one part of the drive while reading data from other sectors. Your RAM is used as a virtual disk to accomplish this, and if using mov's as JR said, could make it even harder.

Plus, the questions Grazie is asking highlight the reason one of the first "stickys" says, update your system specs. It is for your benefit as well as ours!

I have multiple drives, but my sony vegas is on my E drive. It's total size is 247 GB free of 1.81 TB

My C Drive is 394 GB Free of 916 GB.

My video clips are mostly .mov files from my IPhone. WMV files 720p, and MP4's HD

If a codec you're using is 32-bit, or quicktime is 32-bit (and I think it is), then you're probably limited in that process to 2GB of RAM. Open Task Manager and watch what's going on.

Another thing to look at is your dynamic RAM setting in Vegas. This takes memory AWAY from processing so you don't want to max it out.

Rob

> "My video clips are mostly .mov files from my IPhone"

That will do it. Vegas Pro is not the best editor to use with QuickTime MOV files because of the 2GB memory limit.

~jr

Now you've provided more info, get all your media to comply to at least one single VP compliant format. Presently you've got a range of formats that in combination are successfully choking VP.

Look, I can edit iPhone media. I can edit WMV. I can edit most formats. Would I try to combine all these at the same time? Sure. But if VP starts to choke off the process, I'd focus on the media that needed to be pre rendered and move on. I'd advise you try the same. Lesson learnt. We've all been there.

Just 'cos VP can import MANY media formats, don't mean that the NLE process won't then be without issues.

G

You mean the QuickTime memory limit that Apple will not address, because they see it as a competition thing? sure. I have never understood why Sony has not corrected this issues with their own format reader. I mean this would be a simple build update, and yet the issue remains after years and years. Must be a licensing issue.

For those iPhone.mov clips, run them through a simple FFMPEG command to .MP4.

ffmpeg -i "input file name.mov" -vcodec copy -acodec copy "output file name.mp4"

This will re-wrap the audio and video into a format that causes Vegas to read them not using QuickTime.