URGENT - Canon 7D footage making Vegas crash

For HD I recommend you upshift to w7 64 and the 64 bit version of Vegas. My crashing problems have, in general, vanished with 64 bit (am I the only one?) But you will need at least 4 GBs RAM and preferably 6 or more. 8 is optimal. Google RAm discussions for W7 and you will find a variety of folks especially those on Corsair with some great reasons to go to 8GBs.
 
For HD I recommend you upshift to w7 64 and the 64 bit version of Vegas. My crashing problems have, in general, vanished with 64 bit (am I the only one?) But you will need at least 4 GBs RAM and preferably 6 or more. 8 is optimal. Google RAm discussions for W7 and you will find a variety of folks especially those on Corsair with some great reasons to go to 8GBs.

Yes, 64bit Vegas improves things somewhat, but forces you to give up Magic Bullet, some other plug-ins, some codecs, etc.

There is no perfect solution. Especially for those trying to do more tricky work.
 
I understand some folks keep the 32 bit version around simply to run Magic Bullet.

I agree that there will be some tricky stuff to accomplish that just isn't working smoothly. And apparently 64 bit is not the end all be all, given what I'm reading. But I've avoided problems with it (knock on wood). I went to Neo and simply run the batch conversion on AVCHD there doing all the files at once, then archive the AVCHD and delete. Not that I'm having enormous problems with AVCHD (HMC 150 version) but given that others are, I've decided to simply transcode. Since I end up doing a similar thing with FCP when I use it, it seems like not a lot of hassle (but it is!).
 
Tried..epic..it works good. However becuase its only 32bit..its a fail untill 64bit comes out. Because 32bit vegas just fails when you try to render 7d footage period! You will get low memory error and crashes if you apply any FX to the timeline. Go to Vegas 64bit and you wont need anything..with a good machine. And dont use the new quicktime codec..use the older one.
 
From my experience over the last 6 years of using Vegas:

If you want a good time line/render experience free of crashes, stay away from anything quicktime based - be it editing with, or rendering to.

Seriously it isn't just 7D movie files. I am cutting a 30 minute short right now using DNxHD files and it makes me want to throw my computer out the nearest window. I'm not saying it cannot be done, and if DVfilm's EPIC replaces the QT codec Vegas uses and it works then great (any BTW, is that 64bit version ready yet?) but aside from that I would stick with an AVI solution, namely Cineform or Raylight.
 
Epic with 64-bit support released

Epic with 64-bit support released

The 64-bit version of Epic was released last week. Read more HERE. When the Epic plugin is enabled it completely replaces the default Quicktime plugin. The Epic plugin does not support rendering to Quicktime. If you need to render to Quicktime, we recommend rendering an uncompressed AVI, then using the AVI file to render to Quicktime using Quicktime Pro.
 
Last edited:
I've run into render problems using native Canon files a bunch. I'm considering switching to Premiere CS5 because of it, but damnit I love Vegas, but I digress. Normally I get a low memory message during render problems. Usually I just keep trying to render until it finally goes all the way through. If it keeps getting stuck at a certain spot, I try to see what effects are happening there and see if can change/simplify something to make the render go through. Yes it's a pain in the ass.
BUT couple of months ago I couldn't get lucky using this method to save my life and finally tried DNxHD, it's a GREAT solution if you've ALREADY edited and just need to render. The simplest way is to create another folder next to the folder where all your clips are (if you have canon mov clips in random places, shame on you for being sloppy and open up the project and "save as" and check the "copy project media" box, this will create a new project with all inclusive file structure). Use Euginia's method to convert your clips to DNxHD http://eugenia.gnomefiles.org/page/2/ as mentioned previously. Now simply change names of the directories so that Vegas sees the folder with the DNxHD clips in it, and since the file structer and file names are exactly the same, Vegas simply builds new previews and AWAY YOU GO. It's free, very easy and if ALL ELSE FAILS, it works.
BTW you'll probably wanna tweek your colors a little bit. I believe DNxHD expands your color space and in the process the clips loose contrast and aparent saturation. So just stick a Curves plug in on the main out and pull down the blacks till you like what you see :)
 
BTW you'll probably wanna tweek your colors a little bit. I believe DNxHD expands your color space and in the process the clips loose contrast and aparent saturation. So just stick a Curves plug in on the main out and pull down the blacks till you like what you see :)

LOL, Eugenia's method... :)

Anyway, no DNxHD doesn't expand the the color space. However, depending on how you have your project properties set, and how you do the conversion, you might see a difference. I never see any color shifts going to DNxHD.
 
LOL, Eugenia's method... :)

Anyway, no DNxHD doesn't expand the the color space. However, depending on how you have your project properties set, and how you do the conversion, you might see a difference. I never see any color shifts going to DNxHD.

LOL cool, didnt know Eugenia did that, I just thought my eyes were f-ing with me when I used the process, then I A-Bed some clips.

I just use 1080-24p settings and it always seemed the bring down the contrast, although it's probably just a gamma shift I suppose. Thnx for the info.
 
The latest DVFilm EPic I (version 1.1) has a "computer RGB" option so you have the choice of full 0-255 range color or video system color and so no need to mess with a filter.
 
Back
Top