DrewBySnacks
Participant
Topics Started: 3
Replies Created: 18
Has Thanked: 3
Been Thanked: 4
DrewBySnacksAWESOME. 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: PetterDrewBySnacksYeah 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*
DrewBySnacksI’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
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.
DrewBySnacksDo you want one single file for each microphone in the stack, as if it were a single drum….or do you want to be able to mix in the levels of the stacks afterwards? If you have a mix of the stacks you like….either route the microphones of the stack to your main snare channel and treat them as one microphone, and then bounce the mic audio WITHOUT choosing to separate close mics on channels OR if you only want one single snare channel in your DAW, you can route all of your snare mics and channels into a Bus inside SD3, get your balance correct and then send that bus to its own output via Multi-Outputs, which would give you a single snare channel that should match your BUS mix exactly as long as you don’t have any extra processing effects on your output channels. Also make sure all of your output channels inside SD3 have the faders set to zero, or identical to each other. If one output is faded down (or you have compression on channels 1/2 but not the others)….the sound will change.
1
Thanked by: BradDrewBySnacksI mean, in literally every other scenario but this one it’s one of the best mouses I’ve ever owned, why would I buy a different one? All I had to do was disable scroll wheel adjust faders inside SD3, which is a feature I don’t want anyways. It’s a setting inside Superior Drummer, not the mouse. Why would I buy another mouse when this one works great. If you had one with a classic scroll wheel it does the same thing if you have the setting clicked
DrewBySnacksI tried both stand alone and the plugin inside Ableton, same results. I do not want to route the outputs to busses before sending into Ableton, and using the routing method limits to 16 stereo tracks (15 really since 1/2 is reserved for mains in Live). I have 3rd party plugins I am using for EQ etc, and I want to apply all of my own processing to the individual channels before being limited to the busses. Additionally, when mixing I find it incredibly beneficial to have access to all the individual drum mics….a lot of effects can be achieved simply automating the right mic
DrewBySnacksI finally figured out what was happening and why it was so random and inconsistent/impossible to replicate the issue every time. I have a Macbook Pro with a “Magic Mouse” that has touch scroll both directions. I didn’t realize I had scroll enabled to adjust parameters inside SD3, so not only was moving my finger left or right on top of the mouse adjusting the gain fader in the bottom right corner of SD3’s UI window, it was ALSO messing with velocities sometimes.
If anyone else runs this software with a touch scroll mouse from Apple make sure that shit is turned OFF
DrewBySnacksHello! Was a solution ever found to this issue? I found this thread searching for a solution to exactly the same problem. Two years later. I have bleed enabled, and I am exporting a song using the “bounce all microphones” option, but the Overhead Mono microphone does not bounce as its own channel. I am using it to only send the bleed of the shells so I can have an overhead crush channel at mixing. For now my workaround is to do a second bounce with only that channel bussed to the main outputs, but it’s a frustrating workaround to have to go through.
Is there something specific about the Overhead Mono channel in the Death half of Death and Darkness that prevents it from bouncing this way?
DrewBySnacksWell, I THOUGHT I had it sorted but it is still happening. If seems that on one preset, the peak monitoring on the busses is pre-fader, while on the other it is post fader. Is there a setting to switch that somewhere I am unaware of?
DrewBySnacksUpdate: I figured it out in the process of trying to save the different presets. It was INDEED a rookie move/operator error. Somehow when I copied the preset over with a new snare, the routing on the busses got all messed up and multiple busses were going to the same channel, with several going to main outs 1/2….hence why I was absolutely clipping the Hell out of my meter lol.
ugh, at least it was something simple….
Sorry for the delay, got called out to a plumbing emergency with an actively flooding building last night
1
Thanked by: BradDrewBySnacksHey there! Yes I tweaked one of the presets from the premade mixes (tbh I’d have to go back and figure out which one). The only difference between the quiet preset and the preset for the two louder songs is the snare stacks are slightly different, however it is every drum and every mic that has a near 20db difference in output.
Apologies for the vagueness on “faders”. I was generic because I meant all of them. The busses in SD3, the output faders within SD3 AND the individual and bus faders in Ableton (also the master)….all set to 0 db as a starting point. I will save all three presets and upload them here with the quieter one labeled, if you see anything glaringly obvious it would save my day. I’ve been comping these drum takes so much my eyes are starting to twitch lol (home recordings tracked on an e-kit and now I’m trying to finalize into audio for mixing). It’s VERY possible I missed something really obvious. Thank you in advance
1
Thanked by: BradDrewBySnacksAs to the rim thing, that makes sense….I guess I was just hoping. I suppose I could try and find a maxforlive solution via ableton or another 3rd party engine to solve it.
DrewBySnacksI guess it feels like a bug because in other threads multiple tech support people from Toontrack claim it works but they don’t explain how to make it function. I have tried everything I can think of, so it’s either a bug in my setup or operator error on my part lol.
No products in the cart.