I just checked again...

It's called SidechainMixer...

I can supply a link to it from my Dropbox, but there may be a newer version and I don't know if the author wants me to distribute it though he did make it free...

If you can't find a link for it, let me know...

[edit]

Try this...

http://forum.cakewalk.com/FindPost/3164260

[end edit]

Thanks Keni, ol pal!

yorolpal
Yup...that would do it Craig but I don't know why you couldn't route a single tracks output to two different busses. You wouldn't be returning anything to the track. You'd simply be outputting the busses to your master.

Well, now I'm totally confused...a post-fader send is the track output because it is post everything - FX bin, ProChannel, etc. So create two post-fader sends to two different buses. Don't return anything to the track, just dump the bus outputs into the master. In what way is this not what you want to do?
 
Also note that the U and 4K compressors are already set up to do parallel compression internally, thanks to the wet/dry controls. So if you have the ProChannel, you're already covered.
 
If it's just a question of being able to control multiple track sends with a single control, then grouping would take care of that.

Yes Craig...that is what we want to do...we just want to able to pick or create two (or more) " busses" and NOT sends to route the audio of a track out to. We don't want to be limited to one BUS per track. It might all end up at the same place but it's how you get there that matters. I guess those of us who'd like to see this implementation (ala Reaper) don't really get the push back from those who know how to "make it happen" via a workaround in Sonar. Again...just another way to skin a cat. Which, really, is a horrible expression don't you think?

Ah, now I see what you're saying. You want to be able to set the track output SELECTOR to more than one bus. Because you kept saying track output I thought you meant the actual output that appears from the track, not the selector that assigns it.

Bingo! :-)

Yes... Horrible expression but well understood.

There are work arounds galore!

I'm sure there are things you do in Soanr that you might find needing work arounds in Reaper...

In the days of analog, not only could we send to multiple busses, but a common thing to have/do was creating mults which could be used anywhere... Inputs, subs, busses, outs...

Yes, you could create feedback loops.... Bad? Sometimes! ;-)

Using sends can sometimes be tedious as you may have written fader automation that you wish to feed the bus. So using s send means replicating the fader automation for the send... And keeping both modified as changes are needed...

Sending to two busses simplifies this...

There are also occasions when it would be nice to send to a second input... Again, yes it can cause problems, but that's a bit part of exploration and discovery...

SilkTone's little plugin can alleviate some of these situations as well as open more doors to ideas...

This is who deserves the thanks here! ;-)

I'm just the messenger.... Please don't shoot me!

Don't get me wrong... Even in analog some boards and some rooms had very different sets of abilities much as today's softwares do... The trick to me has always been to discover things and use the set of tools at hand to create the final goal...

More players? ...bounce machine2machine? ...more tracks?

I'm sure you guys get what I mean...?

Keni

The other thing that confused me was when you referenced old-school mixing consoles as what you wanted, because that's actually how SONAR works. The difference is that in the hardware mixers, the sends were hard-wired, and there was a fixed number of sends. When you pushed a track's bus button, it was the equivalent of using the send's drop-down menu in SONAR.
 
If you set up a project template in SONAR with six "hard-wired" sends, you'll see what I mean...the send's drop-down output assignment does the same thing as the bus assign button you used to push on the mixer's track strip.
 
Meanwhile, the sidechain mixer approach Keni mentioned will do what you want as well...seems a lot simpler than rewiring.

Anderton
Ah, now I see what you're saying. You want to be able to set the track output SELECTOR to more than one bus. Because you kept saying track output I thought you meant the actual output that appears from the track, not the selector that assigns it.

They really are synonymous...

The actual audio output of the track is being sent to the selected output... What's being asked for is the ability to route the single output of the track two more than one destination at that point.

If a console didn't offer it we all had mults which we fed the output to on a patch bay and it allowed us to then use the mult to send to two different places... Etc...

Word.