Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

integer vs float values in Video/PixelAspectRatio #570

Open
ghost opened this issue Apr 20, 2017 · 4 comments
Open

integer vs float values in Video/PixelAspectRatio #570

ghost opened this issue Apr 20, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented Apr 20, 2017

Hello,

I use a rule where it should be ensured that the Video/PixelAspectRatio is 1. It is defined as value "1.000" because there are other rules within other contexts using values like "1.067". Anyway. In a test video I got a failure because mediaconch reports an integer value of "1" and the rule will fail with "1.000". See attached screenshot.

I am using mediaconch 17.03.

videoascpectratio_mismatch

@JeromeMartinez
Copy link
Member

It is a bug with some files e.g. with containers not having pixel aspect ratio metadata, because one of the raw stream parser (used in case the container has no pixel aspect ratio) was not setting correctly the corresponding field.
Fix on the way.

@JeromeMartinez
Copy link
Member

In next snapshot tomorrow and next official release.

@JeromeMartinez
Copy link
Member

BTW @art1pirat which OS and version are you using. Looks like the default does not have the fail/pass Unicode chars.

@ghost
Copy link
Author

ghost commented Apr 24, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant