MUX Vst : What do you need?

Official support for: mutools.com
RELATED
PRODUCTS

Post

Sorry for bumpin'


Alright, i think i just solved one of the biggest issues mankind has ever faced.

Fresh mux. Add InsertPizHere's midiProgramChange ... change some settings in it and tweak. FINALLY!!! Midi program change in maschine!!!!! HOly cow! Don't know if i should post a thread at NI's forum or play around first ... hmm hmm
:hug:

Post

This works great!
Mr Mutools, you have saved the world.. again!
I wonder if my mishap with Maschine caused this thread to die or everyone to put me on ignore :oops:
Mux has now solved:

Arp in Maschine*
Chordplayer in Maschine
Bank changing in Maschine
Patch Changing in Maschine
Patch changing on effects in Maschine(!)
Modulation wheel in Maschine
Very well working sidechain emulation in Maschine

That is, Mux with some easily available free midi plugins (mainly Piz)

*if the arps actually could stay in sync over long durations .. still looking for the best free one or if i possibly can make one in Mux
:hug:

Post

Great news that everything is working well now :)

Enjoy!

Post

Crackbaby wrote:Sorry for bumpin'


Alright, i think i just solved one of the biggest issues mankind has ever faced.

Fresh mux. Add InsertPizHere's midiProgramChange ... change some settings in it and tweak. FINALLY!!! Midi program change in maschine!!!!! HOly cow! Don't know if i should post a thread at NI's forum or play around first ... hmm hmm

Hey IIIIIII discovered that one! :D http://www.kvraudio.com/forum/viewtopic ... 5&start=15
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

but not the program change though? :o for maschine? If so you're a bad person for not telling me already! :x :hug:

I can only play around with mux for so long durations as my head starts to go hypo .. When you've been struggling with an issue for so long and suddenly a fresh wind whispers the riddle's secret ... ie mux :D
:hug:

Post

Crackbaby wrote:but not the program change though? :o for maschine? If so you're a bad person for not telling me already! :x :hug:

I can only play around with mux for so long durations as my head starts to go hypo .. When you've been struggling with an issue for so long and suddenly a fresh wind whispers the riddle's secret ... ie mux :D
yes you are right, I didn't pay close enough attention!


I am having some issue automating the parameters in Catanya (bridged to 64 bit). It allows me to define them, finds the last touched parameter, but then the knobs don't actually function.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

I'm still trying to get the cash together to pay the ransom on my copy of MUX :D Really I was not that excited until the midi out came along, it REALLY saves me lots of trouble in my host of choice. I almost switched back to reaper because of the routing issues in Studio One but MUX fixes everything nicely, without making my host more complex.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

Ill install catanya tomorrow and see how it works out here
:hug:

Post

Maybe this is just a bug? Is it possible to have the parameter names updated when dragging a control to them when they already have a name? The controls are remapped but the name continues to have the old mapping label.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

If you have named them yourself then it continues to have that name. But if it's a name it got from a previous dragged control then it should get the new one.

Is this what what you mean? :) I like it that way personally but i wouldn't mind either way i guess.
:hug:

Post

Crackbaby wrote:If you have named them yourself then it continues to have that name. But if it's a name it got from a previous dragged control then it should get the new one.

Is this what what you mean? :) I like it that way personally but i wouldn't mind either way i guess.
Well, it looks to be inconsistent at least. I tried this just now:

1. Dragged a control from Diva (cutoff) to Parameter 1. It renames it appropriately as Freq.
2. Dragged cutoff from Ultra Analog to same Parameter 1 control, it names it back as Parameter 1. It didn't inherit the new name.
3. Dragged the same cutoff from both Diva and UA1 to the Parameter 1 control and it won't take either name.

Anyhow not the biggest deal especially if you are creating a MUX from scratch, but if editing it will force you to manually rename the control. I would rather it just inherit the name from the last assigned control. I would call this a bug.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post

braj wrote:
Crackbaby wrote:Well, it looks to be inconsistent at least. I tried this just now:

1. Dragged a control from Diva (cutoff) to Parameter 1. It renames it appropriately as Freq.
2. Dragged cutoff from Ultra Analog to same Parameter 1 control, it names it back as Parameter 1. It didn't inherit the new name.
3. Dragged the same cutoff from both Diva and UA1 to the Parameter 1 control and it won't take either name.

Anyhow not the biggest deal especially if you are creating a MUX from scratch, but if editing it will force you to manually rename the control. I would rather it just inherit the name from the last assigned control. I would call this a bug.
I call it logic :D
The reason is simple: When you map a single parameter then the meta-parameter (MP)can simply take the target parameter name. If you map multiple parameters, and they have different names, then which name should the MP take? Either one would be a fault towards the other parameters. That's why it uses the default parameter name (Parameter N) and it's up to you to give it a proper name.

Post

If you use two instances of diva and then drag both filters to the same parameter, it would show Freq! :)
This is great when unisoning synths without it where you have to stack them. Makes sure you don't mess up :lol:
:hug:

Post

Today i started out on a new project - making a polyphonic synth out of instances of Dune+Etch. Monophonic wasn't too hard :p
Again, Piz helps you out. There's a tool called chordsplitter. While i haven't figured it out 100% yet, i know how to make it work almost good. 12 notes polyphony in a single core environment was a bit uh-oh, but six voices worked fine! The trick is just to assign parameters in a cloneable way. You have to use midi instead of automation/parameter data for this, but that's alright.
:hug:

Post

mutools wrote:
I call it logic :D
The reason is simple: When you map a single parameter then the meta-parameter (MP)can simply take the target parameter name. If you map multiple parameters, and they have different names, then which name should the MP take? Either one would be a fault towards the other parameters. That's why it uses the default parameter name (Parameter N) and it's up to you to give it a proper name.
Oh I was misunderstanding how the parameter knobs worked. I didn't realize it was actually mapped to multiple parameters, i thought one just replaced the other! OK, makes sense to me now! Thanks for clarifying, I'm still just getting my toes wet with MUX :)
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new

Post Reply

Return to “MuTools”