Key Control

[tasmaniandevil]

insert diva
click diva to open the gui
click the „preset“ tab (in the diva gui) to open the preset panel
hit arrow down key

Hahaha, you are not actually using the arrow keys to select any presets then.
That was the crucial detail.
It crashed if you use the arrow key directly after clicking the presets tab.
I can totally reproduce that, thanks a lot for reporting. No need to contact support, as it's easily reproducible now.

[ThomasLehmann]

Oh, one thing I forgot to mention in the video is that the navigation of knobs and stuff also affects the "Last Clicked Control" on the MIDI Assignments page.

Screenshot 2024-07-24 at 14.16.01.png

So if you assign MIDI Controllers like shown above, you can navigate the UI with cursor keys and at the same time modify parameter values via MIDI.

Can I then use the mouse (with my right hand) to jump to the respective parameters in the synth and change the parameter using a rotary control on my midi controller with my left hand? That would be great !

That has worked for many years... (I did improve the fine control thing though)

ah ok, then I think that still won't work in Reason. In Reason, the midi controllers are usually not passed directly to the vst plugin, as Reason's remote system is in between where you have to make such controller assignments. Hive's Midi-table is only accessible for special performance controllers like ModWheel, which makes no sense here. It's because of the concept in Reason, unfortunately.

[humpo72]

what are my options or am I out of luck?

I have a satechi slim X1 keyboard for my Mac. it has a British layout. I can only seem to increase values by small increments using shift & +. And decrease values by large increments by pressing the - key. Getting the CMD key involved just zooms Ableton Live UI for me. would it be possible to add an option to be able to choose the increase/decrease keys? the [ & ] keys below it seem like good candidates with a shift added for smaller increments

[Alex_Longard]

All works!
Only my screenreader can not read on which element the cursor is located. I hope after a few years tooltips will appear.
Thank you very much for such a job, it's great!

[rafa1981]

Consider that there are many keyboards without the numeric section anymore, so with no dedicated +/- Keys. I use one because for me it's a much more ergonomic placement for the mouse.

[elnn]

great initiative.
it would be ergonomic and agile to have a feature where it could accept a user-defined keymap where keys are mapped to parameters for the focus to jump to.
this would increase speed of navigation and also allow a single midi controller to control the entire synthesizer. in such an arrangement, it would be possible for the user to not need to look at the screen for extended periods of time.

[swilow11]

This looks really interesting and is something I will surely investigate. Am wondering if this is contributing to Hive2 seemingly taking over space bar transport function in Bitwig (ie. Space bar does not start transport when Hive gui is in focus). Not a major problem, just takes a click to sort out but is a curious thing and I use multiple instances of Hive2 per project (easily my most used and maybe favourite synth) so it would obviously be better if this didn't happen.

[tasmaniandevil]

Am wondering if this is contributing to Hive2 seemingly taking over space bar transport function in Bitwig (ie. Space bar does not start transport when Hive gui is in focus).

This usually works without problems in Bitwig. No matter if key control is active or not, the space bar is reserved for Bitwig's transport function, unless it's needed in a text input dialog (e.g. the preset save dialog).

However, we did notice the that space bar stops to work at random times. So far we could not figure out why this happens, thus we cannot tell if the issue is on our side or if it's a bug in Bitwig.

Maybe let the Bitwig guys know about this, so they can investigate this as well.

[swilow11]

Am wondering if this is contributing to Hive2 seemingly taking over space bar transport function in Bitwig (ie. Space bar does not start transport when Hive gui is in focus).

This usually works without problems in Bitwig. No matter if key control is active or not, the space bar is reserved for Bitwig's transport function, unless it's needed in a text input dialog (e.g. the preset save dialog).

However, we did notice the that space bar stops to work at random times. So far we could not figure out why this happens, thus we cannot tell if the issue is on our side or if it's a bug in Bitwig.

Maybe let the Bitwig guys know about this, so they can investigate this as well.

Thanks for the reply Will let Bitwig support know too...

[swilow11]

Bitwig suggested the issue is fixed in 5.2 so I'll install the update and see how that goes.

[plugmon]

I'm happy that the preset saver dialog is now much easier to use!
-TAB key to switch between textareas.
-ENTER to proceed saving even when the focus is on description/usage area.
-You can still make new lines by pressing SHIFT+ENTER.
Soooooo frawless!!

But one issue regarding key control system: My US layout keyboard needs SHIFT to be pressed to input "+". Consequently, my value-up operation is forcedly always fine-tuning mode (increase by 0.01).

Also, in older version, direct value input was already available. Now that the new key control system has been introduced, it's unfortunate that direct value input is no longer possible when this system is turned off. There may be times when you want nothing more than inputting values just like before and don't want to be distracted by the focus cursor...

P.S. I tried importing the key control on my custom skin and it works with no problem

[mesayre]

This is great! Thank you for the update and new functionality. A couple of minor issues I'm seeing:

In DIVA, there are some circumstances in which the key control cursor disappears when using the Digital oscillator. For instance, if you have selected the Wave selector for oscillator 2, then hit the left arrow, the cursor vanishes. Hit it again and it will jump over to the modulation enable/disable switch. Something similar happens when moving right from the tune mod source selector, or from the oscillator mix knob.

[dioxine]

Very very strange stuff for me. No, i don't mean this is not good for setting exact values or for accessibility of blind people, but, really, guys from u-he, don't you have another more requested features to do? for example CLAP VoiceStacking support in Bitwig or fully working polyphonic modulation of native parameters?

[AtomOfScent]

P.S. I tried importing the key control on my custom skin and it works with no problem

Is there an easy way to do this for custom skins?

It would be useful if the feature could be enabled by right-click somewhere every script doesn't need to be updated for it (which is unlikely.)

[Urs]

P.S. I tried importing the key control on my custom skin and it works with no problem

Is there an easy way to do this for custom skins?

It would be useful if the feature could be enabled by right-click somewhere every script doesn't need to be updated for it (which is unlikely.)

Skins really just need to have 1 widget added. That's as easy as it gets