No products in the cart.
Anecdote
Participant
Topics Started: 5
Replies Created: 9
Has Thanked: 1
Been Thanked: 1
I actually had the same issue, and it drove me nuts for a few hours. Turned out to be that the Hi-hat trigger was picking up the sympathetic vibrations from the snare, through the rack and cables! Made a few adjustments and the issue went away. Not saying that it’s the same issue with your setup, but maybe check it out.
In most cases, the 16 stereo outputs that are available in Superior Drummer and EZdrummer will work perfectly in your DAW if you want to apply your own effects after the mixer in our plug-ins.
We do, however, understand that it may be desirable to be able to split the stereo channels into dual mono or to be able to get instruments that are typically recorded in mono on a mono channel in your DAW.
There is an option to enable mono outputs in the Settings > Advanced tab in our plug-ins, but this option only works in Nuendo and Cubase.
For other hosts, you are going to have to manually configure your routing to separate the stereo outputs into mono signals.
Routing Toontrack outputs to mono channels
The basic idea is that you configure the mixer in our plug-ins so that the two signals that you want to have in mono in your DAW are panned hard left or hard right on one stereo output, and then split the stereo outputs in your DAW so that you get two mono channels per stereo output in the plug-in.
For example, if you want your kick and snare on two separate mono channels, you can send them to their own output channel in the plug-in, panned like this. For demonstration purposes, we have chosen output channel 3/4.
Then, depending on the DAW that you’re using, you may be able to select channel 3 and channel 4 as separate mono-channel inputs to two mono bus channels or mono audio tracks. Done!
Hosts where additional steps are needed
Some hosts do not let you use channel 3 and channel 4 individually as inputs on a mono track or bus, they can only be used as a stereo group. One example is Studio One, click the button below to see more info. Please contact support with the button at the bottom of this FAQ if we need to add your host to the list.
1
Thanked by: Georges GholamThanks for the reply. Turns out, the tom was being triggered by the Hi-Hat “Stand” slightly rubbing up against the rack (with the cables wrapped around it). Moved the rack arm an inch away and – problem solved! LOL!
Well I’d like to keep around $2000. However that eDRUMin looks pretty nice for the money (if it works well)! Thanks so much!!!
@John said:
As to why you have the ASIO Device Buffer size reset, I do not know and have to ask my colleagues about.
I presume you are using the latest available drivers for your hardware?Regarding your distorsion problem with the Ride: is it possible for you to record an audio example of this and also include an SD3 Project where this is present?
If you ZIP them, you can attach to a post here.BR,
John
John,
It’s subtle, but it’s there.
@John said:
Hi,from the colleagues in the know, here’s a workaround for now for the Buffer size problem:
-Start SD3.
-Open the audio settings dialog.
-Show the ASIO control panel and select your desired buffer size there.
-Go back to SD3.
-Select another device type, for example Windows Audio.
-Select your desired buffer size in the buffer size selector.
-Select device type ASIO again, and select your sound card driver and hit ‘Apply’.
Now the setting should be saved next time you open SD3.
Wonderful! that works!
Thanks!
Yes, everything’s up to date.
Windows 10 Home.
No the Audio Device is not grayed out.
When I open the ASIO control panel from within SD3’s settings and change the buffer to 1024 (in the ASIO control Panel) and then click Apply (or OK), the settings read –
Output latency: N/A
Buffer latency: N/A
Sample Rate: N/A
and the buffer resets to 256 and is still 256 even after I save the project as “Default!”
No products in the cart.