Selur's Little Message Board

Full Version: de interlacing
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
When I de interlace with hybrid I get jagged lines on fast movement looks like jagged lines for a few seconds during the fast movement.

I'm choosing overwrite source input because  hybird wrongly flags huffyuv and  lagrith lossless  codecs as progressive whenthey are interlaced all VHS captures are and shouId be.

I choose top field first because it's a VHS capture most captures from VHS are top filed first. DV is bottom field first.

I also set the field order to 1 (top field) first in the field settings in hybrid.

What is causing this issue? Could it be that the captures are bottom field first for some reason or a bad setting in hybrid? All I'm doing is de interlacing resizing and rendering.

Here are my settings for rendering in hybrid
For bitrate I chose 25,000 resize bicubic 1920x1080
Deinterlacing avisynth overwrite input to top field first then start render.

Thanks for this great free software.Please, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem.
Quote:I'm choosing overwrite source input because hybird wrongly flags huffyuv and lagrith lossless codecs as progressive whenthey are interlaced all VHS captures are and shouId be.
No, that's not the fault of Hybrid. Those formats have no interlaced flags to begin with, so there is nothing MediaInfo/FFMpeg/MPlayer, which Hybrid uses, could find to know the source is interlaced. Wink
Using 'Overwrite input scan type to' is the correct way to let Hybrid know the scan type of the source.
Whether TFF or BFF is the correct order can be easily determined, by looking at the Vapoursynth or Avisynth Preview which using a bob deinterlacer (for example QTGMC with 'Bob' enabled). If you play the content and the motion is fluid, you selected the right scan order. If the motion jumps back and forth, you selected the wrong field order. (see: [INFO] Interlacing patterns)

The field selection ('Select') in the QTGMC settings sets which field should be kept and interpolated during same frame rate deinterlacing.
If you want to overwrite the scan type just in QTGMC you can use 'Order' (by default it's set to '-1' which means the detected scan type is will be used).

About your resizing:
If your source isn't square pixel (PAR 1:1) you might want to configure Hybrid to convert to square pixel and adjust the height according to the width you selected. In general, I would not advise to disable 'Auto Adjust' under 'Picture Resize' unless you are sure you know what you are doing.

Cu Selur
(20.09.2023, 13:59)Selur Wrote: [ -> ]
Quote:I'm choosing overwrite source input because  hybird wrongly flags huffyuv and  lagrith lossless  codecs as progressive whenthey are interlaced all VHS captures are and shouId be.
No, that's not the fault of Hybrid. Those formats have no interlaced flags to begin with, so there is nothing MediaInfo/FFMpeg/MPlayer, which Hybrid uses, could find to know the source is interlaced. Wink
Using 'Overwrite input scan type to' is the correct way to let Hybrid know the scan type of the source.
Whether TFF or BFF is the correct order can be easily determined, by looking at the Vapoursynth or Avisynth Preview which using a bob deinterlacer (for example QTGMC with 'Bob' enabled). If you play the content and the motion is fluid, you selected the right scan order. If the motion jumps back and forth, you selected the wrong field order. (see: [INFO] Interlacing patterns)

The field selection ('Select') in the QTGMC settings sets which field should be kept and interpolated during same frame rate deinterlacing.
If you want to overwrite the scan type just in QTGMC you can use 'Order' (by default it's set to '-1' which means the detected scan type is will be used).

About your resizing:
If your source isn't square pixel (PAR 1:1) you might want to configure Hybrid to convert to square pixel and adjust the height according to the width you selected. In general, I would not advise to disable 'Auto Adjust' under 'Picture Resize' unless you are sure you know what you are doing.

Cu Selur

Most VHS captured recordings are TFF only DV is bottom field first and because DV25 codec has interlaced flagging hybrid media info idenitifes correctly.

When ticking bob and previewing the content goes out of sync so I was thinking to myself if I encode it with bob option enabled I may get out of sync encoded video and it would be a waste of time sometimes encoding can take 1 hour.

I will have to look at field selection I was only setting field order to 1 it was originally set to -1 bottomfield I was sure that would get rid of the wavy lines that only show up on a fast motion scene.

My content is PAL VHS 720x576 @25FPS (CFR) with overscan, I'm just upscaling for the internet but the real technical issue is the de-interlacing should be done first  before resizing so pixel  size is not effected, I'm not sure if hybird resizes first or de-interlaces first it just shows x number of calls or commands for it when it goes into render.

I think you should create a trouble shooting guide for people like me that explains each option and what it does and why. You have done such a great job with hybird 👍 everyone using it needs to thank you as much as possible this trouble shooting guide is a very simple thing you can pin to this forum and other video forums.
Quote:When ticking bob and previewing the content goes out of sync so I was thinking to myself if I encode it with bob option enabled I may get out of sync encoded video and it would be a waste of time sometimes encoding can take 1 hour.
Why? Playback length of neither audio nor video should change.

Quote:I'm not sure if hybird resizes first or de-interlaces first it just shows x number of calls or commands for it when it goes into render.
Avisynth and Vapoursynth Script views show the used scripts.
By default, deinterlacing is always before resizing.

Quote:I think you should create a trouble shooting guide for people like me that explains each option and what it does and why.
Sorry, but at least I got no time for that. Especially since folks don't usually read stuff (like the 'Infos needed to fix&reproduce bugs,..'-thread or the stuff in the 'General Hybrid Infos'-section), seems more like wasted time.

Cu Selur