![]() |
|
Kinsky: Two Bugs in SetAVTransportURI function - Printable Version +- Linn Forums (http://forums.linn.co.uk/bb) +-- Forum: Linn (/forumdisplay.php?fid=1) +--- Forum: Development (/forumdisplay.php?fid=5) +--- Thread: Kinsky: Two Bugs in SetAVTransportURI function (/showthread.php?tid=16190) |
Kinsky: Two Bugs in SetAVTransportURI function - andrewfg - 2012-03-25 16:00 There are bugs in the "bitrate" and "size" parameters that you pass in res elements in the UPnP SetAVTransportURI function. Following is an example of what you wrongly send: <res size="0" duration="00:03:36" bitrate="128" sampleFrequency="44100" nrAudioChannels="2" protocolInfo="http-get:*:audio/mpeg:*">http://xyz.mp3</res> 1) The bitrate="128" is wrong. Your are wrongly interpreting bitrate to mean kilo-bits-per-second. According to the UPnP specification bitrate is defined as bytes-per-second. So in the case of the 128 kilo-bits-per-second mp3 file, the value of bitrate must be 16000 bytes-per-second. 2) Also the size="0" parameter is also clearly wrong; it should show the file size in bytes... RE: Kinsky: Two Bugs in SetAVTransportURI function - stevens - 2012-03-26 10:14 Hi Andrew Can you elaborate on what type of media you are trying to play here? Kinsky gets the metadata that it sends to the renderer from a variety of sources, for example, a UPnP media server, the iTunes plugin or simple drag and drop from a folder to name a few. Can you specify exactly what you are doing in Kinsky that causes it to send this data? Regards, Steven RE: Kinsky: Two Bugs in SetAVTransportURI function - andrewfg - 2012-03-27 17:46 (2012-03-26 10:14)stevens Wrote: Can you elaborate on what type of media you are trying to play here? Kinsky gets the metadata that it sends to the renderer from a variety of sources, for example, a UPnP media server, the iTunes plugin or simple drag and drop from a folder to name a few. It came from a regular mp3 music track on the local Windows file systsem. RE: Kinsky: Two Bugs in SetAVTransportURI function - stevens - 2012-03-28 11:16 Hi Andrew, thanks for the feedback - this is now fixed Regards, Steven |