vpxenc does not utilize aspect ratio information from yuv4mpeg format input

[GoogleCodeExporter]

What is the expected behavior? What do you see instead?

The resulting webm file should have the same aspect ratio as the input file.

The resulting webm file did *not* have the same aspect ratio as the input file; 
the output file had square pixels.

What version are you using? On what operating system?

v0.9.5-26-g5551ef0, on Fedora 13, 64bit

Can you reproduce using the ivfdec or ivfenc tools? What command line are
you using?

The issue occurred with vpxenc.  The command line was:

vpxenc --output=patent-absurdity-libvpx-1024k-k250.webm --good --verbose 
--end-usage=0 --target-bitrate=1024 --min-q=0 --max-q=63 --kf-min-dist=0 
--kf-max-dist=250 patent-absurdity-420.y4m

Please provide any additional information below.

The input file was:
http://media.basilgohar.com/patent-absurdity/patent-absurdity-420.y4m

The output file was:
http://media.basilgohar.com/patent-absurdity/patent-absurdity-libvpx-1024k-k250.
webm

I'll try to leave those files up at least as long as this issue remains open, 
but no guarantees.  You don't need the whole source file anyway, you literally 
just need the first line, as that is the header.

Original issue reported on code.google.com by basilgo...@gmail.com on 8 Nov 2010 at 2:35

[GoogleCodeExporter]

Original comment by iss...@webmproject.org on 16 Mar 2011 at 2:51

[GoogleCodeExporter]

Does patent-absurdity_288p_fade-in_fade-out.y4m have an aspect ratio? Or do you 
have have another example?

Original comment by johannkoenig@google.com on 27 Sep 2011 at 11:40

[GoogleCodeExporter]

Yeah, the original file is not there anymore. ;)  That file you're looking at 
isn't the same one.  Also, I don't think it has the same aspect ratio as the 
original file when I reported this bug originally.  I'll follow-up with another 
example if I find it behaves the same way still.

Original comment by basilgo...@gmail.com on 28 Sep 2011 at 1:31

[GoogleCodeExporter]

Okay, I have some new examples:

http://media.basilgohar.com/patent-absurdity/patent-absurdity_10-seconds_1080p_w
eird-aspect.y4m

and 

http://media.basilgohar.com/patent-absurdity/patent-absurdity_10-seconds_1080p_w
eird-aspect.y4m.webm

The sample aspect ratio of the y4m file is 3:2, while having a resolution of 
1280x1080 (yes, it's weird, that's how the final version was released).  This 
would yield a 16:9 video when played-back.

However, vpxenc is not honoring the sample aspect information in the header of 
the y4m file, and it's (seemingly) just assuming square pixels when it writes 
the header for the WebM file.

Original comment by basilgo...@gmail.com on 28 Sep 2011 at 2:00

[GoogleCodeExporter]

Do you know of a way to make this work? I've tried adding an aspect ratio and 
display dimensions to the file, but it doesn't seem to be helping:

Assuming a display dimension of 1620x1080, based on 1024x1080@3/2

mkvpropedit patent.webm -e track:v1 -a display-width=1620 (crashes, even with 
latest git)
mkvmerge --display-dimensions 1:1620x1080
mkvmerge --aspect-ratio 1:3/2
mkvmerge --aspect-ratio 1:16/9 

Original comment by johannkoenig@google.com on 28 Sep 2011 at 7:58

[GoogleCodeExporter]

Well, firstly, the resolution of the original video is 1280x1080, so I don't 
know if that's causing the crash.  Other than that, I'm really not that 
familiar with the Matroska container, but I am sure that it must support 
non-square sample aspect ratios.  I'll try to play around with it a bit and see 
if I can find out how to make it work.

Original comment by basilgo...@gmail.com on 28 Sep 2011 at 10:18

[GoogleCodeExporter]

Original comment by albe...@google.com on 2 Feb 2012 at 7:06

• Changed state: Available

[GoogleCodeExporter]

Original comment by albe...@google.com on 7 Mar 2012 at 11:32

• Changed state: Unconfirmed

[GoogleCodeExporter]

Original comment by albe...@google.com on 8 Mar 2012 at 12:08

• Added labels: Pri-2, Type-Bug
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by albe...@google.com on 15 Mar 2012 at 6:08

• Changed state: Available

[GoogleCodeExporter]

Please reopen if this is still an issue.

Original comment by johannkoenig@google.com on 6 Nov 2014 at 1:37

• Changed state: WontFix