=== MUX Request List ===

[AndreasD]

1) keysplit module. A module that receives all notes and only let through notes inside a definable range.
2) The same for modulation data. A module that only passes through data that is in a definable range
3) Polysynth Mono mode
4) a (resizable) meter for the front panel to show internal levels
5) open multiple sequences and see all notes in one piano roll editor. The events of the selected sequence are editable
6) midi recorder
7) possibility to start the multipoint envelope at the next beat/bar

[VariKusBrainZ]

A basic step sequencer (assuming my modular midi FR isnt on the cards)

At the moment there is no way to generate a note on message with MUX, or am I wrong?

[sl23]

No3 that's what I meant by monosynth.

No4 good idea, like it.

Like the basic step seq too!

[skitchy]

Crossover module (frequency splitter).
1 in 2 out with a single knob for the split frequency (possibly another for db slope selection). It would make things neater and easier.

Repeated here from another thread - wasn't sure if I'd just missed it.

[hibidy]

A way not to have the "mixer" go behind everything thus having to click more than a couple of times to find it again? I guess this could be a docking thing or an always on top thing, etc.

[> DiGiT <]

m5 we are told will include focus on navigation management tools like a dock/browser or some such direction pending jo's research into what is best i assume.

[MuTools]

A way not to have the "mixer" go behind everything thus having to click more than a couple of times to find it again? I guess this could be a docking thing or an always on top thing, etc.

What "mixer" do you mean? Do you mean the main MUX Vst window being obscured by its child windows?

[sl23]

I'd've thought the mixer in mulab as I have that problem too. Whilst working on mux stuff I can't get to the mixer easily to change a preset or add one as its hidden. Actually I suppose this would apply to the mux VST too as it'd hide any daw .

[hibidy]

A way not to have the "mixer" go behind everything thus having to click more than a couple of times to find it again? I guess this could be a docking thing or an always on top thing, etc.

What "mixer" do you mean? Do you mean the main MUX Vst window being obscured by its child windows?

(sorry I don't have the terminology correct) but the little mixer add ons inside the mux. They are small and easily lost.

Also, if there is not a way to do this, a way to have all the mixer modules docked together

[sl23]

I have a new request, I added it to my first post as request number '16'. Basically about adding Group Frames within Frames.

And another at '17' for Group select.
More here

[braj]

In Studio One the default name for a MUX channel is 'MUX (vst synth)' but the mixer displays all MUX channels as 'Left 1' for whatever reason, if there were any way to have the names match it would be better. Right now I have to rename both. All other plugins correctly name the mixer channels by the VST name.

[braj]

It would also be nice if any control that exists on the front panel is seen by the host as an automatable parameter. This would really really help IMO streamlining workflow considerably.

[memyselfandus]

Something like the logical editor?

[Caco]

It would also be nice if any control that exists on the front panel is seen by the host as an automatable parameter. This would really really help IMO streamlining workflow considerably.

+1

This is an important one for me so that I can control parameters in realtime.

[MuTools]

It would also be nice if any control that exists on the front panel is seen by the host as an automatable parameter. This would really really help IMO streamlining workflow considerably.

I'm afraid that's technically not possible, as far as i see now.
You'll need the meta-parameters for that.