u-he

raring · Post by **raring** » Wed Dec 05, 2018 11:23 am

Now that there is a new SDK for VST3 I ask for revising the UHBIK VST3 plugs (Midi-learn?).
Thank you!

Urs · Post by **Urs** » Wed Dec 05, 2018 11:46 am

Yep, that's on the radar.

MIDI learn is however not possible in VST3 because VST3 plug-ins can not receive a raw MIDI stream (the controller needs to be assigned in order to receive controller data). But as with all our recently updated plug-ins, you can either MIDI learn in VST2 (and use the map in VST3) or assign controllers in a list view.

chk071 · Post by **chk071** » Wed Dec 05, 2018 11:49 am

Hey Urs,

i posted this in another thread: https://www.kvraudio.com/news/steinberg ... d-67-43543

Not quite sure what it means, but, could it be that VST3's now support native MIDI learn?

New Steinberg:Vst:IMidiLearn (Plug-in): allow a Plug-in to get the currently live playing MIDI CC to implement custom MIDI learning.

Urs · Post by **Urs** » Wed Dec 05, 2018 12:05 pm

chk071 wrote: Wed Dec 05, 2018 11:49 am Hey Urs,

i posted this in another thread: https://www.kvraudio.com/news/steinberg ... d-67-43543

Not quite sure what it means, but, could it be that VST3's now support native MIDI learn?

New Steinberg:Vst:IMidiLearn (Plug-in): allow a Plug-in to get the currently live playing MIDI CC to implement custom MIDI learning.

Oi. Who would've thought... we'll check this out!

zvenx · Post by **zvenx** » Wed Dec 05, 2018 12:07 pm

I guess midi didn't go away as planned

and they have rethought it

rsp

chk071 · Post by **chk071** » Wed Dec 05, 2018 12:10 pm

Urs wrote: Wed Dec 05, 2018 12:05 pm
chk071 wrote: Wed Dec 05, 2018 11:49 am Hey Urs,

i posted this in another thread: https://www.kvraudio.com/news/steinberg ... d-67-43543

Not quite sure what it means, but, could it be that VST3's now support native MIDI learn?

New Steinberg:Vst:IMidiLearn (Plug-in): allow a Plug-in to get the currently live playing MIDI CC to implement custom MIDI learning.

Oi. Who would've thought... we'll check this out!

EvilDragon · Post by **EvilDragon** » Wed Dec 05, 2018 1:13 pm

zvenx wrote: Wed Dec 05, 2018 12:07 pm I guess midi didn't go away as planned and they have rethought it
rsp

The only way to greater adoption is not being stubborn assholes who think they know best, trying to "fix" what was not broken and worked perfectly fine in VST2, and LISTEN to developers actually developing plugins instead.

zvenx · Post by **zvenx** » Wed Dec 05, 2018 1:17 pm

Yeah but I definitely didn't get the impression that many anti vst3 developers were against it for what it lacked but they wanted to continue working with vst2 which required little or no additional development time for them.
rsp

EvilDragon · Post by **EvilDragon** » Wed Dec 05, 2018 2:27 pm

Certainly one of the factors, but MIDI learn was a big stumbling block. Look how long it took them to acknowledge and deal with it properly. When was VST3.0 released?

Razzia · Post by **Razzia** » Thu Dec 06, 2018 4:20 am

Just out of curiosity...

to all you guys for whom midi learn is important, do you just create a map and memorize the layout for all your frequently used plug-ins? Always seemed to me like this would take a long time to get the hang of.

Or is it like... you want to test out a particular variation so you map a few relevant parameters while you're doing that?

I have Push 2, which is not exactly ideal since there isn't a particularly clean way (without third party M4L stuff) to define parameter banks yourself in a way that makes sense, but at least everything is labeled on the screen.

raring · Post by **raring** » Thu Dec 06, 2018 9:58 am

I want to test out a particular variation so I map a few relevant parameters while I`m doing that!

zvenx · Post by **zvenx** » Thu Dec 06, 2018 10:11 am

I only do my most used plugins and a few parameters that I use often obvious ones like xy's .... and it is the same cc's for all of those plugins with xy's.
rsp