Interpreting user commands

[id_missing]

I use UMS to listen my MPD (music payer daemon). MPD is hosting an http stream which I have configured in web.conf. Normally I use an MPD client on some other device, like a laptop of phone, in order to control MPD but sometimes I just want to be able to skip to the next track using the actual play back device (PS3 in this case).

Are there any buttons that the user clicks on their player device which UMS is aware of (besides a request for a new track)?

[SharkHunter]

UMS uses DLNA and the only way to control it to use DLNA. Normally pressing "Next" translates by the render to "Get Track X+1". DLNA do have support for stuff like Next,Play,Pause etc. but UMS doesn't use all of those.

[DeFlanko]

Just out of curiosity sharkhunter, whats preventing us from implementing this ability?

[SharkHunter]

Nothing but there are few renders that use it.
It is the render that controls this. We have implemented it in the upnp branch (sort of).

[infidel]

We have implemented it in the upnp branch (sort of).

"next", "prev", "fwd", "rew" are blocked out but not implemented yet in the upnp-3 branch. I'm putting it together, but in my current scheme "next" and "prev" don't point to xmb items but to an internal playlist of the player widget.

[SharkHunter]

We have implemented it in the upnp branch (sort of).

"next", "prev", "fwd", "rew" are blocked out but not implemented yet in the upnp-3 branch. I'm putting it together, but in my current scheme "next" and "prev" don't point to xmb items but to an internal playlist of the player widget.

Thats how most renders implement it. There is no "next" the simply ask for the next item on the list.