Rate Control Settings for new Staxrip...

[Selur]

@The.King: looking at the source, I thing the jerkiness is already in the source.
neither qtgmc, TIVTC, bob+restore(25) or simple deinterlacing really produces a motion that seems to be really fluent
tuning the restore settings might help a bit, but you will probably not really get rid of it.

Cu Selur

[The.King]

If you don't enable those options (de-interlacing, resizing etc) in MeGUI Script Creator then it won't add them to the script.

And how might I do that? Is there a one-click option to disable all of that, or do I need to find each setting manually and then ensure everything is turned off?

If your hand-made script is "ready to go" then just load it for encoding in MeGUI's main window and MeGUI will use it for encoding without touching it.

I thought that's what I did. I had the script ready to go, and put it in the 'Input - Video Encoding - Avisynth Script' path. But MeGUI still applied it's own settings/script anyway?

Have you noticed the latest version of MeGUI can now resize to mod4 or mod2. No more being stuck with mod16 resizing. Happy, happy, joy, joy!!!

I actually know more about avisynth now than I do about MeGUI, so I have no idea what you mean by mod4, mod2 or mod16 resizing.

If you're using QTGMC it'll be slow, especially if like me you're not using the multi-threaded version.

Yep, I don't know enough about the multi-threaded versions of anything. Selur gave me some tips on another program which would take advantage of the multi-core processing my PC is capable of and low-and-behold, although the QTGMC is still power/processor hungry, it was still about 8 times faster than using MeGUI? I've a pretty decent machine without going into the super-nerd category, so I'd expect QTGMC to be quicker - like it is with Hybrid.

In MeGUI, under the 'Misc' tab, there is an 'Input/Output' option to 'Force SAR' to various settings - default, 1;1, 4:3, 8:9, 16;11. Might that be it - or do I need to go into the whole 'crop and re-size settings'?

I don't know which "Misc" tab you're referring to

I'm referring to - hit 'config' for 'encoder settings' on the main input tab. From the x264 config dialogue box that opens, scroll to 'misc' and half-way down the page on the right is the 'Input/Output' I refer to.

Why it set the DAR to 3:2 in your case is a mystery to me.

That makes two of us so!

Logically it'd be because you changed the Input DAR manually

Nope, I didn't do that.

or because you somehow opened a file via a method which can't be used to detect the correct aspect ratio..... such as via directshow or even by using your own AVS script as the "Video Input".

Yep, I did that. As I said initially, because I had the script already written (and I was trying to avoid further automated analysis from MeGUI), I just loaded it via the 'Avisynth Scrip input' on the main window. That's why I was asking if there was a command line that I could write into the .avs file to dictate the AR to either anamorphic or 16:9?

Unless you're trying to re-encode some "exotic" video type,

There's nothing 'exotic' about it, trust me. I posted a sample of the source file in an earlier post - have a look (it's a .vob/.m2v file around post #70/71). Apart from being field blended - which the guys here figured out (PAL --> NTSC) there's nothing strange about it.

[Selur]

There's nothing 'exotic' about it, trust me.

Most people would call field blending pal to ntsc material as kind of exotic.

---
Hybrid is only faster since it uses Avisynth MT 2.6 and not Avisynth 2.5x like MeGui. (+ encoding normally uses 64bit x264 on 64bit systems not sure if normal MeGui does this automatically or if you have to use a 64bit version of MeGui)

---
about the DAR: the DAR is off when using MeGui since you didn't feed it with the source material and modify the existing internal Avisynth script, but you used your avisynth script as input. (avisynth does not signal aspect ratios)

about the modX thing: a resolution is called modX if it's evenly (= without rest) dividable by X.
e.g. 702 is mod2 but not mod4

----

all in all it doesn't really matter what GUI one uses,... all GUIs have their PRO and CONs.

Cu Selur

[The.King]

about the DAR: the DAR is off when using MeGui since you didn't feed it with the source material and modify the existing internal Avisynth script, but you used your avisynth script as input. (avisynth does not signal aspect ratios)

Thanks for that. I thought I was doing the right thing since I had the script written already. In theory so, (even with a fully complete .avs script ready) I should first go to 'tools' --> 'Avisynth script creator (Ctrl+R)' and input the video file, then click the 'clever anamorphic encoding' box (when I do, I only get the option to resize to 'mod16'?), then hit the 'config' button and ???? - copy/paste the content of my .avs file command lines? Does that mean that I stay away from the main input page (seems like I'd be duplicating issues if I did) or what?

about the modX thing: a resolution is called modX if it's evenly (= without rest) dividable by X.
e.g. 702 is mod2 but not mod4

I'm lost there, sorry. 702 is mod2 because it is devidable by x? What is 'x' then?

all in all it doesn't really matter what GUI one uses,... all GUIs have their PRO and CONs.

I'm sure that's the case, but so far Hybrid is looking like a pretty solid GUI to me.

[Selur]

I'm lost there, sorry. 702 is mod2 because it is devidable by x? What is 'x' then?

X = 2

I should first go to 'tools' --> 'Avisynth script creator (Ctrl+R)' and input the video file, then click the 'clever anamorphic encoding' box (when I do, I only get the option to resize to 'mod16'?), then hit the 'config' button and ???? - copy/paste the content of my .avs file command lines? Does that mean that I stay away from the main input page (seems like I'd be duplicating issues if I did) or what?

Haven't used Hybrid for years, but this is roughly how I remember it:
1. open source with MeGui
2. go to the script creator, let MeGui analyze the source, enable anamorphic encoding and do you cropping, than modifiy the script the way you want
3. close the script creator (now MeGui should show you the source)
4. configure the audio and video encoding/processing
5. tell megui to do the encoding

18
mod16->no
mod8-> no
mod4->no
mod2->yes

12
mod16->no
mod8-> no
mod4->yes
mod2->yes


Cu Selur

[hello_hello]

And how might I do that? Is there a one-click option to disable all of that, or do I need to find each setting manually and then ensure everything is turned off?

I was referring to using the AVS Script creator. Unless you're using it, MeGUI can't modify a script.

I thought that's what I did. I had the script ready to go, and put it in the 'Input - Video Encoding - Avisynth Script' path. But MeGUI still applied it's own settings/script anyway?

You must have done something else because it can't modify a script that way. I promise you there's no chance, as it just can't do it. All it'll do is load an existing script and then open the preview window, and you can add the script to the queue to be encoded. You must have done something else if MeGUI somehow changed the aspect ratio.
"Maybe" you used the AVS Script Creator to open your script. If you use an existing script as the source video in the AVS Script Creator, MeGUI will import it as though it's just another video. So from there it can apply cropping and resizing to the new script it creates, although even then you'd need to apply it deliberately. MeGUI just uses the standard AVISynth Import function for the original script. So you'd end up with a new script which looks like this:

Import("E:\Original Script.avs")
#deinterlace
#crop
#denoise
#resize

The original script would be opened, MeGUI could apply whatever further cropping and resizing you choose etc, and that would be saved as a second script which MeGUI can use for encoding. I can't see any other way MeGUI could have modified an existing script, although even then it's not really modifying the original script, it's using it as the source video to create a new one. The original script.... the one you said MeGUI messed with..... have you opened it to confirm it's actually been changed?

I actually know more about avisynth now than I do about MeGUI, so I have no idea what you mean by mod4, mod2 or mod16 resizing.

When resizing video, up until the latest version, MeGUI would only automatically resize to mod16 dimensions (height and width divisible by 16). Mod16 was traditionally used for a few reasons and is still fairly common for AVIs, but these days it's no longer really an issue. Having to stick to mod16 can mean the resizing isn't always exact. For instance you might resize a 1280x720 video to 704x400 for SD (both divisible by 16) but unless you crop a little that'll "fudge" the aspect ratio a bit as 704x400 isn't exactly 16:9. Finally MeGUI can resize 1280x720 video to 704x396 or 720x404, as an example. I'm referring to the resizing function when using the AVS Script Creator to create a script for encoding.

Yep, I don't know enough about the multi-threaded versions of anything. Selur gave me some tips on another program which would take advantage of the multi-core processing my PC is capable of and low-and-behold, although the QTGMC is still power/processor hungry, it was still about 8 times faster than using MeGUI?

MeGUI can use the MT version too as it's just creating an AVISynth script to which you can add QTGMC, but I generally don't run any "serious" filtering so I've never got around to updating the QTGMC components to the MT versions. Today's the first time I've used QTGMC in quite a while.

In MeGUI, under the 'Misc' tab, there is an 'Input/Output' option to 'Force SAR' to various settings - default, 1;1, 4:3, 8:9, 16;11. Might that be it - or do I need to go into the whole 'crop and re-size settings'?

I don't know which "Misc" tab you're referring to

I'm referring to - hit 'config' for 'encoder settings' on the main input tab. From the x264 config dialogue box that opens, scroll to 'misc' and half-way down the page on the right is the 'Input/Output' I refer to. [/QUOTE]

Ahhh..... I forgot MeGUI even had that option when setting up the encoder. I always let MeGUI add aspect ratios to the script so I've never had to use it. I wonder what happens if you add the aspect ratio to the script and use a different aspect ratio when setting up the encoder too? Maybe it's best not to think about such things.....

There's nothing 'exotic' about it, trust me. I posted a sample of the source file in an earlier post - have a look (it's a .vob/.m2v file around post #70/71). Apart from being field blended - which the guys here figured out (PAL --> NTSC) there's nothing strange about it.

When I said "exotic" I was just referring to file types most of use don't work with much. The less common video formats which MeGUI mightn't be able to open using the usual methods.

[The.King]

I've obviously got some pretty tricky files to contend with! I've run both of these through a series of programs and I keep getting the same results - that both contents are: NTSC, not interlaced, or field blended, etc.

After running through an encoder without applying many settings, it's obvious that the resulting encodes are interlaced (loads of horizontal lines), but when I analyse things (on the source file) frame-by-frame, it looks like it's field blended too (plently of backward & forward moving & distortion in every few frames). Yet when I apply Srestore=25, bob() etc., and deinterlace it with QTGMC (fast), I still get a lot of distortion throughout the resulting encode?? It looks terrible.

Can anyone therefore tell me what both of these source files are - blended, IVTC, etc. (being a newbie to encoding I'm obviously missing something) so that I know what settings to apply? If your feeling festive, you might also tell me how you figured it out (remembering I'm a newbie - so nothing mega technical please) - so that I will know how to check it for myself in future.

Many thanks - and Merry Christmas.

[poisondeathray]

They are the same as before : PAL=>NTSC field blend . You treat them the same way

There are different ways to "figure" it out. I followed the step by step instructions posted earlier

ie. AssumeTFF().SeparateFields(), looking for field order, then looking for patterns (is each field same or different?) => wait.... there are blended fields => well what is the pattern? was it blended from 25p or some other rate? then trying bob and srestore . I use bob() for quick diagnosis because QTGMC is slower, once you're satisfied with the pattern, you can replace bob() with a better bob deinterlacer like QTGMC(whatever settings)

If it goes fwd/back/fwd/back, that means you have the wrong field order. Instead of AssumeTFF() use AssumeBFF() or vice versa. If you didn't assume a field order, then avisynth assumes BFF by default

[The.King]

Thanks for that poisondeathray, I'll give it a whirl. It just threw me when I tried

'Yet when I apply Srestore=25, bob() etc., and deinterlace it with QTGMC (fast), I still get a lot of distortion throughout the resulting encode??

I mustn't have done the AssumeTFF() or AssumeBFF() part.

Thanks.

[Selur]

Normally there should be no need to set AssumeTFF() or AssumeBFF() if the material is properly flagged,..

[The.King]

Selur - as per our PM's (re. AR)....

[The.King]

Here we go again it seems...

OK, I've encoded quite a few tricky 'field blended NTSC<--PAL' files now, but this one is completely taking the biscuit....

I know this sample is field blended, interlaced, etc. but no matter what option I use in Hybrid (i.e. QTGMC/ medium / bob, SRestore frate=25fps etc.) [which is also what I did for a lot of other sources from the same program - all of which came out fine] - this, for some reason is causing havoc.

The resulting file after encoding is jerky, shaky and impossible to watch.

I could never get the hang of using just Avisynth & x264 (plus I also don't want and avi container) so this Hybrid program (along with a huge, huge, huge amount of help from Selur) has been top notch. It really is an excellent program. However despite it handling all previous files flawlessly, these new files are causing it a problem and one I don't know how to resolve. I've tried QTGMC, TIVTC, etc. (must have encoded this source about 28 times now with various SRestore settings applied etc., but nothing is watchable. (Please see original sample of source and resulting encode - which is the best I could achieve with Hybrid!)

Is there something else I'm missing? Is the source completely screwed - or is this a weird type of field blended material no one has ever seen before?

Would welcome any help - I'm slowly losing the will to live..........

[poisondeathray]

It's the same as the others. It looks like you got the field order wrong (This one is BFF , not TFF) . This is actually an example where QTGMC can make mistakes (it uses temporal information from the blends, and can give you worse results)

MPEG2Source()
AssumeBFF()
#bobber
#yadifmod(order=0, mode=1, edeint=nnedi3(field=2))
SRestore(25)

I could never get the hang of using just Avisynth & x264 (plus I also don't want and avi container)

You aren't limited to AVI container...

[poisondeathray]

Your sample is an example of why QTGMC sometimes shouldn't be used for deblending. Normally it does ok, but in some scenarios with certain types of motion with blends, it can give worse results. It's incoporating information from blended fields, so the final result includes more of that blended data (thus produces blurrier results) . Years ago , I recall master didee warned of using temporal bobbers with deblending. (didee is the original author of TGMC, the precursor to QTGMC)

I included some screenshots in a zip file comparing yadifmod/nnedi3 vs. srestore vs. qtgmc(slower) + srestore

[The.King]

It's the same as the others. It looks like you got the field order wrong (This one is BFF , not TFF) .

Not entirely. I'm not sure which short mp4 sample I uploaded (there are 28 or so), but I've tried TFF, BFF and a default of '-1' which is from source headers (whatever they are. No matter which I used, all encodes gave a pretty poor result - albeit, some worse than others - but it seemed to be more than just the field order - as no matter what I used, it didn't help. This was probably down to QTGMC and various settings as opposed to just field order.

MPEG2Source()
AssumeBFF()
#bobber
#yadifmod(order=0, mode=1, edeint=nnedi3(field=2))
SRestore(25)

Cheers for that - if I knew what you meant by the below, I could copy it into a avs script and run it.

You aren't limited to AVI container...

I've asked this before but no one could give me a clear answer - other than sticking the script into from front end encoder (MeGUI for example) and when I did (and obviously did something else wrong too) MeGUI processed my avs script alright, but also applied some of it's own (deinterlace) etc. settings too - so I was getting overkill.

If I knew of the program to open an avs script with which would give me an mp4 or mkv encode - I'd probably try Avisynth & x264 again. Otherwise, I'm stuck with front end GUI's.

[poisondeathray]

Not entirely. I'm not sure which short mp4 sample I uploaded (there are 28 or so), but I've tried TFF, BFF and a default of '-1' which is from source headers (whatever they are. No matter which I used, all encodes gave a pretty poor result - albeit, some worse than others - but it seemed to be more than just the field order - as no matter what I used, it didn't help. This was probably down to QTGMC and various settings as opposed to just field order.

No, this was purely a field order issue. If you go through that step by step list, you can come out with a good result . In fact , if you use the exact same script with QTGMC (just replace the yadifmod line), you will get decent results (just slightly more blurry in some frames due to the reasons mentioned earlier)

Cheers for that - if I knew what you meant by the below, I could copy it into a avs script and run it.

I was replying to your comment about "I don't want avi container". You can use a different container if you want. x264 is usually compiled with mp4, mkv, flv, avi +/- other container support


BTW you have to uncomment the "#" if you are copy / pasting

"#" means that line doesn't work

MPEG2Source() 
AssumeBFF() 
yadifmod(order=0, mode=1, edeint=nnedi3(field=2)) 
SRestore(25)

I've asked this before but no one could give me a clear answer - other than sticking the script into from front end encoder (MeGUI for example) and when I did (and obviously did something else wrong too) MeGUI processed my avs script alright, but also applied some of it's own (deinterlace) etc. settings too - so I was getting overkill.

If I knew of the program to open an avs script with which would give me an mp4 or mkv encode - I'd probably try Avisynth & x264 again. Otherwise, I'm stuck with front end GUI's.

If you just load the script into megui, it won't do any other analysis or processing (i.e. load the script into the 1st page, don't use the script creator or anything else in the tools menu)

Another gui you might check out is lord mulder's simple x264 launcher. It's very minimalistic . If you're happy with hybrid, stick with that. But any auto analysis program can make mistakes. You' ve several many examples in this thread alone

I probably mentioned this already, but I was in a similar position to you a few years ago. I learned avisynth through megui. At first I relied on the GUI because I had no fricken clue what avisynth was, but I hated making mistakes or wasting time re-doing encodes because of the errors and sub par results from auto analysis. That's partially why I learned about avisynth in the first place

[The.King]

No, this was purely a field order issue. If you go through that step by step list, you can come out with a good result.

Can you tell me which original post # is where I can find this step by step guide to figure out the source I am dealing with? (If I can make sense of it.)

In fact , if you use the exact same script with QTGMC (just replace the yadifmod line), you will get decent results (just slightly more blurry in some frames due to the reasons mentioned earlier)

If QTGMC will give me a worse result than yadifmod, why would I want to use it? (That is not intended to sound 'smart', I'm just trying to understand if I'm missing the bigger point.) I'm looking for the best quality (within reason) I can get. Not sure what this bit means though -->

(order=0, mode=1, edeint=nnedi3(field=2)

I've seen nnedi somewhere before - isn't that DeHalo Alpha or Anti-Aliasing or something? (sorry, I've been giving myself a small brain haemorrhage for the last few weeks, reading about things I never knew existed - so finding it difficult to remember everything!) Mode is part of the SRestore - right? Can you explain how you derived (order=0, mode=1, edeint=nnedi3(field=2)?

I was replying to your comment about "I don't want avi container". You can use a different container if you want. x264 is usually compiled with mp4, mkv, flv, avi +/- other container support

I think I got stuck on this because I know x264 can use mp4/mkv etc., but when inputting my original avs script into VDub, it was only giving me the option of an avi container - and when I put the avs script into MeGUI, it was applying it's own script too. I was obviously inputting my initial avs script into the wrong place in MeGUI - but I didn't know my way around MeGUI at the time (and still don't now as I've been using Hybrid), so I wasn't sure.

BTW you have to uncomment the "#" if you are copy / pasting. "#" means that line doesn't work.

I don't fully understand this sorry? I know you mean that if there's an '#' listing such as: #bobber or #yadifmod(order=0, mode=1, edeint=nnedi3(field=2)) that I'd have to remove them if I'm copy/pasting, because they won't work - but why won't they work, or why are they included initially? Sorry if that sounds stupid - it's just hard to follow everything when I don't know the context you mean it in.

(i.e. load the script into the 1st page, don't use the script creator or anything else in the tools menu)

Thanks for clearing that up - I'll give it a try.

Another gui you might check out is lord mulder's simple x264 launcher. It's very minimalistic.

Thanks. But you know the way when you said that you just use Avisynth and x264 (way back in an early post) are you just encoding to an avi container via VDub all the time, or if you're using an mp4/mkv container - what are you using to achieve that? Do you still use MeGUI for that purpose?

If you're happy with hybrid, stick with that.

Hybrid really is very good - the best GUI I've come across to date and I got a lot of time & support from Selur too which really, really helped me a lot. It makes Staxrip, (which I was using) look a little "old", but if like any other auto analysis tool, it's going to come up against problems (such as this one over field blended material) then I'm probably better off learning to use Avisynth, x264 and (??) to accurately output mp4/mkv files every time. I'll just need some support along the way here and there.

I probably mentioned this already, but I was in a similar position to you a few years ago. I learned avisynth through megui. At first I relied on the GUI because I had no fricken clue what avisynth was, but I hated making mistakes or wasting time re-doing encodes because of the errors and sub par results from auto analysis. That's partially why I learned about avisynth in the first place

Yep, that sounds exactly like me and where I am at right now! If the support was there for Avisynth (and a noob to avisynth - who wouldn't know one 'field' from another) and I knew where to go to get the support - I'd persevere and try to understand it. Yeah Google is a start, but you end up looking through 6hrs of sites (and a lot of unnecessary jargon which hurts your head) just to find a fraction of the info you need and that's not practical at all - no more than waiting 90 minutes for a part-blind encode to finish (albeit with the help of an Avisynth previewer) and realising that the auto analysis screwed up somewhere. This is a brilliant forum, and I've got a lot of help from the likes of your guys - which I'm very grateful for, but some of the time, it's like everyone is speaking 100mph when my ears are only taking stuff in at 25mph. Not the greatest analogy, but I'm sure you know what I mean.

[poisondeathray]

No, this was purely a field order issue. If you go through that step by step list, you can come out with a good result.

Can you tell me which original post # is where I can find this step by step guide to figure out the source I am dealing with? (If I can make sense of it.)

It's not a complete list of steps, but its a general guideline. Notice the 2 previous times you had problems it was a field order issue... (field order is important to get correct)
http://neuron2.net/faq.html#analysis

In fact , if you use the exact same script with QTGMC (just replace the yadifmod line), you will get decent results (just slightly more blurry in some frames due to the reasons mentioned earlier)

If QTGMC will give me a worse result than yadifmod, why would I want to use it? (That is not intended to sound 'smart', I'm just trying to understand if I'm missing the bigger point.) I'm looking for the best quality (within reason) I can get.

QTGMC in general gives you better results overall. For "normal" interlaced cases it almost always gives better results (when using anything other than the "ultrafast" preset). BUT - For some types of field blending and specific cases, other filters may give better results (another reason to use your own eyes and judgement). You 're looking at exceptions, not the rule. As I said earlier, it would benefit you greatly to look at "normal" cases before looking at abnormal ones.

Not sure what this bit means though -->

(order=0, mode=1, edeint=nnedi3(field=2)

I've seen nnedi somewhere before - isn't that DeHalo Alpha or Anti-Aliasing or something? (sorry, I've been giving myself a small brain haemorrhage for the last few weeks, reading about things I never knew existed - so finding it difficult to remember everything!) Mode is part of the SRestore - right? Can you explain how you derived (order=0, mode=1, edeint=nnedi3(field=2)?

It's in the instructions for yadifmod and nnedi3. I know, I know, the instructions are hard to read and can be confusion, but you should try it...

Yadif is deinterlacer. Yadifmod allows interpolation based on other functions, in this case I chose NNEDI3. For yadif, mode determines single or double rate. mode=0 single, mode=1 double. Order is field order 0=bff, 1=tff

For NNEDI3 taken directly from the instructions

field -

Controls the mode of operation (double vs same rate) and which field is kept.
Possible settings:

-2 = double rate (alternates each frame), uses avisynth's internal parity value to start
-1 = same rate, uses avisynth's internal parity value
0 = same rate, keep bottom field
1 = same rate, keep top field
2 = double rate (alternates each frame), starts with bottom
3 = double rate (alternates each frame), starts with top

as you can see, field=2 is double rate, and bff

BTW you have to uncomment the "#" if you are copy / pasting. "#" means that line doesn't work.

I don't fully understand this sorry? I know you mean that if there's an '#' listing such as: #bobber or #yadifmod(order=0, mode=1, edeint=nnedi3(field=2)) that I'd have to remove them if I'm copy/pasting, because they won't work - but why won't they work, or why are they included initially? Sorry if that sounds stupid - it's just hard to follow everything when I don't know the context you mean it in.

"#" disables a line. It turns it "off". They are meant for "remarks" or comments

If I use #sharpen(1.0) this will do nothing because the line is disabled

If I use sharpen(1.0) this will sharpen

Another gui you might check out is lord mulder's simple x264 launcher. It's very minimalistic.

Thanks. But you know the way when you said that you just use Avisynth and x264 (way back in an early post) are you just encoding to an avi container via VDub all the time, or if you're using an mp4/mkv container - what are you using to achieve that? Do you still use MeGUI for that purpose?

No I typically use x264.exe (no GUI). I don't really use MeGUI any more. x264.exe can output to different formats

[The.King]

Well that just SUCKS completely! I've just spent about an hour readings through everything, making notes, comments etc. in a draft reply and asI was finishing off the post and about to send it - the whole lot of text just disappeared???

[The.King]

OK, so I'm not re-typing out everything I lost earlier - I'd be here all year.

I've run a new encode using yadifmod etc., here's the avisynth script...

 
Current Avisynth script:
-------------------------------------------------------
SetMemoryMax(768)
SetMTMode(5,8)
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\LoadDll.dll")
LoadDll("C:\Program Files\Hybrid\avisynthPlugins\libfftw3f-3.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\RepairSSE2.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\warpsharp.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\Average.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\RemoveGrainSSE2.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\mt_masktools-26.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\TIVTC.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\ffms2.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\yadifmod.dll")
LoadPlugin("C:\Program Files\Hybrid\avisynthPlugins\nnedi3.dll")
Import("C:/Program Files/Hybrid\avisynthPlugins\Srestore.avsi")
Import("C:/Program Files/Hybrid\avisynthPlugins\LimitedSharpenFaster.avs")
Import("C:/Program Files/Hybrid\avisynthPlugins\Dehalo_alpha_mt.avsi")
FFVideoSource("C:\Users\Desktop\xxxx~2.xxx\02x01\VTS_01~2.MKV",cachefile="C:\Users\Desktop\Hybrid\TEMP\80475142mkv_deb1536f480475f7d593219aa1afd74c_41.ffindex",fpsnum=29970,fpsden=1000,threads=1)
SetMTMode(2)
ConvertToYv12(interlaced=true, matrix="PC.709")
Yadifmod(mode=1,order=0,edeint=nnedi3(field=2))
srestore(frate=25,omode=6,speed=9,mode=2,thresh=16,cache=-1)
Crop(0,0,718,480)
Spline16Resize(704,576)
ConvertToYv12(interlaced=false, matrix="PC.709")
LimitedSharpenFaster(ss_x=1.5,ss_y=1.5,Smode=3,strength=100,Lmode=1,wide=false,overshoot=1,undershoot=1,soft=0,edgemode=0)
DeHalo_alpha_mt(rx=2,ry=2,darkstr=1,brightstr=1,highsens=50,lowsens=50,ss=1.5)
distributor()
return(last)
 
OK   
---------------------------

And below is a small sample of what that returned - which as you can see is as bad as QTGMC....

Any ideas?

[poisondeathray]

OK, so I'm not re-typing out everything I lost earlier - I'd be here all year.

Yeah, been there, done that - I've been burned too many times.... If I have to type out a long answer I sometimes type it out in a text file (notepad) first.

And below is a small sample of what that returned - which as you can see is as bad as QTGMC....

Any ideas?

It might be problems running MT; I'll look into it a bit closer .

I thought I uploaded the yadifmod example (for the other video), but it didn't get attached. It works fine for that sample. QTGMC does too (just blurrier for the reasons mentioned earlier)


Can you upload a longer sample of the source, or at least a matching one that caused you to have problems

[The.King]

Can you upload a longer sample of the source, or at least a matching one that caused you to have problems

Yeah no problem, attached is a two minute sample. If you a need longer sample, a different sample from another episode, or you'd like the whole episode, just PM me an email address and I'll share it on Google Drive. Selur had a look at it too, seems like the source is well messed up - probably has some field changes and may be some progressive interlaced mixes?

It's driving me nuts. As I mentioned to Selur, it's like QTGMC bob() frate=25 and correct field order has not been applied even though it has.

[The.King]

It would help if I attached the file.... - it was over 100mb didn't stick. Demuxing another - give me two mins...

[Selur]

btw. if the fluidity of the movement is concerned, simply keeping the content interlaced is also an option,..

[poisondeathray]

I think there is a 100MB limit here. It doesn't need to be large - just small enough that you can replicate the issue with

Selur had a look at it too, seems like the source is well messed up - probably has some field changes and may be some progressive interlaced mixes?

If that's the case, you might need to do some manual work...

[The.King]

Finally....

[poisondeathray]

btw. if the fluidity of the movement is concerned, simply keeping the content interlaced is also an option,..

If it's a mess, that might be the easier option

[The.King]

If that's the case, you might need to do some manual work...

I was afraid you were going to say that.... My brain is already hurting from learning a microscopic amount of avisynth - manual work will push me right over the edge!

[poisondeathray]

Finally....

Took a quick look and it seems fine .

I think your problems might be using MT, and/or FFVideoSource. Both can cause problems with Srestore or some temporal filters. Also MKV (in your script, you used MKV, maybe re-wrapped?) can be problematic for MPEG2 sources

RANT: This is my personal preference, and I know at least quite a few people share the same views: I don't recommend using FFVideoSource for mpeg2 sources. It indexes the video, like DGIndex, but it is still less consistent in my experience. Either DGIndex or DGNVTools for MPEG2 sources for the most consistent results. MPEG2 in MKV is inconsistent as well. The behaviour just isn't the same. I know people use makemkv and you would think just re-wrapping would cause no problems, right...? Wrong. Very inconsistent results. Sometimes it works, sometimes it doesn't. I haven't debugged it or narrowed it down, it might just be a splitter or decoder issue - but I know many people have had the same experience.

You don't need either ConvertToYV12 lines in that script, they are superfluous

[The.King]

Here's the source encoded and keeping it 'interlaced'