Random Hits not actually programmed

[SteveDoG]

Sorry if this has been dealt with before however, a search didn’t throw up anything seemingly exactly the same as this. Is there a solution to SD3 randomly triggering a cymbal hit when there is no programming data relating to that hit whatsoever?  I’ve been programming drums as long as it’s been a “thing” so I have been through everything I can think of and yet, here we are, random cymbal strikes happening with no data to cause them. What’s more, it suddenly appears, it was fine for weeks beforehand and then one day, it decides that, it will  trigger a cymbal randomly for no apparent reason. It’s always a “double hit” as well, that is, it occurs when another part of the kit is hit, so far, either on a snare hit or a tom hit.

Superior Drummer 3 version: 3.2.4
Operating system: Windows 10

Topic

[José Sanguino]

No idea. Sorry. I remember that once I had a MIDI Controller Keyboard which started sending one particular note because the keypad had started malfunctioning and it activated of its own accord. It was an M-Audio Axiom 61 1st generation. Check that the SD3 track, once you have finished recording it, has no MIDI input assigned and listen again. Anyway, I don’t think that’s your case.

Superior Drummer 3 version: 3.2.4
Operating system: Windows 10

[Scott]

SteveDoG wrote:

Sorry if this has been dealt with before however, a search didn’t throw up anything seemingly exactly the same as this. Is there a solution to SD3 randomly triggering a cymbal hit when there is no programming data relating to that hit whatsoever?  I’ve been programming drums as long as it’s been a “thing” so I have been through everything I can think of and yet, here we are, random cymbal strikes happening with no data to cause them. What’s more, it suddenly appears, it was fine for weeks beforehand and then one day, it decides that, it will  trigger a cymbal randomly for no apparent reason. It’s always a “double hit” as well, that is, it occurs when another part of the kit is hit, so far, either on a snare hit or a tom hit.

Superior Drummer 3 version: 3.2.4
Operating system: Windows 10

Are you using an edrum kit? Is it a crosstalk issue? What area you using to input the MIDI?

Scott Sibley - Toontrack
Technical Advisor

[SteveDoG]

Thanks for the replies, no, this is from a programmed beat that was done a couple of years ago. It doesn’t always do it either. Starting a couple of months ago, at times, it just randomly does it.

[Brad]

SteveDoG wrote:

Thanks for the replies, no, this is from a programmed beat that was done a couple of years ago. It doesn’t always do it either. Starting a couple of months ago, at times, it just randomly does it.

Could you post a snippet of the MIDI in a zip file here?

Superior Drummer 3 version: 3.2.4
Operating system: macOS Big Sur (11)

Mac Studio M1 Ultra, RAM 64 GB, 1TB Drive, OSX 13.x-15.x and Windows 10 (VM)
DAW: Fender Studio Pro 8, Presonus Studio One Pro 7
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)

[SteveDoG]

Thanks everyone, I have managed to sort it out. I needed to reassign the midi notes of the two crash cymbal mute hits to other keys and it’s fine now.

• This post was modified 4 years, 7 months ago by SteveDoG.

[Author]

Replies