1

[Stephen Harrison]

So as I explained in the first post in this thread you should try selecting the midi blocks in the timeline (leave out any that are Toontrack blocks) that you think might be causing issues.

Right click and copy those blocks. (yes you may need to do all of this multiple times for all your blocks, or you could just merge them together and do it all at once)

Now paste it kit piece by kit piece. Snare, kick, hi-hat, etc etc …If there is any strange midi in there, don’t paste that because that’s what flips SD3 out. It might be called “note XX” or unmapped midi

Toontrack did patch this issue a while ago ( I saw it in the patch notes of one of the updates)

[Stephen Harrison]

I just ran into this bug yet again.

Strangely It’s a project where I dragged midi into cubase and change the VST to addictive drums then sent it off to a friend to put vocals on it.

I load it up, make a new superior drummer instrument and drag the drums I did before back into SD3. I make a couple of cuts and then start adding stuff to my project. I then want to edit the drums so I goto the grid editor and bang, Cubase is instantly shut down.

The midi doesn’t even have any funny stuff going on. No midi info outside of SD3s mapping. The whole drum section is just SD3 loops after all.

There hasn’t been a patch for SD3 in many many months. Surely there are some in the pipe work?

[Stephen Harrison]

https://www.dropbox.com/s/2gttveof42gpxgc/Recreation.sd3p?dl=0

dropbox link. Midi loop is orange. Double click it and go to the grid editor.

[Stephen Harrison]

Using the latest version.

Support already know about this. There hasn’t been any SD3 patches in the months since I raised the issue.

1

Thanked by: Henrik

[Stephen Harrison]

I made a SD3 drum map as well as some others like Addictive drums.
You can download them from my website http://www.songsfromsolitude.com

[Author]

Replies