Need Simpler Way to Freeze/Record Session Drummer (or Other VI)

 I set up Session Drummer 3 with multiple outputs and multiple MIDI tracks; in other words, I will have a MIDI track and an audio track for kick, a MIDI and an audio track for snare, a MIDI and an audio track for hi-hat, etc. When I freeze, Sonar makes multiple passes through the song, which takes quite a while. Here are the problems: 1-there is too much trial and error setting the levels so that the frozen audio tracks are at the best levels and 2-the resulting audio tracks don't work independently of the MIDI tracks: soloing the audio solos the MIDI as well and I can't drag-copy the audio to a new audio track. This is way too much trouble and takes too long. Advice?

The first benefit is the separation and panning of drums giving it a full sound in the mix. He is then freezing them to save space I believe in order to cut down on cpu usage. Correct Konrad?

I am sorry I don't have advice on an easier way. Rome was not built in a day.

oK i AHVE READ WAY TO MANY FREEZE PROBLEMS,I use both midi and wav tracks for drums in session 3,
so far for what I have found ,1.your computer doesn't have enough memory,you need a min 0f 8gb,and a min i5 and a 7200 rpm HD. AND MoST IMPORTANT A REALLY GOOD INTERFACE.
 
All the lower price intterfaces..(drain to many resources from your computer) for a simple 2 in + midi the rolandusb25ex works well
But if you are like most people they want a min 8 in,I bought the tascam 1641 and it drain s like crazy(only open the ports in use.unless your recording a whole band 1 or 2 ports at a time .
 
Now I run a dual i7,with 32 gb of memory,160gb SSD drive as my primary ,1tb 7200 backup drive(esata)
Motu 828mk3 ,motu midi express 128, the 828 processes it self (can also run as a stand alone mixer) takes the drain of the computer.I sampled my drumers kit and use it in session..works great but as wav files the processing is huge.
 
unless you have a large computer setup, limit your drums to midi.don't record long clips just cut and paste.
 
as for other people complaining about freezes..this also applies.x1 pro is a great program but requires a pro rig with it or just linit to short clips .turn off what your not using(especially antivirus or maitenance programs)and the internet.
 
Gary
 
 

Sorry... still learning about this MIDI drum stuff. I think I see what you're doing now. You're just taking the separate MIDI tracks of all the kit pieces and turning them to audio files on their own tracks so they can be manipulated as such? I thought that kind of thing was easy but preferable to do in real time. Meh... I guess I'll find out myself soon enough. I'll be attempting exactly that very soon.

Hmm... I always kind of expected those wait times. However can't all the tracks be done at once? I'm genuinely curious here.

There is no benefit whatsoever in running separate Midi tracks for each kit piece.

When you insert SD3 (or any other multi output vsti), on the Insert Soft Synth Options page, select Midi Source and All Synth Audio Outputs: Mono

You can then direct each of SD3's kit piece channels in the Mixer page to any of the audio outputs exposed.

Delete any remaining tracks when you've finished. Convert any mono tracks to stereo if you want.

Right, freezing/bouncing.

If you choose to freeze the synth, Sonar will do one pass for each and every audio track and place the rendered audio into the clips pane of each track. The synth will be removed from active duty, but it's only a cvlick away to unfreeze it, make any Midi tweaks and re-freeze.

Right click the freeze button and go into Freeze options. I always make sure "Track Fx" is UNticked because at this stage, I haven't finished mixing.

If you choose to do a bounce to track, Sonar will make ONE pass and render down to brand new tracks. (if you have stereo tracks, you'll need to do these separately in a 2nd bounce) 

This will still leave SD3 live & active, so the first thing you'll want to do is to archive the tracks, or mute them, but if you want to conserve CPU/RAM, you'll have to disconnect it from the Synth Rack. The Browser needs to be undocked in order to reveal the Connect button.

If your bounce is slamming the way you're seeing, I'd check what you're using under Source Category in the Bounce to Tracks dialog. You'll never go wrong if you select Main Outputs.

Some people suggest using Entire Mix, but this can cause problems if you have tracks or busses routed to any additional output pairs on your interface. This caught me out when I first started because I run a dedicated Headphone buss and route this to output pairs 3/4. If you use Entire Mix in this situation, Sonar will sum all active interface busses together and your rendered mix will be 6dB higher for each & every active output pair.

Hope this helps

One thing you can do with Session Drummer 3 is, archive all the Audio Outputs that you don't want to freeze. This is very handy if you use the SD3 Templates that come with X1 as they set up all 12 audio outputs. I use those templates then move the outputs I don't use to their own folder and archive the folder. I do that in case I want to use one of those outputs later down the road. It's easier than setting up the output manually.

Archive also works nice for when you have to unfreeze a track, tweak it, then re-freeze it. Say you have kick, snare, 3 Toms, 3 Cymbals, all frozen and you need to fix something with one of the Toms. You can unfreeze just that Tom, tweak it, archive all the other drums/cymbals except the Tom you tweaked, then re-freeze just the Tom.

As for the volume differences, the only thing I can think of on that is, you are freezing using effects you have on the Master Bus or some other bus you may have the track routed to, and you are processing the frozen track through that bus a second time during playback.

Good luck.

konradh


 Freezing or bouncing is required before exporting as a WAV or mp3 (as far as I know).

Not necessary but a good idea if you are resource bound. Also a good idea before archiving project just in case the synths/fx are unavailable at some point in the future when the archived project is reloaded.

Also, Freezing is Not required pre-epxporting or bouncing. The synth will bounce during export. I usually freeze, but have accidentally left them on and they still make it. :)

Edit: Never mind misread the original post.. thought he wrote SD2 (sorry)  

Rail

2-that Fast Bounce is not lower quality

 
Nope, should be the same quality either way.   Just be aware that there is the time-based bounce bug in X1d, so if you're using any plugins that are set to use project tempo, a real time bounce still may be needed.