This posting is older than 6 months and can contain outdated information.
Felix,
Thanks for your quick reply. It actually turned out to be my fault
as I found out.
I am using the headphone jack on my laptop to send the audio signal to
my stereo
system (I'm testing Remote Buddy in a home theatre system). Apparently,
when you send audio out via the output jack, you lose all speaker
control via the
keyboard keys.
It wasn't Remote Buddy at all (although it took a while to find
this out). I like Remote
Buddy a lot, but am still getting used to it and have yet to
experiment with things like
writing my own behaviors....
Regards,
Michael Durket
On Nov 4, 2007, at 2:41 AM, Felix wrote:
If you use the mute/unmute action, Remote Buddy does the following:
1) On "Mute", it saves your current system volume and then uses
Apple's AppleScript API to set it to zero.
2) On "Unmute", it sets your current system volume to the value it
previously saves and uses Apple's AppleScript API to set it.
If you quit Remote Buddy after you used the Mute action, the level is
already at zero, so when you start Remote Buddy and then use the Mute
action again, it won't be able to guess what volume you previously
had.
The same applies when you use the mute and unmute key. If the level is
already at zero when you press it, it will stay at zero no matter how
often you press it.
To change system volume, press the volume plus and minus buttons on
your keyboard or use the actions supplied in Remote Buddy for that
purpose. And unless you quit Remote Buddy since you used the mute
action, it will also unmute again if you simply execute the unmute
action again.
Apple does not provide a system-wide Mute/Unmute API, so you'll always
have to mute and unmute volume using the same method.
Best regards,
Felix
[standard mail footer removed]
