Re: [Traverso-devel] Routing concept

[Nicola Doebelin]

Am Samstag, 23. September 2006 17:19 schrieb Jonatan Liljedahl:
> Nicola Döbelin wrote:
> ...
>
> > I think AUX busses could easily be derived from tracks, as they are
> > basically stripped down tracks. Maybe you could add a flag to the track
> > object, something like 'is_aux_bus=true', and in case of 'true', disable
> > some features. I'll try to list some of them, but there may be more:
> >
> > - hide the record button / skip all recording-relevant code
> > - don't add AUX send ports / skip all AUX *send*-relevant code
> > - don't allow to connect anything to the input in the patch bay dialog
> > - instead connect all corresponding AUX send ports of all tracks to the
> > input (- lock the track view so as not to be able to move audio clips
> > onto the AUX track)
>
> I really think one should be able to send one AUX to *another* AUX. I
> often do that on my analogue mixing desk!

So you have AUX sends in you AUX return signal path? Never seen that before...

> Also, I always use real channels for aux returns, just so that I can
> send it to other aux'es and use the onboard EQ and such... For me,
> effects are just another soundsource as anything else on the desk, and I
> want the same control for them.

1. This is possible with the routing scheme I proposed, as the output of AUX 
busses can be routed to tracks, the main output, or hardware output channels.

2. Since an AUX bus provides the same processing capabilities as a track (as 
opposed to analogue desks), this shouldn't be neccessary. If you still want 
to do it, see 1.

Nic