29.97i to 59.94p

[OOOOPS]

Greetings,
I'm trying to convert my ntsc dv video from 29.97i to 59.94p for viewing on my pc's monitor, much of it is high motion so it looks terrible on the pc, using the older guide at http://www.100fps.com/ and information at http://avisynth.org/InterlacingAndDeinterlacing.

What is the preferred method of de-interlacing the video? I've read that this method is outdated and I've read that it isn't. So I figured why not ask the experts.

The video will end end up being in divx6 or x264 on the pc.

Thanks,
Michael

P.S. Is there a company anyone here would recommend to capture or scan old 8mm & Super8 film. My attempts at telecine have thus far been unsatisfactory and I don't have the time to build a jig and properly scan several hours of film not to mention the time required to process it.

[Blue_MiSfit]

120fps is good for reference, but it's pretty outdated :)

If you want full motion fluidity at 60p, then bob deinterlacing is the only way to go! Use AviSynth!

You can try something as simple as a dumb bob(), and work your way up. Highest quality results are typically achieved with MCBob(), at the expense of speed. Other good bobbers to try are:

YadifMod(mode=1)
TDeint(mode=1) (with or without edi upsized clip, which is required for yadifmod)

Just some suggestions!

~MiSfit

[thetoof]

I'd go for MCBob() + some denoiser (like dfttest (http://forum.doom9.org/showthread.php?t=132194)) to improve compressibility. I did that for a DV project and the results were great! (especially with x264)

To use MCBob(), get the prerequisites mentionned in this (http://forum.doom9.org/showthread.php?p=1055263#post1055263) post (either on avisynth's wiki or with google search) and copy the function in this (http://forum.doom9.org/showthread.php?p=1055264#post1055264) post to the notepad, save it as a .avsi and put everything in the plugins folder of avisynth.

[Blue_MiSfit]

Indeed. MCBob FTW... assuming you have the time on your hand to endure 1-2fps for SD content (IIRC) :D

Not much better out there to be honest. Most hardware standards converters don't even come close!

~MiSfit

[OOOOPS]

Thanks for the replies and suggestions and sorry to take so long getting back to my own post.
I don't really care about processing time I would rather have a small video that that looks great.
I finally gathered all of the plug-ins and made and tested a clip. The clip looks good, but is output, at 29.97fps.
where in the MCBob v0.3 (http://forum.doom9.org/showpost.php?p=1055264&postcount=10) script do I adjust it to 59.94?

Where in the same script would I set the video to Bottom Field First? I Believe it's here, ORDR = (order==0) ? "TFF" : "BFF", but I'm not sure what to set the value to.

Sorry for the newbie questions, but with a toddler running around the house the time to read, search and understand new ways of processing video via script is just not readily available.
Just to be clear mcbob is supposed to be deinterlacing not virtual dub's smart de-interlace filter?
Thanks,
Michael

[Revgen]

For mcbob...

Put

assumtff()
mcbob()

To bob TFF interlaced content.

Put

assumebff()
mcbob()

to bob BFF interlaced content.

[thetoof]

The clip looks good, but is output, at 29.97fps. Where in the MCBob v0.3 script do I adjust it to 59.94? Your output with MCBob() should be 59.94fps. If not, you must be using selecteven() or selectodd(). Simply remove that command (i.e. only use mcbob()) and it'll be fine

Just to be clear mcbob is supposed to be deinterlacing not virtual dub's smart de-interlace filter?
Yes.

edit: I just checked the script. The following means "order" is 0 (top field first) if the clip is TFF and is 1 (bottom field first) if the clip is BFF. So, it's done automatically and you don't have to specify anything regarding field order.

order = (clp.GetParity == True) ? 0 : 1
ORDR = (order==0) ? "TFF" : "BFF"

[OOOOPS]

I copied the mcbob script refernced above. The only thing I added was
# - MedianBlur by tsp
AVISource("DancingLillyandCoda.avi")
mcbob()
function MCBob(clip clp, float "EdiPre", int "Ed
the red text.
Aparrently I was not actually using mcbob as I had no error messages before.????

Virtual dubs error log states

*] AVI: Opening file "G:\avisynth\59.94doom9.avs"

[i] AVI: Avisynth detected. Extended error handling enabled.

AVI: Opening file "G:\avisynth\Copy of 59.94doom9.avs"

[E] Error: Avisynth open failure:
Evaluate: System exception - Integer Overflow
(G:\avisynth\Copy of 59.94doom9.avs, line 80)
(G:\avisynth\Copy of 59.94doom9.avs, line 28)

line 28
mcbob()
line 80
black = Blankclip(ofields).mt_lut("0").Trim(1,1).Loop(Framecount(clp))

Suggestions
Thanks,
Michael

[Blue_MiSfit]

Are you trying to load your source and run MCBob from within the MCBob script?

The proper way is to leave the script as is, and either load it into YOUR script with Import(...), or rename MCBob.avs to MCBob.avsi thus making it auto-loading.

~MiSfit

[Southstorm]

Do NOT copy and past the script, it is self contained.
To use it properly, Load the necessary plugins then Import McBob like this - Import(McBob.avs) - then proceed with you AVISource()

[thetoof]

Another thing you could do is :

Put all the required plugins for MCBob in the "plugins" folder of avisynth, copy and paste the MCbob v0.3u script in a blank notepad window, save as .avsi in the plugins folder too and call MCBob() in your .avs script (where you load your video and do all the additional filtering you need)

[OOOOPS]

Another thing you could do is :

Put all the required plugins for MCBob in the "plugins" folder of avisynth, copy and paste the MCbob v0.3u script in a blank notepad window, save as .avsi in the plugins folder too and call MCBob() in your .avs script (where you load your video and do all the additional filtering you need)

This works! Now I have new error messages! :). After finding I had missed two of the prerequisites it worked. I'm actually getting between .8 and 1 FPS processing. I assume the slow rate means MCbob is actually being used.

Now however, I have red "ghosts" in my test clip. The Ghost is displayed in virtualdub's (1.7.8) Input video pane so I believe this is being caused by MCBob. Attached is a frame grab using imagegrab. It think it should be sufficient. If not I'll be happy to sign up for some online storage and post my entire test clip.
Thanks for the information,
Michael

Note: the video is standard NTSC SD DV at 720x480. If any more information is needed just ask.

[thetoof]

For screenshots, please use "print screen", crop in photoshop (or anything else you like), upload to imageshack.us and post the link here... much easier for us.

Also, ntsc sd dv + mcbob should give you wonderful results. *waiting for the screenshot*

[Blue_MiSfit]

Indeed.

Try avsP. It's an _awesome_ avisynth script editor. It has totally replaced textpad/virtualdub as my scriptwriting software. It also has very easy image export (right click, save image). It also does macros (in simplified Python), and a GUI for tweaking filter parameters. Love it!!

~MiSfit

[OOOOPS]

here's a screen shot at just under 200kb.
Try avsP. It's an _awesome_ avisynth script editor.
looking into that now.
thanks again,
Michael

[thetoof]

Please upload your images to imageshack.us; it's annoying to wait for attachment approval...

[OOOOPS]

Please upload your images to imageshack.us; it's annoying to wait for attachment approval...

sorry.
try this (http://img384.imageshack.us/my.php?image=ghostrt9.jpg)

[thetoof]

This is weird... could you upload a small 20 mb sample of your unprocessed source?

1 - AVISource("DancingLillyandCoda.avi")
2 - load in vdub
3 - select a few frames
4 - save as "direct stream copy"
5 - compress with 7z
6 - upload to mediafire.com

[OOOOPS]

I installed avisntyh and pasted the plugins directory onto another pc. It works perfectly and the finished video looks great. Now to figure out what is wrong with my main pc.

Thanks for all the help!
Michael

[2Bdecided]

It could be a codec wrongly converting the colour space.

It could even be happening on the way into VirtualDub itself, so the output of the script might be fine.

[OOOOPS]

It could be a codec wrongly converting the colour space.
The question is which one.

It could even be happening on the way into VirtualDub itself
I don't think so. If I use only
separatefields ()
and de-interlace with virtualdub it looks fine. (not a good as mcbob, butt.....)

so the output of the script might be fine.
the audio is, but thats about all.

Any suggestions,

Thanks,
Michael

[2Bdecided]

I'd try throwing info() into the script at each stage in turn, and see what comes out. Note the colour space reported, and whether the info() text itself is the correct colour (should be yellow!).

Cheers,
David.