BubbleUPnP and Pause/Next track

[bubbleguuum]

(27-09-2013 10:31)simoncn Wrote:  

(27-09-2013 09:55)bubbleguuum Wrote:  You can't. It is provided (or not) by the media server.
Although I may systematically add it to avoid recurrent "can't seek and/or can't pause" support questions with some renderers.

Could this metadata be added by BubbleUPnP Server's renderer proxy, so that a noncompliant renderer could be "wrapped" by a compliant renderer proxy?

You mean media server proxies ? Yes it can be added and I probably will add these 2 DLNA fields (if they are not already set by the media server), as it should not have any side effect (ignored by non DLNA renderers). At best it will add seek/pause ability to some renderers where it would have previously failed and at worse it may still fail because the underlying media server may not support it (range requests for seeking).

For the same reason I think you could add them to minimserver for all items whether DLNA media types or not (do not set DLNA.ORG_OP=01 for media types not supporting seeking, if any)

And it is super likely, that I will add these flags too in Android BubbleUPnP, at SetAVTransportURI() time.