don't know if this is possible but it would be nice to have some sort of simplified way of finding the parameters in a given synth within MUX to create the control knobs on the main page. I am trying to figure out how to get controls form Diva on the main page but it is a challenge looking at the list of parameters. Some sort of 'learn' functionality would be nice.

What would be really nice (maybe it exists) is a library o presets that accommodates the most popular plugins with commomn controls premapped.

move a knob on Diva, then hit the menubutton above diva (same window, next to the patchname and save/load buttons), it looks like
---
---
---

There you find a command called "Drag last tweaked parameter". You can add a keybinding to this in the main menu so if you have that command and "enter" bound on your mouse you can assign controls almost instantly

OK NOW we're talking Thanks, that is a huge help!

Is there anyone else experiencing 'out of tune' probs when using the MUX in a host with samplerate different from 44.1 kHz?

Hi Jo,

played a little bit around with the betas, working great so far and have a very little CPU hit too on my system...

I don't know, if you can do something about this problem:

Some hosts (in my case Zynewave Podium and Novation Automap) don't recognize parameter changes and changes of the parameter name when switching presets... , which means at least for Automap, that it is hardly usable...
I noticed, that at least the parameter value of the last touched parameter is updated on preset change, but not the name and not any values of the other 15 ones...

Don't know, if there are different methods to let a plugin submit changes to the host... in Reaper, FL Studio and Ableton Live, everything works as expected, so I am not sure, if there is something you can improve...

About everything else, great work, not a single crash here...

Can't figure out how to get the midi [event output] to be recorded into the piano roll of my hosts FL Studio nor Project5. BTW, if this feature is enabled, you have solved a major workflow issue for me.

Regards, James

James, would an example of this be if you had a midi arp inside a mux and then sent the midi from the arp to the event output of the mux? Not sure i understand what you mean!

Yep that is what I was thinking of myself. I want to use arps with a MuX to allow it to all live on one track, but I want to also export the output if possible to write it to a track.

I want to record the midi output of any midi generating tool like Catanya directly into a piano roll. If MUX could get this done ...

FL Studio does not support recording midi from one track to another - but MUX will hopefully allow us to bypass that FL STUDIO issue/bug.

Regards, James

I would think the Event Output would work, but it seems not. I'm using Studio One v2. If I look at the session MUX there is an option for midi output port but only value is 'none.'

I tried that Kirnu arpeggiator by Arto Vaarala, but it wouldn't sync (no bpm control in the ui either). Do you get that issue with catanya? I own it but i haven't installed it.

An initial test i did was to chain two independent mux's. The first one had a midi controller generator connected to the event out. The second one had a event monitor connected to the event input. The midi CC is at least transmitted through two separate instances of mux.

In the second test i used "Insert piz here"'s midipads. It's basically a midi plugin used for sending various midi messages of choice(check it out!). That one would send it's notes on/off through. Finally i added the arpeggiator mentioned in the above post. Yes, the arpeggiated notes came through.

But here the fun stopped. I added a "normal" vst in between the two mux vst's. Guess what. All silent on the second mux.

As i have never really used FL i'm not too familiar with the problem or how mux could solve it. Maybe a third party program like loopb30 or whatever it's called could help

Is the normal VST you mention designed to pass on MIDI events after responding to them? Passing MIDI on isn't the normal behaviour, in my experience.

I'll double-check MUX Vst MIDI output tomorrow.

This is a old issue in Mulab to record the midioutput, till now it is on the wishlist.