Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattkhan]

I was just playing with MCC, specifically I was sending

MC23.exe /MCC 10020,55:3

to an MC with the following zones

Code: [Select]

<Response Status="OK">
<Item Name="NumberZones">3</Item>
<Item Name="CurrentZoneID">10002</Item>
<Item Name="CurrentZoneIndex">0</Item>
<Item Name="ZoneName0">Music</Item>
<Item Name="ZoneID0">10002</Item>
<Item Name="ZoneGUID0">{1C69970D-1669-4A35-8489-D72807265126}</Item>
<Item Name="ZoneDLNA0">0</Item>
<Item Name="ZoneName1">Films</Item>
<Item Name="ZoneID1">10009</Item>
<Item Name="ZoneGUID1">{7EE0DF13-E080-46A1-9F38-8BE1FD9F36DB}</Item>
<Item Name="ZoneDLNA1">0</Item>
<Item Name="ZoneName2">Tivo & Netflix</Item>
<Item Name="ZoneID2">10015</Item>
<Item Name="ZoneGUID2">{C65DCE15-B142-478C-B2A2-3B6F775F6BCA}</Item>
<Item Name="ZoneDLNA2">0</Item>
</Response>

I then realised that

a) the zone index is 0 based
b) I was actually listening to zone 0 not zone 2

Anyway, leaving user error to one side, sending the aforementioned command in this situation has the effect of sending volume to 100% in zone 0. Suffice to say this had me jumping out of my seat.

Is this a bug or is there some magic meaning to a zone index of 3 in this situation that I'm missing?

[Hendrik]

As far as I can tell, if an invalid zone is specified the command is probably being processed as if no zone was specified, however the encoding of the zone value "mangles" the actual value, so its no longer 55 but some huge value. At least it should probably not mangle the value in that case.