PDA

View Full Version : MeGUI (0.3.5.0) Aspect Ratio problem


son_t
2nd July 2010, 09:50
I'm using this guide to convert an HD recording to MKV, and have come unstuck at the second step.

I'm converting a recording in 16:9 aspect ratio using MeGUI, but the output video's aspect ratio is not correct.

Input is like this:
http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui1.jpg

Output is like this:
http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui2.jpg

This is the video extraction using MeGUI, and it shows the video as having the correct aspect ratio:
http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui0.jpg

But after extraction, the resulting video is loaded into Avisynth script creator, it picks up a 4:3 aspect ratio:
http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui3.jpg

Anyone know how I can fix the aspect ratio for the output video? (Selecting some or all of the option in Avisynth, like the Resize 1440x1080, does not seem to work!)

7ekno
2nd July 2010, 10:44
Why not just change the "Input DAR" box to 16:9?

Tek

son_t
2nd July 2010, 11:00
I've tried that too, still no effect on the output video aspect ratio... :(

(The aspect ratio seem to get lost when using HD Stream Extractor... I'm going to see if I can find another extractor...)

son_t
2nd July 2010, 12:20
Sorted it out now - using MeGUI... I thought I had tried ALL combinations of options but it seems I haven't, as this one works:

http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui4.jpg

Input DAR: ITU 16:9 PAL and Clever (TM) anamorphic encoding

Producing this:
http://i442.photobucket.com/albums/qq149/son_tpics/HDR/HD%20recordings/megui5.jpg

Thanks for reading! :)

P.S. The 18Mb H264 to MKV clip is available here: http://www.megaupload.com/?d=ABX3KD26

Lyle_JP
7th July 2010, 07:12
I too am getting weird problems with aspect ratio. I have one avs file that I didn't even write inside MeGui (so no "clever" boxes were checked), but every output file is 720 pixels high, no matter what it's been resized to in avs. In fact, the video will even open with the correct height and aspect ratio in the preview window, but every ENCODING is still whacked out, with Megui sending the height of 720 to x264 no matter what I do.

Sharktooth
7th July 2010, 13:07
that impossible... play your AVS in your favourite DirectShow media player and check it has correct resolution.
if it's ok, then check your megui encoder preset and make sure there is no resolution set somehow in the custom commandline options.

Lyle_JP
7th July 2010, 21:24
that impossible... play your AVS in your favourite DirectShow media player and check it has correct resolution.
if it's ok, then check your megui encoder preset and make sure there is no resolution set somehow in the custom commandline options.

It's not impossible, but I've managed to consistently replicate the problem, and it looks like MeGUI is off the hook for this one. If anything, it seems to be a bug with x264's direct AVS interface.

Basically, this is what happens. If I try to de-interlace and resize 1080i film-based material this way:
tfm(order=1).tdecimate()
Spline64Resize(640,360) # Spline64 (Sharp)
...then everything is fine. But if I do it this way:
SeparateFields().SelectEven().tdecimate()
Spline64Resize(640,360) # Spline64 (Sharp)
...then MeGUI still opens it fine. The preview window shows me a properly resized image, and the timecode indicates that MeGUI interprets the framerate as 23.976, as it should. But, x264 always creates a file at double the height (720 lines in this case) and half the framerate (11.988). The framerate problem I can fix in the muxer. The size problem, not so much.

For the record, I'm using build 1666 of x264 (x64) and JoshyD's 64-bit version of SEt's MT-Avisynth 2.5.8.

Sharktooth
8th July 2010, 03:15
if megui opens the AVS correctly in the preview, the problem should be elsewhere.
copy the preset settings to the x264 commandline and encode the avs directly using x264 via commandline and see the result.
if it's still altered then there's a problem with avs input in x264.