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.

[BUG] DFM DeRainbow & Motion Compensation cause crash
#8
Works!

But, there is a new problem. Blush

With the 9.16 dev build, Hybrid would set "interlaced=true" for DFM DeRainbow, if the source was interlaced, or if you positioned DFM DeRainbow before the deinterlacer.

With the 9.22 dev build, Hybrid now instead of setting "interlaced=true", does this:

# chroma denoising using DFM-DeRainbow
# deinterlace since the filter does not support interlaced content
AssumeTFF().TDeint(mode=1)
DFMDeRainbow(maskthresh=5,interlaced=false,mc=true,use_Flux5framesT=true)
AssumeTFF().Separatefields().Selectevery(4,0,3).Weave()


Also, again, the Hybrid window has shrunk. I find I'm having to use the horizontal scroll bar a lot. Not sure if this is the best size. Undecided

Edit - Looking at the Wiki, it seems this is actually correct... interlaced=true should not be used.

Quote:False means the input clip is progressive; with true it's interlaced. Interlaced content is processed by using SeparateFields in the beginning and Weave at the end.
Note: this parameter was added as an after-thought, it's not technically correct so use with caution and only as a last resort.
Reply


Messages In This Thread
RE: DFM DeRainbow & Motion Compensation cause crash - by The_Tinkerer - 22.09.2020, 09:26

Forum Jump:


Users browsing this thread: 1 Guest(s)