RobbH wrote:
> I do see >
Code:
--------------------
> > "["mixer","muting","toggle"]"
--------------------
> > referenced to the right player's MAC.
Well, that's the correct API call. I've changed the code to be more
explicit, so it will send "mixer muting 0" or "mixer muting 1" instead
of just toggle. But the current call is correct as per the LMS docs.
RobbH wrote:
>
> Each time, that message is followed by "UPDATING" (same MAC), and then >
Code:
--------------------
> > "["status","-",1,"tags:cdegiloqrstyABKNST""
>
--------------------
> >
> The first time (the attempted mute) the next message begins >
Code:
--------------------
> > "{"mode":"play","mixer
volume":10.0190123954748,"remote":1,"player_connected":1,"digital_volume_control":1,"rate":1,"....
--------------------
> >
>
That's Material asking LMS to return the current player status. I ask
immediately after sending the mute command, but I've noticed that LMS
sometimes returns the old volume - or it takes a while for the mute to
occur. So, for the next release, I ask for the status again after a
further 1/2 second.
>From what I can see, Material is functioning correctly. It send the
toggle mute command, how it is handled is up to LMS.
*Material debug:* 1. Launch via http: //SERVER:9000/material/?debug=json
(Use http: //SERVER:9000/material/?debug=json,cometd to also see update
messages, e.g. play queue) 2. Open browser's developer tools 3. Open
console tab in developer tools 4. REQ/RESP messages sent to/from LMS
will be logged here.
------------------------------------------------------------------------
cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686
View this thread: http://forums.slimdevices.com/showthread.php?t=109624
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
