> I think I know the answer to this now - it will switch back to control > itself. Yes - otherwise you wouldn't be able to stop the alarm.
> What should be displayed on Player A if Player A is controlling Player B > and: > - an alarm occurs on Player B? An alarm popup will be on Player B You might be able to stop it with player A by pressing pause. Then two things could happen: - alarm window vanishes, audio stops - alarm window doesn't vanish, audio stops - but since the alarm has not properly been canceled, the fallback tune starts. Could you try this out ? If the alarm happens on the other device currently you just can stop it from there. > > I'm still seeing weird effects of the alarm code, even after the fix to > stop the popup issue on server restart. i.e. at restart, it now seems to > be losing the player that it was previously controlling (defaults to > control self). You do have the latest firmware (which does not popup the alarm window on reboot anymore) and still see that on restart the touch switches to control itself ? Could you provide logs from the Touch (on radio they are under /var/log/messages) when you SSH into the Touch ? Then one could see if it really comes from the changes alarm code (or is just default behaviour on restart of the Touch) ? -- bluegaspode 1x SB-Controller+Receiver (Duet), 1xSB-Boom. 1xSB-Radio Server (7.4.1) running on SheevaPlug (Ubuntu) with attached Western Digital MyBook Essential. Secondary 7.4 Server on Debianized Buffalo Linkstation LS-CHL. ------------------------------------------------------------------------ bluegaspode's Profile: http://forums.slimdevices.com/member.php?userid=31651 View this thread: http://forums.slimdevices.com/showthread.php?t=74095 _______________________________________________ Touch mailing list Touch@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/touch
