As per the message passed on by the Toontrack Facebook, I'm posting my remarks on SD3 here, like you asked.
Aside of the - frankly glowing - review I gave them on SD3, I also had a few features which are lacking compared to SD2, making it harder to work with inside a DAW environment.
Most importantly, there's the multichannel stereo outs. I had hoped that we'd be getting 16 stereo outs which could, by choice, be set up as mono outs inside of SD3. That would have been the easiest routing option for mix treatment outside of the SD3 GUI environment. In absence of that, I could live with the stereo option as it was in SD2 : stereo outs which could be set to mono in the DAW's virtual instrument routing options. It at least left me with 32 mono outs and the ability to route each invidivual kit element to such a mono out. It also meant I had outputs I didn't use.
With SD3, however, I only have stereo outs in the program which are seen in the DAW as just that : stereo outs. They can't be set to mono like in SD2. What this means is that I have to route each invidivual kit element to a stereo out, which a) prompts me to route the DAW instrument outs for these to a separate mono bus, which is one extra layer and b) because I have to route these individual kits to stereo outs, it means that all of SD3's multichannel outputs are taken! And that is without the surround channels! Three kick mics, one mono snare top, a stereo snare bottom, a hi hat mic, three tom mics, two floor tom mics, two stereo overhead mics and three stereo ambient mics, totalling all 16 outputs. That is hardly what I call economical.
So what I'm requesting - pretty please with a cherry on top - is one of two things : if it would at all be possible, I would ask for the options of choosing either mono or stereo channels inside of SD3, with this being mirrored in the DAW of one's choice, or, if that is too hard to do on a reasonably short term, to reinstate the option to turn the multichannel outs to mono, like in SD2. I have to confess the former option is more appealing to me than the latter, but ultimately, I don't know how easy or hard it is to put this into SD3's code.
My second request pertains the MIDI mapping. While it's easy to have everything close together in the GUI and the amount of tabs are reduced, I'm missing an option to clear all MIDI mapping to custom make your own, which was present inside SD2 as well. In SD3, it's easy enough to swap MIDI notes, but it's not very clean, and it's easy to miss a note (or several), which are doubled on the key bed. I do understand why the MIDI notes are mapped this way, but I've found that for me, at least, it's a lot more convenient to have the MIDI notes's sequence correspond with a mixing desk lay out of a kit, i.e. kick first, then snare, then hi hats, then toms, then overheads, then ambience, and I custom build my maps to work this way. When programming drums inside the MIDI grid of my DAW, it works well visually because all kit elements' layers and its corresponding notes are grouped together in a logical way. I've been doing this for years, so it would be a lot easier to be able to clear the SD3 standard MIDI map, build a custom one and save that, while I'm requesting features anyway. Because that would also be a worthy addition to SD3 : the ability to save and load the standard and custom MIDI maps, so you could instantly switch from one map to another, depending on the work you're doing. It's a lot easier than having to remap everything on older projects, or even put rendered drum files into Tracker (nothing against Tracker, which does an incredible job in its own right, but adapting and loading MIDI maps is a lot faster in some cases). So I'm hoping this could also be addressed in a future update.
Thanks in advance, and keep up the good work. SD3 is an update you can be proud of.