mov 1920/1080 29.97fps

airhogs wrote on 4/13/2010, 11:07 AM
When I first brought the video into my system it was very jittery, I downloaded VLC media player (free) and that seemed to fix the problem. Now when I bring the video into Vegas 8 (VLC media file (.mov) (.MOV) it is still jittery?
I got it to work temporarily with a trial version of Cineform but now it is disabled. Can someone help me understand what is going on? I would like a fix that will work with all the video formats my camera is capable of. 1920/1080 30 or 24fps, 1280x720p 60fps or 640x480 at 60fps

Comments

[r]Evolution wrote on 4/14/2010, 5:42 PM
I use QT .mov's all the time w/ No Problem.
QT/.mov is my format of choice when I'm working in a PC/MAC mixed environment because Vegas plays them and FCP has some problems w/ PC stuff.

What camera are you shooting with?
It's capturing .MOV's?

Use GSpot and tell us what CoDecs these files are using.
If it's too weird of a CoDec... It's another step but, you may need to find a satisfactory intermediate to edit with.

PerroneFord wrote on 4/14/2010, 7:03 PM
What's going on is that .MOV files don't work well in Vegas (or Premiere) because neither program can decode them directly and must make system calls to Quicktime for help. And that is a slow process.

You want .AVI or .MXF containers on the Vegas timeline. Anything else is a recipe for problems.
[r]Evolution wrote on 4/15/2010, 11:49 AM
What's going on is that .MOV files don't work well in Vegas (or Premiere) because neither program can decode them directly and must make system calls to Quicktime for help. And that is a slow process.

This just strikes me as NOT being true... at least for me it's NOT.
All of the Stock Footage & Motion Backgrounds I use are QT .MOV's. So is all the Footage I use when I need to share files between a PC & MAC.

The only problem I've ran into is when the ProRES CoDec is used. PC will not read it.
Other than that QT .MOV's are golden in my book and open/edit in FCP, Premiere, & Vegas.

Maybe your problem lies within QT?
As stated before, maybe you need to edit an Intermediate... MXF?
Once again, what's GSpot saying your file is?
PerroneFord wrote on 4/15/2010, 11:58 AM
Well, I'm sorry it strikes you as not being true, because the fact of the matter is, it's most certainly true, and is easily verified.

I use MOVs all the time on the timeline. Avid DNxHD mostly, but also Jpeg2k in the MOV container, ProRes, 5D, and 7D files, etc. All of them open and play in Vegas. They just don't play "well". And they don't play well because Vegas cannot decode them directly.

If your PC won't read ProRes it's because of your quicktime version. This was solved over a year ago by Apple. I get ProRes files frequently and have no issues reading them.

[r]Evolution wrote on 4/16/2010, 5:50 PM
Well, I'm sorry it strikes you as not being true,
No need to be sorry... you did nothing wrong.

because the fact of the matter is, it's most certainly true, and is easily verified.
What I state is easily verifyable on my system.

-That's the problem with PC's. There are so many different manufacturers, configurations, etc so it's hard to pinpoint why one system does what another does not.

I misspoke... I actually DO have the most recent version of QT & the ProRes Decoder and the ability to play ProRes files on my PC. It appears to be the Apple Intermediate Codec (AIC) -the way FCP captures HDV- that I am having a problem with on my PC. Everyone I've spoken with says AIC on Windows is a No Go as it's proprietary to Mac.

- If you know of a way to view AIC on the PC: Please Share!

What happened to the OP?
I still feel that we need to know what the true CoDec is in the files to offer any type of pinpointed advice.
If the files captured by your camera make your editing experience unbearable... maybe you'll have to allot time for a Transcode to a more efficient CoDec.
Also, if you've found a solution... please post it.
PerroneFord wrote on 4/16/2010, 9:09 PM
There is no way to see AIC on a PC. So that change in statement makes all the difference in the world. That's just Apple being Apple again.