This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] Passing interlaced content
#4
Ah, I see. Hybrid handles the source as configured.
Applying a filter that does not support interlaced content on an interlaced source would cause unwanted results.
When applying a filter, that does not support interlaced content, Hybrid does convert the content to progressive content based on what is configured under "Filtering->Vapoursynth->Misc->Source->Filter interlace handling" and converts it back to interlaced content at the end of the script.
In your example, Hybrid does exactly that. Smile

You are using CAS, which Hybrid assume to not support interlaced content.
Quote:converting interlaced to full-height progressive for filtering (vsCAS)
Hybrid thus deinterlaces the content according to your settings and reinterlaces the content at the end of the script.

"Filter interlace handling" atm. has the following options:
  • separate fields: here the top and bottom fields will be filtered separately
  • separate fields (join): here the top and bottom fields will be filtered as if they are following each other
  • TDeint(): content will be 'bob deinterlaced' using TDeint.
  • QTGMC(preset="XXX"): content will be 'bob deinterlaced' using QTGMC with the set preset (and ', Lossless=2')
Note that if you have filters that apply temporal based operations, deinterlacing and reinterlacing (the default setting) is the correct choice. In case of CAS which only works on static single frames (not tacking the neighboring frames into account), 'separate fields' is probably the most 'lossless' approach.
If you have a better suggestion how Hybrid could deal with this, let me know, and I will at least think about adding that method to Hybrid.
None of these methods should result in improper color space conversions or be unreasonably lossy.

So your options are:
a. use another setting for Hybrid on how to filter interlaced content with filters that only support progressive content.
b. do not use filters that do not support interlaced content

Cu Selur

Ps.: The "Filter interlace handling" will also be applied when a filter that does not support interlaced content is moved before the deinterlacing step in the filter order/queue and while dealing with interlaced content, which later gets converted to progressive content.
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Messages In This Thread
Passing interlaced content - by r3dfx - 21.12.2025, 22:51
RE: Passing interlaced content - by Selur - 21.12.2025, 22:59
RE: Passing interlaced content - by r3dfx - 21.12.2025, 23:51
RE: Passing interlaced content - by Selur - 22.12.2025, 08:04
RE: Passing interlaced content - by r3dfx - 26.12.2025, 09:22
RE: Passing interlaced content - by Selur - 26.12.2025, 09:31
RE: Passing interlaced content - by Selur - 26.12.2025, 21:30
RE: Passing interlaced content - by Selur - 28.12.2025, 08:22
RE: Passing interlaced content - by Selur - 31.12.2025, 06:19
RE: Passing interlaced content - by Selur - 10.01.2026, 20:51

Forum Jump:


Users browsing this thread: 1 Guest(s)