Hive 2 - use labels of XY parameters for assignable controls

Official support for: u-he.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello,

Just a small feature request :)
I have a Push 2 controller and e.g. Massive X has 16 macros which can be automated. When changing the Macro name, the change is also shown in the actual parameter name. This way, the display on the Push also shows the correct label on the display below the physical knobs.
It would super nice, if Hive 2 would do the same to the X1, Y1, X2, Y2,... labels instead of showing those, it would make a lot of sense to see the actual name given to the specific control.

Cheers! :)
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

Unfortunately, renaming parameters on the fly is a bit of a drag in plug-in formats other than CLAP.

CLAP also has an extension named "Quick Controls" which will resolve many of the issues associated with controllers like Push. That extension is still in draft, hence it would be great if the Push team wanted to contribute with their experience.

Unfortunately I have no better news re AU/VST2/VST3, but I'm sure that people are monitoring the situation carefully, and either have old plug-in formats catch up or join our effort.

Post

Thanks for the quick reply Urs... appreciate it :)
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

Do you think it would make sense giving the Ableton team a --- push... regarding this?
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

sQeetz wrote: Sat Sep 17, 2022 12:29 pm Do you think it would make sense giving the Ableton team a --- push... regarding this?
But of course!

We've done our part, and our friends at Ableton know about it, even discussed it at times... what it really needs though is users asking for it, so it gets on the roadmap.

Post

Allright. Dankeschön :) Werde anfangen die Jungs von Ableton zu nerven
MacMini M2 Pro MacOS Tahoe ……… Reason 14

Post

Hi, copy osc1 settings and paste to osc2 does not seem to work. Nothing happens... Am I missing anything?

Post

If you are using the CLAP beta version, then the reason is quite simply that module preset support hadn't been fully implemented yet in the first public preview, revision 13207.
This will work in the next public preview version.
That QA guy from planet u-he.

Post Reply

Return to “u-he”