Ok, i see, nice work. :bravo: I think now we'll have to see if in real life it exists files with several SEIs information. This will probably take a little time. Edit I've take a look at the help file of the last version. You said mastering information follow the HEVC spec. Can you pinpoint me to wh...

Nice. In that case, if possible, put also the frame number before the SEIs (unless it was allready intended to).
After, next step will only be possible if avs+ implement frame properties...

Ok, thanks for the information. As i said, there is a big chance i didn't understood things properly.
I think we will probably have to wait for a full true mt2s UHD file to see what happens in real world...

From the few i've understood (but i'm not sure at all i've understood properly), mastering parameters can change on the fly, it's the core purpose of the HDR thing. In that case, how do you correlate the informations of the MASTERING line with the frame number ? Or asked differently : How do you kno...

Ok, done.
I'll try to test your new version on the HDR file provided in the first post of the link, out of curiosity, to see what result it produces.

Nice for the metadata things.
I've posted [elsewhere], to try so see if someone has an idea how to go to a second step here

Unfortunately i know almost nothing about HDR, except it seems to be some kind of nightmare. I never said anything was missing. It's just that it seems that to convert properly HDR, you need metadata that seems to be only on the h265 stream, and these informations can't be transmitted to avisynth. O...

3. CUVID delivers full 16 bits only, and I don't care to add code for all the conversions when you can simply use ConvertBits(), which also allows extra options, such as choice of dithering method, etc. ... pinterf can implement these conversions way better than me. Great point also indeed... ;) Th...

Thanks for this, i think it will be a great step. :bow: My questions are just to understand how it will work. - What will the fulldepth default value will be ? - In case of 10-12 bits, the ouput will be 16 bits if i understand properly. Is there a possibility to know what was the original "true" bit...

I would say exactly the same thing. Avisynth64 begin to be old and still have issues that has been fixed within avs+.

Don't know if LAV Video Decoder supports Helix or Xvid What i can say : With LAV filters, i can't open Xvid avi file with VirtualDub, it says there is no codec. With ffdshow (i know dev is stoped since a few years) i can open Xvid video file with VirtualDub. But, with LAV filter i can play Xvid avi...

What does your filter do with the interlaced fades in the stream you gave? "Nothing" or some wrong mix-up is also possuble, but in any way there is no possibility to have a true progressive picture in that case, because two IVTC patterns are mixed up. So, I'll deinterlace them after with my deinter...

A "postprocessed frame" is one that did not find a good field match. Ok, that's what tricked me. :facepalm: So, if i understand properly, and want to compare with my filter, i have to just use : dgtelecide() This will only perform the IVTC operation on frames detected telecine, and nothing more. Pe...

Ok, i've got the beta, i'll test this evening when back home. Ohh... another shared idea i'm using to detect telecine (still oriented 3:2). The following : A B C D 0 1 2 3 will result after telecine in (one possible pattern) : A/A B/B B/C C/D D/D 0 1 2 3 4 So, if both SoAD (and not "correlation" thi...

Euh... I was too much curious and get the last 2053 version, but i have an error message telling me that there is not such function as dgtelecide... :?: I've opened an avs file using DGSource, it works fine, but only if i put the license.txt file in the avisynth plugin directory (otherwise, i have a...

Didn't tested yet, i'll do this a little latter properly when more time (very probably this WE). Yes, i think it's limited to 3:2, but honestly, don't remember exactly... :scratch: I've done this "especialy" for anime, which have "standard" 3:2 IVTC, but where the pattern changes at each scene, or e...

Ok, basicaly what you're doing follow the same idea than me, after reading your description. Instead me is a simple pixel difference, the denoising part is just done by removing the 2 LSB... :D After, i do a lot of things, validate IVTC pattern (the 2 frames must be contiguous), if no data are valid...

First, mistake in my part : "Do IVTC" and not "Do telecine". It seems that the english word is not what i though, "false friend", or even more "doesn't exist". "Correlation" = sum abs(X -Y ) : The more X and Y are close, the lower it is. X and Y are a line of data. So, classic algorithms i knew chos...

I notice you did not comment on its speed, even though I specifically asked about it. Sorry... I've totaly zapped this one. Algorithm is "complex" and make probably a lot more computation than a basic/standard. My purpose wasn't realy the speed (even if i've tried everything i can to speed it up). ...

Sorry, no bad/perverse intention... :? I'll PM you later an ftp account with a clip i'm using to made my tests, but i don't remember if it performs better on this specific clip. I think remembering it performs better than the automatic IVTC included in VDub... If my post wasn't clear, i'll re-try to...

I don't know how exactly your IVTC works, but i'll just share with you my work/result of my VDub IVTC filter i've made almost 15 years ago... Get the code on my github if you're curious. At the time, all the automatic IVTC filters worked by detecting interlaced frame by computing fields corrolation ...

Perfect, thanks.

If quant matrices change, though, there is no workaround and we have to wait for a driver fix. Is your workaround safe in that case ? Also, it's possible that i didn't understood this statement properly, and you were not comparing this case with your workaround. And i thought you were not sure your...

admin wrote:OK, thanks to nVidia's fine support, the problem is now understood. It is due to a recent CUVID regression.

Just out of curiosity, as there has been several driver releases since, what is the actual status of this ?
Is it fixed in the driver, or do you still need your workaround ?

Thanks for trying this, even knowing that NV is not causing it... :bow: You can get also my avisynth plugins on my github, i'm using the "all in one plugin" for avisynth, the one called "plugin_jpsdr". Script : SetMemoryMax(192) video=DGSource("File.dgi",i420=false,deinterlace=0,fieldop=0).crop(0,20...