EventGhost

In the new version of eventghost (1572), when I press the mute key it mutes the system and then promptly unmutes it again immediately. When I downgraded back to 1544 everything works fine. So I assume it is a bug in the new version. I have attached my remote.xml file. Mute seems to be the only peculiarity.

Some additional detail:

if I press mute on my keyboard it runs the MCE mute code in eventghost (not sure why it even does this as the 1544 version does not recognize the keyboard as an input device), it toggles mute, runs a bit of python code, unmutes, then sets the OSD based on mute status determined in python code.

If I press mute on my remote, it toggles mute, runs the python code, sets the OSD and then unmutes.

Remote: MCE Remote
Keyboard: Logitech RF Wireless

Let me know if you need more detail.

-dhgb256

dhgb256 wrote:In the new version of eventghost (1572), when I press the mute key it mutes the system and then promptly unmutes it again immediately. When I downgraded back to 1544 everything works fine. So I assume it is a bug in the new version. I have attached my remote.xml file. Mute seems to be the only peculiarity.

If you change the Mute event in "Volume\Mute Volume", to the specific event you want it to react to. The new EventGhost creates an event when the sound is muted and I'm assuming it is what's triggering the unmuting for you.

Any event that has the .mute part will trigger your Mute/UnMute macro right now.

I haven't tested this yet as the sound events are only for Vista/7. So your problem might be something else.

jonib

jonib wrote:

dhgb256 wrote:In the new version of eventghost (1572), when I press the mute key it mutes the system and then promptly unmutes it again immediately. When I downgraded back to 1544 everything works fine. So I assume it is a bug in the new version. I have attached my remote.xml file. Mute seems to be the only peculiarity.

If you change the Mute event in "Volume\Mute Volume", to the specific event you want it to react to. The new EventGhost creates an event when the sound is muted and I'm assuming it is what's triggering the unmuting for you.

Any event that has the .mute part will trigger your Mute/UnMute macro right now.

I haven't tested this yet as the sound events are only for Vista/7. So your problem might be something else.

jonib

Hi jonib,

I assume this was a change in the newest Eventghost? That could explain why the mute macro is firing when I use the keyboard, which would actually be great because my OSD would be correct then even when using the keyboard to mute. I didn't think of this until right now, but could it be that the button is reading twice? Once as it runs the eventghost code and another time windows is reading the native MCE code? That would make sense, but eventghost turns those off for me with the older version. Did something change in the newer version that I should be aware of?

Oh, and I am using Window 7 x64 home premium.

-dhg256

dhgb256 wrote:I assume this was a change in the newest Eventghost?

As far as I know from the forum, a plugin was added that creates events whenever the volume changes in Windows (Vista/7 only).

That could explain why the mute macro is firing when I use the keyboard, which would actually be great because my OSD would be correct then even when using the keyboard to mute.

I would need to see the log from EventGhost to know whats happening. But you should be able to use the new events to show the current volume, however you have changed it.

I didn't think of this until right now, but could it be that the button is reading twice?

Only the log could help to show what's happening.

Did something change in the newer version that I should be aware of?

Sorry don't know.

jonib

So I got it working. I had to change my mute triggerto MCERemote.mute and it stopped all of the weird behavior. I never figured out why it was sending a .unmute, but changing the trigger stopped it.

-dh

dhgb256 wrote:So I got it working. I had to change my mute triggerto MCERemote.mute and it stopped all of the weird behavior.

Glad you got it working.

I never figured out why it was sending a .unmute, but changing the trigger stopped it.

The EvenGhost log should have show what triggered what.

jonib

jonib wrote:

dhgb256 wrote:So I got it working. I had to change my mute triggerto MCERemote.mute and it stopped all of the weird behavior.

Glad you got it working.

I never figured out why it was sending a .unmute, but changing the trigger stopped it.

The EvenGhost log should have show what triggered what.

jonib

Where do I find the log?

-dh

dhgb256 wrote:Where do I find the log?

The left part of the EventGhost window usually shows the log.

jonib

jonib wrote:

dhgb256 wrote:Where do I find the log?

The left part of the EventGhost window usually shows the log.

jonib

Oh, that I am familiar with. But there was no clue as to what was tripping the unmute. It was just a random system.unmute showing up. I did confirm that the button wasn't reading twice. And actually I tried to mute the system from the control panel and it still sent a random system.unmute. it is really weird.

-dh

dhgb256 wrote:Oh, that I am familiar with. But there was no clue as to what was tripping the unmute. It was just a random system.unmute showing up. I did confirm that the button wasn't reading twice. And actually I tried to mute the system from the control panel and it still sent a random system.unmute. it is really weird.

Without seeing the log for myself it's impossible for me to know whats going on. But usually the EventGhost log should show everything it does, unless there is a bug.

jonib

I'm having the same auto mute issue here, where did you find the mcemute action?

In your remote file, find the Mute command and delete it, just the log action, not the whole macro. You can then press the mute button on your remote and it will show up in the log in its full form (e.g., for an MCE remote it shows up as MCERemote.Mute) and drag it over into the spot where you deleted your mute log action. That is what I did and it worked splendidly. If you need screen shots or anything let me know and I'll get them for you tonight when i get back home.

-DH

Hello all!
Reviving this old thread as Ive just encountered this problem on my new win7 build.
This macro used to work perfect on XP but not win7. Using MCE receiver (using the standard plugin) and NON mce remote, EG 4.1.r1640

Here is my macro:

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

And for a SINGLE keypress, i get the below:

MceRemote.370D
Mute Volume
Toggle Mute
System.Mute '100.00'
Mute Volume
Toggle Mute


So for some reason the system is mute/unmuting on a single key press.

Why is it doing this, and how do i fix it?


PS this is not receiver or remote related, since if I execute the "toggle mute" action on its own, its exactly the same behaviour.

Toggle Mute
System.Mute '100.00'
Mute Volume
Toggle Mute

(why is the "toggle mute" action repeating automatically?)

Perhaps the way mute works has been changed from xp to win7 and the EG system control plugin needs to be updated?
Can someone bring this to the attention of the developers please?

Did you try the method I outlined in the post above? Try deleting the system.togglemute() then press mute on the remote and drag the mute action from the log into that spot in your macro. My guess is it will be something like mceremote.370D.togglemute. That worked for me. Good luck!

-DH

Sorry I went back and looked and I realized I forgot to mention an important detail. What was triggering my double togglemute was that the remote was triggering one and then when Windows was muting a toggle event was being logged, which caused it to unmute itself. That is why it is important to have the full device name in your macro, so windows doesn't trip that second mute toggle. But it looks like you already have the full remote referenced, so if my earlier suggestion doesn't work then I have a second suggestion. Another issue I had was when I enabled events for my keyboard buttons it was causing problems, so if you have another device enabled like a keyboard, try disabling it. I can send you my xml file if you want it, just let me know.

-DH