Update documentation and build system for libav

We are using libav after the ffmpeg/libav fork during the 0.6 series.
This commit is contained in:
Julien BLACHE
2011-06-02 21:07:53 +02:00
parent ec5ace7dc9
commit d8685846d0
4 changed files with 22 additions and 19 deletions

12
README
View File

@@ -114,11 +114,11 @@ audio device:
Supported formats
-----------------
forked-daapd should support pretty much all media formats. It uses ffmpeg to
extract metadata and decode the files on the fly when the client doesn't
support the format.
forked-daapd should support pretty much all media formats. It relies on libav
(ffmpeg) to extract metadata and decode the files on the fly when the client
doesn't support the format.
However, ffmpeg is not necessarily very good at extracting metadata, so some
However, libav is not necessarily very good at extracting metadata, so some
formats may cause problems. FLAC, Musepack and WMA use custom metadata
extractors to work around that.
@@ -179,8 +179,8 @@ Artwork
forked-daapd has /some/ support for artwork, with a number of limitations.
Embedded artwork is not supported; ffmpeg doesn't support this yet, if and
when this is added to ffmpeg, forked-daapd will support it.
Embedded artwork is not supported; libav (ffmpeg) doesn't support this yet, if
and when this is added to libav, forked-daapd will support it.
Your artwork must be in PNG or JPEG format, dimensions do not matter;
forked-daapd scales down (never up) the artwork on-the-fly to match the