Stephen HarrisonJust a heads up to people experiencing random crashes out of the blue.
If you are using some custom loops from old projects or other midi/drum programs there is a small chance there will be some rouge midi data within them.
if your experiencing random crashes within a daw like cubase or in stand alone then select all the midi in your Superior Drummer 3 track and “COPY” it.
Now try and paste it again but look at the paste menu option under the kit pieces and check that nothing strange is in there like “MIDI NOTE 58” or something similar. This is basically some midi that completely flips superior Drummer out and crashes it. To work around it paste each individual kitpiece (kick ,snare etc etc) one at a time.
By doing this you are essentially filtering out those bad midi messages.
I post this here because even though it’s been many months since I contacted Toontrack about it they still havn’t patched the problem which is a little disappointing considering how repeatable and catastrophic it can be.
Just a heads up to people experiencing random crashes out of the blue.
If you are using some custom loops from old projects or other midi/drum programs there is a small chance there will be some rouge midi data within them.
if your experiencing random crashes within a daw like cubase or in stand alone then select all the midi in your Superior Drummer 3 track and “COPY” it.
Now try and paste it again but look at the paste menu option under the kit pieces and check that nothing strange is in there like “MIDI NOTE 58” or something similar. This is basically some midi that completely flips superior Drummer out and crashes it. To work around it paste each individual kitpiece (kick ,snare etc etc) one at a time.
By doing this you are essentially filtering out those bad midi messages.
I post this here because even though it’s been many months since I contacted Toontrack about it they still havn’t patched the problem which is a little disappointing considering how repeatable and catastrophic it can be.
1
Thanked by: abstraktron
VoxxaHi! I’ve had four crashes in one day when experimenting with The Grid Editor in Superior Drummer 3. This happened in Studio One 4. I have a home built PC with Windows 10 Pro, 32 Gigs of RAM, Presonius AudioBow iTwo, 2TB SSD drives. Is the error with Toontrack or – perhaps Presonus Studio One?
I hade to fiddle around with The Grid Editor since there was no MIDI files fitting to what I needed. But… four crashes in one session… that’s bad.
JohnHi Voxxa,
which version number is displayed in the SD3 plugin interface?
If you try to replicate what you did to experience those crashes in the standalone, does it crash there as well? Or in a blank Studio One session?
BR,
John
John Rammelt - Toontrack
Technical Advisor
VoxxaI think I have the lateste version of Superior Drummer 3. I bought it last week. Did like the improvements you’ve made compared to nr 2. I’m trying to create a seemingly too intricate rythm as it seems. Can’t find any like it in my MID-files, and I do have a lot of them. It seems when I’m deleting notes it has a tendency to crash. This happens mostly during the copy/paste actions.
MikeHave the same problem.
I have an imported midi file and when i try to edit that Logic Pro crash. I also have problem with dropouts randomly within the same project both when i run it or bounce it.
This have been around for a while now i am suprised that u have’nt solved it yet.
The midi editor has sevral drawback and it is very buggy i general and that is sad.
I use your manager so i should have the latest version
ScottHave the same problem.
I have an imported midi file and when i try to edit that Logic Pro crash. I also have problem with dropouts randomly within the same project both when i run it or bounce it.This have been around for a while now i am suprised that u have’nt solved it yet.
The midi editor has sevral drawback and it is very buggy i general and that is sad.
I use your manager so i should have the latest version
Please provide your system details.
Scott Sibley - Toontrack
Technical Advisor
Oliver ShillitoI too am having the same issue. I was working on a midi file earlier with Standalone SD3 and that one worked fine. Then I load a second midi in and boom, it crashes.
Then I loaded the affected midi into Pro Tools and as soon as I went into grid editor, Pro Tools crashed.
Same thing happens with Logic.
There is clearly some sort of bug in SD3 but I can’t tell what might be causing it.
OSX – 10.14.6 Mojave
SD3: 3.1.7
I’ve attached both the midi files. The Answer does not crash SD3. We Will Drive DOES crash SD3. The contents of them both look similar to me when examined in Pro Tools. What am I missing?
Stephen HarrisonSo 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)
OlofI too am having the same issue. I was working on a midi file earlier with Standalone SD3 and that one worked fine. Then I load a second midi in and boom, it crashes.
Then I loaded the affected midi into Pro Tools and as soon as I went into grid editor, Pro Tools crashed.
Same thing happens with Logic.
There is clearly some sort of bug in SD3 but I can’t tell what might be causing it.
OSX – 10.14.6 Mojave
SD3: 3.1.7
I’ve attached both the midi files. The Answer does not crash SD3. We Will Drive DOES crash SD3. The contents of them both look similar to me when examined in Pro Tools. What am I missing?
Could you save and upload a SD3 project file (.sd3p), please, so we can can see what MIDI mapping and instruments you have when it crashes? Also some crash log could be useful. You can find them in ~/Library/Logs/DiagnosticReports (use Go > Go to Folder with that path). Thanks.
Olof Hermansson - Toontrack
Coder
Oliver Shillitohttps://www.dropbox.com/s/jj8l256ilgexquo/crash%20kit.sd3p?dl=0
Above is a link to a SD3 project with midi in. If you go into that midi it will hard exit SD3.
Oliver ShillitoOliver ShillitoFixed it.
It appears that when you import a midi file into SD3. If there is a note on say a cymbal that you don’t have turned on. Instead of moving that cymbal hit to another cymbal as it usually does. It crashes.
If you load the midi into your daw and move those midi notes, it will import and work fine.
This needs looking into as a bug because it should not be hard exiting because of this.
I have no replicated this issue multiple times. I can confirm that is absolutely what the issue is.
One for the bug list.
ChristofferThanks for the report guys! This will be fixed in the next release of SD3.
Christoffer Lindmark - Toontrack
Coder
MortalCoilHello. I have been having this same problem today. I chopped up a few hi hat grooves (no other drums), lined them next to eachother, then bounced. I then imported that hi hat and tried to change the tempo in midi mapper and it crashes every time.
After reading this thread I now know how to work around this.. But I wanted to bring it to your guys’ attention.
The problem occurs for SD3 in Pro tools 12 and in SD3 stand alone. I can share a crash report and the other file in just a bit…
THANKS!!
1
Thanked by: ChristofferPlease log in to read and reply to this topic.
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.
