Freezing Addictive Drums Sythns

[bmarlowe]

I am using Addictive Drums 2 (latest just updated today) for the first time on my current project. All has gone well. I am using a separate synth per drum simple instrument track. At this point I wanted to freeze the associated synths. For some reason I can't freeze them. Nothing bad happens, they just will not freeze. I have other synths running that freeze with no problem. Any idea as to what I may be doing wrong. - Thanks.

 

[Colin Nicholls]

I don't know why they are not freezing but that sounds like a sub-optimal way to achieve your end-goal. You really have a separate instance of AD2 per drum ?

Any reason why you are not using a single virtual instrument track for AD2, driving it by multiple MIDI tracks? Just one instance of AD2?

[bmarlowe]

Good question.

Previously I did it that way (track per drum instrument) with SI drums (and even before that with TTS-1 drums).  I saw a tutorial by Creative Sauce that set up AD2 that way in Cakewalk (he also showed the way you propose).  I like the complete flexibility it gives me to add any plugin I have to any drum instrument. I do appreciate that AD2 has its own built in mixer (as well as all kinds of processing that can be applied to individual drum instruments).

I actually added specific reverb plugins (running 100% wet) for the hi-hat and snare, with the reverb panned to specific places using the respective pan-pot in the Sonar console. Could I have done similar from within AD2, I guess probably. That said, freezing AD2 synths should work I think.

Edited 6 hours ago by bmarlowe

[Amberwolf]

How many outputs does AD2 have?  If it is like SessionDrummer (3?) and has 8, that covers many drumkits' (well, depending on your music type) with one stereo out per drum, allowing you to setup a set of tracks with one track per output pair and separate fx bins for each one.  I also sometimes setup 2(+) separate tracks with completely different fx chains for teh same drum or set of perc sounds, to mix/fade/switch between them for different parts of a song (there are easier ways, but this works).   That's how I set mine up when I use MIDI-driven drums.    (I often also use sliced up wave files of individual drum hits or pieces of "loops", in addition to or instead of that; these are setup in tracks the same way). 

 

If it's like SI drums and only has one output pair, then there's not much option besides multiple instances if you need to hear all the drums with their own FX live as you compose the drum tracks. 

 

 

Regarding freezing plugin issues--is it that it won't freeze at all, or that it doesn't work right when you do freeze it?  Soemtimes setting your freeze options to realitme instead of fast bounce fixes the latter. 

In my ancient SONAR (probably wouldnt' happen in modern ones?), very occasionally I have run into a problem where Sessiondrummer will go thru all the motions of freezing, and actually show waveforms on every track, right up till the last one  completes, and then they all go blank and there's no sound. When I look I find none of the wave files it just created still exist.  My workaround is to cancel *just* before the end but keep all the partially rendered audio.  I dont remember if I have done this with SD or not, but for problematic bounce-to-tracks for audio clips, I'll select just those tracks, and export those without any fx (and cancel just before the end and keep all the partially rendered audio if it fails too) and then just drag all those audio files into the tracks.   

Edited 5 hours ago by Amberwolf

[bmarlowe]

As I said, Nothing bad happens, they just will not freeze. Press the snowflake, nothing happens.

[Max Arwood]

5 hours ago, bmarlowe said:

As I said, Nothing bad happens, they just will not freeze. Press the snowflake, nothing happens.

It could be a routing problem check your ins and outs for each channel.