Midi assignments for patch up / patch down and scrolling without loading

@univst

I agree this would be a good feature, but it's not quite as simple as "MIDI Learn". The NI M32 and other Komplete Kontrol devices are much more than simple MIDI controllers. My M32 doesn't even send MIDI when using the large knob on the right, or any of the buttons.

@wavesequencer please note what this user has written above, in particular the suggestion to allow fast scrolling through patches via MIDI, with the selected patch not actually loaded until the flood of MIDI CC data stops.

Posted by: @getdunne

↑

@univst

My M32 doesn't even send MIDI when using the large knob on the right, or any of the buttons.

My (new) M32 sends in midi mode midi data for 4 buttons, for the 8 rotary encoders and for the 4D encoder (large knob on the right), except the "press" action of the 4D encoder (confirmed by Native Instruments that this is by design). This is with the default midi template. Komplete Kontrol 3.5 (free) let you make your own midi templates (limited) for the behavior and assignments of the 8 rotary encoders. You can use these midi templates in MIDI mode without Komplete Kontrol. So the M32 is "disabled" in midi mode but that should be still sufficient for scrolling the patch list in Unify I think (f.i. the 4D encoder for scrolling and a button (like "play") to confirm loading the patch.

Maybe a firmware/software update for your M32?

@univst

I tried to install the Komplete Kontrol software, but ran into problems, so I didn't pursue it. I dimly recall that, as you said, one can define MIDI templates including MIDI assignments for the large encoder.

Using a MIDI CC value to select patches is problematic, because Unify currently only supports CC values with a 7-bit range. It's not presently able to support the more complicated MIDI-message sequences typically used with endless encoders like the ones on the M32, and it may never be.

You should probably consider using Unify as a VST/VST3 inside a dedicated live-host program like Gig Performer, Cantabile, etc. Unify works quite nicely this way, so you can still have all of its libraries and powerful sound-design features, while letting the live-host handle interfacing with your MIDI hardware.

Controller specific implementations or profiles are not in the scope of Unify/2 (and not even thinking about MIDI 2.0 at the moment), but adding the ability to assign standard MIDI cc toggle controls for next/previous/random would be something to consider for sure (and a request I've been wanting to implement in Hyperion too).

If the concern with skipping patches is not having to wait for them to load in a performance setting, perhaps one solution for a live-set is a stage performance host like Shane suggests, but also just putting patches into a dedicated library to be pre-selected or tagging patches and filtering with a specific tag for a live-set/performance.

Enabling a 'double click to load' option (and a separate CC assignable 'load now' button) in the Unify 2 would also be a possibility (so that would enable next/previous without immediate load).

@wavesequencer @getdunne

Thanks for your answers and hints.

For me, Unify is generally a great, practical, and inspiring tool for sound design and quickly and easily layering sounds at home.
I have several DAWs, but Unify's "quick and dirty" approach still appeals to me.
I like its open (non-proprietary) structure and documented features.

A few minor improvements would be (at least for me):
- A MIDI assignment option for "patch up" and "patch down."
(actual value of message 0..41 = down, 42-85 = neutral and 86 - 127 = up or seperate midi messages for "patch up" and "patch down")
- A MIDI assignment option for "patch jump value" (default 1).
The actual value of the MIDI message determines how many patches the jump is when a "patch up" or "patch down" MIDI message is received.
For example: For a value of 1, the jump is +1 or -1, and for a value of 10, the jump is +10 or -10 before the patch is actually loaded.
If you link the "patch jump value" to a knob of your midi controller you can dynamically choose the scroll speed (sometimes slow and sometimes fast).
You don't want a direct "jump value" in the "patch up" and "patch down" MIDI messages,
because if you link these MIDI message(s) to your MIDI controller (to a knob), it's difficult to always have the same jump value.
- More keyboard shortcuts (or MIDI assignments), especially for "update patch" and "save patch."
If you currently try to automate "unifying patches" in bulk you have to perform awkward emulated mouse positions (and keyboard actions) to save a patch.
(Global) keyboard shortcuts would make these procedures more robust.

I'm curious what version 2 will bring...

I once asked Shane to add a functionality to store the midi settings .. 
at least store permanently - better load setups .. but this is optional

Right now I have 4 keyboards at my computer ..
- NI Kontrol
- Montage
- Nord Stage
- Hydrasynth

when I start Unify -> ALL midi devices are active. And to the worse .. 
Then I have to switch of 2 for the Nord, 2 for Montage, 2 for Hydrasynth (MIDI/USB) to only use (as preferred) the NI Kontrol.
I cannot store this. Which is really to bad.

After switching on some other MIDI device, am still not sure how it happens, magically suddenly it even switches back on all MIDI INput devices.
So I have to do this over and over - Each and every day. WooHoo

I really love Unify. I unified more than 30.000 ! patches for AU .. but this is really sth which is so annoying.

--

Regarding the upper issue with switching to the next.
It maybe would be cool (as in other UIs with master/details - am sw engineer btw) its standard to delay the selection a bit,
so fast scrolling does not load any patches - this would also help to sort out a lot.
As sometimes when I switch fast Unify even suddenly dies ..
Thank god am only using it in the studio - but would really prefer it in a live situation its even done for this usecase ..

Thanks a lot for all your work ! Great Respect!
- Steffen

Posted by: @uisbf

↑

After switching on some other MIDI device, am still not sure how it happens, magically suddenly it even switches back on all MIDI INput devices.

This is due to the "MIDI device polling" box (at the top of the Settings view) being checked. Un-check it and Unify will not only stop doing this, it will also remember your device on/off selections.