Forums > MaxMSP

help with vst~ and pattr…

November 29, 2009 | 10:56 pm

Hi,

I really need help with this.

What I’ve done so far is a vst~ data wrapper as an abstraction; it works fine, despite some bug here and there. There it is

First, save this as vst_preset (you need it to be open in presentation mode)

– Pasted Max Patch, click to expand. –

and this is the main patch

– Pasted Max Patch, click to expand. –

The core of plugin data saving/recalling is in the lower part of the patch
[p store] and [p recall], and pattr of course.

Basically,the plugin data coming from the vst~ object at centre of the patch are stored in a multislider inside [p store] and then in a pattr (named pattr #1_pattr , where #1 will be Vst1, Vst2,…according to the number of instances open in the main patch). Data from pattr are then recalled from the bpatcher attached to pattrstorage (named #1).

As I said, saving and recalling data seems to be fine, the problem comes when..I can’t explain this in words, I’m italian after all, so here’s the steps:
-save the main patch and open it in two different bpatcher, with a different name as argoument for each one;
-load a plugin and save some preset, then save it in a file; that file will not work in the second bpatcher, that is named differently.

What am I doing wrong?

Any help is greatly appreciated


December 1, 2009 | 11:37 am

hello,

i’m afraid i don’t have time to find out exactly what’s wrong with your patch. I made a similar thing though, which you can find here:

olilarkin.blogspot.com

oli


December 3, 2009 | 9:51 am

Thanks oli, I’ll have a look at your patch, I’ll learn something for sure.

I’ve better focused what seems to be the problem in my patch, I’ll post something the next days.

marco


January 1, 2010 | 8:49 am

Your pattr needs to have the same name. just name it vstpresets or something like this (without #1). I think your complete p recall could be replaced by listfunnel…

I would include another pattr with the vst plugin name in the same pattrstorage. Or you might get surprises if you load a preset file which belongs to a different plugin. (could blow speakers and ears…;-)

Next time, if you have a bpatcher to be loaded in a main patch, you could embed the bpatcher before posting, then you’d have a single patch to paste… (just don’t save that version at home, as you might want to keep them still separate on your drive…)


January 1, 2010 | 10:13 am

Thanks for your reply, stefan.

So, I’ll try give all my vst~ pattr the same name, and replace the p recall with a simpler listfunnel.

And yes, I have to include the vst~ name in the storage file..hope I can post something in the next days, so you can have a look.

Thanks again.

PS: next time I’ll embed!


March 19, 2010 | 4:59 pm

Stefan, many thanks for your hint..now I can recall preset in every instance of my vst handler, and it works great!

Recently I’ve added an autopattr, in order to save the on/off state of the entire bpatcher and the vst loaded by the umenu from a main patch; the result is that the parameters of the vst are no longer saved, and I can’t figure out what is wrong..

Any suggestions?

Thanks


March 19, 2010 | 9:21 pm

I would think there is a bug in your patch…
In this case finding it should be possible, as you have states before putting an autopattr in, which seems to have worked (you know where you put it, I don’t…)
Just go back and analyze step by step till it breaks again…
I need sometimes more time for debugging than for patching…;-)

Stefan


March 19, 2010 | 9:50 pm

And you’re right again, it was a bug, fixed now…thanks for your patience.

Cheers, mate!


Viewing 8 posts - 1 through 8 (of 8 total)