MuTools racks and tracks...

[pljones]

What I was referring to is that if I have a Track with a Rack or a VST it seems to be the same thing. The same path. Is there a difference? Are there different hidden options based on these two specific way of using the track ?

It depends on the wiring.

If the VST is "loose" in a MUX, you can see this explicitly. Racks have "built in" wiring.

So if the VST is in a Rack, then its "outs" are wired to the rack and then follow the Rack's signal path. The target VST (effect) need not be in the top slot of the rack, either, of course.

The signal path within the Rack depends on several factors, including sends and where the fader insert is. If you send to a Rack, all of this matters, starting with the top slot.

( I'm still in M3 mode)

It's not really changed.

[MuTools]

Info tip: The signal flow in a rack is pictured on this page: http://www.mutools.com/mulab/docs/racks.html

[DHR53]

I fully understand how a rack works... I'd like right-click on a blank track to get a dialog for converting to audio, or instrument on the fly. I think the way everything works is obviously flexible but maybe not inutitive when coming from other DAWs...

[pljones]

I'd like right-click on a blank track to get a dialog for converting to audio, or instrument on the fly.

When you draw a part on a track, you get a dialog asking this. Slightly different workflow, same effect?

[janamdo]

When you draw a part on a track, you get a dialog asking this. Slightly different workflow, same effect?

Yes, but first you must doubleclick to get this .. that is not really intuitative ?
For my feeling ridiculaous..
OK with CTRL you get the pencil

[liquidsound]

What I was referring to is that if I have a Track with a Rack or a VST it seems to be the same thing. The same path. Is there a difference? Are there different hidden options based on these two specific way of using the track ?

It depends on the wiring.

If the VST is "loose" in a MUX, you can see this explicitly. Racks have "built in" wiring.

So if the VST is in a Rack, then its "outs" are wired to the rack and then follow the Rack's signal path. The target VST (effect) need not be in the top slot of the rack, either, of course.

The signal path within the Rack depends on several factors, including sends and where the fader insert is. If you send to a Rack, all of this matters, starting with the top slot.

( I'm still in M3 mode)

It's not really changed.

What I see is that if the Track targets the Rack with a VST in the first slot the flow goes as expected but if the Track targets the VST the flow follows the same path in the rack as well. No difference here and so it gets confusing for two things doing the same thing...

[pljones]

What I see is that if the Track targets the Rack with a VST in the first slot the flow goes as expected but if the Track targets the VST the flow follows the same path in the rack as well. No difference here and so it gets confusing for two things doing the same thing...

I don't see having two ways of achieving (nearly) the same thing is confusing. As far as I remember, there are subtle differences that are clear from the semantics. If you target the rack, you are addressing the rack, so automation tracks automate rack parameters. If you target a VST, automation tracks target the VST parameters. That's pretty clear?

[Trancit]

I fully understand how a rack works... I'd like right-click on a blank track to get a dialog for converting to audio, or instrument on the fly. I think the way everything works is obviously flexible but maybe not inutitive when coming from other DAWs...

Sorry, but this is a little bit short-sighted...

For the "older DAWs" like Cubase, Sonar, Logic and I think PT, who offer what you describe here, this fixed layout was always one of the biggest points of criticism...

Newer hosts have removed such restrictions and now it is to complicate to doubleclick...???

[liquidsound]

What I see is that if the Track targets the Rack with a VST in the first slot the flow goes as expected but if the Track targets the VST the flow follows the same path in the rack as well. No difference here and so it gets confusing for two things doing the same thing...

I don't see having two ways of achieving (nearly) the same thing is confusing. As far as I remember, there are subtle differences that are clear from the semantics. If you target the rack, you are addressing the rack, so automation tracks automate rack parameters. If you target a VST, automation tracks target the VST parameters. That's pretty clear?

Automation!
I didn't think of it. I just use it with the Rack as a target and I was wondering about the difference.
Thanks pljones