dhjdhjdhj

I've run into a problem with a couple of new VSTs that I purchased (Aalto and Kaivo, both from the same company) where, if I load one into a new [vst~] object, they will not accept MIDI events. If I then load something else (e.g, FM8, Kontakt) into the same [vst~] object, send it a MIDI event (seems required), and then reload Aalto, Aalto then works just fine.

I'm assuming that the [VST~] object queries the plugin to determine its capabilities and I'm wondering if Aalto is returning the wrong answer and so MIDIEvents are disabled.

vst-support-and-the-cando-request

Aalto works fine for me, if i load it into a brand new vst~. ( i tried both AU and VST and both were fine)

(do you get the same if you use the help patcher?)

the only oddity I've noticed, and already reported to Madrona Labs, is that the automation parameters are incorrect.

Randy has said he will investigate. (this seems to be a regression as there is a video showing it working in an earlier version)

Aalto works fine for me, if  i load it into a brand new vst~. ( i tried both AU and VST and both were fine)
(do you get the same if you use the help patcher?)

the only oddity I've noticed, and already reported to Madrona Labs, is that the automation parameters are incorrect.
Randy has said he will investigate. (this seems to be a regression as there is a video showing it working in an earlier version)

ok, Ive just found out something very interesting which might be relevant...

the issue with automation names being reported incorrectly only happens if the DAC is not started, this is unusual as all other VSTs I have work without the DAC started. (Ive reported this also to madronalabs, and hope now its more specific they can resolve it.. as i have a similar with VEP which I think may be related)

Im not quite sure what you are sending the vst, but perhaps you have a similar issue where at the time you are looking for something (via get -? ) the DAC is not connected, and so the plugin reports incorrectly?

(though I will say, the above behaviour is consistent, loading another VST into the vst~ does not change this behaviour)

I'm not doing anything I don't do with other plugins. Just sending the appropriate message to the [VST~] to load a plugin. DSP is enabled.

Note that I'm doing this under max 5.1.9 but as I said, I have not seen this problem with any of my other plugins (about 80 or so, so not a small number)

I'm not doing anything I don't do with other plugins. Just sending the appropriate message to the [VST~] to load a plugin.  DSP is enabled.

Note that I'm doing this under max 5.1.9 but as I said,  I have not seen this problem with any of my other plugins (about 80 or so, so not a small number)


also the other UI bits and poly vst~ stuff i have of yours, also works with Aalto/Kaivo (for me, under Max 6)

(Ive also used kaivo/aalto in quite a few hosts - VEP,LPX, Live, Bitwig, Numerology and EigenD and except the above automation issue, not had any other issues)

sorry, I know, not too helpful... but if you have an example patch that doesn't work, I can run it here to test for you.

Otherwise, I guess, chat to Randy @ Madrona Labs and see if he knows of any issues (he has a couple of max users i think)

hmm, hard to say... works for me.
also the other UI bits and poly vst~ stuff i have of yours, also works with Aalto/Kaivo (for me, under Max 6)
(Ive also used kaivo/aalto in quite a few hosts - VEP,LPX, Live, Bitwig, Numerology and EigenD and except the above automation issue, not had any other issues)

sorry, I know, not too helpful... but if you have an example patch that doesn't work, I can run it here to test for you.
Otherwise, I guess, chat to Randy @ Madrona Labs and see if he knows of any issues (he has a couple of max users i think)

Yeah, I've emailed Randy as well. Haven't tried it yet with Max6. Very odd though that everything else I've thrown at Max5 to date has been fine.

VST support and the canDo request