Kinsky: Two Bugs in SetAVTransportURI function

[andrewfg]

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...

[stevens Linn Staff]

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

[andrewfg]

(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.

[stevens Linn Staff]

Hi Andrew,

thanks for the feedback - this is now fixed

Regards,
Steven