Do not issue any bug reports against versions earlier than 3.5.4 they will be closed.
Furthermore, we cannot accept bugs about metadata or art handling in 3.5.4 due to the large number of bugs that have been fixed since then. 3.5.4 in general is becoming less supportable, and it is suggested to try to reproduce the bug in the latest nightly.
Before submitting a bug please read http://ampache.org/wiki/support:bugs failure to do so may delay resolution of your report.
Furthermore, we cannot accept bugs about metadata or art handling in 3.5.4 due to the large number of bugs that have been fixed since then. 3.5.4 in general is becoming less supportable, and it is suggested to try to reproduce the bug in the latest nightly.
Before submitting a bug please read http://ampache.org/wiki/support:bugs failure to do so may delay resolution of your report.
FS#162 - Add an API call to select formats supported and auto transcoding
Attached to Project:
Ampache
Opened by Marco Antonio Mauro (marcus905) - Tuesday, 19 April 2011, 02:26 GMT-8
Opened by Marco Antonio Mauro (marcus905) - Tuesday, 19 April 2011, 02:26 GMT-8
|
DetailsI think it would be beneficial to have a way for API clients to tell the server which codecs they can decode through a priority sorted list (and eventually a codec-specific preferred bitrate, encoding scheme and quality setting for each supported codec) so the server can automatically transcode the song an the fly or through the use of a cache before sending it in case it's needed (the song is in a different format or the client wants a specific bitrate/quality settings because it's in a bandwidth constrained environment).
Conversely there should be a way for the server to advertise which codecs are supported for transcoding on the moment the client requests the song list so that the client could be able to mark/hide the songs it cannot decode and/or ask the user which format they want for a specific song. This would be useful because many clients (iAmpache, Lullaby and Amdroid, but these are just the ones I personally tested) support just some codecs (namely mp3 and m4a for iAmpache and mp3, ogg and m4a for Lullaby/Amdroid) This would also require a multiformat transcoding subsystem, maybe using ffmpeg, sox or gstreamer as the backend. |
This task depends upon