Can I use mp4 and mov in the same project

markrad wrote on 7/6/2013, 3:25 AM
VIDEOCAM: Samsung HNX-H100
File: MP4
Type: Sony AVC
Video: 00:00:12.212, 14.985 fps interlaced 1920x1080x12, AVC
I DON'T WANT 14.985 fps but no way to change that I can see.

Audio: 00:00:12.523, 48,000 Hz, Stereo, AAC
(The audio cycles on and off @ 1 sec intervals in Vegas 9) plays fine using Quick Time movie player.


Camera: Canon Rebel SLR T3i
File: MOV
Type: QuickTime
Attributes: Archive

Video: 00:00:31.098, 29.970 fps, 1920x1080x24, H.264
Audio: 00:00:31.098, 48,000 Hz, 16 Bit, Stereo, 16-bit

The mp4 files are WIDE screen and the MOV files are NOT. All files properties show them all as 1920x1080 so I don't understand this.

Unfortunately I have use both sources. Is this even remotely feasible??

Thanks for any help. Today would be nice!


TheHappyFriar wrote on 7/6/2013, 5:56 AM
Vegas lets you use almost anything on the timeline at the same time. It's both it's biggest plus and negative (because it allows you do not worry about making a ton of proxies, but then it also allows huge issues if you don't pay attention).

If they're both supposed to be wide screen, on the one that isn't (MOV), right click on it in the media pool, properties, & change the pixel aspect ration to it's correct value (1.0 for 1920x1080 I think).

As for the 14.985, you can speed up the clip but I'm betting it'll just stutter when viewed with the other one.
John_Cline wrote on 7/6/2013, 6:33 AM
The Samsung HNX-H100 records at 1920x1080 30 fps progressive, not interlaced 14.985 fps. It is possible that the Samsung is somehow recording to a non-standard MP4 format but it is almost certainly 1920x1080 30 fps progressive. How are you determining the properties of the files from the two cameras?
markrad wrote on 7/6/2013, 10:29 AM
In answer to John's question- in Vegas I right clicked on each file and selected properties.
straight copy and paste:
Video: 00:00:11.745, 14.985 fps interlaced, 1920x1080x12, AVC
Audio: 00:00:12.011, 48,000 Hz, Stereo, AAC
Name: HDV_0012.MP4
Type: Sony AVC

My most immediate problem is not knowing if the MP4 files will even be usable with the audio problem that is happening in Vegas. missing codec maybe? I'm stuck.
Also why is one camera wide screen and the other not?
Both say 1920x1080x12 and x24 ?
John_Cline wrote on 7/6/2013, 4:58 PM
Either the Samsung camera is writing the information into the file's header incorrectly in some non-standard way or that Vegas is reading it incorrectly. You could just manually change the parameters of the file's properties in Vegas to progressive and an aspect ratio of 1.0 (Square) pixels. That doesn't solve the incorrect frame rate issue which also likely has something to do with the audio dropouts, the file is almost certainly 29.97 fps not 14.985. It is next to impossible that the file is actually interlaced since the Samsung camera only records 30 fps progressive. The file may be able to be fixed by running it through the "Quickstream Fix" function in a program called "VideoReDo." There may be other programs out there that can rewrite the file's header to be correct so that Vegas interprets it correctly. Maybe someone else knows of such a program.
markrad wrote on 7/7/2013, 2:37 PM
I tried John's suggestion for using the VideoReDo application.
Using the limited free trial version I used the QuickStream Fix tool on a sample Samsung HDV clip and it solved the audio problems.
I'm not sure what it did to fix the issue or if I incurred any loss in the process but I'm just happy I have footage I can now use. Thank you John!

Changes that I see comparing the before and after file properties:

BEFORE: 14.985 fps interlaced, 1920x1080x12, AVC
Type: Sony AVC

AFTER: 29.970 fps, 1920x1080x24, H.264 (what is the x24 anyway?)
Type: QuickTime

Using Vegas Pro 9.0e (Build 1147)
john_dennis wrote on 7/7/2013, 2:44 PM
"x24" denotes the number of bits used to describe the color.

8 bits for Red, 8 bits for Blue, 8 bits for Green equals 24 bits for RGB.
John_Cline wrote on 7/7/2013, 4:47 PM
The QuickStreamFix in VideoReDo is a lossless process. In your case, it just fixed the header to properly reflect the actual frame rate of the video.