[Dean Stadtlander]

To Everyone that responded. The best I can tell, the problem was caused by an update to Davinci Resolve, a video editing program that also uses Farlight for audio editing. I’ve used it for a few years with no issues, but I updated it a few days prior to my problems with SD3. I completely uninstalled it. I’ve been able to load SD3 for the last two days without issue.

I appreciate everyone’s input and help. It’s good to know that there is a strong and helpful Toontrack community when you need it.

 

[Dean Stadtlander]

I’ve placed several DMP in a shared Box folder. The link is below.

https://app.box.com/s/ovj9foo08kmyytvxax0yej38t1r4pb01

 

[Dean Stadtlander]

DrumJack52, Great idea, unfortunately that didn’t work either.

[Dean Stadtlander]

Olof,

I’ve turned in a ticket. Every time I try to attach a file, I get the following message.

The file type of your attachment “Dean Stadtlander issue.zip” is not allowed. Allowed file types include: GIF, JPEG/JPG, PNG, TIFF, BMP, MP4, TXT, RTF, PDF, ZIP, RAR, TAR, GZ, and certain Toontrack project files.

I’ve tried several times and renamed the zip file a few times. Any other options?

 

 

 

[Dean Stadtlander]

Olof, I’ve tried to zip the file, but even at 3,353 kb it says the file is too big.  Is there another place to upload files?

[Dean Stadtlander]

Brad, great idea, I wasn’t thinking.

[Dean Stadtlander]

When it crashes, it just disappears, so I don’t get any dialogs. But I did a search and found the .dmp files. I tried to upload the file, but it says it’s too big to upload. It’s only 6,183kb. I tried to read it as a text file but there are lots of symbols, and some readable data. Is it something that can be cut in two to upload?

 

 

[Dean Stadtlander]

There is an errlog.doc file in my Superior3 folder, under Toontrack, under ProgramData. There are hundreds of lines of errors, but this is the early part of it.

 

TIMESTAMP 20240519 21:43:26 SL-AREA33ORIGIN
Error in configfile ‘padconf’ line 1587 :No such Member ‘crash6’

Error in configfile ‘padconf’ line 1587 : unknown Bundle entry ‘member’

Error in configfile ‘padconf’ line 1594 :No such Member ‘crash6’

Error in configfile ‘padconf’ line 1594 : unknown Bundle entry ‘member’

 

I’m looking for ‘padconf now.

[Dean Stadtlander]

Everything else on my DAW is working fine. It’s just when I load SD3 and only for the past few days. I’m using a PreSonus Studio 24C for my interface. Everything seems fine there too. My driver is from 2022. So I should actually look for an update once this is fixed. I think it’s up to date though.

Reply To: SD3.4 Crashing at Startup version: 3.4.0
Operating system: Windows 10

[Dean Stadtlander]

Thanks for the reply. It crashes in stand alone. When I run it in Studio One, it starts up, but the sounds are distorted. Studios One hasn’t had an update since February, and SD3 was running fine after that.

Windows will let you uninstall and revert the most recent updates.

I’ve done some searching about SD3 crashes and other windows crashes and haven’t found anything.

For the SD3 reinstall, I used the Product Manager. It pushes you to use the standard Windows program uninstall process. I reinstalled using the Product Manager. Here is why I think the problem might be with one of the start up files, when I reinstalled SD3, the drum kit that comes up at start up (only for about 30 seconds before SD3 crashes and disappears) is the default kit that I’ve been using recently. It is from Area 33 Origins, not the original kit from the SD3 core library. I’m planning on looking through the SD3 files today to see what files have been changed recently so I can try to revert back to an earlier version of the start up files. I think something may be corrupted.

 

Reply To: SD3.4 Crashing at Startup version: 3.4.0
Operating system: Windows 10

[Dean Stadtlander]

I figured out the issue. Roland pads use trigger input #7 as the hi-hat input. The hi-hat pedal is tied to that input. As long as you have the hi-hat pad in input #7 it is waiting to be controlled by the linked controller input. If you have your hi-hat controller connected to the dDrumin 10 like I’m doing, the trigger in input #7 on my TD – 20 isn’t controlled by the pedal. I moved the pad to another trigger input and now it works fine.

Reply To: 2 Hi-Hat Pads version: 3.3.6
Operating system: Windows 10

[Dean Stadtlander]

Christoffer. I’ve upgraded to 3.3.4 and so far, the problem seems to be fixed.

Thank you.

[Dean Stadtlander]

Perfect! Thank you.

Is there an anticipated release date?

[Dean Stadtlander]

John,

Thanks for looking into this for us. I’m using a Roland TD20 as the basis for the preset. I’ve edited from there. I have a large kit, and I’m triggering through two modules. A Roland TD20 and a Roland TD8. I go midi out from the TD8 into the TD20. From there I go to a PreSonus Studio 24c, and into the computer.

When I first started using SD3 at the end of 2021, I didn’t have this issue. It seems like most of my problems are with added instruments to presets. The standard kit drums seem to stay properly mapped (with a few exceptions) when they are reloaded, but the added instruments need to be remapped every time. For example, my highest tom is on midi note 33 for the center and note 34 for the rim. I can remap everything and it will play fine. Before I open another kit or project, I’ll save the project, save the midi preset and save the user kit. When I reopen the project, the kit loads properly, but my 4 added instruments are mapped incorrectly. The center on the tom that is on midi note 33 ends up as tom 1 center instead of instrument 1 center. The rim stays mapped to the rim sound on instrument 1. Instrument 2 center goes to tom1 and the same for instrument 3. Those three are tomes that are all pitched higher than tom 1. Instrument 4 is a tom pitched lower than floor tom 2. and the center reverts to floor tom 2 instead of instrument 4. Again, the rim stays properly mapped. This is in the core library.  In the Darkness library from Death and Darkness, instrument 1 and 3 centers revert to tom 1, instrument 2 reverts to tom 2, and the lowest tom goes to instrument 1. The instrument 1 rim ends up as tom 1 rim, and instrument 4 ends up as crash 4. I can remap and everything works fine, until I change projects or kits. I have similar issues with Death for Death and Darkness, The Metal Foundry, The Progressive Foundry and with the Rock EZX, all with slight variances on how the mapping reverts when a project or kit is opened.

Let me know if I can give you more information.

I love SD3, but this is frustrating.

Reply To: cannot save custom midi mapping in SD3 version: 3.3.3
Operating system: Windows 10

[Dean Stadtlander]

I’m having the exact same issue. I have a large kit. 9 toms, 5 cymbals, ride, 2 hi hat pads, kick, snare. On my user presets, I add in toms, cymbals, etc. to match up with my kit. Modifying and saving kits is no problem. I can go in and map each pad to the appropriate drum in the kit, and everything works great. I’ve saved my midi map under user presets found under the MIDI In/E-Drums Settings tab multiple times. I’ve saved each user preset kit as a new project. Every time I leave a customized kit and open another project or kit, and then go back to the edited kits, they revert back to different midi mapping, and my added instruments aren’t mapped correctly. How can I save my kits, so they work when I come back to them?

Reply To: cannot save custom midi mapping in SD3 version: 3.3.3
Operating system: Windows 10

[Author]

Replies