MuLab 7.0.47

[MuTools]

FR: assignable shortcut to close windows. (I would use esc). With buttons as tiny as mulab window management is one of the least ergonomic parts of the workflow. Also clicking the tiny fonts to get the vst window again.

Focused windows can already be closed by [Esc]. Note that in case of VST editors sometimes the vst editor keeps the focus and eats the [Esc] and so MuLab doesn't receive the [Esc].

[MuTools]

I have created some multisamples and saved them in a "MultiSample" folder I have created into the User folder. In the Mulab browser, if I choose "Multi-Samples" and "User Library", I don't see my multisamples...

Fixed in the next version. Thx.

[MuTools]

There is a new M7.0.11 in http://www.mutools.com/galaxa/

What's changed:

• Moved to Edit Front Panel button at the right of Show Modular Area button.
• Multi-Sample presets were not shown in the project browser. Fixed.
• Some MUX front panels showed a panel less width than the total width. Fixed.

How to update:
OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.
Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.

[pljones]

Just reading through the galaxa docs:

Most of MuLab's functionality is located in the context menus which popup when you right-click an object! You can never do something wrong by right-clicking somewhere. At the contrary: Try right-clicking every possible object on the screen and you may discover extra functionalities!

It might be worth rewording this because right-click now can be destructive - it deletes some things.

Also tiny typo I just spotted

...a lot of audio because the CPU has alost no time anymore to handle the UI.

Should be "almost".

Can the "Swing" knob have double-click to directly edit value added, please? (Mostly for consistency.)
Also, can the metronome have the three options (off, play+record, record only) added before "Edit Metronome Sound" on its right-click menu? (Heh, and metronome would be a fun use of step sequencer?)

... The output of a track goes to its target module. For a more detailed introduction, click here.

The "click here" doesn't go to a more detailed introduction to the composer, it goes to "mulab/introduction.html", the bullet list of features. There does need to be a "slower" introduction, explaining the concepts of track and part and the different track types. The existing page is fine as a "how do I" but doesn't explain "what is a".

... Then you have the choice for an Audio Part, a Sequence Part or an Automation Part (cfr Overview) ...

"Overview" links to "mulab/overview.html" which doesn't really supply any information of relevance or enhancement.

Tip: If you're used to other software with reversed behaviour, see this preferences doc page.

"preferences" links to "common/preferences.html" which doesn't mention any preference for that behaviour. It might be best just to say which preference to look for.

Can there be a method through the user interface to toggle how splitting works (cfr "Standard Copy Part Is Shared Copy" on/off behaviour) - seems awkward to need to go to settings, switch, come back, split, then remember what you left the preference at next time.

It might be helpful to move the "MIDI Channels" section to just after the "Sequence Parts", as it's related.

... You can also automate MIDI controllers, aftertouch and pitchbend. See the Composer info page for more details.

Yes, "Composer" is a link and yes, it links to "mulab/composer.html" rather recursively...

You can drag & drop audio files and MIDI files onto the composer.

... and what happens? Just add it creates audio part / sequence part? What happens if I drop a REX audio file? Or a MIDI file with multiple channels into a track with a single channel? Does it matter where in the Composer I drop ("+" sign, existing track, below the tracks)? (See "mulab/slicing-drumloop-samples.html" - "Also when dropping a short audio file on the composer, MuLab will slice it into a sliced sample part." - should be mentioned here?)

... But when you record the notes you're playing, i.e. the score, then you're recording the note events into an event sequence.

Mmm, "the score" isn't really clear. I'd suggest something like:
"But when you record which keys are pressed, how hard and how long for or which pedals are pressed, then you're recording events into an event sequence."

...Note that thanks to the modular structure you cannot only record audio inputs directly...

Minor typo "cannot only" should be "can not only" (i.e. positive, rather than negative ability, with negated exclusion rather than positive exclusion).

With MuLab you can easily use sampled drum loops, even if they have a different tempo than your current composition.

Nice pic of the Audio Lab but this page really needs to explain the interaction with sequence parts and the composer more visually.

The below picture demonstrates what you can do with the arrow and pencil mouse tools:

It might be clearer to have one picture but then comment on the differences for the pencil tool. As it is, the wording in the boxes on the picture is slightly inconsistent and makes a comparison tricky.

... you can also use multi-point envelope parts, see the composer doc page.

Should be "automation"?

...

I'm trying to limit my FRs to features that exist but don't necessarily appear to be in the right place... but this one is a real FR: can we have a "squeeze to fit range" function - if my selected controller values lie in 70 to 120 and I say squeeze to fit 80 to 100, then they're proportionally adjusted (so (((n - 70) / (120 - 70)) * (100 - 80)) + 80 in this case for each selected value n). I think I could work out the percentage and reference values but this would be easier to use.

mulab/pics/rackdesk.png

and

docs/mux/pics/rack.png

need updating for the new Rack on/off button. Doc for rack also needs this added. (Actually, lots of the screenshots need updating for M7 as a few things have changed visually.)

-- EDIT TO ADD: that's about it for the mulab/* pages, I think! --

[sl23]

Why is the Edit Front Panel white? Can it be changed to match other buttons please, it looks out of place. Not really sure why you moved it either, I thought it was fine where it was?!

[pljones]

It's not white for me?

And I guess the tool icon wants to be at the end because it's a menu rather than doing something immediately, like the other two. Sort of "everything else".

[sl23]

You haven't coloured your buttons then, it's white for me when all my buttons have been coloured a sandy brown colour.

I see what you mean about positioning, not bothered just curious, thanks for your answer though

[pljones]

Ah, no - I tend not to do much with the main theme colours. Sounds like you found a bug, though

[sl23]

Your graphic looks plain to me? But maybe you're right, a bug?

[MuTools]

@pljones: Thx for the doc feedback, i'll process that asap. (flu atm)

@sl23: Please post a screenshot of what you see. And/or try reinstalling M7 from its main package then applying the M7.0.11 update.

[pljones]

-deleted- Well, it was confusing... ctrl-click in MuX brings up the add module menu, so ctrl is actually toggling to pencil mode - which I hadn't realised... panic over...

[sl23]

Reinstalled - same thing happens.
I uploaded pic to dropbox as I don't know any image sites offhand.

[bibz1st]

Meanwhile, a possible minor bug. When copying a module in the MuX, I sometimes get a pencil cursor (which I don't think makes sense) --

I sometimes get this if I press and hold ctrl then right click to select but if done the other way round (right click then hold ctrl ) it doesn't happen.

[pquenin]

I created a Mux patch in M6, with a noise generator. In M7, this noise generator generate nothing, and I can't get it to generate something.
Is this a bug or I am doing something wrong ? It was OK in M6.

[Taifunk]

I created a Mux patch in M6, with a noise generator. In M7, this noise generator generate nothing, and I can't get it to generate something.
Is this a bug or I am doing something wrong ? It was OK in M6.

if you are inside the polysynth try to check if the noise generator is connected to event input