Smart bob filter: DGBob() 1.6.0: Now with slow motion

[len0x]

Originally posted by neuron2
Woohoo, the only YV12 smart bob filter!

That is soo great!
I've already put it in GK instead of simple bob.
(You know how much I love putting new filters in there )

[FredThompson]

Yeah, the journal entry shows what a HUGE improvement this is.

I've never hyperboled, though I have bowled drunk and in the dark...

thank you neuron2,
after see the journal pictures
with very clear differences,
i was trying to DGBob in my .avs script with 480x480 (29,970 fps)
but give double framesrate and middle time.
with a help of sh0dan(thanks again sh0dan)
is working great in my script using
selecteven() after DGBob(0).

great work, great result!
congrats.

[sh0dan]

Did some real-life encodes. Great quality - possibly the best I've seem.

I do however still get some "marching ants" on high-contrast edges. There also appears some clear (very high contrast) ghosts. I'll PM you a link to some material.

I cannot seem to find any useable threshold as both too low and too high thresholds just make it worse.

[Guest]

Please get version 1.2.1 from my website. It fixes a terrible bug in RGB support, which affected DV and other files.

@sh0dan

I'm downloading the clip to have a look. Thank you for it.

[Guest]

OK, I understand the problem and know what to do about it. Standby for an improved release.

[gotaserena]

Would you recommend using this filter (+ some way of decimating) as an alternative to a do-it-all deinterlace filter?

[Guest]

Originally posted by gotaserena
Would you recommend using this filter (+ some way of decimating) as an alternative to a do-it-all deinterlace filter?

I don't know what you mean by a "do-it-all deinterlace filter". I've never seen one and I can't imagine one, so I have no way to respond to your question.

Since you refer to decimation, perhaps you are thinking of using it for inverse telecine. I do not recommend that. Field matching followed by postprocessing of combed frames will always be preferable.

[Guest]

Version 1.3.0 is now available at my web site. It cleans up sh0dan's clip pretty well. It is not perfect but I don't think it can be. This version considers more pixels in the temporal neighborhood to further improve motion detection.

[Guest]

I've released what I hope is the final version for a while: DGBob() 1.4.0. This version adds an optional artifact protection feature. It requires more processing and may increase flicker a bit, but it almost guarantees that no visible artifacts will be produced. It should be used only if required; most clips do not require it.

I cannot think of any ways to improve things at this point, unless some bugs are found.

[sh0dan]

Seems like a very good idea! DGBob is way better that anything else by now - so it seems like a good idea to get it into decomb now - I'm looking very much forward to a 5.0 final - even though I guess there is still a long way to go.

Keep up the great work!

Edit:
Could you make a big, bold statement saying: "DGBob DOUBLES the framerate of your video!" - I've already seen several "problems" related to that. Possibly you could also put in there, what selecteven() does.

[Guest]

Originally posted by sh0dan
Could you make a big, bold statement saying: "DGBob DOUBLES the framerate of your video!" - I've already seen several "problems" related to that. Possibly you could also put in there, what selecteven() does.

ROTFL.

Better yet, how about an option to produce non-doubled output? I could do it, but I already have in mind a new straight deinterlacer. But if it would prevent confusion...

[Guest]

DGBob() 1.5.0 is released at my website. It adds non-doubled frame rate output.

Hey sh0dan, less than half an hour to do that, including updating my web site.

[gotaserena]

Thanks sh0dan, and neuron2 for the prompt implementation.

yes,i'm thankfull to neuron2 and sh0dan for this all too.

with the new DGBob1.5.0 don't need to use
selecteven()!

uding
DGBob(x,true)
runs fantastic without give double framesrate and middle time.

[sh0dan]

No need to thank me on this one - the D.G. Master of Digital Downright Deinterlacing Code has shown his mastery face once again! (sorry - the sentence above just flipped into my mind somehow )

Anyway - DGBob is a very good contester for a FieldDeinterlace() replacement. However - even though it gives the best "smart bobbing" available, there is still the flickering issue that should get solved, if it can be considered to be a 100% replacement.

But for a "proof of concept" DGBob rocks!

[Guest]

Originally posted by sh0dan
there is still the flickering issue that should get solved, if it can be considered to be a 100% replacement.

Which issue is this? Are you talking about the marching ants or something else? Can you please provide a test clip? Thank you.

[sh0dan]

If you use the latter part of the testclip I sent you, you should be able to reproduce - notice the outline of the static text. I get flicker - even with the latest version.

It's a great filter - and for what it does I don't expect it to do miracles - I have though about the possibility of doing a "bob-postprocessing" filter, that was able to detect this flicker and elimiate it.

(But please ignore me, and get back on the decomb - it's much more important than this - DGBob is already a big step forward!)

[Guest]

I noticed that, but the video content is changing underneath the edges of the letters in some places. I'm not sure what I can do about it. Anway, let me finish up Decomb 5 first and see if I have an unconscious brainstorm about this.

[ADLANCAS]

Do you recommend use Dgbob with interlaced sources ?

I have a script that produces much better results with Dgbob than SeparateFields(), SelectOdd()/SelectEven() and a noise filter.
Script is here:

http://forum.doom9.org/showthread.ph...0&pagenumber=2

Thanks,

Alexandre