MuLab 9.0.59 App + Plugin

[MuTools]

Max 16 stereo inputs and max 16 stereo outputs.
So that's max 32 input pins and max 32 output pins.

[bbreakz]

Max 16 stereo inputs and max 16 stereo outputs.
So that's max 32 input pins and max 32 output pins.

Great thanks, will give this a go tonight

[WoF2302]

Hi,
I noticed under Windows 10 (64 bit) that there is a difference between MUX 8 and MuLab 9 in the step sequencer when a step sequencer output (A) controls another or multiple step sequencer input(s) (B).
In MUX 8 the loop runs through the step sequencer (B) and in MuLab 9 (plugin) the step sequencer (B) always stops at step 1 and the loop is not run through.

(--> Step Sequencer (A) -----> Step Sequencer (B) --->
I
I--> Step Sequencer (C) --->

Is it a bug or is it supposed to work that way?

Thank you

[MuTools]

Attention:
There seems to be a potential crash bug when doing Audio Setup in MuLab 9 App.
Researching this in depth and working on a fix.
Until the fix please first save your project before doing Audio Setup so to avoid loosing anything.

NB: I'll reply on other pending posts later.

[MuTools]

Hi,
I noticed under Windows 10 (64 bit) that there is a difference between MUX 8 and MuLab 9 in the step sequencer when a step sequencer output (A) controls another or multiple step sequencer input(s) (B).
In MUX 8 the loop runs through the step sequencer (B) and in MuLab 9 (plugin) the step sequencer (B) always stops at step 1 and the loop is not run through.

(--> Step Sequencer (A) -----> Step Sequencer (B) --->
I
I--> Step Sequencer (C) --->

Is it a bug or is it supposed to work that way?

Please post a MuLab 8 project file (.MuProject, zipped) or MUX 8 preset file (.Mux, zipped) that demonstrates the issue, thus a MUX with the step sequencer setup you mean and that plays differently when played in MuLab/MUX 8 and when played in MuLab 9. Thanks.

[WoF2302]

Here the *.zip file: download/file.php?mode=view&id=45176
Thanks for the help.

[MuTools]

MuLab App 9.0.34 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.34 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• Finetuned gridless event recording into the Live Matrix.
• When recording with a count down into the Live Matrix, then the focused scene automatically starts playing after countdown.
• Live Matrix: "Record Live Matrix" now also in the Live Matrix options menu. (before it only was in the transport record button options menu)
• MuLab App -> Audio Setup: When increasing the samplerate or buffer size this could lead to a crash. Fixed.
• MuLab Plugin: The MuxSynthNumStereoInputs/Outputs and MuxEffectNumStereoInputs/Outputs MainSetup settings are replaced by the "Plugin Edition Number Of Stereo Inputs/Outputs" preferences.
  Note that if you have changed the original values before then you need to re-set these preferences.
  Note that changing these preferences still needs a restart of the host DAW.
• MuLab Plugin: Improved behavior when the host is using "Always On Top" eg. Reaper -> View -> Always On Top.
• Color Picker: When GUI Scale was eg. 150% the color picker's layout was not right. Fixed.
• Other small improvements.

[MuTools]

Here the *.zip file: download/file.php?mode=view&id=45176
Thanks for the help.

Thanks for the MUX preset.
Researching & reflecting on this case.
I'll get back on this.

[Kalamata Kid]

When overlapping parts on a track can you hear both?

[MuTools]

When overlapping parts on a track can you hear both?

Yes.
But it's not recommended because it's difficult to handle GUI-wise.

[Kalamata Kid]

^^^
Good to see that when overlapping parts on the same track both are heard!
This is good news.
This will allow me to fade (x-fade) in/out each part independently.
I will enlarge the track so to handle the parts more easily.

[MuTools]

Hi,
I noticed under Windows 10 (64 bit) that there is a difference between MUX 8 and MuLab 9 in the step sequencer when a step sequencer output (A) controls another or multiple step sequencer input(s) (B).
In MUX 8 the loop runs through the step sequencer (B) and in MuLab 9 (plugin) the step sequencer (B) always stops at step 1 and the loop is not run through.

(--> Step Sequencer (A) -----> Step Sequencer (B) --->
I
I--> Step Sequencer (C) --->

Is it a bug or is it supposed to work that way?

Thanks again for reporting this.
It's an important aspect indeed, it's about how all composers, step sequencers, sequence player modules and any such future modules are being musically synchronized. That's a complex aspect certainly now that also the composer has become a module. Anyway, long story short: In the next M9.0.35 update the MUX patch you shared should sound the same as in M8 again.

[MuTools]

MuLab App 9.0.35 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.35 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• Improved synchronisation of linked step sequencers.
• Project Audio Input was not working anymore. Fixed.
• Project MIDI Output was not working anymore. Fixed.
• When dropping a MuClip on the Live Matrix, focus is shifted to the Live Matrix so that Play will start playing the Live Matrix.
• Other small improvements.

[dreammachine_nl]

Late to the party ; I just downloaded MuLab 9 App!

In the 9.0.35 App, I found a bug wrt to the Audio Track's Monitor switch. It should have 3 options: Off, Monitor When Enabled, Monitor Always. Monitor When Enabled (red) doesn't work correctly: it always monitors the Audio Recorder's input (like Monitor Always, green).

This is, I think, because the Record Arm button of the Audio Track is somehow no longer synchronised with the On/Off switch of the corresponding Audio Recorder module (i.e. when you click Record Arm, it doesn't change the On/Off state of the Recorder Module or vice versa). In Mulab 8 this does work correctly.

Another bug wrt the Project Audio Input module inside the Composer modular area: although, by double-clicking it, it shows the 'Select Audio Inputs' window, it doesn't put through any audio from the selected inputs. Instead this modules behaves exactly the same as the regular Audio Input module inside the Composer modular area. It even makes an input pin appear on the Composer module; it probably shouldn't do that.
Same goes for the Project Event Input inside the Composer modular area: it is indistinguishable from the 'normal' Event Input and behaves exactly the same (pin and all).

Cheers, TDM

[robert_p]

Hi, Is there any way to display Program Change message on the automation lane? I can see that all 128 cc controllers and plugin parameters are available for use, but Program Change works only with the list editor.