This is far from intutive!!! I was trying to figure out how to do this on my V5 today without luck. I had to search this forum (which isn’t that easy sometimes) and find this post then try something that seemed wrong / counter-intutitive - bold press on a toggle option. It does work but it feels like there is a better solution waiting to be found. Now where did I put my looking glass?
[Edit] Also be aware that this setting is made in a chain context menu but is actually global, i.e. a change to the mode of a MIDI input made in chain 1 affects that input for all chains.
Totally agree on this. We must improve it, but I didn’t want to delay having this (on testing) and hope the community give feedback to find a better solution before merging on stable.
It is, perhaps, a characteristic to learn in the same way one MIDI learns a control parameter, rather than select from an option…?
So use the same technique for going into midi learn to enable the option selection menu and employ a selection for a list there so you can see the options that are available. For this.
Could even be dome from within the menu item that Midi Capture appears in.
@jofemodo Great idea. I was just needing that feature a couple of weeks ago as I wanted one MIDI input behave like stage and the other 2 in Multitimbre.
But you were saying, that you were thinking of removing the Clone To Midi Channel feature.
I am mainly using it to use three sfz samples at once.
I haven’t figured it out, but I really liked the option to split a chord into its part and lets say play the bottom note as tuba, the middle as trombone and the upper as trumpet. I don’t know if the midi filter can do that.
But that’s one of the more sophisticated scenarios I would have in mind.
Regarding midi clone, I’ve realized it’s better to keep it. Although Omni mode can be used for getting similar results, it’s not exactly the same, and clone works better for some cases.
Instead of chord, Have you tried to use clone + transposing for this?
I think it could work nicely.
Sounds challenging to implement. Imagine a chord being played but the middle note triggering before the lower note. A simple rule based MIDI router may send the middle note to the wrong destination then adjust after it receives the whole chord.
I try different controllers.
Please can you try this:
Channel #1 - selected OMNI controler 1,
- unselected OMNI controler 2,
Channel #2 - unselected OMNI controler 1,
- selected OMNI controler 2,
Somehow I suspect that WIDI Bud Pro can also cause the problem. Midi from it are on midi channel 1.
I have the same behavior in both the test build and the stable build.
Could anyone else try a similar configuration? It would be best if controller 2 was of the wind controller type and influenced/transmitted to cc11. It can then be clearly recognized because it affects the volume (ie expression) of channel 1 for me, which should not be the case.
Channel 1 with - selected OMNI or MULTI controler 1,
- unselected OMNI controler 2,
CC messages doesn’t reach ANY chain directly. They are captured by zynthian MIDI learning system and they can be assigned to ANY parameter in ANY chain. Not matter the MIDI input configuration.
Some engines, perform some auto-MIDI-learning when added to a chain, and this can be a problem and result in collisions.
I’m not fully convinced about this and we are probably changing this behaviour in chain_manager branch.
Regarding current stable, i’m thinking about it too.
Until then, try to unlearn those controllers from the engines you don’t want.
This is quite a significant change, it should really go in the wiki.
One thing I notice is that it’s very difficult to switch modes on each capture option using a touchscreen through VNC. I can switch the options on and off easily but the bold-press in this particular menu is causing me trouble. I can do bold press in other menus without so much issue.
I had this issue too - couldn’t figure it out. I’m midi din from the RK008 sequencer. I went back to 2023 stable version for now. I’ll make a new sd just for ORAM testing/learning.
Mostly used as a hardware version of Omnisphere, so I need multi-timberal mode for sure. I’m looking forward to using the new sequencer and doing stuff all in-the-box.
I think I got a bit frustrated trying to get it all to play only the channel I want. I just need channel 1 to receive midi 1 only. I did see the page for selecting the midi input but couldn’t get it set how I need so I reverted.
I have spare sd’s so I’ll make one for ORAM and use that when I have test time [=patience] to mess around.
Same with the sequencer. I like the launchpad integration a lot! Gotta mess around wth it more.
From the “MIDI input” screen, try “bold” clicking on the device to change the receiving mode (ACTI or MULTI). You can access this screen from the chain options and also, globally, from the admin menu.
