No products in the cart.
Hello!
First, I’m a novice with this so forgive me for my ignorance. What I’m trying to do is record what I’m playing on my kit directly into Reaper as I’m playing it. Almost every video I’ve seen is showing a track that is already recorded and putting that in Reaper, but that’s not what I’m wanting to do. I’m also not wanting to separate every piece of the kit into its own track. For now, I just want one track recording what I’m playing.
So far, I’m able to select the SD3 plugin in Reaper, and if I hit record and click on the drums in the window that pops up, it does record those sounds. But when I play anything on my kit, it doesn’t recognize that I’m playing. I’ve used SD3 to record directly in SD3 before, and that’s worked just fine. But is there something different I have to do to make the plugin recognize that I’m playing the drums?
Thank you in advance for all of your help!
First of all, you have to make sure that the Reaper track which contains your Superior Drummer 3 plugin is set to record MIDI and not audio. Then, make sure that you are recording from the appropriate MIDI port (In Reaper you can select multiple MIDI ports as active in your “Preferences” window, so you must plug in your e-drum kit to a specific MIDI port and select that one for the track you are planning to use). Within the track, next to the record enable button, you can choose if you’d like to hear sound from SD3 or not while recording (it’s an icon for a speaker: set it to “on” or “auto” if you’d like to hear SD3 while recording, or to “Off” if you would like to hear just your e-drum kit). After that, if your e-drum kit MIDI notes are set properly to match SD3’s, when you play back the MIDI in your track, you’ll hear SD3 playing back your beat/groove.
1
Thanked by: entner.chrisBEST ANSWER
First of all, you have to make sure that the Reaper track which contains your Superior Drummer 3 plugin is set to record MIDI and not audio. Then, make sure that you are recording from the appropriate MIDI port (In Reaper you can select multiple MIDI ports as active in your “Preferences” window, so you must plug in your e-drum kit to a specific MIDI port and select that one for the track you are planning to use). Within the track, next to the record enable button, you can choose if you’d like to hear sound from SD3 or not while recording (it’s an icon for a speaker: set it to “on” or “auto” if you’d like to hear SD3 while recording, or to “Off” if you would like to hear just your e-drum kit). After that, if your e-drum kit MIDI notes are set properly to match SD3’s, when you play back the MIDI in your track, you’ll hear SD3 playing back your beat/groove.
Superior Drummer 3 version: 3.3.0
Operating system: Windows 10
Don’t know the exact terminology that Reaper uses but you may be confusing MIDI port with MIDI channel. MIDI port is the connection between the e-kit and computer. There are 16 channels per MIDI stream/connection. So you want Reaper to not only look at what physical port (probably a USB connection these days) the e-kit is connected to but what MIDI channel so that both e-kit and the track SD3 is getting it’s MIDI from are the same channel (1 of 16).
As an aside make sure that the USB ports on the computer are set to never turn off aka go into power saving mode. By default Windows will turn them off (even on a desktop) after a certain amount of time.
Don’t forget there’s going to be a good bit of latency between when pads are hit and sound is made so keeping time while listening to the sounds can be a little difficult unless the amount of buffers used in Reaper or any recording s/w is lowered to as low as it can go and the computer doesn’t choke.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
1
Thanked by: entner.chrisThank you both for your quick and detailed responses! So my audio interface was disabled in the MIDI Devices menu in Preferences, so you helped me find and fix that. And then after switching the input to MIDI on the track (which I don’t know how I didn’t think to do that) everything is working exactly how I would like it to be working!
One last question. I am using ASIO4ALL and I have the buffer size as low as possible, so the latency is pretty minimal (but that shouldn’t be a concern because I do plan to only hear the sounds coming from my kit, but record the SD3 sounds) but I do slightly hear that crackle sound when I have Record Monitoring On. Will that crackle sound show up in my recording or is that just something that I’ll hear as I’m playing it?
Thank you again! You have already helped a ton and made my life a lot easier!
Thank you both for your quick and detailed responses! So my audio interface was disabled in the MIDI Devices menu in Preferences, so you helped me find and fix that. And then after switching the input to MIDI on the track (which I don’t know how I didn’t think to do that) everything is working exactly how I would like it to be working!
One last question. I am using ASIO4ALL and I have the buffer size as low as possible, so the latency is pretty minimal (but that shouldn’t be a concern because I do plan to only hear the sounds coming from my kit, but record the SD3 sounds) but I do slightly hear that crackle sound when I have Record Monitoring On. Will that crackle sound show up in my recording or is that just something that I’ll hear as I’m playing it?
Thank you again! You have already helped a ton and made my life a lot easier!
Superior Drummer 3 version: 3.2.7
Operating system: Windows 10
Is there any reason you’re not using the drivers for your audio interface? You should always use those if at all possible. It’s also possible that the buffers are too low and your computer is struggling. Are your samples on an ssd (preferably separate from your system drive)? Do you have SD3 set to cache samples when in Reaper? How much ram do you have?
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Is there any reason you’re not using the drivers for your audio interface?
My guess is that emtmer.cris does not have a dedicated audio interface. That’s why he’s using ASIO4All! – entner, you should know that ASIO4ALL won’t give you the best results when working with a DAW. That’s where the crackling comes from. And if the computer you are using does not have enough RAM and a good CPU, you’ll always have the same problem. If you’re using a laptop… don’t. – You should get a good desktop computer and at least a mid-range price, 2-channel audio interface with its own up-to-date ASIO drivers ASAP if you’re planning to do more serious work.
I guess I started using ASIO4ALL when I tried using SD3 standalone, because I was getting a lot of latency using my audio interface’s drivers. I do have an audio interface, by the way! Everything is on an SSD, but it’s on the same SSD. I did create a separate partition from my windows partition, however. I do have the “Cached” setting turned on in SD3 within Reaper. And I have 32 gigs of RAM. Is there a way to make sure SD3 is using as much of that as it needs?
I’m on a desktop, not a laptop. My CPU is an Intel i7-8700K, so I would think that would be good enough. But on the note of not using ASIO4ALL, I’m currently messing around with the other options in this window (see attached image). Which one of these systems would be the best one to use? And could you also help me with the settings that I should try once I select the best one?
Thank you again!…and again!!!
I have never tried any other than the ASIO drivers created by my device’s manufacturer. Years ago I was forewarned by Computer Music Magazine about the amount of latency which you would get if you used Windows Media Drivers, so the moment I could lay my hands on an interface with ASIO drivers, that was the choice for me. Lower block sizes for your audio interfaces will allow you to play and listen to your virtual instrument in “real time”. There’s always a little latency, of course, but I remember reading in Computer Music Magazine that as long as your latency is below 42 milliseconds, it’s OK. Over 42 ms it is impossible to play and listen to your virtual instrument at the same time. It has to do with the ability of the human brain to coordinate its actions with the results produced and perceived. I’m pretty sure you must have seen on TV how a reporter starts babbling and has to remove his/her earpiece because he’s listening to the return signal from the studio with plenty of delay: that is what would happen to you, more or less, if you tried to play and listen to your instrument with a latency of over 42 ms. Direct monitoring is advisable if you cannot achieve low enough latency values. I normally use it when recording vocals: you must turn off the monitoring from the track the vocalist is recording, and let him/her listen to the direct signal the microphone is sending. How? Well, it depends on your interface. Some interfaces have a knob which will increase your mic input’s volume relative to your DAW’s reference tracks (other instruments already recorded, a click track, etc). The vocalist will hear himself/herself straightaway, with no latency (remember: the track which is going to record the mic imput should be disabled for monitoring – it’s the device’s direct monitor level which will allow your singer to hear himself. – Of course, the same trick can be applied to other instruments. Sometimes the direct monitoring has to be activated from within your interface’s software mixing console. The results will be the same.
In your case, you can turn off the monitoring for your SD3 track (you may even DISABLE the plug-in, since the MIDI notes sent by your e-drum will be recorded anyway) and listen to your e-drum sounds against the reference tracks in your DAW. You won’t be affected by latency. If you play a MIDI keyboard with internal sounds, you may use those while you are recording your MIDI performance instead of overloading your CPU with your virtual instrument – You can enable your preferred instrument afterwards, since the MIDI notes are already recorded. If you wish to record an electric guitar which will be later processed through an amp simulator like Native Instruments Guitar Rig or IK Multimedia’s Amplitube, you can split your guitar’s cable and record the clean signal from one, and plug the other into a real guitar amp. Just turn off the monitoring from the track where you’ll be recording your guitar and that’s it! Use your amp as a reference for your playing together with your DAW’s reference tracks. You insert your amp simulator afterwards.
Hope this helped a bit at least. Keep on drummin’!
1
Thanked by: entner.chrisHoly cow this is all extremely helpful! Especially the stuff about recording guitar, because that’s something that I’m also doing. I’ve been recording my guitar using ASIO4ALL and getting pretty good results. The latency is usually under 10 ms, but I will absolutely try splitting my guitar cable so that I can hear what I’m playing with zero latency. Would I need something like this to do so?
And then basically have one cable plugged into my amp and one into my audio interface, right?
You have seriously helped out a ton and I can’t thank you enough!! And thank you for taking the time to type all of that out!!
I guess I started using ASIO4ALL when I tried using SD3 standalone, because I was getting a lot of latency using my audio interface’s drivers. I do have an audio interface, by the way!
Everything is on an SSD, but it’s on the same SSD. I did create a separate partition from my windows partition, however. I do have the “Cached” setting turned on in SD3 within Reaper. And I have 32 gigs of RAM. Is there a way to make sure SD3 is using as much of that as it needs?
I’m on a desktop, not a laptop. My CPU is an Intel i7-8700K, so I would think that would be good enough. But on the note of not using ASIO4ALL, I’m currently messing around with the other options in this window (see attached image). Which one of these systems would be the best one to use? And could you also help me with the settings that I should try once I select the best one?
Thank you again!…and again!!!
Superior Drummer 3 version: 3.2.7
Operating system: Windows 10
None of those options are good – use the drivers for your audio interface. What is the exact interface that you’re using? Anything other than the specific drivers for it are going to give you issues. As far as the samples on the same ssd – if it’s an NVME type drive that would be okay. Anything else might be an issue. I have a separate ssd that just has my system on it, another just for samples and one for session.
Partitions on an ssd are not necessary. As a matter of fact they can lead to issues. Separate drives for things are good when it come to making backups of your system. That way when (not if but when) a drive fails you only temporarily lose that one drive. Run off the backup until the bad drive gets replaced.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
I’m using a Motu M2. I’ve installed the drivers for it, so I don’t know if it just isn’t showing up in the menu for some reason. It is an NVME drive, also.
I’m using a Motu M2. I’ve installed the drivers for it, so I don’t know if it just isn’t showing up in the menu for some reason. It is an NVME drive, also.
MOTU stuff is good although their Windows support has in the past been a little sketchy. When you say it doesn’t show up in the menu are you talking about something in Reaper? Make sure that Windows isn’t trying to use the interface for it’s own sounds. Windows is notorious for not allowing sharing of an audio interface between system sounds and an audio program like a daw. If Windows IS using it that would be why Reaper might not see it. It’s a case of whatever sees the interface that grabs the use of it.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
Yes. A cable like that would allow you to record your clean guitar in one Reaper audio track with the monitor recording turned off, and listen to what you’re playing in real time by plugging the other output of the cable into a real amp. That would give you direct monitoring, no matter what kind of buffer for latency you’re using.
Check in your Reaper Audio Preferences. In the first pull-down menu you should see “ASIO”, and once you have selected that, BELOW you can select the ASIO driver you would like to use (you might see your previous ASIO4All and the MOTU ASIO driver among the choices in the pull-down menu). Take a look.
Does the motu have direct monitoring? Does it come with its own mixer? (Like RME or focusrite) if it does then you don’t need a splitter. Most audio interfaces allow monitoring before it goes through the DAW.
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
Does the motu have direct monitoring? Does it come with its own mixer? (Like RME or focusrite) if it does then you don’t need a splitter. Most audio interfaces allow monitoring before it goes through the DAW.
It’s confusing – the product page says the M2 has direct hardware monitoring but nothing is mentioned about CueMix which is the s/w that MOTU uses for some of their other interfaces that provides for I/O routing and direct h/w monitoring.
BTW – is there supposed to be some kind of graphic in post 2929082? I get a warning from Firefox that because of embedding Toontrack won’t allow whatever it is to show because of some security issue.
Jack
aka musicman691 on other forums
Superior Drummer 3.4.0
Area 33 1.0.0
Death and Darkness 1.0.1
PT 2021.6
OSX 10.13.6
3.46 GHz hex core 2012 MacPro 48 gig ram
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.