by bubbleguuum » Mon Dec 23, 2013 6:52 am
There's a bug with the UPnP/ DLNA renderer that exist in all versions of MM from the current stable version to the latest beta.
The renderer does not notify volume changes through the RendereringControl service LastChange eventing.
Subscribing to RendereringControl eventing returns the initial LastChange value but with a bogus Volume variable whose value is always 100,
even if the current volume is not 100.
Afterward, LastChange is never evented again (for example if a user manually changes the volume), and the subscribing control point cannot
see volume changes.
It is very easy to observe with a tool like DeviceSpy, subscribing to RendereringControl events.
It would be a good idea to also check if other RenderingControl variables (Mute, ...) are properly evented.
There's a bug with the UPnP/ DLNA renderer that exist in all versions of MM from the current stable version to the latest beta.
The renderer does not notify volume changes through the RendereringControl service LastChange eventing.
Subscribing to RendereringControl eventing returns the initial LastChange value but with a bogus Volume variable whose value is always 100,
even if the current volume is not 100.
Afterward, LastChange is never evented again (for example if a user manually changes the volume), and the subscribing control point cannot
see volume changes.
It is very easy to observe with a tool like DeviceSpy, subscribing to RendereringControl events.
It would be a good idea to also check if other RenderingControl variables (Mute, ...) are properly evented.