VideoHelp Forum


Try StreamFab All-in-One and rip streaming video! Or Try DVDFab and copy Blu-rays! or rip iTunes movies!
+ Reply to Thread
Page 3 of 3
FirstFirst 1 2 3
Results 61 to 63 of 63
Thread
  1. Member
    Join Date
    Apr 2021
    Location
    Florida
    Search Comp PM
    I will have to capture again. I deleted it.

    Also I figured out that I could take my original OBS capture and use Virtualdub to re-encode back into huffyuv. It created a huffyuv file that was marked correctly.

    You are most certainly correct about tape quality. This one has mild tracking problems. I can capture the same tape and it will freeze at random points in different captures.
    I wondered if there is some latency issue that OBS didn't have. Maybe I was just lucky before?

    I am creating an ISO and hope to test an interlaced DVD tonight.
    I will un another capture and post a sample afterwards.
    Quote Quote  
  2. Originally Posted by DB83 View Post
    Here is the sample.

    I posted a lagarith version from the same VHS source some days ago in another topic.
    Thanks for the sample. As near as I can tell, the video itself has no interlacing information. The original AVI spec doesn't have such a flag. The video file doesn't have an ODLM2 extension that could be used to flag interlacing. And finally the huffyuv codec has no private interlacing information that I know of. It looks like MediaInfo just calls any huffyuv 2.1.1 video interlaced if it is over 288 lines tall. If you crop your video and save it as 288 lines or less MediaInfo report progressive. If you crop to frame height over 288 (for example 292) it will report interlaced. It doesn't matter if the content is truly interlaced or progressive. Also, if you use some of the other huffyuv variants (ffmpeg, ffdshow, huffyuvmt) MediaInfo will always report progressive.
    Quote Quote  
  3. Member DB83's Avatar
    Join Date
    Jul 2007
    Location
    United Kingdom
    Search Comp PM
    ^^ Thanks for the insight. As earlier, I did suspect that mediainfo was making a broad assumption based on the codec.
    Quote Quote  



Similar Threads