missing MIDI controller support in MuLab

[Hermu]

for entry level users MuLab is a nice and easy to use sequencer, controlled by mouse or MIDI controllers with limitations.

for semi professional or professional users, which want to use MuLab with much more tracks and MIDI controllers, the first good feeling will be lost, because MIDI controller configuration is to expensive and not always successful. Other Sequencer software on market have automatic MIDI controller configurations and allows to use different controllers.

i know MuLab is a one men show, but MIDI controller support is absolutely essential for advanced users.

[pljones]

I doubt the financial reward from the tiny comparative number of sales would justify the expense of re-prioritising things, though. It's usually better to market a product to a specific audience that to try to be a jack of all trades and master of none.

[Hermu]

I doubt the financial reward from the tiny comparative number of sales would justify the expense of re-prioritising things, though. It's usually better to market a product to a specific audience that to try to be a jack of all trades and master of none.

which means, no MIDI controller support in any time soon?

[MuTools]

I think you've chosen an inaccurate title for this topic, harming MuLab and the MUX, which won't be good for its future development.

MuLab and the MUX do support MIDI controllers. You can easily map a MIDI controller to any parameter, or even multiple parameters, even setting different value ranges for these parameters.

Besides that, you wrote:

for semi professional or professional users, which want to use MuLab with much more tracks and MIDI controllers, the first good feeling will be lost, because MIDI controller configuration is to expensive

Why?

Right-click parameter + tweak MIDI knob = done.
I don't call that expensive.

and not always successful.

When not?

Other Sequencer software on market have automatic MIDI controller configurations

You can save session and MUX presets that are setup as you like.

and allows to use different controllers.

MuLab supports up to 16 MIDI input channels. So if you tell your MIDI controllers to send on chan X and Y, you can use up to 16 MIDI CC devices. Not too bad. Even for a pro.

i know MuLab is a one men show, but MIDI controller support is absolutely essential for advanced users.

I won't say MuLab is perfect yet. Still many wishes indeed. Please see http://www.kvraudio.com/forum/viewtopic.php?t=357048

[Hermu]

I think you've chosen an inaccurate title for this topic, harming MuLab and the MUX, which won't be good for its future development.

MuLab and the MUX do support MIDI controllers. You can easily map a MIDI controller to any parameter, or even multiple parameters, even setting different value ranges for these parameters.

Besides that, you wrote:

for semi professional or professional users, which want to use MuLab with much more tracks and MIDI controllers, the first good feeling will be lost, because MIDI controller configuration is to expensive

Why?

Right-click parameter + tweak MIDI knob = done.
I don't call that expensive.

and not always successful.

When not?

Other Sequencer software on market have automatic MIDI controller configurations

You can save session and MUX presets that are setup as you like.

and allows to use different controllers.

MuLab supports up to 16 MIDI input channels. So if you tell your MIDI controllers to send on chan X and Y, you can use up to 16 MIDI CC devices. Not too bad. Even for a pro.

i know MuLab is a one men show, but MIDI controller support is absolutely essential for advanced users.

I won't say MuLab is perfect yet. Still many wishes indeed. Please see http://www.kvraudio.com/forum/viewtopic.php?t=357048

1. MIDI Controllers can send CC, CC on/off, Note on/off or SysEx
with MuLab only CC works
CC on/off is interpreted as pressing button twice
Note on/off can not assigned and plays only notes, because MuLab makes no differ between MIDI controller or MIDI keyboard

2. not working assignements
Fader 1, channel 1
Fader 2, channel 2
Fader 3, channel 3

workaround:
Fader 1, channel 1
Fader 2, channel 2 -> changed to "any"
Fader 3, channel 3 -> changed to "any"

faders with the same CC and different channels didn't work.

3. Parameter "Solo" can not selected

4. Direct assignement for "Mute" and "Solo" is not realised

5. MIDI controller support has MIDI out port to send commands to MIDI controller (e.g. motorfader, button light on/off)

6. after changing to a different MIDI controller all previous assignements must reassigned in each session! MIDI controller remapping could be a solution.

[MuTools]

Thanks for the detailed list. I'll check things and reply asap, also on http://www.kvraudio.com/forum/viewtopic.php?t=360576 Talk soon.

[MuTools]

1. MIDI Controllers can send CC, CC on/off, Note on/off or SysEx
with MuLab only CC works
CC on/off is interpreted as pressing button twice
Note on/off can not assigned and plays only notes, because MuLab makes no differ between MIDI controller or MIDI keyboard

You can map any MIDI CC + Aftertouch + Pitchbend to parameters.
Being able to map MIDI Notes to parameters is a new request. I've added this on the wishlist. Note that it's not a 'quicky' to realize and i'll evaluate how many users want this.

2. not working assignements
Fader 1, channel 1
Fader 2, channel 2
Fader 3, channel 3

workaround:
Fader 1, channel 1
Fader 2, channel 2 -> changed to "any"
Fader 3, channel 3 -> changed to "any"

faders with the same CC and different channels didn't work.

There indeed was a practical problem there. I've tuned some things and a new version M4.4.7 will be available soon.

3. Parameter "Solo" can not selected
4. Direct assignement for "Mute" and "Solo" is not realised

Mute and Solo are not parameters.

5. MIDI controller support has MIDI out port to send commands to MIDI controller (e.g. motorfader, button light on/off)

After having read that other topic about this too, i've added this to the wishlist.

6. after changing to a different MIDI controller all previous assignements must reassigned in each session! MIDI controller remapping could be a solution.

If you want to save e.g. a VST + its mapped MIDI CCs, you could wrap it into a MUX and save it as a MUX preset.

[MuTools]

There indeed was a practical problem there. I've tuned some things and a new version M4.4.7 will be available soon.

MuLab 4.4.7 is available as an application patch in http://www.mutools.com/mulab/cedar/

How to install:

* Download the relevant app patch zip file for your platform.
* Extract the new app file.
* Copy this new app file into your current MuLab folder, thereby overwriting the current app file.

Mapping MIDI CCs on different channels to parameters of a single-timbral module/plugin should work fine now.

[> DiGiT <]

where did this guy go? is he still interested in his requested feature? it seems he stopped in to flog your program and then disappeared. i would say he really got your attention somehow! even so, i must say that was a quick turn around. was he paying you an hourly wage for a custom feature request? well we all have better midi cc support now, so i guess its a moot point.

[megalodonnl]

where did this guy go? is he still interested in his requested feature? it seems he stopped in to flog your program and then disappeared. i would say he really got your attention somehow! even so, i must say that was a quick turn around. was he paying you an hourly wage for a custom feature request? well we all have better midi cc support now, so i guess its a moot point.

Just say ur pro

[MuTools]

3. Parameter "Solo" can not selected
4. Direct assignement for "Mute" and "Solo" is not realised

Mute and Solo are not parameters.

I must correct myself: The mute of a Mixer Strip is a parameter and thus it's automatable and MIDI CC mappable.

I just noticed it's not in the right-click mute context menu though (taken note) but you can map it via right-click somewhere else on the mixer strip or on the rack -> Map MIDI Controller -> then select the child mixer strip as the target module.

[Hermu]

3. Parameter "Solo" can not selected
4. Direct assignement for "Mute" and "Solo" is not realised

Mute and Solo are not parameters.

I must correct myself: The mute of a Mixer Strip is a parameter and thus it's automatable and MIDI CC mappable.

I just noticed it's not in the right-click mute context menu though (taken note) but you can map it via right-click somewhere else on the mixer strip or on the rack -> Map MIDI Controller -> then select the child mixer strip as the target module.

yes i know but i can't use it, because my controller only supports CC on/off or Note on/off. Which means press "Mute" button - mute is on, release "Mute" button - mute is off.

[MuTools]

Yeah i know what you mean, it's the same issue as with the MIDI shortcuts we had some time ago. I'll see what i can do i.e. if there is a quick way to support 'button' CCs. Can't do MIDI notes -> parameters mapping on short term though, sorry, taken note about that on the WL.

[MuTools]

Ok, so the problem is that certain MIDI devices sent out their buttons as MIDI CC value 0 = off and value 127 = on and when you map that MIDI CC to a mute it will go on when you press the button and off when you release the button, right?

Question 1: Can't you program your MIDI device so the button switches between on and off with each press?

Question 2: Does anyone have tips for me how this is well handled in other apps?

[sl23]

With regards Q1, you have a Novation SL MkII if I remember correctly, does that do as you described? Afaik the Impulse doesn't do that. Actually, I regret getting the Impulse and wish I'd bought my original choice of the SL MkII.