Log in

View Full Version : x264.exe not parsing AviSynth script properly.


Gew
2nd August 2010, 15:20
Hi guys!

Strange, x264 usually handles .avs input well. This time though, it's all messy. This is my script:

loadplugin("temporalcleaner.dll")
a=avisource("clip.09-03-29_11-57.00.avi",fourCC="DVSD",audio=true)
b=avisource("clip.09-04-02_12-24.00.avi",fourCC="DVSD",audio=true)
a+b
trim(200,0)
fadein(100)
fadeout(400)
crop(8,0,-8,0)
AssumeBFF().SeparateFields().SelectEven()
temporalcleaner
tweak(bright=15)
bilinearresize(512,288)


As you may see, very basic stuff. Thing is, my output is 512x576@12.50fps. Really strange parsing of my script. PAL DV clips are 720x576, so it has apparently only downscaled horizontally. Furthermore, my lazy discard-field deinterlacing is totally ignored, as output indeed becomes interlaced :/ Just downloaded most recent x264.exe build from 264.nl site, and same issue there. Am I doing something wrong?

Chikuzen
2nd August 2010, 15:32
loadplugin("temporalcleaner.dll")
a=avisource("clip.09-03-29_11-57.00.avi",fourCC="DVSD",audio=true)
b=avisource("clip.09-04-02_12-24.00.avi",fourCC="DVSD",audio=true)
a+b
trim(200,0)
fadein(100)
fadeout(400)
crop(8,0,-8,0)
AssumeBFF().SeparateFields().SelectEven().AssumeFrameBased()
temporalcleaner
tweak(bright=15)
bilinearresize(512,288)


If your avs is fieldbase, x264 automatically does weave and encodes interlace.

Gew
2nd August 2010, 15:39
That fixed everything. Thank you Chikuzen! :)

Another funny(?) thing though, not sure if it's a bug in latest mkvmerge, or if it's a natural occurrence after that interlaced x264 encode. Anyways, after I pulled that messy .avs script, and got interlaced x264_output.mkv, I pulled a simple "mkvmerge -o foo.mkv x264_output.mkv an_audio_file.mp3". When I loaded this one in MPC, it was stretched like I-don't-know-what. Now, I run mediainfo.exe on the file, and it reports "Display aspect ratio: 56.889". Performing the same mux with an x264_encode.mkv out of the "fixed" .avs gives a normal AR. Wicked, really.