Quick question on crosstalk

[Joker47]

Every so often, one of my cymbals, or even a drum pad will cut out while playing. I assume it’s having crosstalk problems, but I can’t purposely reproduce it. That is, after a cymbal cuts out  while playing along to a song, I can’t stop and recreate that same thing by hitting the cymbal and anything else.

My question is: Is it the cymbals crosstalk settings I need to adjust, or is it whatever other pad that is affecting it that I need to adjust?

If it’s the “guilty” pad making the cymbal cut out, how do I find what it is if I can’t reproduce it manually?

Thanks,
J

[Chaser]

Every so often, one of my cymbals, or even a drum pad will cut out while playing. I assume it’s having crosstalk problems, but I can’t purposely reproduce it. That is, after a cymbal cuts out  while playing along to a song, I can’t stop and recreate that same thing by hitting the cymbal and anything else.

My question is: Is it the cymbals crosstalk settings I need to adjust, or is it whatever other pad that is affecting it that I need to adjust?

If it’s the “guilty” pad making the cymbal cut out, how do I find what it is if I can’t reproduce it manually?

Thanks,
J

It sounds more like you are running out of Polyphony.
Xtalk is When  striking a trigger causes another trigger to sound.
If you place instruments in a Mute Group one cancels out the previous..immediately.

If the maximum number of polyphony voices are playing, triggering an additional one will cause low-priority voices to stop so that higher-priority voices can sound usually cymbals or low toms which resonate longer and are at low priority (default settings)
There are a number of Kits at the 200mb range (max) or near it so if you have added layer(s) to any of the instruments it will start cutting off or stopping sounds.
You'll notice it more doing cymbal swells or rolls etc.You can adjust the Priority settings for each instrument from Low/Med/High.

Xtalk  pg 20

Priority (Polyphony)...Mute Groups  pg 17

Strike Performance Drum Module User Guide v1.5

Alesis Strike Pro Kit - Optimizing Trigger Response

[Joker47]

Thanks Chaser. Thanks also for correcting my terminology. 

I did go and change the priorities on the most offending pads and cymbals. So far, it seems to be a big improvement.

Pretty sure it'll be a non-issue here in the near future, as I had planned to pick up a second Strike module for expansion. Neither will be fully "loaded", so I'm hopeful this will not be an issue again.

Regards,
J

[Chaser]

Thanks Chaser. Thanks also for correcting my terminology. 

I did go and change the priorities on the most offending pads and cymbals. So far, it seems to be a big improvement.

Pretty sure it'll be a non-issue here in the near future, as I had planned to pick up a second Strike module for expansion. Neither will be fully "loaded", so I'm hopeful this will not be an issue again.

Regards,
J

IMO..It was a big mistake for Alesis to create a sample library using stereo samples that eat up double the Polyphony and a module with limited Ram..
not only did this eliminate the ability to use both layers (kits are maxed at 200mb)...they promoted the modules weakness.
I haven't used the Factory Library in years...but I did an experiment that worked very well and improved overall performance..