Vegas detects 120 FPS for my 30 FPS clips...

Crawdaddy79 wrote on 6/7/2014, 2:40 PM
(Using Vegas Movie Studio 12)

Hello forum,

I'm wondering if any of you have experienced this before, and if you do, know a way around it.

The issue I'm encountering is when Vegas renders my video, it interlaces my frames due to a perceived frame rate mismatch, when there is none. How can I tell Mr. Vegas that the video in my project file is actually 30 FPS, so that my video remains crisp?

I've tried (I think) every possible combination of blend fields, interpolate fields, upper/lower field first, adjust source media to better match project settings... nothing seems to be a workaround other than actually rendering at 120 FPS, which isn't ideal at all.

These clips were recorded with a Drift Ghost HD action cam.

Here are examples:

Raw 30 FPS video sample: http://www.crawspace.com/vids/vegas_sees_120fps.mp4

Rendered 30 FPS video sample: http://www.crawspace.com/vids/vegas_interlaces_to_30fps.mp4

Screenshot of Vegas video properties: http://www.crawspace.com/vids/vegas_sees_120fps.png

Thank you for your time!

Comments

musicvid10 wrote on 6/7/2014, 4:25 PM
Means your video is probably shot at variable frame rate.
Refer to your camera specs, set the FPS manually in the Vegas project.
Caution: Some cameras saying 30 fps are actually 29.970.
Crawdaddy79 wrote on 6/7/2014, 6:14 PM
Unfortunately, it isn't a variable frame rate (I didn't even know there was such a thing). I forgot to mention that Windows, VLC, and WMP all report that the file is 29.97 FPS.
Chienworks wrote on 6/7/2014, 11:36 PM
You don't *have to* use Vegas' recommendation for project settings. If you know it's wrong and you know the right values, then use the right values.
Crawdaddy79 wrote on 6/8/2014, 7:58 AM
Using or not using the recommended settings makes no difference... The issue is that I can't render from this source format without blending between frames. Blending happens naturally when there's a framerate mismatch, and Vegas thinks the video is 120 FPS when it isn't.

Thanks!
Chienworks wrote on 6/8/2014, 10:07 AM
Have you disabled resampling? That will avoid the frame blending.
Crawdaddy79 wrote on 6/8/2014, 11:09 AM
I had not tried that... I did, and it did fix the blending issue, but added another... now the video is choppy. :(

In the meantime, I have found a workaround, and that's to re-render the clip using other software, and import that one into Vegas (in my case, I'm using Microsoft Expression Encoder - free, but not easy to get running because of Silverlight and .Net Framework, etc...).
musicvid10 wrote on 6/8/2014, 1:11 PM
Upload an original sample of your footage somewhere (not Youtube).
It's usually an easy workaround.
Crawdaddy79 wrote on 6/9/2014, 7:54 PM
Here is an original sample of the video:

Raw 30 FPS video sample: http://www.crawspace.com/vids/vegas_sees_120fps.mp4
musicvid10 wrote on 6/9/2014, 9:27 PM
Your footage is constant frame rate, and Vegas Pro 8 reports it correctly (29.97).
Looks like a bug report to me.
Former user wrote on 6/9/2014, 9:44 PM
Vegas Pro 11 reports it correctly as well.
Jillian wrote on 6/9/2014, 10:20 PM
Movie Studio 12 (32 and 64 bit) report it as 120fps progressive.

Movie Studio 13 reports it as 29.743 progressive.
Crawdaddy79 wrote on 6/11/2014, 7:52 PM
Haha... Thanks Jillian for the sanity check. Glad you had the right version on hand, and sorry to see that out of all of them, only 12 is bugged out.
Crawdaddy79 wrote on 6/12/2014, 7:40 PM
Okay two updates:

1) This doesn't apply to clips straight out of the camera. Those actually are detected @ 30 FPS. I use VideoDub to chop off relevant parts, and it's the output of VideoDub that sprouts the issue.

2) A workaround is to set the undersample rate of each relevant clip to 0.25. It renders perfectly after that.
musicvid10 wrote on 6/13/2014, 1:06 PM
Oh, so you were not working with source audio, but something that was altered by another program.

I wish you would have shared that in your first post.
Sorry, I do not know what VideoDub is or what it does, or how it was set when you used it..
But you've confirmed that it is probably not to do with Vegas.
Best of luck.

Crawdaddy79 wrote on 6/13/2014, 7:31 PM
Well, it is to do with Vegas because all other programs (including previous and recent versions of Vegas) recognize the output for what it is. The source is irrelevant.

VideoDub losslessly and quickly chops your video; a total necessity for how I manage my footage. There is no conversion.
musicvid10 wrote on 6/13/2014, 7:43 PM
The source is irrelevant.
I'll let that statement speak for itself.
Crawdaddy79 wrote on 6/13/2014, 8:42 PM
Haha okay. Not sure why you're going so far out of your way to be condescending to people who come to this board who come for help, but if you need to take statements out of context to do it, then have at it.

Cheers.
musicvid10 wrote on 6/13/2014, 9:04 PM
Additional:
Codec ID (major_brand) is isom. If changed to mp42 (using mp4BOX) it might work more consistently across Vegas versions. I've seen this behavior before.