Quantcast To deinterlace or not? Size to render? - digitalFAQ Forum
  #1  
06-28-2022, 07:07 PM
BruceOlsen BruceOlsen is offline
Free Member
 
Join Date: Jul 2019
Posts: 41
Thanked 6 Times in 5 Posts
I'm restoring old (1985-1995 VHS) home vids for the rest of the family.

It's on a lordsmurf workflow and I'll insert an unsolicited plug for his gear right here. It's functioned perfectly from day one.

The vids will be stored on my OneDrive for playback (though there's a chance I'd also load them onto a private YT channel). Nobody wants them as DVDs.

Based on the posts here MP4 seems to be the consensus, but it's completely unclear to me whether de-interlacing is necessary. Also, what size they should be rendered to?

Thanks
Reply With Quote
Someday, 12:01 PM
admin's Avatar
Ads / Sponsors
 
Join Date: ∞
Posts: 42
Thanks: ∞
Thanked 42 Times in 42 Posts
  #2  
06-28-2022, 09:04 PM
keaton keaton is offline
Premium Member
 
Join Date: Jan 2017
Location: USA
Posts: 160
Thanked 77 Times in 54 Posts
There are options to encode as interlaced for h264 (i.e. mp4), at least with ffmpeg. the -flags +ildct+ilme is the part of the command that does this. As an example, See this post NTSC 4:3 aspect ratio: 720x540?? Of course, with that, it then comes down to whether the video player you use will play it back nicely. I love the theory of not having to deinterlace the video, since the analog world is all interlaced. But sometimes the reality of the progressive/deinterlaced world we live in now makes it more difficult for PCs/tablets/phones to properly handle interlaced content. This option is not mentioned often, so I wanted to at least do that. It's something you'd have to experiment with to see whether it would work well for the use cases you plan to use it for.

If you are going to encode the file as deinterlaced, i.e the default for mp4, then it can be useful to do the deinterlacing on the AVI with QTGMC to either go from 30 frames per second (aka 60 fields interlaced) to 60 progressive frames per second. Or, if you find the video players or streaming setup you use don't play 60 frames per second very well, there is an FPSDivisor=2 option in QTGMC that will decimate back to 30 progressive frames per second for the final output. Or you can use the often mentioned SeparateFields().SelectEvery(4,0,3).Weave() to decimate the 60 fps back to 30 fps after running QTGMC.

Assuming capture at 720 x 480, and you want it to look 4 x 3 (640 x 480), you can either try the Spline36Resize option to go from 720 to 640 (or 704 to 640 if you use Avisynth to trim off the black vertical edges) or you can specify an aspect ratio option when you encode, with say ffmpeg using the sar options (see post referenced above). The options there are again sort of dependent on the players or setup you are using. If the players being used can properly take 720 x 480 or 704 x 480 file with a SAR flag that will make it display it in proper 4 x 3, then you could prefer that. However, if you have some players that don't honor that and those that are viewing care about it looking proper and not slightly stretched, then you can do the Spline36Resize to force the file to be 640 x 480 with a SAR of 1/1. That way, I think you would have less chance of a player incorrectly displaying the correct aspect ratio. DVD was much better about honoring the aspect ratio. But with H264, there are so many video players out there and not all of them handle simple standard features like aspect ratio (or deinterlacing, for that matter) as well.
Reply With Quote
  #3  
06-28-2022, 11:27 PM
BruceOlsen BruceOlsen is offline
Free Member
 
Join Date: Jul 2019
Posts: 41
Thanked 6 Times in 5 Posts
Thanks. I don't know how it will be played, but it would be on iOS or MacOS or Win or Android. Perhaps casting via Chromecast or its Apple equivalent (AirPlay?)

So the most universal format.

Is some non-mp4 format better?

I'm hoping to narrow the range of choices here, btw
Reply With Quote
  #4  
06-29-2022, 06:03 PM
keaton keaton is offline
Premium Member
 
Join Date: Jan 2017
Location: USA
Posts: 160
Thanked 77 Times in 54 Posts
H264 is the most common format these days. Most common containers are mp4 or mkv. I may be mistaken, but I've heard Apple could have some issues with mkv. So, perhaps mp4 is the most likely to work with all possibilities. I suppose if you don't know what use cases you have, and want to play it safe, my choice would be to crop the black vertical edges and resize to 640 x 480. Of course, also masking off the head switching noise on the bottom edge. In Avisynth, that would look something like crop(4,0,-12,-8).addborders(0,4,0,4). Just an example, tweak to appropriate amounts on each edge so you've got 704 x 480. Then use Spline36Resize(640,480). When you encode to H264, the SAR would be 1. Who knows, but I'd like to think that's the option that would be the hardest for a player to screw up when determining aspect ratio.
Reply With Quote
The following users thank keaton for this useful post: BruceOlsen (06-30-2022)
  #5  
07-03-2022, 11:18 AM
lordsmurf's Avatar
lordsmurf lordsmurf is offline
Site Staff | Video
 
Join Date: Dec 2002
Posts: 11,921
Thanked 2,170 Times in 1,870 Posts
For streaming, deinterlace is required. Only use QTGMC, either via Avisynth or Hybrid.

- Did my advice help you? Then become a Premium Member and support this site.
- For sale in the marketplace: TBCs, workflows, capture cards, VCRs
Reply With Quote
Reply




Similar Threads
Thread Thread Starter Forum Replies Last Post
Vegas Pro render settings? Denicio Encode, Convert for streaming 0 01-10-2022 02:31 PM
ATI AIW and MPEG-2: deinterlace or NOT deinterlace? puleddu Capture, Record, Transfer 9 06-13-2020 11:05 AM
Deinterlace during capture, or later? sanlyn Capture, Record, Transfer 6 08-10-2017 05:58 PM
Render Problem - Vegas Pro 13 RABinMS Edit Video, Audio 0 02-01-2015 11:38 AM
Best Youtube render for Sony Vegas 10 fuzzblaster Encode, Convert for streaming 7 09-30-2013 03:00 PM

Thread Tools



 
All times are GMT -5. The time now is 05:59 PM