Reply to thread

Message

<blockquote data-quote="Marcus Venturi" data-source="post: 1133844" data-attributes="member: 121570">A few details about the implementation of the UPnP gapless playback.Normally in UPnP the controller - is responsible for controlling how the renderer plays the files.The controller calls the UPnP action &quot;SetAVTransportURI&quot; to tell the renderer which song to play and then starts playback with the &quot;Play&quot; action. The renderer just takes the song from the given URI and plays it.When the song is finished the controller calls the action &quot;SetAVTransportURI&quot; again and starts playback again with the &quot;Play&quot; action.This concept makes gapless playback impossible.But there is also an UPnP action called &quot;SetNextAVTransportURI&quot;.This tells the renderer which song to play after the current song has ended.In this case the renderer is responsible for playing the next song and not the controller.Now the client has only to call the action &quot;SetAVTransportURI&quot; for the first song and then the action &quot;Play&quot;.Before a song ends the client calls the action &quot;SetNextAVTransportURI&quot; to keep the renderer playing.This allows the renderer to play gapless (if he is capable) between the current and the next song, that's all the magic.And this is the reason why most controller / renderer combinations are not able to play music gapless, because either the controller or the renderer does not implement the &quot;SetNextAVTransportURI&quot; action.My ANDROID client checks if the renderer supports the &quot;SetNextAVTransportURI&quot; action. If yes, it is used to allow gapless playback.</blockquote>

[QUOTE="Marcus Venturi, post: 1133844, member: 121570"] A few details about the implementation of the UPnP gapless playback. Normally in UPnP the controller - is responsible for controlling how the renderer plays the files. The controller calls the UPnP action "SetAVTransportURI" to tell the renderer which song to play and then starts playback with the "Play" action. The renderer just takes the song from the given URI and plays it. When the song is finished the controller calls the action "SetAVTransportURI" again and starts playback again with the "Play" action. This concept makes gapless playback impossible. But there is also an UPnP action called "SetNextAVTransportURI". This tells the renderer which song to play after the current song has ended. In this case the renderer is responsible for playing the next song and not the controller. Now the client has only to call the action "SetAVTransportURI" for the first song and then the action "Play". Before a song ends the client calls the action "SetNextAVTransportURI" to keep the renderer playing. This allows the renderer to play gapless (if he is capable) between the current and the next song, that's all the magic. And this is the reason why most controller / renderer combinations are not able to play music gapless, because either the controller or the renderer does not implement the "SetNextAVTransportURI" action. My ANDROID client checks if the renderer supports the "SetNextAVTransportURI" action. If yes, it is used to allow gapless playback. [/QUOTE]

Verification