Yamaha DTXpress/DTXplorer/DTXtreme group photo

Yahoo Groups archive

Yamaha DTXpress/DTXplorer/DTXtreme

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

Message

RE: [DTXpress] Re: pcy135 vs. orginal dtxpress

2014-06-03 by <Kevin_Verrier@...>

Hello,

I am trying to use 2 mono pads on either channel 2 or 3 on original DTXpress. I have tried splitters (similar to what I already use for channel 9/10) but cant get it to work. Only the pad connected to the tip of the jack will trigger. If there are dual zone inputs why cant I get the ring trigger to work? Do I need a special/custom trigger?

Kevin

Kevin Verrier

Staff Engineer| Varian Semiconductor Equipment | Silicon Systems Group | Applied Materials

Office (978) 282-2045 | Mobile (603) 918-9261 | Fax (978) 283-8427

The content of this message is Applied Materials Confidential. If you are not the intended recipient and have received this message in error, any use or distribution is prohibited. Please notify me immediately by reply e-mail and delete this message from your computer system. Thank you.

** Save a tree. Please don't print this e-mail unless needed.

From: DTXpress@yahoogroups.com [mailto:DTXpress@yahoogroups.com]
Sent: Tuesday, June 03, 2014 4:03 AM
To: DTXpress@yahoogroups.com
Subject: [DTXpress] Re: pcy135 vs. orginal dtxpress

All inputs 1-8 on the original DTXpress are dual zone so the PCY135 should work. The PCY135 manual recommends setting the GAIN in the TRIGGER menu so that it registers 90-95% when hit hard (for the DTX series). You also have the adjustment pot on the cymbal itself so it is worthwhile adjusting that as well (there are no recommendations in the manual as to what to set it to!).

On the module, make sure the PAD TYPE is set to one of the dual zone cymbals such as PCY Crash, PCY Ride. If you are still having problems, try the "misc" pad types such as "misc 2" "misc 4" or "misc 6".

Keith

Attachments

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.