Hi! I'd like to know if it would be possible in future updates to make the MIDI clips to audio process faster? Especially for midi tracks routed to Kontakt. For exemple, if I want to bounce a violin midi clip routed to Kontakt, I have to select both the midi track and the Kontakt track, then I have to click on the track tab, then I have to click on render track option which opens up a menu, then I must specify that I want to bounce the clip. In S1 for exemple all you have to do is to click on the midi clip and hit ctrl+b, it's so fast and intuitive. Any plans to integrate something similar in an upcoming update?

I don't know whether you're using a version of SONAR that was released since synth recording was introduced, but I don't use simple instrument tracks so I just record-enable the instrument's audio track and the MIDI track when recording. Then after recording the part, I already have rendered audio as well as MIDI without having to do anything else. This is also good for backup, and of course, sometimes you want to make some edits that are easier with audio than with MIDI.
 
However you can also simplify your current process. You can assign "Bounce to Track" as a keyboard shortcut (ctrl+B is unassigned with the default keyboard shortcuts, so you can use that if you like). Create a Preset that sets up the dialog box the way you want for bouncing. The preset will persist until changed, so if you're bouncing a bunch of Kontakt tracks, all you'd need to do after selecting the audio and MIDI tracks you want to bounce is hit Ctrl+B, then Enter.
 
 

I'm using the latest Sonar Pro version. Thanks for the keyboard shortcut tip, I'll try that out!

Cool! But don't overlook synth recording - the "Friday's Tip of the Week" for Week 84 discusses how I also use it with songwriting.

You can just click the freeze button and it will render it to audio and free up your RAM in 1 click.

I use this function all the time and have set up a bounce to track shortcut,  but I get what you are saying! Having to select both the audio and synth track seems unnecessarily convoluted.  One small change that would make a big difference would be to have Sonar assume that when you select a midi track and choose 'bounce to track' it should use the VST synth out to which  the track is routed. I could be wrong, but I can't see any situation where this would not logically be the case.
 
 

tenfoot
I use this function all the time and have set up a bounce to track shortcut,  but I get what you are saying! Having to select both the audio and synth track seems unnecessarily convoluted.  One small change that would make a big difference would be to have Sonar assume that when you select a midi track and choose 'bounce to track' it should use the VST synth out to which  the track is routed. I could be wrong, but I can't see any situation where this would not logically be the case.
 

But what if there are multiple MIDI tracks routed to that synth?   I wouldn't want to "disable" those other MIDI tracks by essentially freezing the synth.   Unless there's some way to bounce that specific MIDI+Synth combo to an entirely different track altogether... 

stevec

tenfoot
I use this function all the time and have set up a bounce to track shortcut,  but I get what you are saying! Having to select both the audio and synth track seems unnecessarily convoluted.  One small change that would make a big difference would be to have Sonar assume that when you select a midi track and choose 'bounce to track' it should use the VST synth out to which  the track is routed. I could be wrong, but I can't see any situation where this would not logically be the case.
 

But what if there are multiple MIDI tracks routed to that synth?   I wouldn't want to "disable" those other MIDI tracks by essentially freezing the synth.   Unless there's some way to bounce that specific MIDI+Synth combo to an entirely different track altogether... 

I'm talking about the bounce to track function  SteveC - it has nothing to do with freezing the synth. Bouncing to an entirely different track, as you describe, is precisely what it already does. The synth remains active and untouched.
 
Ironically, there is already no need to select the source midi track if you a ARE freezing a synth. but you have far less options in the bouncing process and face the very limitation you mention. 
 
I am pretty certain there Is absolutely no advantage to having to select the downstream synth track as well as the midi track when using the bounce to track feature on a midi track. It just seems to be one of those legacy limitations from days long since past. That said, it is by no measure a show stopper:)

tenfoot
I am pretty certain there Is absolutely no advantage to having to select the downstream synth track as well as the midi track when using the bounce to track feature on a midi track.

What if multiple instruments in a multitimbral synth are all listening to the same track?

Anderton

tenfoot
I am pretty certain there Is absolutely no advantage to having to select the downstream synth track as well as the midi track when using the bounce to track feature on a midi track.

What if multiple instruments in a multitimbral synth are all listening to the same track?

Hmmmm...fair call, but that's a whole lot of inconvenience for a rare exception. By all means include a check box for the upcoming 'set midi bounce by track output' option so that it can be disabled in the event of an Anderton exception:) Everyone's a winner!
 
To be clear, this is by no means anything I consider a priority fix. I was just agreeing with the OP that it could be simpler.