Can't mute audio

[farbox]

Thanks for your reply.
IF you read my post carefully, you will see I mentioned that the ACTION (ie what EG is going to do, by using its internal plugin commands) is what is at fault (since when this action is executed on its own regardless of user input, the result is the same). And this bug is not due to anything to do with remote/receiver or the related event (which tells EG to do something).

The "system.togglemute()" that you suggest to delete appears in the log screen (ie left side, ie what EG is seeing/doing, I included it so people can see what EG is doing), therefore not something I've added or I can delete..
I think you are confusing one side of the screen with the other. On right side we tell EG what to do, on left side EG receives the command and tries to do it. If an inbuilt EG ACTION is not working properly, its not the fault of the user right hand side macro programming.
Since other people have experienced the exact same behavior I think this could be an EG bug..
Thanks for your reply anyway!

[farbox]

I think I've solved it!

If I have the below as my macro I get the the mute/unmute bug as discussed (<Event Name="Mute" /> being the standard MCE remote mute button):

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="1640">
<Macro Name="Mute Volume" Expanded="True">
<Event Name="Mute" />
<Event Name="MceRemote.370D" />
<Action>
System.ToggleMute()
</Action>
</Macro>
</EventGhost>

However if I disable the <Event Name="Mute" /> which is the standard MCE mute event everything works fine as below:

<?xml version="1.0" encoding="UTF-8" ?>
<EventGhost Version="1640">
<Macro Name="Mute Volume" Expanded="True">
<Event Name="Mute" Enabled="False" />
<Event Name="MceRemote.370D" />
<Action>
System.ToggleMute()
</Action>
</Macro>
</EventGhost>

I have this setup so I can use the original MCE remote as well should I want to. However EG seems to be treating an event, as an action, very bizaare....

On further testing, It seems that if the MCE MUTE event is anywhere in macro folder, EG exhibits this double mute/unmute behavior, so its executing an uncommanded (un evented) action. Perhaps this is because there is hardwired MCE mute function in Win7, since it was fine on XP?
Can someone test my macros above to see if they get the same result?

[dhgb256]

Sorry it has been a while since I've dealt with this, so I think I confused both of us. you need to make sure that your macro trigger is specific to your remote (e.g., mceremote.mute not just mute). otherwise you'll trigger the mute with the remote and when windows mutes the system it triggrrs again. you've done deleted the mute trigger, now just press the mute button on your remote and it should log as something like mceremote.370d.mute. drag this over where your mute trigger used to be and you're all set.

[farbox]

I understand what you are saying, however "Event Name="MceRemote.370D"" is the SPECIFIC trigger that EG registers for the actual non MCE remote I'm using, and thats the desired event for me and my setup ie I want mute when I press that specific button on that remote.
The bug seems to be with the standard EG MCE remote event. It seems if this is present in a macro, it gets registered as a valid event regardless of whether it was commanded or not.
In other macros, I can put two or more EVENTS, from two or more remotes/keboards/triggers etc, and triggering one doesnt mean EG registers the other events as triggers as well, however in the case of MCE MUTE event it seems its doing this, and thats why I think this is either an EG bug, or related to the way Microsoft has hardwired the MUTE (since it must be a system wide action in windows).
Did you play with my macros? See if you get the same effect (as I said try to execute the MUTE action on its own in the two macros (right click the MUTE ACTION and select Execute). The effect happens REGARDLESS of an EVENT trigger (ie it doesnt matter if you are using a remote or any remote AT ALL)).

[dhgb256]

Perhaps my terminology is confusing this, so in your macro file you can't have an event name=Mute, because it causes the double mute toggle. Change your event name from "Mute" to whatever it logs your mute button as for your remote. For my 2 remotes it is Auvisio.Mute and MCERemote.Mute. When you delete the mute event from your macros, it will still log the button press in the log screen, so change the event name to whatever it logs your button press as. If you do this it will solve the problem and your mute toggle will work correctly.

-DH

[farbox]

YES, ive already said that deleting the MCE MUTE event solves the problem somewhat, however the bug remains!!!!!!!!!!!!!!!!!!!!

so in your macro file you can't have an event name=Mute, because it causes the double mute toggle.

I've mentioned several times that this "event name=Mute" is not something I created out of thin air, its the included standard EG MCE REMOTE mute button event, and if including it in a macro, and using it in the usual way as any other event causes this problem, its a bug!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I hope someone has a look at my previously included macros, and see if they can replicate this problem, and get a developers opinion as to why this behavior is happening.
The two of us seem to be complicating things more by discussing different things!

[dhgb256]

I've mentioned several times that this "event name=Mute" is not something I created out of thin air, its the included standard EG MCE REMOTE mute button event

The standard MCE remote mute event changed from "Mute" to "MCERemote.Mute". So change the event name to "MCERemote.Mute" and it will not give you trouble any longer and will work as intended. The newer versions of EG reads an event named "Mute" to mean ANY mute event, not just a remote control event (see Jonib's explanation in Post #2). So the System.Mute '100.00' is being read as a Mute event and is firing your macro a second time, causing the unmute.

-DH