DrewBySnacksHey all! I have found a massive glitch inside of Death and Darkness SDX.
In the “Death” half of the pack, there is a microphone labeled “OH Mono”. This channel WILL NOT bounce as audio, regardless of which method is used. The only way to capture or bounce the audio from this microphone is routing it into a channel in a DAW or using Loopback audio through an interface into a DAW and resampling it. None of the bounce methods, whether “basic”, “bounce all microphones”, or “bounce outputs”. I even turned every other channel off, sent it solo through 1/2…bounced the output and no audio. Doesn’t matter if all bleed is enabled, or any other option. I have eliminated every variable.
There are posts in this forum at least a couple years old listing this issue, with zero replies from any Toontrack staff. I have made my own posts with no replies, and I have even contacted customer support breaking down the issue along with an example file. I can’t seem to get anyone from Toontrack to reply or acknowledge this issue. PLEASE HELP!!!!
What do I need to do to get a customer service or tech agent to respond to me on this?
Mark KingBefore you bounce do you actually see any activity on oh mono? If not then maybe it’s not used in the preset you are using. I’ll have to take a look myself when I get a chance as I haven’t noticed it.
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
DrewBySnacksI built the preset from scratch, and I even went so far as to delete or mute every other microphone and channel to confirm that I was ONLY receiving audio from the OH Mono channel. It is active and has bleed channels sent to it.
This glitch exists in both presets, default kit and a custom one with that channel…in both the stand alone AND plugin version.
The audio plays back if you bounce it in real time. Right now my workaround is: bounce all microphones in my mix, in which everything else bounces exactly as I want. THEN I have to set up a channel in my DAW to record the audio from either Superior Drummer’s plugin channel, or use Loopback audio/resample to capture it. These are the only ways to bounce that microphone.
Any stacks or separated bleed stems, etc all bounce without issue. It is only this microphone which does not. Again, EVEN simplified bounces which are just supposed to bounce a stereo mix. If you solo the OH Mono channel, it will play back in real time but if you bounce it you will have a track of silence.
Mark KingGot you. Yes that doesn’t sound right.
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
1
Thanked by: DrewBySnacks
BradHey all! I have found a massive glitch inside of Death and Darkness SDX.
In the “Death” half of the pack, there is a microphone labeled “OH Mono”. This channel WILL NOT bounce as audio, regardless of which method is used. The only way to capture or bounce the audio from this microphone is routing it into a channel in a DAW or using Loopback audio through an interface into a DAW and resampling it. None of the bounce methods, whether “basic”, “bounce all microphones”, or “bounce outputs”. I even turned every other channel off, sent it solo through 1/2…bounced the output and no audio. Doesn’t matter if all bleed is enabled, or any other option. I have eliminated every variable.
There are posts in this forum at least a couple years old listing this issue, with zero replies from any Toontrack staff. I have made my own posts with no replies, and I have even contacted customer support breaking down the issue along with an example file. I can’t seem to get anyone from Toontrack to reply or acknowledge this issue. PLEASE HELP!!!!
What do I need to do to get a customer service or tech agent to respond to me on this?
Operating system: macOS Ventura (13)
I have been able reproduce this using both your preset as well as the default preset.
Mac Studio M1 Max, RAM 64 GB, 1TB Drive, OSX 12.x/13.x and Windows 10 (VM)
DAW: Studio One Pro (always up to date)
DTX Express III (Extreme triggers), Nektar LX88
OWC Thunderbay Mini (4 X 1TB Sata SSD), Express 4M2 (4 X 2TB M.2 SSD), Envoy Express (1TB M.2 SSD)
Presonus Quantum, Faderport & Faderport 8
Black Lion Sparrow Mk2 A/D, FMR-RNP-RNC, MIDI Xpress 128, BM5A, KRK VXT4, Equator D5
2020 Macbook Pro 16GB RAM, 512GB SSD Audio(mobile rig)
1
Thanked by: DrewBySnacksDrewBySnacksI’m glad to hear others are able to reproduce this issue and it isn’t just with my computer, hopefully we can get a response from tech support soon with a patch! For now, just be aware to anyone who uses that pack that you’ll have to do some extra trickery to bounce it! I use that channel as my Mono Crush mic for all the shell transients, so it was very obvious to me that it was missing on my bounce. I imagine others might not catch it and be wondering why their mix changes when they finalize it, especially if they bounce down to a single stereo file in SD3
DrewBySnacksYeah I made sure to eliminate as many variables as possible before calling it an actual glitch (I’ve been guilty plenty of times of thinking something was a glitch as opposed to my own ignorance lol) TBH, I was hoping that was the case this time :/ *le sigh*
PetterThanks for reporting this issue, we have been able to reproduce this and we have forwarded it to our development team for further investigation.
Petter Adsten - Toontrack
Support & Betatesting
1
Thanked by: DrewBySnacksDrewBySnacksAWESOME. I literally found the perfect “base” drum sound for recording via e-kit with my thrash band and that OH Mono mic is crucial to it. I’m a very experienced drummer, not such an experienced engineer….so I was assuming/hoping it was operator error (like when I kept getting drastically different decibel levels on bounces and it turned out the touch scroll on my Apple mouse was adjusting the output gain lol) Glad to hear this one wasn’t just my ignorance, bummer there’s a bug. Thank you for getting right on it!
Looking forward to being able to quick-bounce my new preset.
1
Thanked by: PetterNo products in the cart.