Beta D idea
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
I am very excited about working in the modular plug area. Being able to create a mixing environment by using the embed featur together with Mux and Musynth is really an incredible prospect: you can make the relevant controls all visible in the plug area - this can really help keep complex mixes under control I think! congratulations on very fresh thinking.
One difficulty I have though is keeping track of which parts are feeding which modules: I know I can "view all inputs" from the context menu but I am wondering if there mightn't be a more immediate or visible way to see the connections.
One idea: would it make any sense to be able to put parts also in the plug area: so you could have a part module feeding a musynth - tab to view its editor - command-tab to reveal the part in the composer?
Also a thought: it would be great when you have racks in the modular plug area to see their sends represented somehow.
One difficulty I have though is keeping track of which parts are feeding which modules: I know I can "view all inputs" from the context menu but I am wondering if there mightn't be a more immediate or visible way to see the connections.
One idea: would it make any sense to be able to put parts also in the plug area: so you could have a part module feeding a musynth - tab to view its editor - command-tab to reveal the part in the composer?
Also a thought: it would be great when you have racks in the modular plug area to see their sends represented somehow.
-
- KVRAF
- 1645 posts since 24 May, 2002
But what about the timeline?semiquaver wrote:I am very excited about working in the modular plug area. Being able to create a mixing environment by using the embed featur together with Mux and Musynth is really an incredible prospect: you can make the relevant controls all visible in the plug area - this can really help keep complex mixes under control I think! congratulations on very fresh thinking.
One difficulty I have though is keeping track of which parts are feeding which modules: I know I can "view all inputs" from the context menu but I am wondering if there mightn't be a more immediate or visible way to see the connections.
One idea: would it make any sense to be able to put parts also in the plug area: so you could have a part module feeding a musynth - tab to view its editor - command-tab to reveal the part in the composer?
A part needs a timeline...
Nice point. But not immediately sure how to implement this (quickly).Also a thought: it would be great when you have racks in the modular plug area to see their sends represented somehow.
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
a part could appear with a time ruler above its upper edge perhaps ? Maybe there is a better solution, but my fantasy would be to be able to hang out in the modular plug area. or at least a way to see right away which parts are feeding which modules.
-
- KVRAF
- 1645 posts since 24 May, 2002
Something which pops up in my mind: when you select a plug, all parts in the current composition that target that plug are automatically selected.semiquaver wrote:a part could appear with a time ruler above its upper edge perhaps ? Maybe there is a better solution, but my fantasy would be to be able to hang out in the modular plug area. or at least a way to see right away which parts are feeding which modules.
Just like selecting a part focusses its target.
But maybe this could also be unwanted/annoying behaviour?
What do you think?
-
- Hun #3
- 4260 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
sounds like a good workaround to me (I've been thinking about the 'have to select a part to target a synth' problem too) ...
You could also use it as an analysing/navigator tool of sorts ("what synth is where in my song?"). At least I couldn't see how it would be an annoyance or slow things down.
Marco
You could also use it as an analysing/navigator tool of sorts ("what synth is where in my song?"). At least I couldn't see how it would be an annoyance or slow things down.
Marco
-
- KVRAF
- 1645 posts since 24 May, 2002
I think you're right. It shouldn't hurt as default behaviour.Bonteburg wrote:sounds like a good workaround to me...
You could also use it as an analysing/navigator tool of sorts ("what synth is where in my song?"). At least I couldn't see how it would be an annoyance or slow things down.
At the contrary: it will make MU.LAB more easy, transparant, understandable
So will do.
I think this is a separate topic.I've been thinking about the 'have to select a part to target a synth' problem too
In fact, you don't have to select a part to play a synth.
E.g. You can just plug in a synth in a rack and it's immediately playable
Or if already plugged in, just focus it by left clicking it, or via its context menu -> "Focus".
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
That would be great I think!when you select a plug, all parts in the current composition that target that plug are automatically selected.
Just like selecting a part focusses its target.
- KVRAF
- 7137 posts since 8 Feb, 2003 from London, UK
Me too!semiquaver wrote:That would be great I think!when you select a plug, all parts in the current composition that target that plug are automatically selected.
Just like selecting a part focusses its target.
-
- KVRAF
- 1645 posts since 24 May, 2002
Alrightpljones wrote:Me too!semiquaver wrote:That would be great I think!when you select a plug, all parts in the current composition that target that plug are automatically selected.
Just like selecting a part focusses its target.