UnboxB problem

[Cannonaire]

A while ago it was suggested that I try out UnboxB for removing dot crawl. At the moment I seem to have gotten the dot crawl under control without it, but I would still like to try it to see what kind of results I can get with it. Unfortunately, all I can manage to get out of it looks like this:


I also get an AvsP error window with this in it:

Code: Select all

Exception exceptions.WindowsError: 'exception: access violation reading 0x79735C6F' in <bound method PIScriptEnvironment.__del__ of <avisynth.PIScriptEnvironment instance at 0x035B1710>> ignored

If it helps, I'm on Win7 64 bit.

[Cannonaire]

*Update*
I just realized the error is coming from TFM and not UnboxB, though that doesn't bring me closer to a solution.

[mirkosp]

Could you post your script?

[Cannonaire]

Here are the currently active/pertinent lines:

Code: Select all

mpeg2source("K:\video_rip\outlaw_star\e06.d2v",cpu=0)
TFM(order=-1, field=-1, mode=1, PP=0)
UnboxB(strong=1)
#UnboxB(strong=0)
TDecimate(mode=1, cycleR=1, cycle=5, rate=23.976, hybrid=0)
Trim(27071, 27346)

[mirkosp]

Mmmh... unboxb should go before the tfm. Either way, you might want to try and re-rip and re-index your vobs. Looks like that might be the issue, since I don't really see anything wrong with that script.

[Cannonaire]

The documentation I read said to put UnboxB after deinterlacing but before decimating.
http://forum.doom9.org/showpost.php?p=1 ... ostcount=1

The problem is definitely with the function of the UnboxB line of the script. I've gotten the footage to look great otherwise. Regardless of where I put the UnboxB line, it causes the same problem, be it before or after TFM. I also tried it with AMVIVTC and got the same results. As far as what I am getting in the preview, a lot of the correct colors seem to be coming through, just all scrambled, except for the jagged green lines. Those are present even in a completely black frame.

And another update, I only get the error message when using both TFM and UnboxB. Either one by itself will not give me the message, and I also don't get the message when using AMVIVTC with UnboxB.

This isn't urgent for me. I don't specifically need UnboxB for this footage; I just want to be able to use it properly for when I do need it. Thanks for your help so far.

[Cannonaire]

Of course, if I had bothered to actually read the thread following that documentation a week ago, I would have read about other people's problems and found the solution earlier. Turns out it doesn't like 720x480 for some reason, so adding the inevitable Crop line before UnboxB fixed the problem. Guess it's not a total waste though. A search of this forum for UnboxB shows only two threads, this one and the other one where UnboxB was first reccomended to me.

Results: First impressions are fantastic. It removes dot crawl which other functions like Checkmate don't even begin to touch. I need to analyze a bit more to check for artifacts.

[mirkosp]

Ah yeah, I totally forgot about it going between tfm and tdecimate as opposed to other dot crawler remover. Sorry for that.
Glad it works now, though.

[Scintilla]

I'm going to assume you are running an old version of MPEG2Source, on AVISynth 2.5.7 or higher.
What fixes this for me is to add the line SetPlanarLegacyAlignment(true) right after the MPEG2Source call.

That, or re-index your VOBs with a newer indexer (e.g. DGIndex) and load with a newer MPEG-2 decoder plugin (e.g. whatever version of DGDecode comes with the DGIndex used).

[Cannonaire]

Thanks for the suggestion, I'll try that a bit later when I have the time. I only recently installed everything for making AMVs (as in, I wasn't doing any editing before 2 months ago), but I should try to keep everything up to date. The DVDs were ripped and indexed in that timeframe by myself. I am using Avisynth 2.6 right now, and I believe DGIndex is up to date. Does SetPlanarLegacyAlignment cause any problems with newer plugins? I read the description here: http://avisynth.org/mediawiki/Internal_ ... _functions

First impressions were nice, but UnboxB does blur the living hell out of the material I'm working with right now. Even with only the strong=0 line. The dot crawl is fairly minor, and it seems it as well as a lot of rainbowing were there before the telecine/interlacing process, so I've had to work with it a different way. Right now I have it looking good though, and I now I can use UnboxB in a few areas if it is truly needed. Thank you!