setting up other CC's for Control A & Control B than Aftertouch & Expression in Hive?

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

Post

Hey all,

I love that we can change the MIDI CC's of the "Control" A and "Control B" since alot of us don't have AT or Expression - but still want to be able to modulate all the presets in an easy way.

Although I have not been able to get it to work. I have set up MIDI CC #19 and #23 inside Hive, both as Default in Preferences and in the MIDI Tables tab (see screenshots), but it doens't seem to work.
Have I missed something here? Binding other functions of Hive to any MIDI CC is working fine.

(Using VST3, REV 8115 inside Cubase 9.5.41)
You do not have the required permissions to view the files attached to this post.

Post

Yeah should be like that. Works just fine over here...

Post

Found the problem, it seems to be a bug: MIDI Learning is working with VST2 version but not with VST3!

I noticed though that some presets (for example "Dr. House") have both AT *and* Control A defined as different usage. So "Control A" can't really be thought of as another name for "Aftertouch"?
I must have missunderstood the purpose of Control A and Control B.

I solved the issue by using VST2 and making use of Cubase's ability to transform midi messages.

Post

That's technically a known issue/VST3 limitation and not a bug. I think MIDI Learn may have just been added to the VST3 SDK in the most recent update, but it was otherwise something that didn't exist in VST3 without unsupported workarounds.

Post

Funkybot's Evil Twin wrote: Tue Dec 25, 2018 11:42 pm That's technically a known issue/VST3 limitation and not a bug. I think MIDI Learn may have just been added to the VST3 SDK in the most recent update, but it was otherwise something that didn't exist in VST3 without unsupported workarounds.
Makes one wonder what the hell Steinberg is doing..... VST3 specs has been around for how many years now?

Post

Funkybot's Evil Twin wrote: Tue Dec 25, 2018 11:42 pm That's technically a known issue/VST3 limitation and not a bug. I think MIDI Learn may have just been added to the VST3 SDK in the most recent update, but it was otherwise something that didn't exist in VST3 without unsupported workarounds.
Thanks for that information. Guess I'll stick with the VST2 versions for a bit longer...

Post Reply

Return to “u-he”