View Full Version : VOB opened by VirtualDub good, but bad using AVS ...
AmiRage
13th January 2005, 19:04
I'm pretty clueless, for days I'm trying to simply deinterlace several different DVD sources using AVS and VirtualDub. It's no problem at all when using VirtualDub only, directly opening the VOBs using VirtualDub, but when using AVS (.d2v via MPEG2Dec3.dll or DGDecode.dll) it's impossible to deinterlace at all as the frames already seem to be broken, when being served to VirtualDub or whatever.
Here's an example of one frame, switching between these two versions of the same frame should show my problem, especially when looking at the red parts left and right of the doors of the tram.
Good = using direct import of VOB using VirtualDub ...
http://img22.exs.cx/img22/3991/goodpurevirtualdubtest7cd.th.png (http://img22.exs.cx/img22/3991/goodpurevirtualdubtest7cd.png)
Bad = using simple AVS script (see below) ...
http://img22.exs.cx/img22/2175/badvirtualdubthroughavs8yi.th.png (http://img22.exs.cx/img22/2175/badvirtualdubthroughavs8yi.png)
LoadPlugin("C:\AviSynth\DGDecode.dll")
MPEG2Source("M:\...\....d2v",cpu=0,cpu2="ooooxx",iPP=true)
#MPEG2Source("M:\...\....d2v")
I already re-/deinstalled DivX, XviD, AviSynth (several different versions) ...
Any hints? :confused:
Thanks in advance.
Guest
13th January 2005, 19:19
What do you think is broken? I don't see any issues with the frame you call "bad".
Maybe you need to upsample interlaced rather than progressive. Add this:
YV12toYUY2(interlaced=true) after the mpeg2source() line.
Also, you should not have two cpu parameter settings.
AmiRage
13th January 2005, 19:25
Originally posted by neuron2
What do you think is broken? I don't see any issues with the frame you call "bad".
:confused: Do you really see no difference between these two pictures?
Looking at the areas I mentioned above there's a IMHO visible difference, the interlace is somehow broken.
Originally posted by neuron2
Maybe you need to upsample interlaced rather than progressive. Add this:
YV12toYUY2(interlaced=true) after the mpeg2source() line.
Thanks, this seems to be a cure here, but is there something "broken" on my system as I can't remember ever having had this problem before.
Originally posted by neuron2
Also, you should not have two cpu parameter settings.
Ok, thanks for the hint, but this doesn't seem to be the problem here.
Edit: Upsampling not really cured the problems with a lot of remaining combing artifacts.
Guest
13th January 2005, 19:29
"somehow broken"???
I'm a newbie, please explain to me what that means. Thank you.
AmiRage
13th January 2005, 19:34
Originally posted by neuron2
"somehow broken"???
I'm a newbie, please explain to me what that means. Thank you.
Thanks for answering, neuron2, but please stop kidding by calling yourself a newbie. I'm the newbie. :rolleyes:
If you don't see a difference between both pictures, I think we can stop here.
I already regret having posted here without a diploma ...
Guest
13th January 2005, 19:39
Well, gosh, don't take offense!
If I could see a differnece I'd say so. So I'm asking what is the difference you see. And you reply "somehow broken". Can you not be a little more detailed about it?
Does anyone else see what AmiRage is pointing out?
stickboy
13th January 2005, 19:43
neuron2:
Open the full-size images and look at the headlights and at the tram's bottom-half, right-side.
AmiRage
13th January 2005, 19:58
Thanks, stickboy, I think you've seen what I mean. :)
Ok, here's a direct comparison:
http://img118.exs.cx/img118/7968/12goodandbad9bc.png
Leak
13th January 2005, 20:10
Originally posted by neuron2
If I could see a differnece I'd say so. So I'm asking what is the difference you see. And you reply "somehow broken". Can you not be a little more detailed about it?
Does anyone else see what AmiRage is pointing out?
Well, I was wondering what this all was about too until I took the ".th" out of the file names - of course severely downscaled thumbnails look the same... ;)
Looks like bad chroma upsampling to me; perhaps he's using a bad YV12 codec with VirtualDub?
Adding a "ConvertToYUY2(interlaced=true)" at the end of the script probably fixes this when you're looking at it in VD, but you really want to remove it when you encode using "Fast Recompress", as this error will then only manifest while previewing in VD.
This (http://forum.doom9.org/showthread.php?threadid=56972) YV12 codec probably also helps, and you can then just ignore my solution above.
np: Rie Tanaka - Raison d'être (Chobits Original Soundtrack 001)
Guest
13th January 2005, 20:47
That's the upsampling issue, which I mentioned in my first reply.
AmiRage
13th January 2005, 22:41
Originally posted by Leak
This (http://forum.doom9.org/showthread.php?threadid=56972) YV12 codec probably also helps, and you can then just ignore my solution above.
Thanks for the hint, but it doesn't help here.
Are there any known issues with ATI/Radeon?
But nevertheless I think I'll try on a clean installation the next days.
Wilbert
13th January 2005, 23:02
Looks like bad chroma upsampling to me; perhaps he's using a bad YV12 codec with VirtualDub?
That has nothing to do with a bad YV12 codec. How is the codec suppose to know that it is better to upsample interlaced in this case :) I guess Helix codec also upsamples progressively ...
@AmiRage,
For an explanation have a look at: http://www.avisynth.org/Sampling
Leak
13th January 2005, 23:16
Originally posted by Wilbert
That has nothing to do with a bad YV12 codec. How is the codec suppose to know that it is better to upsample interlaced in this case :) I guess Helix codec also upsamples progressively ...
Uh, emmm... yeah. It's bad, but not exactly the codec's fault - what was I thinking? :confused:
np: Iwasaki Taku - R.O.D (R.O.D The TV Original Soundtrack 1)
Guest
13th January 2005, 23:50
AmiRage, you edited to say that changing the upsampling didn't really cure it because there are still lots of combing artifacts. Those are separate problems. How did you do the deinterlacing? What is your full script now?
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.