MU.LAB terminology: Targets

[liquidsound]

How about: "Connect To" which is also in the MPA and it is really what you are performing when you choose a Target.

[Branis]

Player sounds confusing to me. Target is more generic as you could be selecting:

Synth
Effect
Rack Mixer Strip
etc

Agreed, I can't really think of a mixer strip as of a player.

How about: "Connect To" which is also in the MPA and it is really what you are performing when you choose a Target.

I like this idea, sounds very logical and intuitive.

[MuTools]

I've been reflecting a bit more on this.

Now while writing the docs, i realize we need a general term for the 'plug-in' object anyway. (that's what i meant with: we need a noun, not a verb, though i do like the easy-sounding "Connect To" idea)

For example, when describing the MPA, the docs say: "Double-click the background to add a new X." In the M2 docs, the word 'plug-in' was used.

But from M3 on i would rather go for these terms:

Module = the generic word for the object that generates and/or processes sound/midi.

Plug-In = extern 'modules' e.g. VST plug-ins. Each plug-in is a module, bit not each module is a plug-in.

Device = MU.LAB own 'complete' modules like Synthia, Sampla, MuVerb, ...

The word 'Target' is not really matching in the sentence "Double-click the background to add a new target." (or does it?)

So a rack, a rack's mixerstrip, a VST plug-in, a ReWire plug-in, Synthia and MuVerb are all modules, and are all part of the modular game. The word module is quite well know, implicits the modular architecture and was also used in the hardware synth/effect world. So all good points for 'Module' imho.

What do you think?

I don't want to exaggerate the importance of this, but we need a basic well defined terminology, otherwise, when using terms at random, things can become more confusing.

Looking forward to your thoughts.

[MuTools]

The word 'Target' is not really matching in the sentence "Double-click the background to add a new target." (or does it?)

Anyway, the word 'Target' does not describe the musical-object-that-generates-and/or-processes-sound-and/or-midi very well. 'Target' may be a bit too generic. Maybe that's also why it's a bit confusing for (some) newbies. Target what, where, who? The word 'module' is a bit more accurate description, certainly taking the habits of the (hardware) sector into account e.g. sound module, effect module, ...

Just thinking.

[liquidsound]

I understand you want a Noun rather than a Verb but you could use both appropriately where needed...

Here some more suggestions:

"Assign To" or "Assign..."
"Plug To"
"Flow To" (this one is baaad)
"Connect To" or "Connect..."
"Output To" or "Output..."
"Route To" or "Routing..."
"Link to" or "Link..."
"Map to"


If you say "Create or Add" than it doesn't sound right if to a Rack or Strip because you are actually Connecting/Routing to.... while Creating/Adding an element, that it's not there yet, it make sense...

"Choose Output" convey a sense of Flow and Direction and it is not committed to something already there or about to be created.

Even in Modular synths the main thing is Output/Input/Target/Routing etc.

Maybe you have to use a Verb and a Noun...

Target has been working so far but M3 may (WILL ) take you in the Big Arena and you are right, you need a more approachable set of terms for the forthcoming audience.

[liquidsound]

If you say "Create or Add" than it doesn't sound right if to a Rack or Strip because you are actually Connecting/Routing to.... while Creating/Adding an element, that it's not there yet, it make sense...

I am correcting myself here because in the MPA it does make sense because you really "Adding to" or "Create into" the MPA, while from a Track it is not just Creating or Add but also Connecting to or Outputting to or Targeting.

So we have "Signal flow" and "Elements" creations...How can we cover these two aspects with just one word?

[Nielzie]

Maybe a VERY SHORT introduction could be given at the first use of MuLab splash screen with the fundamental "Gems" of MuLab.
Very brief and to the point. Maybe with a button saying "Got It! Let's begin"

Yes, i'm thinking about that too.

Like "Do you want an intro on using MU.LAB?".
If yes, then it will open a tutorial webpage with a basic tutorial (movie).

I think that's a great idea!

[MuTools]

I'm close to deciding to use:

Module
Device
Plug-In

as defined in my previous post.

So Module is the main word.

I understand you want a Noun rather than a Verb but you could use both appropriately where needed...

Here some more suggestions:

"Assign To" or "Assign..."
"Plug To"
"Flow To" (this one is baaad)
"Connect To" or "Connect..."
"Output To" or "Output..."
"Route To" or "Routing..."
"Link to" or "Link..."
"Map to"

You're right, we indeed also need a verb for the 'part -> module' action.

Personally i would go for this sentence:

"A sequence part sends its events to its target module".

So this gives:

Track/Part context menu -> "Choose Target Module"
"Target Module Set By Track"
"Choose MIDI Clock Output Module"
"Double-click the background to add a new module"
Modular editors: "Connect module x to module y"

Does that sound logical + intuitive to you?

[liquidsound]

It is definitely more explanatory than just "Target".

From an old user stand point it may sound too elaborated and it's understandable because MuLab users all know, by now, what Target is and how MuLab works, for sure.

In fact, if it was for us, we could leave things as they are but...
MuLab is really an exceptional DAW and we must think for the future and conforming to the world out there is important also.

I have been working with M3 and let me tell you: it is really an amazing music tool (Lab )and you'll see, eventually you'll be busy dealing with all kinds of new customers and new demands.
So I think you are right in beginning to be more out there especially with more standard definitions.

More users opinions needed.... any one out there?

[Improviser]

You're right, we indeed also need a verb for the 'part -> module' action.

Personally i would go for this sentence:

"A sequence part sends its events to its target module".

So this gives:

Track/Part context menu -> "Choose Target Module"
"Target Module Set By Track"
"Choose MIDI Clock Output Module"
"Double-click the background to add a new module"
Modular editors: "Connect module x to module y"

Does that sound logical + intuitive to you?

Well, although we've become familiar with "Target", etc, I think that your sentence:

"A sequence part sends its events to its target module"

so perfectly describes what's going on that we (and new users) probably do need start trying to get used to the items that stem from it (Track/Part context menu -> "Choose Target Module"; "Target Module Set By Track", etc, as above.

Les J.

[MuTools]

I've pulled the trigger.

[TheGuysanIdiot]

Hi All,

Sorry I am a bit late on this.

Modular Theme gets my vote.

Module = All components (collective term)

Plug-In = A Third party FX/Instrument

Device = An In-House FX/Instrument

All that is needed is Docs/Texts/Videos explaining terminology for Newbies and users moving from another DAW.

These are my thoughts after reading all that has gone before and taking best bits from all. IMHO.

OZ

[liquidsound]

Wouldn't it be a little better to keep everything as a Module?
And then perhaps in the Context Menu expand on terms?

Not easy to keep it Simple but Flexible....

[liquidsound]

I've pulled the trigger.

Was that loaded or Russian Roulette?

[pljones]

I'm so late all I can say is "I agree" .