summaryrefslogtreecommitdiff
path: root/contrib/eventcmd-examples/multi.sh
diff options
context:
space:
mode:
authorLars-Dominik Braun <lars@6xq.net>2014-03-31 17:35:28 +0200
committerLars-Dominik Braun <lars@6xq.net>2014-03-31 20:20:22 +0200
commitc872f00508ce4afe3b8ec863b23595c31fd8b4be (patch)
treec441d537a5ead0d659bb05e83e8b4bd7d4066f87 /contrib/eventcmd-examples/multi.sh
parent8e685c992516834e35bcccea1f61c39a9d847e2f (diff)
downloadpianobar-windows-c872f00508ce4afe3b8ec863b23595c31fd8b4be.tar.gz
pianobar-windows-c872f00508ce4afe3b8ec863b23595c31fd8b4be.tar.bz2
pianobar-windows-c872f00508ce4afe3b8ec863b23595c31fd8b4be.zip
Use libav/ffmpeg for audio decoding
libav 9.12 and ffmpeg 2.2 have been tested. Here’s why: My mp4 “parser” *cough* never was a mp4 parser in the sense that it actually understood the file format. Instead it grepped the input stream for “magic” strings (section identifiers). That alone should be sufficient to throw away the code and rewrite it. Additionally libfaad2 has not been updated for ages. I guess it was abandoned in favor of libav/ffmpeg. With libav/ffmpeg, which we support both as long as the API’s don’t diverge too much, pianobar gains fast and reliable AAC and MP3 decoding without bothering too much about the details. Most users will have it installed already. On my own machine libav consumes about 2/3 CPU time compared to the previous solution when playing AAC. Unfortunately memory usage doubled and my attempts to disable unused protocols/formats/codec failed due to libav’s API limitations. While cleaning up a small detail regarding the eventcmd API has changed too: Song duration and position are measured in seconds instead of milliseconds now. Since libav/ffmpeg keeps track of accurate timing the precision pianobar keeps track of can be reduced, while still being sufficient for most users.
Diffstat (limited to 'contrib/eventcmd-examples/multi.sh')
0 files changed, 0 insertions, 0 deletions