#6048 closed defect (invalid)
Audacious pops up error when finished playing any m4a file
Reported by: | Lord Vlad | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Audacious pops up an error when finished playing any m4a file:
How to reproduce :
Audacious 3.8.1 (Arch Linux) ffmpeg version N-82953-g33d7f822f8 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 6.2.1 (GCC) 20160830 Play any m4a file in audacious and let it end, a pop up will appear saying : Erreur de lecture de file:///home/XXX/Musique_new/OST/Undertale/Castle-Undertale_No_Mercy_Run.m4a : Erreur de lecture inconnue (consulter la console pour obtenir des informations d'erreur détaillées) (yes, sorry for my french locale, it just says to go to the console anyway) When running audacious in a console the following lines appear in the console : WARNING ffaudio-core.cc:185 [aac]: <0x7fde2c05aac0> Multiple frames in a packet. ERROR ffaudio-core.cc:185 [aac]: <0x7fde2c05aac0> Prediction is not allowed in AAC-LC. ERROR ffaudio-core.cc:214 [log_result]: avcodec_receive_frame failed: Invalid data found when processing input
I was told in audacious bug report sections that this was actually a problem with ffmpeg, so I'm here. If these error messages are unsufficient, please tell me what I should do to get more error messages, or more detailed ones.
Might be a duplicate of #5781 ? IDK
Change History (2)
comment:1 by , 8 years ago
Component: | ffmpeg → undetermined |
---|---|
Resolution: | → needs_more_info |
Status: | new → closed |
comment:2 by , 8 years ago
Resolution: | needs_more_info → invalid |
---|
I get no such messages decoding any M4A file using ffmpeg
. Looks like an issue in Audacious, probably this:
Bug #691: Bogus errors printed at end of .m4a file (due to use-after-free)
If you get such messages from ffmpeg
itself then please test using a build from the current git master branch, provide the input file, and your ffmpeg
command with the complete console output.
Sorry, but this currently has no similarities with a valid ticket. Please feel free to reopen if you can explain why there is a bug in FFmpeg.