VST~ Presets Location
I’m trying to create a max collective that uses the KTGranulator (http://koen.smartelectronix.com/KTGranulator/) plugin with the VST~ object.
I can get everything work but when I open the patch in max 6 runtime on another computer, the presets don’t load and I can’t seem to find where they are saved.
There are a couple of things you might want to consider with your patch.
Specifically related to the Granulator VST, (or any vst), the best way to save the file is to send the VST~ object a "write" message, and manually save the preset file rather than including the name of what you want to save in the message object. That will open a dialog box that shows you a) where it’s saving it and b) the name of the preset (which will include either .fxp or .fxb as a file extension. go with .fxp as a preset — fxb is for a bank, though both should work). Then you can include that preset file with your patch.
Second thing: you are referencing "gigaverb" in your patch, though you don’t include that external.
Finally, you might want to either check out the "list all externals" option in the file menu to double-check all of the externals you’ll need to include, or alternatively you can build a collective. If you go with the latter solution, you will have to manually add the preset and vst plugin to that script.
Hope this helps.
This is really helpful! Thanks for pointing out the obvious with the gigaverb~
Vis-a-vis the vst~ object: When I send a "write" message to the vst~ object, I get an error, with the max window saying "write: requires preset name." this seems like an au specific thing, though I could be wrong. (PS: I’m working in max 6)
Any other thoughts on how to save a preset?
I also tried sending specific params within the KTGranulator but it doesn’t seem to work when I send the vst~ a message for the specific params I want to edit (specifically: MaxDelay within KTGRanulator)
Oh that’s right. I forgot it was an AU.
AU’s often allow you to set parameters using the parameter number, and KTGranulator does as well. Save that data in a coll object, load it when the patch loads, dump the data to vst~ and you’ve got a preset!
If you open the ZIP attached, you’ll see how I set it up.
Thank you so much!!