Please make MUX Modulars Presets conform to VST PGC Standards

[docbot]

MUX is such a great tool, but it's missing out on a simple, but essential feature that would make it increadible for live performances.

It's presets can't be changed via Midi Program Control Messages and Presets don't get reported to the VST interface in the DAW (Sylenth1 does this very well btw).

if I could simply load up a new patch for a track by sending a Midi Program Change MSG it would be such a game changer for performing live. No need to touch the laptop, load a new song in the daw, everything could flow uninterupted while keeping play on, you could keep a Bassdrum going and just lower the volume fader of the channel MUX is on, while it loads a new patch. And since MUX has multiple outs and can host multiple VSTs you don't have to waste any CPU resources having multiple tracks in one Live/Bitwig/Whatever session, you just keep your note data seperate from your VSTs in MUX and change the MUX Modular Patch via a simple touch of a button that triggers a Midi Program Change Message.

<3 please please please make this possible

[pljones]

How does this work with hierarchical patch organisation? How do I pick a user patch I've written that no one else has?

[docbot]

well usually Midi Program Changes just send a number to the synth/instrument which defines what patch to load

one way to do this without changing the whole mux/mulab preset system is just to say Factory Presets are on Bank 1 and every folder within the factory presets is a subbank.

Bank 2 would be the User presets folder with every folder in it being a subbank

there are 128 possible banks, each with 128 sub banks, each with 128 presets possible.

Right now, since Mux doesn't adhear to Midi Program Change Messages at all, it can have folders within folders within folders etc.. That wouldn't be possible since there can only be banks > subbank > preset

another way would maybe be to put a second preset manager that's exclusively for Midi Program Changes changes into mux. So there could be a new "save as midi program preset / save to midi program preset matrix" which would put a preset in sort of bank table that's recallable by midi program messages.

[pljones]

If it was going to work, I think the idea of having a user defined mapping might be best - not portable between installs but at least usable. You don't want to break everyone's way of working just for a feature like this which only some want.

[docbot]

If it was going to work, I think the idea of having a user defined mapping might be best - not portable between installs but at least usable. You don't want to break everyone's way of working just for a feature like this which only some want.

yeah, but it's not really an esoteric request, more like presets in vsts are supposed to work anyway.

[pljones]

You're basically saying there can only be one way to organise things. That's rubbish. What if I want to work differently because it suits the projects I'm working on? I define my own patches. Why can't I decide how they're organised just because you think things should work a specific way?

[MuTools]

Docbot, please note that even if it would be possible to load a MUX preset via a MIDI event, it could take a bit of time to load that preset, eg. when many samples have to be loaded or when many VSTs have to be instanciated. In certain cases that could take up to several seconds or more! So i hope you're not thinking that would be an instant action.

For live use pls note that you can open several projects at the same time. So what about loading projact A and perform it live and meanwhile already load the next project B in the background so you can switch quite instantly to it and then replace project A by your 3rd live project so it's ready to switch to when you have finished live performance of project B. And so on. A -> B -> A -> B -> ...

[docbot]

Docbot, please note that even if it would be possible to load a MUX preset via a MIDI event, it could take a bit of time to load that preset, eg. when many samples have to be loaded or when many VSTs have to be instanciated. In certain cases that could take up to several seconds or more! So i hope you're not thinking that would be an instant action.

For live use pls note that you can open several projects at the same time. So what about loading projact A and perform it live and meanwhile already load the next project B in the background so you can switch quite instantly to it and then replace project A by your 3rd live project so it's ready to switch to when you have finished live performance of project B. And so on. A -> B -> A -> B -> ...

thanks for your answer I am aware that this can take quit some time depending on the patch size and complexity, but it's quit easy to hide in a live context, you could just have a drumloop sample running or reverb effect while the new preset loads.

If it was possible, I'd actually still do a A -> B -> A -> B approach. The problem is more that without Midi Program Change implemented it's not possible to do this without touching the software gui. I would rather send a Midi Program change message from a hardware sequencer on a specific midi channel to do the loading.

hope this makes sense

[pljones]

Personally I'd like a way to enable/disable MUX patches based on MIDI control - I think that would be far more flexible and faster. Load the project, wait for the loading time, use MIDI control to select which part of the project actually incurs CPU usage to process events. This way the user has control: they configure each project as fits best to their needs.

[jackxavier]

mux is great! i love it but it definitely needs a way to swap patches via midi program change (all plugins need this imho). nobody wants to watch anybody mess around with a laptop on stage. native instruments, u-he, fab filter, arturia, applied acoustics, bluecat's - they all have implemented great ways of using midi program change. i like ni's way in reaktor - where you can drill down into banks and subbanks. makes it easy for nerds like me who want to have a live set per bank. tassman modular is nice in that it lets you setup your own patch playlist of sorts.

side note: recently discovered 2 work arounds: 1.) is use bluecat's patchwork. it's a bit of a pain to setup sometimes. 2.) ableton via the max for live patch "Loader": https://valiumdupeuple.gumroad.com/l/agUro - you can load racks (with any plugins inside, like mux) via midi. it is probably not as efficient as if mux had pgc built in but still, has worked great so far.

[dakkra]

Something to note, MIDI program change isn't consistently implemented the same way or completely throughout various hosts. It's cause for much grief, which is why at my work (shall remain unnamed as this is my personal account) we do preset changes on a specific MIDI CC channel, with up to 127 presets (the factory bank if you will) as the selection range.

I don't think MUX is really well setup for this kind of feature. Like has been stated, preset complexity is non linear (different sizes) meaning there's no predictable time/response to each preset change. This just doesn't work well in music where timing is very important.