Thanks

I’m not sure how you came by these names because the example patch you send is completely missing the most obvious part – the bit where you send the message “params” to each of the vst~ objects when you load them and then the logic you’d use to collect the output from the third outlet of the vst~ object. Unless you know the *specific* name of a parameter that is specifically related to whatever the currently loaded plug-in is, you’ll be sending messages from now until the cows come home and nothing will happen.

Perhaps you might find these tutorials to be of some use to you.

http://cycling74.com/2005/04/14/investigations-part-1/
http://cycling74.com/2005/04/21/investigations-part-2/
http://cycling74.com/2005/04/28/investigations-part-3/

http://cycling74.com/2005/05/02/investigations-part-4/

I have reviewed the documentation you provided and while helpful I still think this is an issue. I have attached the patch with the VST included as it is a free VST that you can use to see what I am talking about and this does not jsut happen for this VST it happens to all VST's that I have tried using, but works fine in MAX 5. I have also provided a screen shot showing the params are correct in my patch. For what I want to do the steps you provided seem to much for a simple task. You can test this in max 5 and it works. Then test this in 6 and change the setup of your midi controller to the values I have or to whatever you like for you own controller. You will see that this works in 5 and does not work in 6. If you could provide something that might have changed in the way this works in max 6 that would be great.

[attachment=189086,3577]

http://valhalladsp.wordpress.com/category/frequency-shifter/

1) I tried using a different VST (Guitar Rig) to ensure that the problem was not due to a specific VST, got its parameter list but was unable to change any parameter

2) I then loaded the identical patcher under Max 5.1.9 and observed that it worked fine.

Something else of note: I normally just use parameter index and values rather than names and those work fine in both Max 5 and Max 6. So I normally display the data coming from the fourth outlet of the vst (that outlet shows parameter index and value whenever a parameter is changed, either by tweaking the VST GUI or by sending a new parameter in programmatically). Under Max 5, if I send one of the parameters by name (like vx6025 did), then I see the corresponding parameter index for that name.

However, if I do the exact same thing under Max 6, then the parameter index that I see is always 1, no matter what name I send in (including bogus names).

So there’s clearly something wrong with how incoming names are being processed in a vst~ under Max6

I’ll log it

Thanks

Andrew

In Max5 its named for example “Filter2Freq” (it works). And the same parameter in Max6 named “Filter 2 Freq”. There are newly SPACES between! And it didn’t work with spaces!

Not all VSTs are affected of this space-phenomena.

Please help, it would be grate if common stuff like this will work

the names can be helpful for displaying the parameters somewhere, but for parameters
it is enough to use the integer ID.

from the viewpoint of the VST interface i may say that named parameters never had another
purpoe than displaying those names to the user. a VST host program such as a max patch
should only work with IDs.

but there are also some plug-ins with empty or nondescriptive paramater names, otoh, which
would be the first reason already to use numbers. :)

Cheers

-A

:) and when it will be released?