Vorbis encoding is broken #37198

New Issue

Shinsuke Irie · 2013-10-24T07:40:05+02:00

Shinsuke Irie commented

2013-10-24 07:40:05 +02:00

%%%--- Operating System, Graphics card ---

Ubuntu 13.10 amd64 + GeForce GTX670

- Blender version with error, and version that worked ---

2.69 RC3 (official build)
r60907 (own build)

- Short description of error ---

The vorbis encoding seems broken.
Audio track in .ogg file (theora+vorbis) made by Blender cannot be played properly with a media player.
I confirmed that both 2.69RC3 and own build cause the problem.

2.69RC3:

Encoding ... no error
Playing ... some media player such as VLC and Totem causes frequent sound jumpiness

own build (r60907):

Encoding ... "Error writing audio packet!" in console
Playing ... error for lack of audio data happens, no sound at all

I'm not sure if this is Blender's bug, but at least I can make proper .ogg files by using command line avconv tool.
%%%

%%%--- Operating System, Graphics card --- Ubuntu 13.10 amd64 + GeForce GTX670 - Blender version with error, and version that worked --- 2.69 RC3 (official build) r60907 (own build) - Short description of error --- The vorbis encoding seems broken. Audio track in .ogg file (theora+vorbis) made by Blender cannot be played properly with a media player. I confirmed that both 2.69RC3 and own build cause the problem. 2.69RC3: - Encoding ... no error - Playing ... some media player such as VLC and Totem causes frequent sound jumpiness own build (r60907): - Encoding ... "Error writing audio packet!" in console - Playing ... error for lack of audio data happens, no sound at all I'm not sure if this is Blender's bug, but at least I can make proper .ogg files by using command line avconv tool. %%%

Shinsuke Irie commented

2013-10-24 07:40:05 +02:00

Changed status to: 'Open'

Sergey Sharybin commented

2013-10-28 13:51:13 +01:00

%%%Errors which you see with own builds might be caused by you using newer FFmpeg where API might have been changed.

As for official builds -- it happens with previous release as well, and could be caused by totem using gstreamer instead of FFmpeg. Both blender and ffplay are playing the file nicely.%%%

%%%Errors which you see with own builds might be caused by you using newer FFmpeg where API might have been changed. As for official builds -- it happens with previous release as well, and could be caused by totem using gstreamer instead of FFmpeg. Both blender and ffplay are playing the file nicely.%%%

Sergey Sharybin commented

2013-10-28 18:31:09 +01:00

%%%Actually, will look into this eventually.%%%

Shinsuke Irie commented

2013-10-28 19:15:18 +01:00

%%%MPlayer shows the following message in console:

Too many audio packets in the buffer: (4096 in 1082704 bytes).
Maybe you are playing a non-interleaved stream/file or the codec failed?
For AVI files, try to force non-interleaved mode with the -ni option.

In MPlayer, audio track can be played with proper speed, but video track gets strange speed instead.
Note that the MPlayer uses FFmpeg/Libav for Vorbis playback.
%%%

%%%MPlayer shows the following message in console: Too many audio packets in the buffer: (4096 in 1082704 bytes). Maybe you are playing a non-interleaved stream/file or the codec failed? For AVI files, try to force non-interleaved mode with the -ni option. In MPlayer, audio track can be played with proper speed, but video track gets strange speed instead. Note that the MPlayer uses FFmpeg/Libav for Vorbis playback. %%%

Sergey Sharybin commented

2013-11-26 10:33:34 +01:00

Added subscriber: @schlaile

Sergey Sharybin commented

2013-11-26 10:33:34 +01:00

@IRIEShinsuke, glanced in the issue right now. It might be related on non-monotonic PTS for the frames. At least because of this non-monotonic thing FFmpeg-2.0.2 doesn't work.

Will look further later today (need to go for some uni stuff now). Or will ask @schlaile to help me.

@IRIEShinsuke, glanced in the issue right now. It might be related on non-monotonic PTS for the frames. At least because of this non-monotonic thing FFmpeg-2.0.2 doesn't work. Will look further later today (need to go for some uni stuff now). Or will ask @schlaile to help me.

Shinsuke Irie commented

2014-01-19 08:13:27 +01:00

Any update on this?

Anyway, why are we using ancient FFmpeg still? The official builds use v1.0 on Linux and v0.10 on Windows, though the upstream release has already moved to v2.1 branch. Such old libraries have many bugs (including security vulnerabilities), so they should be updated as soon as possible.

Any update on this? Anyway, why are we using ancient FFmpeg still? The official builds use v1.0 on Linux and v0.10 on Windows, though the upstream release has already moved to v2.1 branch. Such old libraries have many bugs (including security vulnerabilities), so they should be updated as soon as possible.

Sergey Sharybin commented

2014-01-19 14:56:39 +01:00

No update yet. It is in my list of review for the next week.