How to record Superior Drummer ....

[Toadwick]

I just migrated to Luna from Pro Tools and need to record drum audio from Superior Drummer (SD). Problem is I don't know how to set up the track sends. In Pro tools I'd create & name the tracks for individual parts (kick, snare, etc) and then assign Superior Drummer parts to those channels. In Luna I have created the tracks but can't get Superior Drummer to find them. Do any of you have experience in using SP to create drum parts? Suggestions are desperately needed. Thanks in advance.


jim

 

[LesBrown]

I just migrated to Luna from Pro Tools and need to record drum audio from Superior Drummer (SD). Problem is I don't know how to set up the track sends. In Pro tools I'd create & name the tracks for individual parts (kick, snare, etc) and then assign Superior Drummer parts to those channels. In Luna I have created the tracks but can't get Superior Drummer to find them. Do any of you have experience in using SP to create drum parts? Suggestions are desperately needed. Thanks in advance.


jim

Luna doesn't yet support multiple outs from virtual instruments.

My workaround is to record SD3 in Logic Pro and export separate midi tracks to Luna. Another option is to copy/past SD3 midi from one Luna track into as many other tracks as the kit needs, then delete the hits in each track that don't belong to that part. There are more threads here specific to SD3, that discuss other options until Luna gets multi-out support for VI's.

 

[squeakyanimal]

My approach is fairly simple: I keep SD3 as a stereo instrument until it’s time to mix. At that point I use the bounce to audio feature in the plugin to commit the part and drop all those files in to tracks. Done!

 

[slamthecrank]

The most simple answer to this is to do exactly what Superior Drummer's manual says to do:

Always use the "Bounce To Audio" feature inside of SD, locate those files after bounce, and drag them into Luna as audio tracks.

There are 2 reasons for this:
1) It saves time (it's very fast).
2) Your bounced audio will receive the full articulations etc. from SD (if you only use the SD instrument without Bouncing To Audio, you are not hearing or getting the full articulations from the "print"... especially if you are using it as a multi-out instrument inside your DAW. )

 

[MakerDP]

2) Your bounced audio will receive the full articulations etc. from SD (if you only use the SD instrument without Bouncing To Audio, you are not hearing or getting the full articulations from the "print"... especially if you are using it as a multi-out instrument inside your DAW. )

Hmm.... I'm going to have to look into this. So the VI does not sound the same as its printed audio?

 

[AlexR]

The most simple answer to this is to do exactly what Superior Drummer's manual says to do:

Always use the "Bounce To Audio" feature inside of SD, locate those files after bounce, and drag them into Luna as audio tracks.

Yup,
You can bounce all individually mics, and if you want the same processed sound you have in SD3, duplicate the SD3 track (so you can save your original set up) , go in the mixer page and assign the various SD3 tracks to individual outputs (kick, SN etc) then you can bounce the SD3 project by output and have the drum kit separated and already mixed

 

[rickwaters]

That's how I've been handling it.

 

[Neofolk]

UAD seems to not care about this. "we're playing the long game"& "Do you know how long it took Logic to..." It's absolutely unacceptable that multi-out vst isn't supported in 2023 (not to mention a handful of other vital features for modern composing). Those older DAWS were discovering what they could do vs. now we have the roadmap. There's no excuse other than they are stringing users along. I know it requires programming, but they certainly have the resources. Instead we get the daily emails of "don't miss this killer legend compressor deal". It's gross and I wish more users would speak up. As my grandmother would say, either shit or get off the pot.

 

[BeingHumans]

The most simple answer to this is to do exactly what Superior Drummer's manual says to do:

Always use the "Bounce To Audio" feature inside of SD, locate those files after bounce, and drag them into Luna as audio tracks.

There are 2 reasons for this:
1) It saves time (it's very fast).
2) Your bounced audio will receive the full articulations etc. from SD (if you only use the SD instrument without Bouncing To Audio, you are not hearing or getting the full articulations from the "print"... especially if you are using it as a multi-out instrument inside your DAW. )

And remember to check the phase on those tracks after you import them.

 

[Drjack69]

UAD seems to not care about this. "we're playing the long game"& "Do you know how long it took Logic to..." It's absolutely unacceptable that multi-out vst isn't supported in 2023 (not to mention a handful of other vital features for modern composing). Those older DAWS were discovering what they could do vs. now we have the roadmap. There's no excuse other than they are stringing users along. I know it requires programming, but they certainly have the resources. Instead we get the daily emails of "don't miss this killer legend compressor deal". It's gross and I wish more users would speak up. As my grandmother would say, either shit or get off the pot.

I don’t actually think they’re stringing people along. It’s been a much-requested feature since day one (when first released for Apollo). It makes sense that we like it and talk to our friends about it positively. But… what I do think is that in order to implement it, it’s a huge undertaking… probably requiring a heck of a lot of work. I’ve mentioned how I can only assume that it’s a massive headache to implement on here a few times and haven’t had anything other than I don’t think they anticipated how many people were like me and asked out loud “really? You don’t do that?”

 

[squeakyanimal]

Hmm.... I'm going to have to look into this. So the VI does not sound the same as its printed audio?

There is a setting that enables/disables all the mic bleeds. Back in the day when I first started using the SD line, I believe this was set to "disabled" by default in order to keep the VI from sucking up all CPU power. Thus when one bounced, the sound was a bit more "detailed" or "real" or whatever as the render included the mic bleed.

I'm not sure whether this is still the default; at some point when my machine got beefy enough I toggled to "enable," saved the settings, and forgot about it. But yes, if the bleed is disabled for real time VI listening, the printed track will be slightly different.

 

[Billy_bSLAYER]

I posted a while back how I go about SD/EZ recording, I have the standalone app output via cheap UMC1820 interface -> Optical Out -> then -> Apollo Optical In. Then in Luna I have the 8 Optical channel recording in real-time where I apply real mic techniques to process the signal as if using a real kit. This can be done using the standalone on the same machine or separate.

 

[AlexR]

I posted a while back how I go about SD/EZ recording, I have the standalone app output via cheap UMC1820 interface -> Optical Out -> then -> Apollo Optical In. Then in Luna I have the 8 Optical channel recording in real-time where I apply real mic techniques to process the signal as if using a real kit. This can be done using the standalone on the same machine or separate.

are you having the standalone app follow the MTC in Luna( and how were you able to accomplish that?) or just free rolling ?

 

[Drjack69]

I posted a while back how I go about SD/EZ recording, I have the standalone app output via cheap UMC1820 interface -> Optical Out -> then -> Apollo Optical In. Then in Luna I have the 8 Optical channel recording in real-time where I apply real mic techniques to process the signal as if using a real kit. This can be done using the standalone on the same machine or separate.

That’s a great workaround… that you shouldn’t have to do!

 

[hotspot]

Bounce to audio is simply the best practice, whether in Luna or anywhere else. Problem solved.

There are still some other VIs needing multi out, of course…

 

[Drjack69]

Bounce to audio is simply the best practice, whether in Luna or anywhere else. Problem solved.

There are still some other VIs needing multi out, of course…

For archiving stuff I agree. But unless your computer can’t handle it and you need to free up CPU, I don’t understand what you mean? Why would you print to audio unnecessarily? Genuinely curious.

 

[hotspot]

Why would you print to audio unnecessarily? Genuinely curious.

Ah, I see. It's just part of my workflow, depending on the process I'm working on. I work exclusively with audio tracks when mixing. Without exception.
For many reasons. The least of which is that it puts a pointless strain on my computer to have to work through virtual instruments in this step. It's more of a deliberate separation of steps, because I don't want to mess around with the sources anymore at that point, I just want to mix and finalize.
This is my way of organizing my work, which is important to me.

I even bounce production projects completely as audio, close them and create a completely new project for mixing.

 

[Drjack69]

Ah, I see. It's just part of my workflow, depending on the process I'm working on. I work exclusively with audio tracks when mixing. Without exception.
For many reasons. The least of which is that it puts a pointless strain on my computer to have to work through virtual instruments in this step. It's more of a deliberate separation of steps, because I don't want to mess around with the sources anymore at that point, I just want to mix and finalize.
This is my way of organizing my work, which is important to me.

I even bounce production projects completely as audio, close them and create a completely new project for mixing.

I can see your logic there. It’s certainly a way of concentrating on the task at hand. But I’m not sure it’s widespread practice. I could be wrong. Maybe I’m the only one who only does that when archiving stuff.

 

[hotspot]

But I’m not sure it’s widespread practice. I could be wrong

I don’t know for sure, but after messing around and mixing up steps for years, I found my way. And I know a few studio people doing it that way.

 

[AlexR]

I can see your logic there. It’s certainly a way of concentrating on the task at hand. But I’m not sure it’s widespread practice. I could be wrong. Maybe I’m the only one who only does that when archiving stuff.

It is a very common practice at least for me as well. Once a song is done all VIs gets bounced down into audio. Not just for archival or mixing purpose but because since 90s, and i had countless session with VIs going wonky when moved to a different system, or sent over by clients (sample libraries missing, VI settings changed, different plugin version, missing plugins etc) so yeah. print it to audio and save some grief