Re: GPU Deinterlacing
Posted: Thu Feb 21, 2019 4:00 pm
32 bit version
Support forum for DG Tools
[RESOLVED] GPU Deinterlacing
Page 1 of 2
Re: GPU Deinterlacing
Posted: Thu Feb 21, 2019 4:42 pm
I'm baffled. I get the same results as gonca. Are you absolutely positive we are working with the same sample?
Re: GPU Deinterlacing
Posted: Thu Feb 21, 2019 5:06 pm
Long shot but....
I am on AviSynth+ version r2728
I am on AviSynth+ version r2728
Re: GPU Deinterlacing
Posted: Thu Feb 21, 2019 5:06 pm
Yes. I just verified it by downloading the file which I have uploaded, and made a CRC check against my local original file. It's the same.
Strange, strange, strange ......
Strange, strange, strange ......
Re: GPU Deinterlacing
Posted: Thu Feb 21, 2019 5:34 pm
Do you have access to another system that you can try it on?
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 2:11 am
No, not with NVIDIA GPU. But as gonca and you got the same result, I conclude that something is borked here.
Perhaps there is something pathalogical with the file? I tried with the ffms2 (Libav) sourcefilter, like
and got a fields sequence with clear, unblended pictures at 119.88 fields per second like babb cbcc dcdd edee ..........
MPC-HC with internal LAV filters and YADIF SW deinterlacer plays the file nicely without blends like abcde .... (single rate, 29.97fps) or aabbccddee (bobbed 59.94fps).
Perhaps there is something pathalogical with the file? I tried with the ffms2 (Libav) sourcefilter, like
Code: Select all
ffms2("W2gutoff.m2ts")
assumeTFF()
separatefields()
MPC-HC with internal LAV filters and YADIF SW deinterlacer plays the file nicely without blends like abcde .... (single rate, 29.97fps) or aabbccddee (bobbed 59.94fps).
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 4:17 am
Problem solved!
Installing the latest slipstream of DGDecNV solved the problem. I had still the previous slipstream from January on my system. Sorry for all the confusion, I should have thought of this earlier
Installing the latest slipstream of DGDecNV solved the problem. I had still the previous slipstream from January on my system. Sorry for all the confusion, I should have thought of this earlier
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 8:17 am
I'm happy for you but I don't think DGDecNV ever had such a bug. What slipstream was it that you claim has such a bug? I can retest with that version.
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 10:32 am
I am not 100% sure but I think it was the one published around January 31. Was this slipstream 165?
If DGDecNV wasn't the culprit I only hope that the issue will not return.
If DGDecNV wasn't the culprit I only hope that the issue will not return.
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 10:53 am
I tested with slipstreams 168 and 161
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 10:54 am
Yes, it was 165. I will check it when I get the cropping/resizing fix released.
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 2:09 pm
Not seeing any blended fields with build 165.
Re: GPU Deinterlacing
Posted: Fri Feb 22, 2019 3:41 pm
I'll also test with 165 when the current job is finished. I have absolutely no clue what else could have made the fix. I've tried almost all other options.
Re: GPU Deinterlacing
Posted: Sat Feb 23, 2019 3:23 am
I reinstalled slipstream 165 and the problem is back. 
So at least I am happy that I found a likely, reproducible cause for my problem.
There is perhaps a faint probability that the .dgi and the .dll are not from the same slipstream, but wouldn't this have caused an error in avisynth?
I may try such criss-crossing later today. So far such misalignment (old .dgi, new .dll) has normally produced an error - in my experience.
Edit:
Even a .dgi which was created with slipstream 165 works ok with the .dll of slipstream 168. I conlcude from this that the culprit is the .dll of slipstream 165 - at least on my system. It's all reproducible here.
So at least I am happy that I found a likely, reproducible cause for my problem.
There is perhaps a faint probability that the .dgi and the .dll are not from the same slipstream, but wouldn't this have caused an error in avisynth?
I may try such criss-crossing later today. So far such misalignment (old .dgi, new .dll) has normally produced an error - in my experience.
Edit:
Even a .dgi which was created with slipstream 165 works ok with the .dll of slipstream 168. I conlcude from this that the culprit is the .dll of slipstream 165 - at least on my system. It's all reproducible here.
Re: GPU Deinterlacing
Posted: Sat Feb 23, 2019 11:05 am
So still looking weird. I don't think it's worth digging further, especially as the latest version is working fine for you. I'll mark this resolved, but post again if the problem recurs with later versions.
Re: [RESOLVED] GPU Deinterlacing
Posted: Sat Feb 23, 2019 11:11 am
Ok. Thanks.
Edit:
Happy to confirm that slipstream 169 is working well here, no blends.
Edit:
Happy to confirm that slipstream 169 is working well here, no blends.