Canon .mov files crashing 9.e? or just me?

Alf Hanna wrote on 8/6/2010, 6:19 AM

I"ve been experiencing T2i Canon MOV files crashing Vegas. I can repeat this and it always happens. I get about 6 minutes into any timeline dropping .mov files in,and it abnormally terminates. Am I alone in this problem?

Lots of RAM (8 GB) lots of hard disk. It works fine with AVCHD files. I can throw an hours' worth in and it renders it just fine. This happens even if I convert the MOV to AVI using Neoscene.

thoughts?

Comments

musicvid10 wrote on 8/6/2010, 9:19 AM

"This happens even if I convert the MOV to AVI using Neoscene."

That's extremely unusual. Try reinstalling your video drivers (fixed a similar problem for me), then reinstalling Vegas if that doesn't work. Do you have any codec "packs" on your machine? What version of Vegas?

vicmilt wrote on 8/6/2010, 1:29 PM

1 - forget the Canon MOV files - they must be transcoded using the latest version of NeoScene www.Cineform.com

2 - I continually pre-render (TOOLS>RENDER TO A NEW TRACK) bits and pieces of my project as I'm working, using the Cineform Codec in AVI at 1920x1080. Once they are done I drag them down to the very top track - a track comprised only of PreRendered pieces. I name them with the edit name and a suffix: YourEdit v 25-3 for the third pre-render.

3 - At the end of a project I once again re-render all my pre-renders in the same way.. YourEdit v 25ALL
HOT TIP: If you solo the track with all your pre-renders there will be no recompression required. That will make this step super fast - ok, not SUPER fast, but quick, anyway.
I don't understand why this is, as the top track SHOULD take precedence, but if you don't solo it - it will chug along slowly rendering one frame at a time, and might crash.

4 - Using the final single rendered new track I can then solo THAT and RenderAs whatever is needed. This technique simply works - but I have no idea why :>)

v

Dach wrote on 8/6/2010, 7:26 PM

Transcoding the native files is a must. I have Production Assistant and for that reason I batch render the files to Sony MXF files and have no problem.

Chad

Dreamline wrote on 8/7/2010, 1:13 AM

Use DVFILM EPIC I to make proxies. It's faster, better and more efficient. Avoid all those neolame problems.

http://dvfilm.com/products.htm

mats-mats wrote on 8/7/2010, 3:18 AM

I would not recommend EPIC I tried it and it looked god but, butt these proxy files are a pain……
It crached my computer a couple of times. Its hard to know if you watch the proxy or the source file. I couldn’t switch it off (when I wanted to) or It switched on itself. And the worst, the proxy files doesn’t look that god and creating them takes way longer than neoscene. NeoScene is great because I like to know what the end result will be.

Dreamline wrote on 8/7/2010, 12:03 PM

Works like a charm on three different computers of mine. The best part is it even works on old computers. If it's not working for you... It's probably user error because it doesn't get any simpler than Epic.

How can you not tell if you are looking at a proxy or the original footage? It has a thin red outline around the proxy footage. Can you see red?

Proxies render extremely fast and take up less HD space. It's a win win on every level.

Epic is the best thing since sliced bread. Try the demo if you don't believe me

The Canon HD files, Vegas 9e, & Epic are a perfect trio. I use it almost every day.

I suggest you reevaluate DVFILM EPIC I.

Ros wrote on 8/8/2010, 10:23 AM

FishEyes is right,

Epic really works like a charm!

You render from the original, no messing up and now availaible for 64bit Vegas. Best solution for using Canon's HDSLR footage from my point of view.

Rob

Alf Hanna wrote on 8/8/2010, 11:31 PM

All very interesting, in that some of you say I *must* render to Cineform, which I have done with no change to the results, i.e. it still crashes. I'll try the Epic but don't understand why that would give me any different change from Cineform.More to follow.

Dreamline wrote on 8/8/2010, 11:53 PM

The reason is Epic does everything for you.

Configure Epic to save the proxy files in the same folder as clips being used in the project. The Vegas Preview can be configured to change between the original and the proxy.

It couldn't be faster or easier!

Mindmatter wrote on 8/10/2010, 11:47 AM

Lots of info her for my ordered T2i...thanks to everyone! I wasn't even aware of the potential problem.

On a side note, why can't Vegas handle the Canon files? Will an update possibly address that problem in the future?

musicvid10 wrote on 8/10/2010, 12:52 PM

On a side note, why can't Vegas handle the Canon files? Will an update possibly address that problem in the future?

1) The Canon-centric forums have been flooded since this HD MOV format was released. It's not just Vegas, the files themselves are NLE antagonistic.
http://www.google.com/search?q=canon+mov+files&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official

2) Probably (just my guess that Sony dev is hard at work on the problem).

Mindmatter wrote on 8/10/2010, 2:07 PM

Thanks for the infos. stumbled upon this while googling the issue:

it's about a free transcoding method that seems quite efficient, it might be interesting for the OP or various people.

Dreamline wrote on 8/11/2010, 4:06 PM

You couldn't pay me to waste my time that way. How terribly complicated.

DV FILM EPIC is far better.

24Peter wrote on 8/23/2010, 2:14 PM

Alf - have you tried updating QT on your Vegas computers. I think you need at least 7.6.6 Old versions create the issue you describe (at least they did for me.) Now I have no timeline issues with Vegas 9e. and my 5DII/T2i .mov files. There is an occassional "black frame" issue however. But closing and reopening Vegas right before I render usually solves that problem.

Udi wrote on 8/24/2010, 2:15 AM

I used the method suggested by Rob Frank in
http://www.sonycreativesoftware.com/forums/ShowMessage.asp?Forum=4&MessageID=715913

Here is the extract:

(I'm working with Vegas 32 bit... I have not as of yet tried this with 64)

Use CFFexplorer (you can find it and instructions in the blink3times repair in this thread:
www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=648152

But instead flag the following files for greater than 2gig:

Vegas90.exe
fileIOProxytStub86.dll
fileIOSurrogate.exe
QT7plug.dll (in the QT7 folder in fileIOplugs)

Before this I could only open up to 19 of the mov files. Anything more then I would basically hang. After the tweeks I can now open all 35 files on the time line, save, close, then re-open.