Another question regarding the send-behaviour of mulab.

[LYTZ]

Hey all,

here's another question regarding the send-behaviour of mulab.

When I double click in the rack and insert a send,
the slot of the rack where the send is inserted will get connected
to the (fx-)rack i sent it to in the session mux.

When I just connect the Audiosends (in the session mux) from a rack to the rack where I want to send it to,
nochting happens. Why's that?

It might be a good workaround for the whole send-issue a lot of people are complaining about
to let mulab insert a send into the rack automatically, when an audio send is connected via the mux.
It might still not be perfect, but doing it that way is at least way much faster than it is right now
and would nicely tie in with the modular architecture of mulab.

Is this technically possible in general?

Also: Can it be, that the racks somehow are MUX-Devices in itself?
That would explain the technical difficulties with the copy-sends-to-another-rack thing.

Best,

tL.

[mutools]

When I double click in the rack and insert a send,
the slot of the rack where the send is inserted will get connected
to the (fx-)rack i sent it to in the session mux.
When I just connect the Audiosends (in the session mux) from a rack to the rack where I want to send it to,
nochting happens. Why's that?

Cause that way is not supported. (yet)

It might be a good workaround for the whole send-issue a lot of people are complaining about
to let mulab insert a send into the rack automatically, when an audio send is connected via the mux.
It might still not be perfect, but doing it that way is at least way much faster than it is right now
and would nicely tie in with the modular architecture of mulab.

I understand. Will research what can be done.