MVP-8400, NI-3000 & keybeeps

LegacyUser

How can I change the beeping sound heard when a button is pressed from the default to something else I provide?

I've tried uploading a WAV file into the panel (which can play when I trigger with a SOU command so I know the panel likes it) but I cannot get it to play on a keypress. I've tried setting the 'sound' event in Netlynx for the button & I've also tried setting this at runtime with ^BSO but no go. All I get is the default beep sound.

This, placed in the ONLINE event for the panel, does work so I know the found file is present and good:

SEND_COMMAND TP, "'@SOU-mybeep.wav'"

This command below, presumably, sets the sound for state 1 (off) of button 100 to the same beep as above. It does not work. This is sent immediately after the above in the ONLINE event so I know the panel is receiving it.

SEND_COMMAND TP, "'^BSO-100,1,mybeep.wav'"

This must be terribly easy as I've searched these forums high and low and find no references to such things.. what am I missing?

Ty
-J

Joe Hebert

lostboy wrote:

How can I change the beeping sound heard when a button is pressed from the default to something else I provide?

I don?t think there is a direct way to do this. However, what you can do is disable the button hit panel sound in the setup page and use the following code to trap every button push on each TP and then play your sound. I?ve never tried this myself but it should work. dvTP can be a single TP device or an array of TPs.

BUTTON_EVENT[dvTP,0] {	
   PUSH: {
      SEND_COMMAND BUTTON.INPUT.DEVICE, "'@SOU-mybeep.wav'"
   }
}

lostboy wrote:

This command below, presumably, sets the sound for state 1 (off) of button 100 to the same beep as above. It does not work. This is sent immediately after the above in the ONLINE event so I know the panel is receiving it.

SEND_COMMAND TP, "'^BSO-100,1,mybeep.wav'"

When you say button 100 are you saying a button with the channel code of 100 or the address code of 100? It needs to be a button with the address code of 100.

LegacyUser

Joe Hebert wrote:

I don?t think there is a direct way to do this. However, what you can do is disable the button hit panel sound in the setup page and use the following code to trap every button push on each TP and then play your sound. I?ve never tried this myself but it should work. dvTP can be a single TP device or an array of TPs.

BUTTON_EVENT[dvTP,0] {	
   PUSH: {
      SEND_COMMAND BUTTON.INPUT.DEVICE, "'@SOU-mybeep.wav'"
   }
}

Makes sense, I'd just thought there was an inbuilt way for the panel to beep when it registers a button press.

Joe Hebert wrote:

When you say button 100 are you saying a button with the channel code of 100 or the address code of 100? It needs to be a button with the address code of 100.

The button has its address code set to 100. The channel code for this button is 10.

In any event, what does "^BSO" actually do? The way the docs read it sounds like it sets a sound that will be played when a touch 'hit' is registered on a particular button. If thats not what it is supposed to do, I wonder what it really is to do? Likewise for the "sound" parameter in both the ON and OFF states of a button in TPDesign....?

Thanks
-J

DHawthorne

lostboy wrote:

Makes sense, I'd just thought there was an inbuilt way for the panel to beep when it registers a button press.



The button has its address code set to 100. The channel code for this button is 10.

In any event, what does "^BSO" actually do? The way the docs read it sounds like it sets a sound that will be played when a touch 'hit' is registered on a particular button. If thats not what it is supposed to do, I wonder what it really is to do? Likewise for the "sound" parameter in both the ON and OFF states of a button in TPDesign....?

Thanks
-J

It looks to me like it's a feedback item - that is, the button state feedback changes to oof, and the sound assigned to off with ^BSO plays. But I can't get it to work on my test panel ... doesn't seem to do a thing. The WAV I'm testing with is there and works fine, @SOU will play it. Afraid I haven't time to play around with it more though ...

LegacyUser

DHawthorne wrote:

It looks to me like it's a feedback item - that is, the button state feedback changes to oof, and the sound assigned to off with ^BSO plays. But I can't get it to work on my test panel ... doesn't seem to do a thing. The WAV I'm testing with is there and works fine, @SOU will play it. Afraid I haven't time to play around with it more though ...

Yup yup, this is what I thought and the behavior I am seeing.

So what do most of you guys do about keybeeps on panels -- do you disable this sound all together or just leave the defaulted AMX sound?

DHawthorne

I usually turn off keybeeps on a press, and turn them on for misses. I like feedback that you missed a button (easy enough to do depending on the button size and view angle), but I dislike a "noisy" panel. I'd rather have the negative audible feedback than positive. But I just use the default.

jjames

I am in no way responsible for any damages this may cause.

This was actually discussed in the P2 class I took in Tampa in April of '05. You can replace the default sound by going to the sounds folder of the AMX system pages on your computer. It's usually this:

C:\Program Files\Common Files\AMXShare\G4SupportFiles\__system\graphics\sounds

Here, you'll see audioTest, doubleBeep and singleBeep. If you copy the files out of there and put them in a different folder (for safe keeping), then rename the wav file you wish to use as your default "beep" to singleBeep or doubleBeep then upload with not doing a smart transfer, but a full system transfer, you'll be able to use your files instead of the default AMX. (.... whew - talk about a run-on sentence.)

I've done this with graphics as well, such as the so called "custom frame". (http://www.amxforums.com/showthread.php?t=598)

I am in no way responsible for any damages this may cause.

Joe Hebert

Thanks for the tip Jeremiah. I'll have to try it some day.