The way I use busses for drums is completely normal. There's nothing remotely unusual about it. And the same for vocals, and guitars and so forth. And I believe I am usuing them for what they are designed for, which is to group the output of tracks so that they can be processed as a group. Putting redundant plugs with the same settings in order to get rid of overhead by freezing, to me, seems like a misuse of the system because of limitations.

I'll try one more time ... if you freeze a bus you can not change any of the tracks that point or send to the bus. Defeats the whole purpose of busses (as you said above).

You obviously aren't understanding what I'm saying. The busses would be grouped with the tracks that use those busses, and those busses would ONLY be available (via sends) to the tracks in that group. So the whole group can be frozen. You couldn't make changes to the tracks because they FREEZE WITH THE BUSS.


I mean a major point of DAWs is to improve the way we work over traditional schemes, and you wouldn't have to use it if you didn't want to. But it would make for a significant lessening of used memory for resources that are not required when the associated tracks (the only tracks that will ever use them) are frozen.

ORIGINAL: droddey

The way I use busses for drums is completely normal.

Is that why you avoid answering my direct questions?

ORIGINAL: droddey
You obviously aren't understanding what I'm saying. The busses would be grouped with the tracks that use those busses, and those busses would ONLY be available (via sends) to the tracks in that group. So the whole group can be frozen. You couldn't make changes to the tracks because they FREEZE WITH THE BUSS.

OMG! Have you used the existing Freeze function on a track? When you Freeze a track you can still CHANGE LEVEL AND PAN! That's what's great about Freeze. With your changes to Freeze you would take that away. Because if you Freeze a bus you can't allow changes to level and pan of the tracks associated with the bus. You can't have the Freeze function do two different things.

Can't believe I'm still replying to this .

Dude

Of course I've used it. I've made it plain that I'm suggseting an IMPROVEMENT to the system, not something based on how it works now. The point of this suggestion is to remove the overhead of busses when tracks that use them are frozen, and the point of the group is that you know that only the tracks in that group could ever access those busses. So it would obviously be something above and beyond how freezing works now. It would be more equivalent to a 'bounce and archive in place' type of thing, so something halfway between freezing and bounce+archive. So it wouldnt' require the maintenance of a separate set of tracks to which the various sub-busses are bounced, that would be handled automatically for you since that would be the purpose of this feature.

I was using the term 'freeze' because that's closer to what it would be than bounce+archive, in terms of convenience. But it's nothing like either of them exactly as they exist now.

Is that why you avoid answering my direct questions?

What question is that? If you mean why shouldn't I (and all the people who mix drums) use and manage redundant plugins instead of SONAR being improved to make that less necessary, I don't see the point of that.

Can you route the bus to an aux track then freeze it?

Not an option in 2008 when this thread was started. It would be better to create your own thread rather than drag up such an old one. Patch points and aux tracks did not exist in SONAR when this thread was created. At that time and now the answer is the same, bounce the bus. Currently it is possible to route buses to aux tracks or skip buses entirely and use aux tracks. Still aux tracks work like regular audio tracks without any clips in the track there is nothing to freeze. It is possible to create clips in an aux track by recording, just like a regular audio track.