I have a problem with the dimension of a movie it's SAR meant to be 1.85:1 but when I open it in AvsPmod I find it stretched
the question here : How can I resize the picture here without inserting any resize filter? I tried to put the proper SAR in MeGUI command line box, but I got the same result, Thanks in advance.
+ Reply to Thread
Results 1 to 17 of 17
I don't use MeGUI so someone else can help with the question you have. I'm commenting on your very peculiar script. Is there any reason you have that sequence of filters? After the TFM/TDecimate there shouldn't be any need for either QTGMC or ChangeFPS. I'm curious as to the reasons you're using them.
Well, if you really want to QTGMC telecined material that's probably the way to go about it.
And I'm pretty sure it's the DAR that's supposed to be 1.85:1 not the SAR or the PAR. I don't really know what you're saying and since I don't use MeGUI or know what AVSPMod even is, I can't be much help. If you don't want to resize then the base image will never be 1.85:1 and if the AVS in AVSPMod means what I think it does, it won't care about the DAR anyway.
What's the frame rate of the original video? Maybe I'm missing something, but I've use QTGMC after the video is de-telecined, however I'd be thinking you'd normally need to run it in progressive mode if you do. At least that's what I do:
The script in the OP seems like it'd produce an "odd" kind of output to me.
As far as MeGUI goes, there's no need to input the SAR manually (leave it set to "default' in the x264 encoder configuration). Enable anamorphic encoding when creating a script and MeGUI will add the appropriate DAR to the top, which it'll later use for setting the SAR when encoding. As an example:
Selecting the "encode non mod16" anamorphic encoding method will disable resizing. It doesn't mean the video will be non-mod16, just that it can be if the source is non-mod16.
Add the encoding job to the queue after saving the script and MeGUI will take care of the SAR.
MeGUI also has an aspect error setting hidden away in it's AVISynth Profile configuration. It only applies to MeGUI's anamorphic encoding and how much it's allowed to "fudge" the aspect ratio. It's set to 1% by default.
Of course if the original video consists of square pixels there's no need for anamorphic encoding. Just don't enable resizing if you don't want to resize. The output will have the same resolution and 1:1 pixel aspect ratio.
Last edited by hello_hello; 2nd Jun 2014 at 02:10. Reason: spelling
Many Thanks for this, bro "hello_hello" a very good tutorial from you, you're genius
Is there any difference between running QTGMC in progressive mode and simply converting to YUY2 beforehand?
I regularly use QTGMC in progressive mode for progressive video. It's good at stabilising the picture (ie old wobbly Xvid encodes) and makes a pretty good noise removal filter.
In the example script from the first post, I assumed the video would be 29.970fps with pulldown, so "TFM().TDecimate()" line would take it back to 23.976fps progressive, and then QTGMC could be run in progressive mode to "clean up" the video if need be. I've run it that way on the odd occasion when the source video hasn't been very good quality. If that's not what's happening, I'm not sure what TeNSoR is trying to do.
Mostly, I use QTGMC as a noise filter/picture stabiliser something like this (with a faster preset for HD):
QTGMC(InputType=1, Preset="slow", EzDenoise=2)
Some sample encodes from back when I first started playing around with using QTGMC in progressive mode.
Personally I don't use anamorphic encoding myself. I resize everything to square pixel dimensions instead. There's pros and cons for both methods. For me, the major anamorphic "con" is not all hardware players support anamorphic video correctly, so the encoded video will still look stretched or squished even if the correct SAR is used when encoding. If that's not an issue for you then anamorphic encoding is fine. Persoanlly if I'm re-encoding anyway, I just resize to square pixels while I'm at it (anamorphic encoding unchecked). MeGUI will calculate the aspect ratio error for you so you can resize as accurately as possible.
To resize "freely" you might want to enable the ability to resize "up". I think having it disabled by default is silly, but you can enable it in the Avisynth profile configuration (pic 3, post #6).
Sorry, another question, What's the best filter to remove these dirt and lines here:
Last edited by TeNSoR; 2nd Jun 2014 at 03:47. Reason: Screen
AviSynth unblender such as SRestore. But to be sure we'll need a sample, 10 seconds with steady movement.
Those vertical lines will me much harder to remove and I've never seen a good way to treat those.
As is common for Ultra and most of the Indian DVD companies, it's field-blended from a PAL source. This does a decent job of removing most of the blends and restoring it to its original 25fps:
Yadif(Mode=1)#or your favorite bobber
I have no idea how to get rid of the scratches, since many don't move much.