The MUX is the heart of MuLab. It's a modular synth and effect plug-in with which you can build a vast range of sounds and FX. Below are some links to more detailed pages about the MUX.

Now soon the MUX will also be available as a Vst plug-in.
So please let me know which practical aspects and features are really essential for you to make it very usable as a Vst plugin in your favorite host(s). Looking forward to your posts.

Cheers!

Jo

==

About the MUX:

http://www.youtube.com/watch?v=1uOGuki6cjs
http://www.youtube.com/watch?v=2v2ddeh_gXk
http://www.youtube.com/watch?v=QxhuFy11Z_0
http://www.mutools.com/mulab/docs/mux.html

To give you a sonic impression of what the MUX can do, all of these demo songs are purely made with the MUX engine:

http://soundcloud.com/mutools/
Last edited by mutools on Mon May 21, 2012 7:04 am; edited 1 time in total

This is pretty exciting news , you may also want to post this over in the Effects and also the Instruments sections of the KVR forums . On to my question : Will the MUX include musynth , musampla ,mudrum , and all of mulabs effects and instruments presets ?? Seems like it would ??

Very interesting to have Mux as a vst.
If I had one thing I could change in is to have a browser (dont care wich side it would be in) that can always be open to select presets and object for Mux.
Would speed up my workflow, but then again the browser is never far away in Mux

If the multisampler will work in MUX vst, then Kontakt has a new rival

Yep , Im looking forward to this MUX plugin , if its got mudrum , multisampla , musynth , echo , reverb , and all the instrument presets of mulab , I'll be buying this and jbridge !! mulabs instruments are awesome , enough said !!

Will do so soon.
(when the next new MUX tutorial is ready, it's in the pipeline)



Yes!!

The most important feature for me would be to have the same rectangle selection ability as in the composer view.

The only other thing that I find myself wishing for is an encapsulate feature. Often when I'm playing with a modular fx patch or something, I'll come across one subset of the patch that I think I'd like to reuse in the future. So I save the main patch, delete all the modules except for the subset I'm interested in, then save this new patch and reload the old one. Being able to select a group of modules and have them moved to a new MuX module would be very handy for me, but then I might just have a funny workflow :)

It's gonna be a powerhouse of a VST!

It sure will be from what i just read about all included synths and effect presets

Almost too powerful perhaps? I mean if you have the MUX vst (and a host sequencer), there is not much reason to upgrade or switch to MuLab anymore?

There is no much need to buy the MUX VST for MuLab customers...

It mainly targets the people using different hosts... there are many people buyimg new instruments/effects but only a few changing their main host, so it's a very important step for Jo...

i think as much ease of use and efficient interaction with mux resources is what it needs. if you can impress users with an extremely powerful browser and tight workflow that attempts to eliminate clicks and mouse mileage, i think it will be a hit. i personally prefer software that not only has depth but attempts to make it easy to put it all to work. if i have to imagine whats going on because of a lack of visual feedback or an intuitive interface, there should be something else extraordinary about the software in question to keep my interest. no scratch that, i dont have patience for software that isnt obvious and supremely useable.

You don't get the MuLab way of working. MUX is still just a way of making sounds. It's not the composer. I hardly use MUX but I move to MuLab when I'm putting music together because it's got the best work flow of the (two) DAWs I use.
Disk streaming in MultiSampla (as an option). On the fly sample-rate conversion would be good, too. Those are two things that stop me using MUX.

it will also be possible to use it as a comprehensive vst chainer and save those chains I suppose?

Would make an ideal workaround within limited (versions of) hosts too then

Yes, sure!

You can insert any VST plugins in the MUX, connect them in the way you want and save that as a preset for re-use. And of course when the host saves a project, al MUX data is inluded in that save too.

When playing back samples, then an eventual difference between the sample's samplerate and the audio engine's samplerate is taking into account and compensated in real time.

So how do you mean?

I know that the MUX can be extended and improved, it already has an interesting wishlist.

Now question is what would be best:

A) Release MUX Vst as it is now (besides some essential improvements) then R&D MuLab 5 and MUX 2 in parrallel and release them later this year.

B) Postpone the release of MUX Vst and first R&D MuLab 5 and MUX 2 in parrallel and release them later this year.

I think A is best. Because the sooner MUX Vst 1.0 is available the better, on condition it is a useful, worthy version. Then while MUX Vst 1.0 is already rocking, i can work on the bigger projects MuLab 5 and MUX 2.

Sounds good?

Now with this topic i'm curious for those 'essential improvements', i.e. what needs to be done to the existing MUX to make it a useful MUX Vst 1.0. Maybe it's already worthy as it is now?