Deinterlacing

Anything related to video and my tools that is not a support request.
Mat1926
Posts: 13
Joined: Thu Mar 15, 2018 9:16 am

Re: Deinterlacing

Post by Mat1926 » Sun May 06, 2018 10:01 am

admin wrote:
Sun May 06, 2018 9:41 am
Second, you should update to the latest DGDecNV slipstream 147. I'm reluctant to support older versions.
I just updated to the latest 147 version, and like you said nothing fails now, having the commands on separate lines also works...Regarding the NVIDIA driver number, now I am updating to the latest one 397.31....

User avatar
admin
Site Admin
Posts: 3973
Joined: Thu Sep 09, 2010 3:08 pm

Re: Deinterlacing

Post by admin » Sun May 06, 2018 10:09 am

OK, cool. Does that also mean x264 launcher is not failing now too?

About undoing telecine. First we need to know if it is soft or hard telecine. Load the source in DGIndexNV and then save project. What is the film percentage reported at the bottom of the DGI file?

Mat1926
Posts: 13
Joined: Thu Mar 15, 2018 9:16 am

Re: Deinterlacing

Post by Mat1926 » Sun May 06, 2018 10:23 am

admin wrote:
Sun May 06, 2018 10:09 am
OK, cool. Does that also mean x264 launcher is not failing now too?

About undoing telecine. First we need to know if it is soft or hard telecine. Load the source in DGIndexNV and then save project. What is the film percentage reported at the bottom of the DGI file?
No X264 launcher does not work!

Code: Select all

Simple x264 Launcher (Build #1124), built 2018-02-27
....
....
x264 [error]: could not open input file `0'
The film % is 0.00.
What are the expected values here?!

Thnx

User avatar
admin
Site Admin
Posts: 3973
Joined: Thu Sep 09, 2010 3:08 pm

Re: Deinterlacing

Post by admin » Sun May 06, 2018 10:24 am

Please give the exact steps you do to get this error in SimpleLauncher. Also give the full log from SimpleLauncher. It works fine for me without error.

Telecining stuff comes after we resolve this error.

Mat1926
Posts: 13
Joined: Thu Mar 15, 2018 9:16 am

Re: Deinterlacing

Post by Mat1926 » Sun May 06, 2018 10:32 am

admin wrote:
Sun May 06, 2018 10:24 am
Please give the exact steps you do to get this error in SimpleLauncher.

Telecining stuff comes after we resolve these errors.
The issue is in the new custom preset that I just made :facepalm:, I used an older one that worked in the past and the x264 launcher now works w/o issues at all. I need to investigate the changes I made to this preset. Now there are no issues with the x264 launcher...

Thnx

User avatar
admin
Site Admin
Posts: 3973
Joined: Thu Sep 09, 2010 3:08 pm

Re: Deinterlacing

Post by admin » Sun May 06, 2018 10:42 am

OK, on to inverse telecining.

Because you have 0% film, that is hard telecining and you will need to use IVTC filters rather than just fieldop=1 in DGSource(). If this is not making any sense to you, you'll have to do some research on it on your own. Other video forums can be very helpful in this regard. This forum is for support of my tools and related matters.

DGTelecide().DGDecimate():

The advantage here is that it is CUDA-accelerated and so it will be faster and leave more CPU for encoding.

TFM()/TDecimate():

The advantage here is that it is more flexible with additional parameters for tweaking.

If DGTelecide().DGDecimate() is not meeting your needs, I'd love to hear more about it with a view to enhancing it as needed.

Mat1926
Posts: 13
Joined: Thu Mar 15, 2018 9:16 am

Re: Deinterlacing

Post by Mat1926 » Sun May 06, 2018 10:47 am

admin wrote:
Sun May 06, 2018 10:42 am
If DGTelecide().Telecide() is not meeting your needs, I'd love to hear more about it with a view to enhancing it as needed.
You said this "DGTelecide().Telecide()", is this what you really meant ?!

User avatar
admin
Site Admin
Posts: 3973
Joined: Thu Sep 09, 2010 3:08 pm

Re: Deinterlacing

Post by admin » Sun May 06, 2018 10:55 am

Of course not.

DGTelecide().DGDecimate()

Mat1926
Posts: 13
Joined: Thu Mar 15, 2018 9:16 am

Re: Deinterlacing

Post by Mat1926 » Tue May 08, 2018 1:23 pm

After finding out the field order, do we still need AssumeTFF() in our code ?

Code: Select all

AssumeTFF()
DGTelecide().DGDecimate()
Also, what if some interlacing artifacts were detected at the edges after our previous step, do you think something like this is needed?

Code: Select all

QTGMC(preset="fast").SelectEven()
Thnx

User avatar
admin
Site Admin
Posts: 3973
Joined: Thu Sep 09, 2010 3:08 pm

Re: Deinterlacing

Post by admin » Tue May 08, 2018 1:58 pm

You should not need an AssumeFPS() call, as DGSource() sets it for Avisynth+. It is harmless to include, however, as long as it is set correctly.

You have telecined material (unless you are now talking about a different source). You can't sensibly use QTGMC on it.

If you have artifacts with DGTelecide/DGDecimate, please link to an unprocessed sample video and give your script.

Post Reply