sdk.steinberg.net

Musicians struggle all the time to handle MIDI, especially young ones. Even I struggle sometimes even though I speak MIDI for 30 years. MIDI-CC is a black box system, that no one can understand without looking in the manual of the product, or all the products you work with. That was OK for the time ...

bluecataudio wrote: ↑

Mon Jun 24, 2019 8:36 am

Also MIDI CC can be used for many things (not only parameter changes)

What are these many things? Are you sure that these things are not workarounds to do something an audio plug-in is not supposed to do?

Hi, from my personal point of view, a plug-in should not handle MIDI-CC at all. It's the responsibility for the host to map input events to parameter changes. The host knows what external hardware is connected and which routings are active. A plug-in does not have the knowledge about this. As a plus...

it's a)

Why don't you create a plugin capable to process 6 channels at once ? Why does this need to be on different tracks ? Most use-cases can be implemented via multiple event input busses and/or the note expression feature in VST3.

Hi,
sure it's possible, but involves work from your side.
Read
https://github.com/steinbergmedia/vstgu ... _changes.h
especially the section: code_changes_3_6_to_4_0.

I hope this helps,
Arne

For everyone who uses the dialog, can you tell me why you use it and not the vst validator? Is there something missing in the validator?

Hi Will,
this was not intended. There's just one header include missing in testbase.h: The next SDK will include this change.

Sorry for the inconvenience,
Arne

Hi,
we consider to remove the dialog as most of the tests are available in the validator.
To get a better picture, please tell us if you use it and if you will miss it.

Thanks,
Arne

Check the "Open in Low Resolution" option in the Finder Info for the editorhost app.