SD3 Crashes Pro Tools When Dragging Notes to/from an X-Drum in the Grid Editor

[GregRockN]

I can produce a consistent crash of SD3 and Pro Tools when grabbing and trying to drag notes to an X-Drum in the Grid Editor.  The crash causes Pro Tools (ver. 2020.3.0) to close and then automatically re-launch.  I am running a 48kHz 24-bit Pro Tools session.

How to reproduce:

1. Use Yamaha kit
2. Add an X-Drum (10″ Zildjian EAK splash) to the kit.
3. Create some notes in the Grid Editor on any of the other instruments in the kit.
4. Grab some of the notes from the other instruments in the grid edit with the Pointer Tool, and then try to drag them to the X-Drum (“Instrument 1”) instrument at the bottom of the instrument list in the Grid Editor.
5. Alternatively, grab a note on the X-Drum and try to drag it to one of the other instruments.

On my system, this dragging of notes to/from the X-Drum will cause a crash 100% of the time.  My system is Windows 10 Pro (version 1903).  I have saved the SD3 session and uploaded it here as an attachment.  NOTE:  I have also created a brand new Pro Tools session, created an instrument track, inserted SD3 and then imported the SD3P session into SD3… and I get the same crash phenomena that I have in the original Pro Tools session.  Therefore the problem/bug is contained within the SD3P that I have attached to this forum entry.

Superior Drummer 3 version: 3.1.7
Operating system: Windows 10

• This post was modified 5 years ago by GregRockN.

Topic

[mickg]

Wow. Now that’s the way to explain a problem. I’ll try to replicate the problem and let you know how it goes. Only difference is that I’m running ProTools 12.5

Superior Drummer 3 version: 3.1.7
Operating system: macOS Mojave (10.14)

[Bear-Faced Cow]

I managed to crash your project in standalone. However, the be X-Drum doesn’t appear to be a factor. It appears to be dragging your MIDI across a lane that doesn’t contain a kit piece, in this case Cymbal 5, crashes SD3. I wasn’t able to crash it using an SD3 groove and the same kit setup. Just user MIDI.

It also doesn’t happen if I cut and paste the MIDI between a kit piece and the X-Drum.

100% reproducible.

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

• This post was modified 5 years ago by Bear-Faced Cow.

1

Thanked by: GregRockN

[GregRockN]

You are absolutely right.  The problem is that Cymbal 5 in the Grid Editor does not have a kit piece assigned to it, and dragging notes across that lane causes the crash.  Thank you for your help to figure that out.

Something in my SD3 session appears to be corrupted.  If I exit the Grid Editor and go to the Drums tab, cymbal 5 DOES appear to have a kit piece assigned to it.  Yet, if I manually trigger cymbal 5 with a mouse click it does play a sound but the visual on-screen in the GUI is that cymbal 4 is being struck (the audible sound is the crash kit piece assigned to cymbal 5, but the visual on screen is that cymbal 4 is vibrating from the hit).  I looked at the MIDI mapping for cymbal 5 and cymbal 4 and they do not share the same notes.  So somehow some internal “SD3 wires” have gotten crossed up/messed up on cymbal 5 in my session.  I’m not sure what I would have done to get into that bad state.

This morning I have re-loaded the Dry Yamaha Rock kit, and added my X-Drum.  Cymbal 5 now works as it is supposed to in the Drums tab (both visually and audibly), and also has an assigned kit piece in the Grid Editor.  And now I can successfully drag notes across all lanes in the Grid Editor (including cymbal 5) without crashing Pro Tools.

I think there would still be value for the tech folks at Toontrack to take a look at my SD3P session file and produce a fix that would not crash Pro Tools if notes in the Grid Editor get dragged across a lane with no kit piece assigned.  That bug caused some frustrating losses of work and time for me.

Superior Drummer 3 version: 3.1.7
Operating system: Windows 10

[Bear-Faced Cow]

Just for laughs (my brain loves a technical challenge), I thought I would import your MIDI into a rebuilt project as well and it worked without any crash.

Looking at your project, the X-Drum did have an assigned lane in the Grid Editor, but the interesting thing that I noticed was that your project was lighter than the rebuilt one by about 80K. That makes me go hmmm…

jord

---

Jordan L. Chilcott

Web Site: https://jordanchilcottmusic.com/

[Joe List]

This happens to me every single day. I am so mentally corrupted by this…..

Superior Drummer 3 version: 3.2.4
Operating system: macOS Mojave (10.14)

[JessSoelberg]

Yep, this is happening to me, too. Cymbal 5 was working earlier in my session, but it looks like it’s been corrupted. In the “drums” tab, it shows that I have a china cymbal loaded, but when I click it, cymbal 4 moves around as if I had clicked on cymbal 4! Now when I try to create a note in cymbal 5’s lane in the grid editor, it causes my DAW to crash. How annoying.

Superior Drummer 3 version: 3.1.7
Operating system: macOS Catalina (10.15)

[Author]

Replies