nsagr.blogg.se

I do need to clarify that I use Addictive Drums for almost all of my drum needs.

But about the sync issues.mine is synced with my start and stop. Ok, I understand all of the routing stuff now. JamStix, EZD, BFD, Cakewalk Session, all sync with start/stop, but this doesn't. I searched for a sync option, such as AD1 and AD2 have, but haven't found it. The module isn't syncing with the start/stop in Reaper for me. The cymbals and everything else are already grouped into out-1 by default upon loading MT-Drums, only slightly panned L to R, so essentially any phase issues would already have been worked out by the developer.Īre yuo using this with low buffer settings (low latency)? Do you have an asio driver interface? WHat exactly is happening when you start/stop?

I did test the output in mono and didn't notice any phasey jet-sound stuff going on. The hard panning L/R is within the MT-Drums mixer itself in order to separate each individual piece. Did you check your drum mix with reaper in mono to see if there are phase cancellation problems? Meaning keeping the recorded output as MIDI instead of audio? Just explode the full MT-Drums MIDI output by note-row without changing the output.Ĭhanging the panning too far from what it is already may introduce some weird things, like phase issues. Not everyone ever renders the parts to audio other than a total mixdown of project, so they can't explode them to mono tracks Not sure what you mean by explode each item to new one-channel items, though. I put the toms on 4 (that's the way I have EZDrummer set up - toms on 1 stereo track), the ride and bell on 5, crash left on 6, crash right on 7 and china on 8. Jeff: I just tried this for separating the 13 components, using only 7 of the 8 outs, by combining them in pairs and hard panning L/R within each pair.Ĭool! I did a small variation though. Nice drum VSTi - crisp clean sounds - low CPU (>.2% here!) - uncomplicated, easy to use GUI.

I render ALL midi very early in my process for various reasons, so this solution was like a bonk to the head, a "duh" moment. Pan accordingly on the TCP.Īwesome solution! The only thing that some people won't understand though is that not everyone ever renders the parts to audio other than a total mixdown of project, so they can't explode them to mono tracks. I just tried this for separating the 13 components, using only 7 of the 8 outs, by combining them in pairs and hard panning L/R within each pair.Īfter recording, simply explode each item to new one-channel items, where they will now be in mono. Are yuo using this with low buffer settings (low latency)? Do you have an asio driver interface? WHat exactly is happening when you start/stop? This is weird because I do not experience this at all. is there any way to get it to start/stop in sync? Doesn't sync up with the DAW, though (although it does pick up the BPM).