MUX Vst : What do you need?

[Crackbaby]

Uhm ... could you maybe move "revert preset" and "save preset" a little bit away from each other in the menu
Luckily it was easy to redo what i had done

[MuTools]

yes i know that would work. my point is you could simply pump midi into a standalone mux or play from a controller. ok whatever. dumb idea.

And postpone multi-core for that, or a adding an arpegiator/FM/wavetables and all the other MUX requests..?

I think after the MUX release, which i'm working on hard now, then i'll do multi-core for MuLab, as promised.

i must say that most of my suggestions wrt ease of use (ie less mouse mileage/less clicking about) and better organization of visual feedback seem to echo in this and other threads... im sorry but those things are what i want most for mux. the above suggestion is what my brain comes up with when what i truly think it needs is too involved to be approved atm

As you know i have a very long wishlist for MuLab/MUX. I try to sort all items per priority. Priorities depend on all the input i get from various users. I try to make good balances and give good solutions. I think MuLab certainly is usable as a standalone host to play a VST plugin. Anyway, i'm happy to read that you like bmrzycki's solution. If there is a good creative solution, that's great

[MuTools]

Uhm ... could you maybe move "revert preset" and "save preset" a little bit away from each other in the menu
Luckily it was easy to redo what i had done

I've added a "Are you sure?" alert. That's consequent with the Revert Session function. In the future, when the Undo/Redo system has been extended to also undo a revert function, this "Are you sure?" alert can be removed again.

[> DiGiT <]

And postpone multi-core for that, or a adding an arpegiator/FM/wavetables and all the other MUX requests..?

As you know i have a very long wishlist for MuLab/MUX. I try to sort all items per priority. Priorities depend on all the input i get from various users. I try to make good balances and give good solutions. I think MuLab certainly is usable as a standalone host to play a VST plugin. Anyway, i'm happy to read that you like bmrzycki's solution. If there is a good creative solution, that's great

yeah sorry i wasnt really in need of a standalone, just brainstorming for stuff peoples might want. im sure it was already considered anyway. mux and mulab are certainly useable however i think balance is super important. sometimes i think it takes too long to get where you need to be and the clutter and confusion created along the way simply needs to be minimized. the potential of mux (as hosted within mulab or as vst) is hindered by this kind of concern:

if i load a mux preset with some vsts inside with all my mappings and i want to view the vsti ui i have to do a lot of steps. when i open the mux ui, the play editor windows is displayed. then i have to click in the deep editor button. and then i have to choose among the loaded vsts which one is the one i want to view and finally i have to double click in it. besides involving a lot of steps just to view a plugin ui; 3 windows are open in the process. that's a lof clutter and confusion.

to me that could rank as high as multi-core. but maybe thats just me. do you have multiple screens to view mulab or the mux environment? i dont.

[MuTools]

No i don't use a multi-screen setup here so i do know what you mean, and i agree it's an important aspect of the usability. But i'm just a human and i can only go step by step. And i try to work in a structured way. The multi windowing aspect is something i'll certainly research further in the M5 design stage.

[hcv242]

check the video details text box for some info:

[MuTools]

Thanks a lot for these videos!! These explain it all
Both problems have been fixed in the next version, which will be available soon.

[MuTools]

New MUX Vst 1.0.17 packages are available in http://www.mutools.com/mux/cedar

If you already installed MUX Vst 1.0.12 or up you can just update the DLLs if you want.

What's changed:

• Fixed a possible crash bug when drag-dropping VST parameters.
• Fixed an important bug that could possibly cause various instability problems or crashes.
• Also on loading a MUX preset, the VST host is notified about name changes.
• "Super Modulator" renamed to "Multi-Point Envelope".
• Improved labelling of VST inputs/outputs.
• Finetuned doubleclick detection.

[hcv242]

i think that i have a few more bugs to report...ill just have to find a way to reproduce them.

[MuTools]

Any description already? Is that using the newest version 1.0.17 or with the previous version 1.0.16?

[Crackbaby]

Thank you for notifying the host of names!!!

[hcv242]

no. these problems are "old". one has to do with adding outputs in mux vsti. i add a second output but it's always mute. i have to add a third one for the second to play audio. i dont need to connect the third one for the 2nd to start working and i can even delete the third one that things keep working. there are a few more that i can't reproduce.

"- Finetuned doubleclick detection. "

nice...this was really annoying.

[> DiGiT <]

when i opened the mux deep editor it took my entire screen forcing me to quit the host it was running in. any way to poll the screen resolution and resize where appropriate?

[Crackbaby]

Digit, not 100% sure what you mean, but you can resize by holding your mouse cursor in the bottom right corner and it will turn into a hand letting you resize.

[> DiGiT <]

not when the borders of the mux window are beyond the screen edge