Encoding a Theora video at 320x200 results in a video length discrepency.

Bug #900981 reported by Chris
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ffmpeg2theora
New
Undecided
Unassigned

Bug Description

I have encoded a Theora video at 320x200 resolution using FFCoder with ffmpeg2theora. The video file is for a cut-scene movie in a PC/Android game.

The game engine uses the APEG Theora player. And I have the game set up so that there is a separate audio (ogg) track playing independently of the Theora video stream. They play in synchronization during playback.

But whenever I play back the Theora video in the game, the video gradually starts edging ahead of the audio track, and the two do not remain in-sync The video stream plays faster and reaches the end well before the audio track does. I have re-encoded the Theora video numerous times at 320x200 with various settings but it always gives the same result.

When I played back the affected Theora video in windows, using VideoLan's VLC Media Player, I noticed that the length of the video was all messed up. It was something like 07:48/06:13 when the progress slider was moved to the very end of the bar.

The 320x200 Theora file seems to think that it is only 6 minutes and 13 seconds in length, when it actually runs for 7 minutes and 48 seconds. When played back in the game using APEG, it seems that the video stream is being sped-up to play faster, so that it finishes by the 06:48 mark, rather than playing out its full length of 07:48, as it should.

If I encode the Theora video to 320x240 or any higher resolution, the bug does not occur. Incidentally, FFCoder is the only encoder that seems to allow me to encode Theora to 320x200 using ffmpeg2theora. Other programs tend to crash if I try to encode at 320x200 or 320x240.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.