Vegas chokes on .mov files?

24Peter wrote on 12/28/2009, 11:42 AM
Running 8c. on Vista. Have had three successfully edited projects so far with .mov files directly from my 5D II (preview sucks but these aren't mission critical). Today, whenever I add .mov files to timeline, Vegas crashes. Any ideas? (I'm not asking about transcoding or using proxy or intermediary files - just want to know if anyone has solved this particular issue without aforementioned "solutions".)

Comments

John_Cline wrote on 12/28/2009, 11:50 AM
Vegas depends on whatever version of Quicktime you have installed on your computer to open and deal with .MOV files. Quicktime has always been a little unstable but lately Apple has released some really unstable versions, so I'd be looking at Quicktime as the culprit, not Vegas. Personally, I have found that anything much past v7.2 of Quicktime has just resulted in a crash fest.
musicvid10 wrote on 12/28/2009, 12:15 PM
Specifically, Quicktime 7.6.4 is broken, not just with Vegas. 7.6.5, which was supposed to fix the problem, apparently has not.

There's a download link for 7.6 here. Note that you will have to roll back iTunes from 9 to 8, as well.
http://www.custcenter.com/cgi-bin/sonypictures.cfg/php/enduser/std_adp.php?p_faqid=4787&p_created=1254146741&p_sid=dZuNlLMj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9OSw5JnBfcHJvZHM9MCZwX2NhdHM9JnBfcHY9JnBfY3Y9JnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9bXA0&p_li=&p_topview=1
Spot|DSE wrote on 12/28/2009, 5:57 PM
Bear in mind that Vegas merely calls on QT to decode anything in a .mov package, even if it's DV in a .mov package.
Quicktime has periodically had very weird issues with all NLE systems, including Apple's own NLE in the past.

You shoulda seen the nightmare that QT3 brought to the table.
Roll back QT to an older version, you'll generally see immediate improvement/repair.
BudWzr wrote on 12/28/2009, 6:33 PM
.mov is an open container format, Apple has no problem with people putting motion jpeg or anything else in them because they open Quicktime by default to play it.

That gives Apple exposure as the "go to" program for .mov.

When Google bought ON2 (the makers of VP6 the Flash codec), Adobe never had a "Flash codec", they licensed VP6 from ON2. Now Adobe abandoned VP6 for H.264 so they have a new file extension for "Flash" which is .F4V.

This way, developers have a way to make their H.264 web video open in the Adobe player because MP4 & MOV are already defaulted to QuickTime.

Apple is adding QT support for other formats at a feverish pitch in order to capitalize on this confusion and make further inroads into Windows. Apple is even hawking Xvid support.

As it stands now, HD video downloaded from YouTube opens in Quicktime, and Adobe is under a lot of pressure to establish their own H.264 container quickly.

The reason YouTube uses .MP4 for H.264 is because it opens with QT (not Adobe player) and plays natively on iPhone. That gives Google enormous market penetration. Plus, Apple users will get their "it just works" massage, and Windows users already know how to re-associate media to their favorite player.

Google scored a tremendous coup by buying ON2. ON2 recently contracted with China to offer VP7 as a broadcast format. Though not as good as H.264, the Chinese will think it's great (for the discounted price of course). The Chinese can't pass up a good deal, so they hoist on their own petard.

So ON2 is Google's "loss leader" as they penetrate the far east. Very astute!

Hahaha, go Google go!
24Peter wrote on 12/29/2009, 8:03 AM
Thanks for the replies. What's maddening is I was able to do three other .mov projects within the last few days without issue. Anyway, I just converted the .mov files to Sony .mxf files in Vegas and all seems OK.
BudWzr wrote on 12/29/2009, 2:52 PM
Next time, see what's inside the .mov with Gspot. Gspot will show you what filters can decode the streams and whether your machine has them loaded. If you're using libavcodec open the VFW interface and enable that filter, then just drop it right on the timeline.