Mulabs MUX is for sale

[Ingonator]

I've uploaded my triple-unolx here: https://drive.google.com/?tab=mo&authus ... kVURDE2d28 .. See if only WorkUNOLX1 is needed. The others, 2-5, are the muxes inside the muxes but maybe they are stored inside the first one (filesize would indicate that)

The link does not seem to work. It just opens the main page of Google Drive...


Ingo

[MuTools]

one thing that i don't think has been mentioned is that (afaik) the current 49euros deal only offers upgrades/support for MUX VST v1, while the full 75euros cost covers MUX VST v1 and v2 (whatever/whenever that is). it's a bit confusing, and I'm not even sure what v2 is or will be.

Just so that I understand correctly: The current promo deal is cheaper and expires at the end of August, but the original (non-promo price) covers MUX v1 and v2.

No, that has changed.

In the pre-release phase the MUX was launched at 75 euro for v1 + a free upgrade to the next v2. But after some intense discussions, the MUX now is available at a promo price of 49 euro for v1. After the promo period it will be 59 euro also for v1. Upgrades to v2 will be gentle.

[MuTools]

Only downside in comparison to doing "simple" layers inside Ableton Live 8 is that with MUX it uses much more CPU.

I think it doesn't use more CPU but i assume when inserted separately in Live it's spread over multiple cores, while each MUX instance is processed on a single core. Live cannot disassemble the MUX to spread it over multiple cores. When R&Ding multi-core support for MuLab i'll do my best to apply it on the MUX so that also the MUX Vst plug-in will have MC support. That's the intention, no promise yet though, needs some more research first.

[MuTools]

With the 16 controller limit you'll need to make muxes in the muxes.

Hey Crackbaby not sure if you saw my reply on that here: http://www.kvraudio.com/forum/viewtopic ... 29#5040129

[Ingonator]

Only downside in comparison to doing "simple" layers inside Ableton Live 8 is that with MUX it uses much more CPU.

I think it doesn't use more CPU but i assume when inserted separately in Live it's spread over multiple cores, while each MUX instance is processed on a single core. Live cannot disassemble the MUX to spread it over multiple cores. When R&Ding multi-core support for MuLab i'll do my best to apply it on the MUX so that also the MUX Vst plug-in will have MC support. That's the intention, no promise yet though, needs some more research first.

Of course you are correct. Didn't think about that...

If using multiple tracks they are using different cores of course.

Anyway a multicore support for MUX would be a great idea.


Ingo

[DarkStar]

one thing that i don't think has been mentioned is that (afaik) the current 49euros deal only offers upgrades/support for MUX VST v1, while the full 75euros cost covers MUX VST v1 and v2 (whatever/whenever that is). it's a bit confusing, and I'm not even sure what v2 is or will be.

Just so that I understand correctly: The current promo deal is cheaper and expires at the end of August, but the original (non-promo price) covers MUX v1 and v2.

No, that has changed.

In the pre-release phase the MUX was launched at 75 euro for v1 + a free upgrade to the next v2. But after some intense discussions, the MUX now is available at a promo price of 49 euro for v1. After the promo period it will be 59 euro also for v1. Upgrades to v2 will be gentle.

Got it, thank you. So holding on for "v1 + v2 at 75Euros" to reappear would be a waste of time (and a lost opportunity).

[zendorf]

I hope he's able to get that. Something about juce that might be part of the issue. If it can't be done on the mu end, it's gonna be a long hard wait for some it to get fixed.

I can't repeat it using U-No-Lx 1.70 in MUX 1.0.38. I could repeat it with ValhallaRoom though, so i saw the issue before.

Anyway, if it's repeatable, please email TAL about this.
If they need my assistance in order to narrow this down, i'm open to that.
But the menus are on plugin side, the research should start there.

I have also got the same problem with Tal Noisemaker inside the MUX. None of the filtershape or OSC target menus will pulldown, they just flicker on and off. Sounds like it is a problem with Tal plugins.

I can't exactly hassle the dev, since it is a freebie, but when I buy TAL-U-NO-LX then I will let him know about it.

[Crackbaby]

With the 16 controller limit you'll need to make muxes in the muxes.

Hey Crackbaby not sure if you saw my reply on that here: http://www.kvraudio.com/forum/viewtopic ... 29#5040129

I did, but if you want to be able to control several layers of a synth by using the gui of one of the layers you need to have them in the 16 controllers. Otherwise the knobs and sliders wont move on the other layers. Maybe instances is a better word.
What happens when you do this is that the current layer/instance you tweak a slider on (the synth's gui) will force the mux controller to move, which will force all other layers/instances to have their slider move also - If you have assign that slider to the controller of course.

The idea is that you can continue to use the vsti's gui as normal, but have it stacked with identical vsti's with the addition of separate detune, transpose and whatever else you might have in mind.

I know i can be a bit annoying as i always do things the way they're not intended to be done..

*forgot to hit submit*

There's not enough words to tell how much i like mux! I've been longing for something like this since the first time i found a limitation in a vst. That would be just about when i started using them. I like that there's limitations. The amount of things you find and figure out when fighting them makes it worth it.

I feel pity for those at the NI's forum who hasn't read up on my post about mux. A crowd is like syrup. It takes forever to start moving. Once a few will reply to my topic more will follow. They will see what a marvelous tool this is.
Yesterday i couldn't get the demo of Torq running, but a dj software that support vst (which i think torq is the only one doing it) and Mux will take creative dj'ing to a new level. Even traktor seems limited in comparison. Just make sure the plugins don't increase latency (which mutools brilliantly added a function for checking!). Take Etch, Perumt8 and ubermod. See what you can come up with! I will ... right now

https://drive.google.com/?tab=mo&authus ... kVURDE2d28 see if this link works better. You should be able to hit one of the files and click download. I really hope it works because it's such a simple way to upload files for me

[Crackbaby]

I have also got the same problem with Tal Noisemaker inside the MUX. None of the filtershape or OSC target menus will pulldown, they just flicker on and off. Sounds like it is a problem with Tal plugins.

I can't exactly hassle the dev, since it is a freebie, but when I buy TAL-U-NO-LX then I will let him know about it.

So Tal's and Valhalla's plugins suffer from this. Any others?
What about using a shortcut for "add last tweaked parameter"? With tal's i have to use the menu button to add them. I don't know if you use a shortcut for it. The "general" one should work. If you could try it out i would appreciate it a lot!

Need to take a little musical break or my brain will explode!

[Ingonator]

https://drive.google.com/?tab=mo&authus ... kVURDE2d28 see if this link works better. You should be able to hit one of the files and click download. I really hope it works because it's such a simple way to upload files for me

Hi,

guess i found the problem with your files. I could only download the files when i am logged in into my own Google Drive account.
Looks like you did not enable the files for free download?
Usually it is possible to enable the download for anyone having the donwload link.

BTW i got a Google Drive account too but i found it seems to be easier to use Dropbox. With Dropbox mp3 files and WAV files could be even played directly in the browser which does not seem to be possible with Google Drive.

I added my first own MUX preset (for U-NO-LX) here:
http://www.kvraudio.com/forum/viewtopic ... &start=465

I just updated the MUX preset with dome "tricks" i found in your presets.

Direct link for the MUX preset:
https://dl.dropbox.com/u/53230726/U-NO- ... 0Layer.zip

screenshot:


The envelope and filter controls work for both U-NO-LX layers at once.


UPDATE:
Second MUX preset (4 layers) added here:
http://www.kvraudio.com/forum/viewtopic ... &start=465


Ingo

[Crackbaby]

Just wanted to share a neat little trick.

Sometimes you end up with quite a lot of active modules in a mux. In an FX chain for instance, you may not always use all the effects. Maybe you created one with all the ones you usually use (i have .. several ). Those you don't use but still are active will drain cpu for no good reason (i think?). Some vst's have parameter for on/off.
A plugin called "plusdistortion" (great on synths!!!) has such on/off. But, it's only active at 99%-100% or maybe it's 1-infinity . Normally if it's set to "on" the bigger range, ie 1-99% you can just apply that to maybe a knob for mix or volume - one you know will be >1 when you use the effect.
In this case it won't work though. So what i did is create the chain of possibilities. Which is: Constant modulator into Modulation Mapper into Parameter Event Generator. With this chain you can do just about anything you want.

Constant Modulator knob is the one i drag to the "distortion" knob (which will be bigger than 0 when i use the plug). Modulation mapper will have offset set to 100%. Parameter Event Generator is 99.5%.
Since the offset is 100 and the parameter 99.5, the constant modulator will go from 99.5 to 199.5(!). At 99.9999.. it's on so it will be on all the way to 199.5.
So when you tweak the constant modulator the first 0.5% of it will have the effect off, higher than that and it's on.

Now ... if only all effects had on/off or bypass... And automationable ..

This mux im working on is just Plusdistortion (by DTQ i think, it's modeled after a guitarpedal) which then runs into a new plug, a freeware one modeled after a marshal eq. I hope this can be a good and supereasy eq+dist for synths. When using vintage synths i like the idea of using guitar pedals as effects. Had this been the early 90's that would have been the case! I've become one of those nostalgics, haven't I..?

[Trancit]

Just wanted to share a neat little trick...

It's not automatic, but always a good idea is to drap the complete modules on the front panel at least of those you want to access with a single click on the front panel and these, which could use a lot of CPU but are not always in use...

Alt+left click on the module toogle processing on/off...it's quite an easy way to shut off/ bypass modules easily...
Very useful too, if you are working on a patch and need to compare wet/dry signal...

[Crackbaby]

And so the monster mutated in its muxolious glory!

By the gods of muxolania and scent of muxk, this is how it muxed along:

Apart from the EQ, all plugs are from the same guy at Distorque Audio.
First there's the Vitamin C compressor with tweaks for compressoion (+on/off) and attack/-release (so either short attack long release or superpump of long attack short release). This one splits into the first tonestack(marshal eq) and the fuzzface which in turn splits into the treblebooster and a mixer where the signal from treblebooster joins up - the half the signal had is trebleboostered. The signal from the first tonestack is then mixed with this signal which goes into the plusdistortion which goes to the second and last tonestack.

The result? 16 knobs of crunchyness! With the split signals you can regain or retain some of the original dynamics and mix it just right! I love listening to how sounds and rythms build up when you distort some drums in a loop

[Crackbaby]

Just wanted to share a neat little trick...

It's not automatic, but always a good idea is to drap the complete modules on the front panel at least of those you want to access with a single click on the front panel and these, which could use a lot of CPU but are not always in use...

Alt+left click on the module toogle processing on/off...it's quite an easy way to shut off/ bypass modules easily...
Very useful too, if you are working on a patch and need to compare wet/dry signal...

Ah good point! I always forget to do that haha
And you just solved a thing for me! If you drag the module to the workspace and then click to open it from there, then you loose the green on/off switch. That has always bugged me a little but ... as you said ... alt+click ..

[Trancit]

If you drag the module to the workspace and then click to open it from there, then you loose the green on/off switch...

If you mean with workspace the front panel then there is something wrong with your MUX...
Either with MUX internals or with VST, a click on the module dragged to the front panel should open the same editor window like open the module from the deep editor...