What Render settings to use with 720x480 video files

kmcghee wrote on 1/30/2018, 11:03 PM

I am trying to make videos for my students, we are a small school, and I only have access to a very old Canon FS10. Specs here https://www.cnet.com/products/canon-fs10-camcorder-flash-card-series/specs/

 

The videos are all *.mod and are 720x480 29.970 fps

When I look for info on the best settings all I get is 480p and I know that is not what my video is. I know I should just get a better camera,but its not in the cards right now and I need to make due with what I have. When I render the video the quality is noticeably worse than when editing or viewing original footage, so the default settings when I select make movie, save to hard drive and pick mp4 is not correct. Can anyone tell me what settings you use?

Comments

EricLNZ wrote on 1/31/2018, 1:32 AM

What are you rendering them for i.e. their purpose - DVD discs, thumbdrives or internet?

vkmast wrote on 1/31/2018, 3:57 AM

Canon FS camcorder standard def mod files (NTSC, PAL)

kmcghee wrote on 1/31/2018, 8:29 AM

What are you rendering them for i.e. their purpose - DVD discs, thumbdrives or internet?

Rendering for youtube.

 

kmcghee wrote on 1/31/2018, 10:32 AM

It looks fine in the preview, it looks fine in windows playing on VLC, it looks fine on my 52" Flat screen, aside from it not being 16x9, but on youtube text is much grainer, and I have a killer internet connection so its not a bandwidth issue, I just don't think its formatted right for internet video.

kmcghee wrote on 1/31/2018, 10:34 AM

Either way the default render settings to not match the video and I want to get them to match as close as possible.

 

cris wrote on 1/31/2018, 1:57 PM

It looks fine in the preview, it looks fine in windows playing on VLC, it looks fine on my 52" Flat screen, aside from it not being 16x9, but on youtube text is much grainer, and I have a killer internet connection so its not a bandwidth issue, I just don't think its formatted right for internet video.

It's probably YouTube's encoder. You could try to set the rendering parameters to match the information at https://support.google.com/youtube/answer/1722171?hl=en

Musicvid wrote on 1/31/2018, 9:46 PM

Your files will tranfer perfectly in Handbrake to 480p mp4. Pretty much a sleeper project.

There's an outside chance you have to change the extension to .mpg but probably not needed.

kmcghee wrote on 2/1/2018, 12:48 AM

Your files will tranfer perfectly in Handbrake to 480p mp4. Pretty much a sleeper project.

There's an outside chance you have to change the extension to .mpg but probably not needed.

I will look into this but I have many videos I have already done editing to that I would like to encode properly but I can't make heads or tails of all the advanced settings.

kmcghee wrote on 2/1/2018, 1:14 AM

Looking around and learning more I have determined that the video I am using is NTSC DV widescreen but that Movie Studio loaded all my video with an aspect ration of 0.9091 according to properties of the video imported. But when watching clips in VLC I could tell they were squashed in movie studio, don't know why they were. So using that info I matched those settings in my project, but when I look in the advanced render settings I have only two choices that match this, MainConcept Mpeg-2 widescreen and use the template Program Stream NTSC. or I can use Video for Windows and Template NTSC DV widescreen, thoughts?

EricLNZ wrote on 2/1/2018, 1:46 AM

Please clarify - are you shooting 4:3 or widescreen 16:9?

If you are shooting widescreen then the PAR should be shown as 1.2121. You can either alter it for each clip in its Properties/Media Tab or stretch the whole project when rendering but that would probably stretch out any titles. Alternatively use Track Motion to stretch. There's several ways of correcting the squash problem.

YouTube wants Square pixels, mp4 files and progressive (not interlaced) so you cannot match the output to the source. Try using Main Concept AVC/AAC Internet 480p Widescreen. Personally I'd increase the templates bitrates to Max 14,000,000 Average 10,000,000. Some may say that's an overkill but YouTube will screw the bitrate right down anyway.

Handbrake as recommended by Musicvid does a good job at deinterlacing but you need to export first to a file to run through Handbrake. If using this method I'd export as a NTSC Widescreen DV AVI file and run this through Handbrake.

vkmast wrote on 2/1/2018, 3:12 AM

Please clarify - are you shooting 4:3 or widescreen 16:9?

https://www.vegascreativesoftware.info/us/forum/skewing-distortion-of-produced-mp4--96914/ should explain much re. JVC/ Canon/Panasonic (ca. 2008) .mod files.

https://www.vegascreativesoftware.info/us/forum/an-error-has-occured-while-opening-a-codec--90383/ as well.

Pity that the links in those threads do not work any more.

(Try SDcopy and set the widescreen flag there. See what happens with your aforementioned .mod+.moi files. SDcopy converts the mod files to mpg and puts the creation date and time into the file name.)

kmcghee wrote on 2/1/2018, 8:54 AM

Please clarify - are you shooting 4:3 or widescreen 16:9?

If you are shooting widescreen then the PAR should be shown as 1.2121. You can either alter it for each clip in its Properties/Media Tab or stretch the whole project when rendering but that would probably stretch out any titles. Alternatively use Track Motion to stretch. There's several ways of correcting the squash problem.

YouTube wants Square pixels, mp4 files and progressive (not interlaced) so you cannot match the output to the source. Try using Main Concept AVC/AAC Internet 480p Widescreen. Personally I'd increase the templates bitrates to Max 14,000,000 Average 10,000,000. Some may say that's an overkill but YouTube will screw the bitrate right down anyway.

Handbrake as recommended by Musicvid does a good job at deinterlacing but you need to export first to a file to run through Handbrake. If using this method I'd export as a NTSC Widescreen DV AVI file and run this through Handbrake.

They are 1.2121 in the file, but movie studio makes them 0.9 ish, so I have to automatically readjust.

kmcghee wrote on 2/1/2018, 8:54 AM

Please clarify - are you shooting 4:3 or widescreen 16:9?

https://www.vegascreativesoftware.info/us/forum/skewing-distortion-of-produced-mp4--96914/ should explain much re. JVC/ Canon/Panasonic (ca. 2008) .mod files.

https://www.vegascreativesoftware.info/us/forum/an-error-has-occured-while-opening-a-codec--90383/ as well.

Pity that the links in those threads do not work any more.

(Try SDcopy and set the widescreen flag there. See what happens with your aforementioned .mod+.moi files. SDcopy converts the mod files to mpg and puts the creation date and time into the file name.)

Thanks I will look over the links, and I will give SD Copy a try next import.

Musicvid wrote on 2/1/2018, 1:56 PM

Shouldnt he be able to force PAR in vegas media properties?

kmcghee wrote on 2/1/2018, 2:05 PM

What would be the benefit of converting using Handbrake and what is PAR?

vkmast wrote on 2/1/2018, 2:08 PM

Shouldnt he be able to force PAR in vegas media properties?

Yes. (Note that SDcopy puts the creation date and time into the file name)

PAR = Pixel Aspect Ratio

kmcghee wrote on 2/1/2018, 5:31 PM

So in theory sdcopy with the widescreen flag should pull off the mod files, change them to mpg and let movie studio know that it is a widescreen video, or handbrake would do the same but instead of a flag option its a selection of the correct

PAR

vkmast wrote on 2/1/2018, 8:31 PM

SDcopy did (still does) that with my .mod files since 2008 or so. I have not used Handbrake for that.

Musicvid wrote on 2/2/2018, 2:13 PM

handbrake would do the same but instead of a flag option its a selection of the correct PAR

Doubtful you would need to do that. How about try it, and get back to us?

There are a dozen different ways that programs use to glean information from video files, and flags are sometimes the biggest liars -- "expecting" conformity across the board is about as silly as expecting the same burrito from the joint across the street.