Log in

View Full Version : using srestore


Amateur
5th January 2011, 18:59
FINALLY got this script to work for me so now i just need to know how to implement it properly.

here is a sample (http://www.mediafire.com/?97l81kmhm8v38mv) of a peanuts show i'm trying to encode. megui analysis shows it to be hybrid film/interlaced mostly interlaced and does tivtc with top field first but that leaves a good amount of blending.

i tried adding srestore(omode=4) to my script but it doesn't appear to be doing anything.
** - chose omode=4 because the wiki documentation says that mode will use the smaller blend possibility.

and this is what the preview looks like
http://img171.imageshack.us/img171/9125/98399959.jpg

then went through omodes 1-5 with similar results

so i decided just try srestore() with nothing specified and the frames went from nearly 46000 to just under 19000. is this function supposed to remove more than half of the frames? will the video still look right?

full script (in case something else in the script can be modified to reduce the blending effect)

LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\DVDs\Peanuts 1970s Collection (vol. 1)\e1\VTS_01_1.d2v", cpu=4, info=3)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, interlaced=true, threads=0)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\TIVTC.dll")
tfm(order=1).tdecimate(mode=1,hybrid=3)

srestore()

undot()

FluxSmoothT(temporal_threshold=6)

vmToon(strength=100, luma_cap=150, threshold=2, thinning=100, ssw=3,ssh=3)

warpsharp(depth=100, blur=3, bump=100)

LanczosResize(640*2,480*2).turnleft().sangnom().turnright().sangnom()

BicubicResize(640,480,0.333,0.333) # Bicubic (Soft)

apparently srestore() didn't even get rid of all of the blending. the frame above got fixed but here is a few frames later
http://img811.imageshack.us/img811/5514/59214478.jpg

Didée
5th January 2011, 19:21
There is no fieldblending in your sample. It should be fine with standard IVTC. No point to use Srestore here, it will make things only worse.

Amateur
5th January 2011, 20:11
somehow i posted the same thread twice. if you can delete the other thread to clean up the board
http://forum.doom9.org/showthread.php?t=158923

and didee, here is a picture after using megui to only resize and impliment ivtc
http://img705.imageshack.us/img705/2613/70713353.jpg
script produced automatically by megui is
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\DVDs\Peanuts 1970s Collection (vol. 1)\e1\VTS_01_1.d2v", cpu=4, info=3)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, interlaced=true, threads=0)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\TIVTC.dll")
tfm(order=1).tdecimate(mode=1,hybrid=3)
#crop
LanczosResize(640,480) # Lanczos (Sharp)
#denoise

maybe what i'm seeing isn't actually called field blend then? but what is causing this? and how do i get rid of it?

Didée
5th January 2011, 20:37
The sample seems free from any kind of blending.

It is YOU who is CREATING the blending. :)

tfm(order=1).tdecimate(mode=1,hybrid=3)



TDecimate ReadMe:
hybrid -

Controls how or if video sections (30p) should be dealt with. Possible
settings:

0 - no handling
1 - blend decimation of 30p sections into 24p and leave 24p untouched (modes 0 and 1)
2 - vfr via mkv w/ timecodes file output (modes 3 and 5)
3 - blend conversion of 24p sections into 30p and leave 30p untouched (modes 0 and 1)

If you were just following the result of MeGUI's analysing, then you have a perfect example why you should never trust the decisions of a machine. Machines can calculate, but don't have a brain.

Amateur
5th January 2011, 21:41
ah...ok. well i changed hybrid to 0 for no handling and it seems to have solved that problem. is there an advantage or disadvantage to using tdecimate over yadif? when i changed it so that it is interlaced only and uses yadif, that also seems to have fixed it. maybe i'm doing the same thing in different ways?

at least now i know what megui is doing when it chooses mostly film or mostly interlaced and what to look for in case it's analysis is wrong. thank you.

Didée
5th January 2011, 22:30
is there an advantage or disadvantage to using tdecimate over yadif?
It's not a question of advantage or disadvantage ...

When TFM.TDecimate (inverse telecine) is appropriate, then Yadif (deinterlacing) is WRONG.

When Yadif (deinterlacing) is appropriate, then TFM.TDecimate (IVTC) is WRONG.


The reason that both methods look somewhat similar - in this case here - is that the progressive source actually is a 12 fps animation. The result of deinterlacing to 30p certainly is choppy, but not very obvious.
Part of the misery is today's "standard" of digital 60Hz displays. The correct way is to perform IVTC to get a 24p video. But when playing 24p on a 60Hz desktop, then the result is not fully fluid, either. For that, one would need to run the display at 24 or 48 or 72 Hz refresh rate. Some TFTs allow, some TFTs allow not ... and most users don't switch, because they aren't even aware of the issue. They watch choppy video day in day out, and think e'rything is like it has to be. :devil:

Amateur
10th January 2011, 03:34
??? don't think that applies to this thread at all. and i think you have to reformat your drive before a mac will recognize it. i'm guessing you would have to somehow backup your data online so you could download it onto the macintosh.