DGDecode colorspace change

[gastorgrab]

*I had a little problem with my firewall so i apoligise in advance if this is a double-post

My first post here, please be patient.

I've posted something similar over at VideoHelp.com but either noone is interested or noone knows the solution. I occasionally like to do XviD encodes of DVD rips and have been using DGIndex since DVD2AVI.dg. Great application, Thank You.

As time goes on the application becomes more complex, and i'm trying to keep up but.....

Anyway, I tried this after Wilbert posted a link to a SmoothDeinterlace that works with AviSynth 2.56a;


---------
LoadPlugin("C:\Ut\Video\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\Plugins\SmoothDeinterlacer.dll")
#
mpeg2source("DeeperIntoTheBlue.d2v",cpu=6)# DGDecode Output is YV12
#
ConvertToYUY2(interlaced=true)# Smoothdeinterlacer requires YUY2
SmoothDeinterlace(tff=true)# Output is Progressive

---------


The result was a blocky-ness that i'm not used to seeing. I began wondering if the ConvertToYUY2 had something to do with it;

Does this conversion use part of the information from the wrong field or does "(interlaced=true)" take care of things? http://img509.imageshack.us/img509/5710/dein7sf.jpg



The problem was later resolved by changing the script to;
---------
LoadPlugin("C:\Ut\Video\DGMPGDec\DGDecode.dll")
LoadPlugin("C:\Program Files\AviSynth 2.5\Plugins\SmoothDeinterlacer.dll")
#
mpeg2source("IntoTheBluePreview.d2v",cpu=6,upConv=1)
#
SmoothDeinterlace(tff=true,doublerate=false
---------


....but I still don't know why it happened in the first place.

DGDecode.dll obviously know's what colorspace the video uses. It also knows if the source is interlaced or progressive. Should i include "AssumeFieldBased" before attempting to change (ConvertToYUY2)?

Something to do with this maybe?

DGDecode automatically uses the PROGRESSIVE_FRAME flag to switch between field/frame based upsampling on a per-frame-basis

Can i assume from this that DGDecode will neither call the source Interlaced or Progressive? (just somewhere in between)
.

[Wilbert]

Forgot to reply in that forum. I'm sorry :)

Does this conversion use part of the information from the wrong field or does "(interlaced=true)" take care of things?
Yes, you should use that when your source is interlaced (in that case it uses information fromt the same field for the conversion).

I don't understand why upConv=1 is of any difference to your blocking issue.

If you use a different deinterlacer (KernelDeint for example), do you also see blocking?


mpeg2source("DeeperIntoTheBlue.d2v",cpu=6)
KernelDeint(order=1)
ConvertToYUY2()

[gastorgrab]

Forgot to reply in that forum. I'm sorry :)


Yes, you should use that when your source is interlaced (in that case it uses information fromt the same field for the conversion).

I don't understand why upConv=1 is of any difference to your blocking issue.

If you use a different deinterlacer (KernelDeint for example), do you also see blocking?


mpeg2source("DeeperIntoTheBlue.d2v",cpu=6)
KernelDeint(order=1)
ConvertToYUY2()


In that order? I only changed to YUY2 to use SmoothDeinterlace.

I tried LeakKernelDeint, but i don't have alot of experience with it. The results looked similar to the first SmoothDeinterlace attempt (i probably wasn't using it correctly).

LeakKernelDeint(order=1,sharp=true) - Using "sharp=true" was probably a bad idea in hindsight.

I ended up using what i'm most familiar with. I'll re-rip that disc, try a few different methods, and investigate a little closer with PhotoShop.

--edit--

This is strange indeed.

Using this;

LoadPlugin("C:\Ut\Video\DGMPGDec\DGDecode.dll")
mpeg2source("D:\VTS_07_1.d2v",cpu=6)
Info()


I get; 'FieldBased (Separated) Video: NO'
http://img370.imageshack.us/img370/8063/sv0qe.jpg
http://img467.imageshack.us/img467/8254/dg4uo.jpg

Either DGDecode isn't passing this info to AviSynth, or it isn't seeing the source as interlaced.
(or i did something wrong again)

*VTS_07_1.VOB is the original source material, DeeperIntoTheBlue.
*Using DGIndex version 1.4.5. - Any known issues?


---edit---


The results of KernelDeinterlace (two consecutive frames)
http://img212.imageshack.us/img212/8655/16ac2.jpg
http://img212.imageshack.us/img212/58/20fc.jpg

Definately not blocky. I remembered a different attempt.

This is inefficient deinterlace attempt. I'll do some more reading.
.