PDA

View Full Version : Maybe a little bug with toggle mute



Spiroo
January 23rd, 2003, 02:18 PM
When I am using "toggle mute" it doesn't want to set the sound on :( It turns it off normally but after ... nothing :/
I'm using standard settings for this command.

Maybe you have seen that I'm posting a lot... sorry to bother you but I just had my ATI HF remote :)

Ron
January 23rd, 2003, 02:39 PM
Give us some detailed info:

Soundcard, OS, exact action settings, what volume channel you chose etc etc

Asking questions is good as long as you keep them small (as you are doing :-) )

Spiroo
January 23rd, 2003, 02:44 PM
System Conf : ASUS A7N8X Deluxe (nForce2 thus audio inside)
OS : Windows 2K Pro Fr
Action setting : Volume Mute Toggle
Volume ID = 4
Step Size = 0

Event : X10 _DN_Mute

No plugin activated except the one for ATI.

Ron
January 23rd, 2003, 03:06 PM
could you give the description of the volume channel you chose, since the number ( 4 ) is different for every soundcard I don't know if that is the correct one.

Spiroo
January 23rd, 2003, 03:39 PM
sorry.
It is : NVidia nForce Audio>Mastervolumes>mastercontrols>mastermute

Spiroo
January 23rd, 2003, 03:41 PM
In fact it is the wrong channel : it works when I use:
NVidia>LineOut>mastercontrols>Mute
but the icon in systray doesn't change it still remains the normal one (ie when sound is not mute).

Ron
January 24th, 2003, 12:33 AM
Lets see if we can debug the master volume thing.

Try these steps:

download the attached gml file.

Change the volume channel assigned to the first action in the multigroup:
[get volume] ( Note: there is a bug in 3.2.8beta1 and lower that causes Girder to forget the volume channel, so download 3.2.8beta 2 for the fix)

First unmute the master volume via the windows volume mixer.

Then trigger ( f5) the multigroup : [display levels]

Note the numbers that appear

Now mute the master volume via the windows volume mixer.

Then trigger ( f5) the multigroup : [display levels]

Note numbers again.

Post noted numbers here.

Spiroo
January 24th, 2003, 02:41 AM
* Master Volume test
In both case (mute or not) I get :
left : 65535
right : 65535

Spiroo
January 24th, 2003, 02:44 AM
I tried again using the Master Volume Toggle Mute.. and with Girder 3.2.8b2 it works... when I test the command through the interface.. but not with the event from my RC.

Ron
January 24th, 2003, 04:12 AM
Have you tested on the mute channel ? This is the only channel that will work correctly with the mute toggle.

And about the remote not working, is the remote sending multiple signals ? Install the logger to find out...

Spiroo
January 24th, 2003, 04:31 AM
oups sorry about the channel I didn't sleep last night and I'm getting very tired :)

Using MasterMute
Mute : left = right = 1
Unmute : left = right = 0

the remote is working properly because it works perfectly when I use the wave mute channel.

Ron
January 24th, 2003, 04:35 AM
So let me get this straight,

Girder works fine if you use F5 but not when you use the remote ?

Spiroo
January 24th, 2003, 05:03 AM
Yes.
When I use the Master Mute channel, it works using F5 but not wuth the remote and when I al using Wave Mute channel, it works with both...
It's strange isn't it ? :p

Ron
January 24th, 2003, 05:06 AM
Yes very strange since as far as Girder is concerned F5 or remote is exactly the same. So there must be something else going on. Start with a clean GML. Maybe there is another command that has the mute thing going.

Spiroo
January 24th, 2003, 05:13 AM
Even if I create a new file it's the same problem...

Ron
January 24th, 2003, 05:18 AM
send that file to the girder support email address ( see girder about box )

Spiroo
January 24th, 2003, 06:35 AM
So ?
Is there any mistake in my file ?

Ron
January 24th, 2003, 08:56 AM
hang on. I'm not busy with girder all day, I have a life :-)

Ron
January 24th, 2003, 09:47 AM
Your GML file looks good. Could you for my peace of mind install the logger plugin to check if this is definately not caused by plugin issues.

pretty please :-)

Spiroo
January 24th, 2003, 11:21 AM
Using toggle Mute on Mastercontrols>Master channel, logging plugin record after the first time I press the button:
Dev: 62 X10_UP_Mute 20:16:23 Friday, January 24, 2003
Dev: 62 X10_DN_Mute 20:16:22 Friday, January 24, 2003

And when I press it again :
Dev: 62 X10_UP_Mute 20:17:53 Friday, January 24, 2003
Dev: 62 X10_DN_Mute 20:17:53 Friday, January 24, 2003
Dev: 62 X10_UP_Mute 20:17:53 Friday, January 24, 2003
Dev: 62 X10_DN_Mute 20:17:53 Friday, January 24, 2003
Dev: 62 X10_UP_Mute 20:16:23 Friday, January 24, 2003
Dev: 62 X10_DN_Mute 20:16:22 Friday, January 24, 2003

It appears that the button is pressed twice. I don't know why because I'm sure I pressed it once :(

Any idea ?

Ron
January 24th, 2003, 11:29 AM
I don't know why this is happening, but as a fix try putting an antirepeat time of 250 ms in the eventstring.

Just glad we are getting closer to a solution.

Spiroo
January 25th, 2003, 04:50 AM
Using these settings it works...
But the problem still rmeains : why does the prog believe that the button has been pressed twice ?
(Moreover the same problems appears with a multicommand group witch switch on/off the monitor...). But the fix using the anti repeat delay doesn't work here.... :(

Ron
January 25th, 2003, 04:54 AM
seems to be a plugin problem.

Spiroo
January 25th, 2003, 05:27 AM
So it should come from the X10 plugin. I will send an email to its developper :)

Ron
January 25th, 2003, 05:59 AM
The monitor thing could be a girder/windows bug.

avekevin
March 6th, 2003, 11:22 PM
As a followup to this post, I have been experiencing problems with the mute toggle for some time.

When I try to mute using the mastercontrol channel, my ATI plugin will always crash. The channel will mute fine, but when I unmute the plugin crashes.

I tried the Line Out mute toggle and it works great.

Config:

DIGN 3e / Sony KV-32HV600 / ATI Remote Wonder
Windows XP Pro SP1 / Girder 3.2.4
ABIT NV7-133R (nForce sound)/ Athlon XP 1700+ / 512 Meg RAM
ATI AIW Radeon 7500 / Seagate

Regards,

Kevin