Bug 12533

Summary: Audacious plays AAC faster
Product: Mageia Reporter: Robert Ottlovich <timpul>
Component: RPM PackagesAssignee: Götz Waschk <goetz.waschk>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal Keywords: Triaged
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: audacious CVE:
Status comment:

Description Robert Ottlovich 2014-02-02 19:22:13 CET
Audacious plays the raw aac audio file faster than it should be. Other player such as VLC plays it correctly (ie. 60 secs audio is 60 secs in real). The change is approximately 10% (60 secs audio is played about 54 secs). The problem maybe is in ffaudio.so plugin which is a part of Audacious and connects to ffmpeg.

When this raw aac audio stream is packed into a container such as mp4, Audacious plays it correctly. (This raw aac audio file has no problem with my cheap cell phone as far as the length's concerned.)

This problem has not been corrected since Mageia 3.




Reproducible: 

Steps to Reproduce:
Robert Ottlovich 2014-02-02 19:26:10 CET

Hardware: i586 => x86_64

Manuel Hiebel 2014-02-03 16:41:32 CET

Keywords: (none) => Triaged
Assignee: bugsquad => goetz.waschk
Source RPM: (none) => audacious

Comment 1 Götz Waschk 2014-02-03 19:26:32 CET
I couldn't reproduce this, do you have a sample file?
Comment 2 Robert Ottlovich 2014-02-05 21:28:28 CET
Sure.

AAC is unpacked from Youtube or converted by ffmpeg (ffmpeg -i input.wav -acodec aac -strict -2 output.aac) or created by NeroAAcEnc (Linux binary). Te problem remains the same.

Compressed file contains:
- 30 sec PCM WAV (comes from audio CD)
- an aac file
- an mp4 file
- screenshot
- ffmpeg version in txt

Ffmpeg cli how mp4 was created:
ffmpeg -i mintazene-448kbps.aac -f mp4 -acodec copy -bsf:a aac_adtstoasc mintazene.mp4

dropbox dot com/s/s9l2nr6v4zq24cv/aactestfiles.tar.bz2
Comment 3 Götz Waschk 2014-02-06 13:15:58 CET
The aac file is shown as 28s long while the wav and mp4 file are 30s long. I couldn't hear a difference though and I couldn't measure the elapsed playback time. However, I could measure this using mplayer:

$ time mplayer mintazene-44_1khz.wav
MPlayer SVN-12.r35916.4.mga3.tainted-4.7.2 (C) 2000-2013 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing mintazene-44_1khz.wav.
libavformat version 54.59.106 (external)
Audio only file format detected.
Load subtitles in ./
==========================================================================
Trying to force audio codec driver family libmad...
Opening audio decoder: [pcm] Uncompressed PCM audio decoder
AUDIO: 44100 Hz, 2 ch, s16le, 1411.2 kbit/100.00% (ratio: 176400->176400)
Selected audio codec: [pcm] afm: pcm (Uncompressed PCM)
==========================================================================
AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:  29.8 (29.7) of 30.0 (30.0)  0.2% 


Exiting... (End of file)

real	0m30.120s
user	0m0.156s
sys	0m0.041s
# time mplayer mintazene-448kbps.aac
MPlayer SVN-12.r35916.4.mga3.tainted-4.7.2 (C) 2000-2013 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing mintazene-448kbps.aac.
libavformat version 54.59.106 (external)
libavformat file format detected.
[aac @ 0x7fc0da9d8b40]max_analyze_duration 5000000 reached at 5015510
[aac @ 0x7fc0da9d8b40]Estimating duration from bitrate, this may be inaccurate
[lavf] stream 0: audio (aac), -aid 0
Load subtitles in ./
==========================================================================
Trying to force audio codec driver family libmad...
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
libavcodec version 54.86.100 (external)
AUDIO: 44100 Hz, 2 ch, floatle, 467.5 kbit/16.56% (ratio: 58441->352800)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [pulse] 44100Hz 2ch floatle (4 bytes per sample)
Video: no video
Starting playback...
A:  29.8 (29.7) of 27.2 (27.1)  0.5% 


Exiting... (End of file)

real	0m30.170s
user	0m0.293s
sys	0m0.055s
# time mplayer mintazene.mp4
MPlayer SVN-12.r35916.4.mga3.tainted-4.7.2 (C) 2000-2013 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing mintazene.mp4.
libavformat version 54.59.106 (external)
libavformat file format detected.
[lavf] stream 0: audio (aac), -aid 0, -alang und
Clip info:
 major_brand: isom
 minor_version: 512
 compatible_brands: isomiso2mp41
 encoder: Lavf55.12.100
Load subtitles in ./
==========================================================================
Trying to force audio codec driver family libmad...
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
libavcodec version 54.86.100 (external)
AUDIO: 44100 Hz, 2 ch, floatle, 420.9 kbit/14.91% (ratio: 52608->352800)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [pulse] 44100Hz 2ch floatle (4 bytes per sample)
Video: no video
Starting playback...
A:  29.8 (29.7) of 30.0 (30.0)  0.6% 


Exiting... (End of file)

real	0m30.137s
user	0m0.293s
sys	0m0.048s


As you can see, the aac file is shown as 27.2s long,  but the playback still takes the same 30s.
Comment 4 Robert Ottlovich 2014-02-06 19:27:50 CET
Do you say that the length of the files are the same? In this case why do Audacious and SMplayer notify us wrong value?
Comment 5 Götz Waschk 2014-02-14 14:25:10 CET
I don't know why audacious shows a different time. But I guess it is still playing it at the right speed. Can you confirm?
Comment 6 Samuel Verschelde 2015-09-21 13:18:33 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 7 Marja Van Waes 2015-10-27 06:56:00 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Resolution: (none) => OLD
Status: NEW => RESOLVED