New IVTC for Avisynth

[manono]

Hi Divine-

neuron2 is on Sabbatical for awhile, so he won't be able to help. I've never done a vid cap in my life, so I may not be able to help. However, neuron2 added a feature to Decomb recently, designed for your problem. This may help with some, if not all of the problems you describe. Anyway, this is a quote from the Help File included with Decomb:

y0 and y1 (integer, default 0) define an exclusion band for the field matching. If y0 is not equal to y1 this feature is enabled. Rows in the image between lines y0 and y1 (inclusive) are excluded from consideration when the field matching is decided. This feature is typically used to ignore subtitling, which might otherwise throw off the matching. y0 and y1 must both be positive integers and y0 must be less than or equal to y1; if this is violated an exception will be thrown.

And I'm sure there are others that have dealt with this problem first hand and may be able to offer some advice.

[h00z]

I can't thank you enough for making Decomb. I tried it on my own Cowboy Bebop rips and I have to say that it is the nicest rip that I have ever done of the series. Kudos man... I can't wait to see where this ends-up if it's this good already.

[Divine]

Thanks for your reply manono.
I have already played around with these y0 & y1 integers before, but it didn't seem to help in my case :(

[wmansir]

I hate to dig up such an old thread, but I just have one decomb question simple unworthy of it's own thread, and it's on the topic that this thread ended on.

Do the y0 and y1 values start at the top of the frame or the bottom? So is y0=0 (or 1) refer to the top line or the bottom line?

I'm encoding "Ran" and it has hard coded, interlaced subtitles on the bottom 100 lines, as an example could someone give me the y0 and y1 values to exclude this section of the frame?

[Guest]

Hmmm, maybe that's why it didn't work for Divine. :)

I just checked the code and I don't subtract the values from the frame height. Since I believe y=0 is the bottom line, that would mean it is referred to the bottom. Ooops. I'll double check this on my test files tonight and post again. Meanwhile, can you try an experiment and let me know? Try y0=0,y1=100. If it works, I'll probably just revise the help manual to say it is referred to the bottom. :p

[wmansir]

I haven't tried encoding the movie yet. I noticed the interlaced subs while preparing the source and remembered this feature of decomb, but was unclear how to configure it. However, after some searching I did find a few frames that were incorrectly pulled down because of the interlaced subs and y0=0, y1=100 gave the correct pulldown.

However, just to be sure I tried y0=380,y1=479 and it also gave the correct pulldown on the problem frames I encountered. I checked the results several times, because I don't understand why both settings would work. If anything I would expect the incorrect settings to make a bad pulldown more likely. Here are the instructions I used :

Telecide(post=false)

Telecide(post=false,y0=0,y1=100)

Telecide(post=false,y0=380,y1=479)

All were followed by:
Decimate(cycle=5)

I usually use 3.8, but I also tried these settings with 3.91, with identical results.

[Guest]

Stranger and stranger! :eek:

Can you make available the part of the source clip that shows this? Thank you.

[wmansir]

You've got PM.

I'm still trying to upload the file to the address provided. I'll send you another PM when it's available.

However, I was surprised at the speed hit from using exclusion, not that I would expect you to optimize for a very infrequently used option like this. I normally get 0.5 to 0.6 RT in CCE with Decomb, but using y0 I'm got 0.23 RT.

I think instead of using the y0 option I will process the sections seperately (since my subs are on a black boarder and do not overlay the video) and then stack vertical. Like this:

top=Crop(0,0,720,380).Telecide(guide=1).Decimate(cycle=5)
bottom=Crop(0,380,720,100).FieldDeinterlace().Decimate(cycle=5)
stackvertical(top,bottom)

With this method I get 0.20 RT, but I don't have to worry about the subtitles triggering unnecessary postproccessing on the video.

[Guest]

Please do get me the clip, as I'd like to get this capability working properly, even if you do have a workaround. Thank you.

[Guest]

@wmansir

Please try this test version and let me know how it works. The numbers are referenced to the bottom.

[wmansir]

Did you get the ran clip from my PM?

Using the examples from that clip, it seems you have worked out whatever bug was causing y0 and y380 to give the same results. However, it appears that y=0 is the top line.

Example 1, y0=0,y1=100, version 4.01
http://www.imgmag.com/images/wmansir/Ran_4_Y0_401.jpg

Example 1, y0=0,y1=100, version 4.02
http://www.imgmag.com/images/wmansir/Ran_4_Y0_402.jpg

Example 1, y0=380,y1=480, version 4.01
http://www.imgmag.com/images/wmansir/Ran_4_Y380_401.jpg

Example 1, y0=380,y1=480, version 4.02
http://www.imgmag.com/images/wmansir/Ran_4_Y380_402.jpg

Example 2, y0=0,y1=100, version 4.01
http://www.imgmag.com/images/wmansir/Ran_14_Y0_401.jpg

Example 2, y0=0,y1=100, version 4.02
http://www.imgmag.com/images/wmansir/Ran_14_Y0_402.jpg

Example 2, y0=380,y1=480, version 4.01
http://www.imgmag.com/images/wmansir/Ran_14_Y380_401.jpg

Example 2, y0=380,y1=480, version 4.02
http://www.imgmag.com/images/wmansir/Ran_14_Y380_402.jpg

I had hoped to put those images inline, but it doesn't matter. If you check them out you will see that for each example of the four versions only y0=0,y1=100 version 4.02 gives bad results. The other three are exactly the same, even the p,c,n numbers.

[Guest]

The clip I downloaded was corrupt for some reason.

Thank you for the results. I'll investigate the numbering issue more but it appears to be working now, no?

[wmansir]

Yes, it appears to be working fine, with y0=0 referencing the top line.

I just dowloaded the clip again and it seems to work fine for me. If it's a RAR problem, it may be because they are 3.0 rars and need Winrar 3.0 or higher to open. The clip uses the Huffyuv 0.2.2 codec available from doom's downloads.

But anyway, thank you for your help.

[reddragon72]

does this work with cce2.5? I cannot get it to load if it does. I have tried several ways and nothing. I don't have enough drive space to create big AVI files so I was triing to frame serve into CCE like I do with avisyth normally, but when I add the lines for this it crashes CCE.

LoadPlugin("c:\windows\system32\mpeg2dec.dll")
LoadPlugin("C:\Program Files\AviSynth2\plugins\Decomblegacy.dll")
mpeg2source("D:\dvdeditedvideo\dvdxcopy\van\van.d2v")
#AVISource("D:\dvdeditedvideo\dvdxcopy\van\van_d2v-vfapi.avi")
#ResampleAudio(44100)
Telecide
Decimate15


thanks for any help.

[scmccarthy]

Why do you have lines that are commented out? Also, trust me, you should always use parenthesis, even when they are empty.

Stephen

[lark]

i agree with the parenthesis.
most probably the avisource is commented out,
because there's already mpeg2source.

don't ask me about the resampleaudio.

regards
t :)

[manono]

Hi-

Before plugging your scripts into CCE and having them crash, you should probably open them first in VDub for testing. Then when they crash (as yours certainly will), at least you'll get an error message to point you in the right direction for fixing them. So, what is this:

Telecide
Decimate15 ? Do you really mean to say:

Telecide()
Decimate(5) ?

[hakko504]

AFAIK you need to uncomment the Resampleaudio line to make CCE accept the .avs

[Guest]

Originally posted by manono
Telecide
Decimate15 ? Do you really mean to say:

Telecide()
Decimate(5) ? He must have grabbed a REALLY OLD beta from that old thread.