Page 1 of 1

wrong framerate interpretation

Posted: Thu Nov 29, 2018 2:19 pm
by bartcuijpers
While working around another issue (viewtopic.php?f=4&t=780), I noticed that QT files with the DNXHD codec (exported from AE) with a framerate of 50p are interpreted as 25p resulting in a encoded file playing in half speed.

A source file to test with:
https://drive.google.com/open?id=11DptO ... eS2fBFfDM1

Thanks!

Re: wrong framerate interpretation

Posted: Sat Dec 01, 2018 11:07 am
by admin
An example to follow: Submit samples right away :-) Great! I will take a look.

-steinar

Re: wrong framerate interpretation

Posted: Sat Dec 01, 2018 11:20 am
by admin
Hi bartcuijpers,

I think you need to submit your workflow. In my tests FFAStrans seem to find the correct fps of 50.

-steinar

Re: wrong framerate interpretation

Posted: Sat Dec 01, 2018 12:29 pm
by bartcuijpers
After some re-testing the problem seems to be different than I thought at first...
The output file isn't playing in half speed, but the duration metadata is incorrect; showing double the duration.
When playing the file in VLC it stops at 6 seconds.

I made a package including the workflow, input- and output files;
https://drive.google.com/open?id=1mUvoz ... r4ISOL-q6v

Thanks for responding!!

Re: wrong framerate interpretation

Posted: Sat Dec 01, 2018 3:56 pm
by admin
I have found the problem and it is indeed a bug. Thanks for reporting. Expect a fix in the next version. In the mean time, I suggest you skip the "A/V Media" decoder. It's not needed in your workflow and it's the one that introduce the issue.

-steinar

Re: wrong framerate interpretation

Posted: Mon Dec 03, 2018 6:06 am
by bartcuijpers
Thanks Steinar!

For my information... when is the AV decoder mandatory?

Bart

Re: wrong framerate interpretation

Posted: Mon Dec 03, 2018 8:30 am
by admin
If you want to apply filters. The "A/V Media" actually creates an AviSynth script and all the filters are avisynth based.

-steinar