Err: synths receiving MIDI control signals

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I'm working with a variety of arpeggiators which output MIDI CC's (Cream & Thesys) and I'm trying to send CC modulation data to a basic Mulab synth (the standard one which loads with a new project) but I'm not getting any reaction from the synth. I set CC in the arp plugin, right-click > 'Map MIDI Controller' in the synth to the same CC# as the plugin, and yet nothing happens.
Using a MIDI Event Monitor I can see those messages are being transmitted by the plug-in but aren't being acted upon by the synth.

Any idea what's going on?
"Music is directly tied to the technology of a culture."
"Modular gear is the craft beer of music."

Post


Post

mutools wrote: Sat Mar 21, 2020 8:12 pm Does this help: http://www.mutools.com/info/M8/docs/mux ... llers.html
That's what I've done (described in my original post) but it's just not working for me.
"Music is directly tied to the technology of a culture."
"Modular gear is the craft beer of music."

Post

Thing is: Are you sure you have mapped the CCs in the module that is receiving the CCs?
Please double check via module -> Edit MIDI CC Map.
If you're sure it's all setup right the please post a simple project that demonstrates the issue.

Post

Does it work if you replace the VST arps with a MUX module that outputs a MIDI CC?

Post

pljones wrote: Sat Mar 21, 2020 9:55 pm Does it work if you replace the VST arps with a MUX module that outputs a MIDI CC?
That's a good thought and I did try that with the Mu StepSequencer (I created a modulation lane) and routed an arbitrary CC number to a Basic Synth and also tried to a MU preset instrument but still no go. Very vexing as I'm sure I've gotten this to work at some point in the past.
I'll work on some screen shots and a sample file to upload next.
"Music is directly tied to the technology of a culture."
"Modular gear is the craft beer of music."

Post

So, following David's lead on a post form last week I tried mapping my CC to the *module > parameter* and not just the *parameter* itself (as described in the Help documentation) and now my automation works.

I can see that in some cases a single parameter is controlling multiple sub-level controls (like the TIME feature in the Basic Synth) and that mapping to the module allows for deeper-level connections to be made but I don't understand why there's even an option but I still don't understand why right-clicking on a parameter to map a CC doesn't work (or even why it's an option in the first place if it doesn't really work as expected)?
"Music is directly tied to the technology of a culture."
"Modular gear is the craft beer of music."

Post

That's also explained on that doc page.

Post Reply

Return to “MuTools”