MuTools

MuTools · Post by **MuTools** » Thu Jul 12, 2012 9:50 am

hcv242 wrote: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.

Sorry about the late reply on this. You're right. That's fixed in the next version.

Crackbaby · Post by **Crackbaby** » Sat Jul 14, 2012 1:18 pm

mutools wrote:@Crackbaby: Did you hear something from the Valhalla dev about that weird UI issue?

No, i totally forgot about that

But i've been chatting to him about it before sort of and he had some plans to redo parts of it. The problem i encountered back then was different from this though (it was about maschine not storing the parameters).

That is not an issue though when i run it through mux

I've made a couple of custom Ubermods with 8-16 assigned knobs within various ranges so that i can 'morph' through settings. I did a one knob mux where that knob controlled every parameter of Ubermod (30+ i think) going from one preset to another. But later i figured it was best to split the parameters up on all 8 or 16 knobs.

I see version 1.0.24 is up!

hcv242 · Post by **hcv242** » Sat Jul 14, 2012 11:09 pm

> DiGiT < wrote:
hcv242 wrote:http://soundcloud.com/migueltorga
wuaaah! you have some nice grooves there!

you should check out 'live effects' preset

thanks for the feedback

braj · Post by **braj** » Sun Jul 15, 2012 2:23 am

Sorry if this has been asked before, but how does MuX work in a 64 bit system running a 32 bit host with a mixture of native and jbridged plugins? I'm planning to use it in Studio One. I tried on my current 32 bit machine and got a crash when trying to use Diva with a synthedit arp (CK Pattern Arp Plus). Anyhow this plugin looks extremely promising so I am hoping the above scenario is supported

pljones · Post by **pljones** » Sun Jul 15, 2012 6:29 am

MuX 64bit can only see 64 bit plugins. So it will only see any jBridged 32bit->64bit ones. If you jBridge MuX 64bit into a 32bit host, MuX is still running in a 64bit address space, so nothing has changed with that constraint.

Crackbaby · Post by **Crackbaby** » Sun Jul 15, 2012 7:08 am

Last night i made three muxes with the new Oxium synth from xils lab. With their 16 knobs they all represent a different theme. First one was an FX synth, second a "lead" synth and the third a bass synth. Maybe it doesn't sound like much and im not sure how to show you..
First of all, this was aimed to be used with Maschine so just being able to modify a synth that much with it's controls without needing a GUI is nothing but amazing. But it turned out to be a great preset maker as well!
The sounds will only be as generic as you set the ranges and how you build the parameters. You can go within safe ranges and make it sound great no matter how you tweak. Or, if you extend the ranges into the dangerzone you might end up with a sonic nightmare where you loose track on what you're doing.
But there's really no need for that.. Just make another mux focusing on the more crazy stuff

The FX Oxium i made with mux is based on an osc controlling a filter. With 16 knobs to control envelopes, pulsewidth, resonance etc etc you end with some pretty wild effects

Sorry for morning ramble but i just wanted to express how awesome mux is!!

Crackbaby · Post by **Crackbaby** » Sun Jul 15, 2012 9:17 am

Is there a difference how mux vst and vsti sends parameters to host?
This is very hard to describe!!

With MuxEffect (the VST) everything works fine! The correct parameters will be shown (loaded/sent?) in all situations. In Maschine there's three situations:

I load MuxEffect and change MuxPatch - parameters are correctly updated with each patch.

I load a Maschine Preset i have saved where i had a MuxEffect with a MuxPatch loaded - Parameters are also here correctly updated. (A Maschine Preset is basically a VST with a certain patch and/or settings. If you load a patch in a vst and tweak a few knobs and then store it as a Maschine Preset - that is how it will be loaded next time).

Third situation: This is if i have nothing loaded at all in Maschine, a VST that is not Mux or a Maschine Preset with a VST - ie there is NOT a MuxEffect loaded. Now when i load the MuxEffect - parameters are correctly shown. (difference with vsti version as written below)

Lets enter the problem with the MuxSynth (the vsti).

First situation. I load MuxSynth and then start to go through my patches. All parameters are shown correctly and are updated.

Second: I load MuxSynth, load a certain patch in MuxSynth and then store it as a Maschine Preset. If i reset/change the parameters by loading another patch in MuxSynth (as in first situation - i go through some patches), and then reload the Maschine Preset to get that certain patch with it's parameters loaded - the parameters do not get updated!

Third situation: I have nothing loaded, a Maschine Preset with a VST or just load a VST straight. Now i load a Maschine Preset with MuxSynth with a certain patch. The parameters are those of the standard default synth you get when loading MuxSynth. Not those of the certain Mux Patch I had stored. Maybe this could be a lead in finding the bug.

I put great effort in trying to describe the problem

Hopefully it made sense

It could be a maschine issue but please check as it is a huge dealbreaker if you want to use mux synths in maschine. As you can read in above post, im slightly thrilled about it....

Edit: 1.0.24 32 bit version was used

MuTools · Post by **MuTools** » Sun Jul 15, 2012 11:35 am

No there is absolutely no difference between MUX and MUX (Vst Synth). I'm quite sure you can repeat the problem with MUX if you do exactly the same. I think the problem lays on Mashine's side, as i think Mashine should update its displays after loading a patch/preset to one of its hosted VSTs. Now as an experiment to know that indeed that is the problem, i've added an extra 'updateDisplay' (=VST command) after the MUX (fx/synth) got loaded by the host, in order to give the host an extra push. So please try the new version 1.0.26 and see if all is working fine, new 32 bit version in http://www.mutools.com/mux/cedar
This 1.0.26 package only contains the DLLs, hope you know how to update them, else let me know. Please feedback if 1.0.26 is working as you want.

Crackbaby · Post by **Crackbaby** » Sun Jul 15, 2012 11:38 am

It works!!!! Thank you! That's awesome!!! Fantastic!!

bassmonsta · Post by **bassmonsta** » Sun Jul 15, 2012 11:49 am

Is preset loading disabled ? I can't load any of the presets I've made. is there a release date yet?

MuTools · Post by **MuTools** » Sun Jul 15, 2012 11:58 am

bassmonsta wrote:Is preset loading disabled ? I can't load any of the presets I've made. is there a release date yet?

Which version are you using?

Crackbaby · Post by **Crackbaby** » Sun Jul 15, 2012 1:56 pm

Alright, this is a chunky bug!

If i load MuxSynth in Mulab and add a vsti and connect it to the event and audio it will be out of tune if i run Mulab at 48kHz! But at 44.1kHz it's fine. My brain exploded twice trying to figure out why all synths suddenly were out of tune

Note it's only when a vsti is loaded in a mux in mulab, not when a vsti is directly loaded in mulab.
This was with the .26 version of mux and mulab 4.36.

Glad i checked before i hit 'post' - If i run Maschine at 48kHz it will go out of tune there also (the vsti i have loaded in a mux that i have loaded in maschine).

Is Mux locked to 44.1kHz somehow?

MuTools · Post by **MuTools** » Sun Jul 15, 2012 5:14 pm

Crackbaby wrote:It works!!!! Thank you! That's awesome!!! Fantastic!!

Note that it was just an experiment in order to locate the problem.
I'm not sure if i can keep this as a permanent solution. I think the host should update its relevant editors when loading data into a vst. I'll check this further.

MuTools · Post by **MuTools** » Sun Jul 15, 2012 5:18 pm

Crackbaby wrote:Alright, this is a chunky bug!

If i load MuxSynth in Mulab and add a vsti and connect it to the event and audio it will be out of tune if i run Mulab at 48kHz! But at 44.1kHz it's fine.

I plugged in MUX Synth in MuLab at 48 kHz ad also in FL10 at 48 kHz, both times it plays ok i.e. in tune with other (non MUX) synths. Maybe there is a Maschine bug that it does not give the correct samplerate to its plugs. What happens if you plugin other non-MUX synths in Maschine @ 48 kHz?

Crackbaby · Post by **Crackbaby** » Sun Jul 15, 2012 6:59 pm

It happened when using Mulab as well, so not just Maschine. Ill see if i can figure out what's causing it here.

MuTools

KVR Audio

MUX Vst : What do you need?