Yamaha DTXpress/DTXplorer/DTXtreme group photo

Yahoo Groups archive

Yamaha DTXpress/DTXplorer/DTXtreme

Index last updated: 2026-04-28 22:44 UTC

Thread

no snare with closing hi-hat

no snare with closing hi-hat

2001-07-20 by deeoo@hotmail.com

First of all, hi everybody. I'm new to the group and just bought a 
DTXpress. I love playing drums at 2 a.m. :)
Anyway, I found that when I play the snare simultanious with the 
closing of the hi-hat (footpedal) and hitting the hi-hat (pad), the 
snare sound is skipped. I have this all the time. 
Am I the first? Can I fix this?

Re: [DTXpress] no snare with closing hi-hat

2001-07-21 by Rick Kelsall

--- deeoo@... wrote: > First of all, hi
everybody. I'm new to the group and
> just bought a 
> DTXpress. I love playing drums at 2 a.m. :)
> Anyway, I found that when I play the snare
> simultanious with the 
> closing of the hi-hat (footpedal) and hitting the
> hi-hat (pad), the 
> snare sound is skipped. I have this all the time. 
> Am I the first? Can I fix this?
> 
> 
Hi, yes you can fix it...
For each bit of the kit you can pick another trigger
which you think might interfere or trigger by mistake.
So you can nominate other triggers that you want
ignoring when you hit a trigger - like your hihat.
This is pretty useful in some circumstances, like if
you have the pads switched into the sensitive mode
then it is really easy to have other pads trigger by
mistake (if you are really tearing it up).  So its not
a completely crazy idea.
However, I think this is the feature causing the
problem on your kit.  I reckon your snare is being
excluded by the settings on your hihat.
You should be able to go into the settings for the
hihat where there is a list of pads that could trigger
by mistake.  I think you can either reduce the level
or remove the snare from its list.  The exact menu
option I can't remember - you can tell it's ages since
I've looked at it but there is one to do that! :)

=====
Rick        __     __
 Kelsall    /  \~~~/  \
      ,----(     ..    )
     /      \__     __/
    /|         (\  |(
   ^ \   /___\  /\ |
      |__|   |__|-"  Rarr!

____________________________________________________________
Do You Yahoo!?
Get your free @... address at http://mail.yahoo.co.uk
or your free @... address at http://mail.yahoo.ie

Re: no snare with closing hi-hat

2001-07-21 by deeoo@hotmail.com

Thanks Rick! After your explenation I found the Reject option in the 
manual (and now it made sense). And yes, the hihat rejected number 2 
(the snare). It put the reject value to 0 and it's fixed! Yea!
--------------------------------
Show quoted textHide quoted text
> Hi, yes you can fix it...
> For each bit of the kit you can pick another trigger
> which you think might interfere or trigger by mistake.
> So you can nominate other triggers that you want
> ignoring when you hit a trigger - like your hihat.
> This is pretty useful in some circumstances, like if
> you have the pads switched into the sensitive mode
> then it is really easy to have other pads trigger by
> mistake (if you are really tearing it up).  So its not
> a completely crazy idea.
> However, I think this is the feature causing the
> problem on your kit.  I reckon your snare is being
> excluded by the settings on your hihat.
> You should be able to go into the settings for the
> hihat where there is a list of pads that could trigger
> by mistake.  I think you can either reduce the level
> or remove the snare from its list.  The exact menu
> option I can't remember - you can tell it's ages since
> I've looked at it but there is one to do that! :)
> 
> =====
> Rick        __     __
>  Kelsall    /  \~~~/  \
>       ,----(     ..    )
>      /      \__     __/
>     /|         (\  |(
>    ^ \   /___\  /\ |
>       |__|   |__|-"  Rarr!
> 
> ____________________________________________________________
> Do You Yahoo!?
> Get your free @... address at http://mail.yahoo.co.uk
> or your free @... address at http://mail.yahoo.ie

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.