Loading automatically a default preset from a vst

    May 21 2011 | 7:21 pm
    I'm trying to load a vst and then, load automatically one of the default preset from this vst. But I'm going crazy because I didn't find any way to do this. I don't want to create a new preset, only want to use those which already exist in the plugin.
    I tried to manually open the vst, select a preset and then, use the message "write" to save it in .fxp but it doesn't save all the paramaters... so I can't use this option to recall an existing preset.
    Any idea ?
    Thanks for your help !

    • May 22 2011 | 10:24 am
      "plug delay, open, 7" should work.
      try to [deferlow] the message in case the 7 vanishes.
      IF it vanishes or not might also be different from plug-in to plug-in.
    • May 22 2011 | 10:45 am
      Thanks for the help Roman.
      I've already tried to send integer to the vst object but I have always the same error (for all vst) like "program 7 outside effect's range"
      Another weird thing, I've tried to change presets with MIDI, so I tested the Minimoog V vst, and when I send to it [midievent 176 0 X] and then [midievent 192 X], it's work fine and I can change the presets. But when I do the same thing with the vst I use (Chipsounds), it doesn't do anything.
    • May 22 2011 | 10:49 am
      Here a screenshot of the vst I use.
    • May 22 2011 | 8:13 pm
      midi program chance is not supported by the most plug-ins.
      but changing the preset number should work ... except when a plug-in doesnt use VST style presets (which i doubt, because otherwise remote control and save-with- project will not work in most host programs.)
      ask seb if chipsound has "normal" presets, then it _should work to send it "7".
    • May 22 2011 | 9:15 pm
      For the preset number it's weird because no matter which vst I load, I always have the same error "program 7 outside effect's range" when I send a integer in the vst~ and I don't understand it.
      "ask seb" ? Sorry I don't understand your sentence. Who's seb ? :-)
    • May 22 2011 | 10:44 pm
      This is an example of my error with Chipsounds (but I have it also with Waves, minimoog, Native Intruments, Guitar Rig, etc.)
    • May 23 2011 | 8:41 am
      By the way, I check the user guide of Chipsounds and there's a list of control change mapping we can use to control the gui. And there's no CC for the presets control.
      I tried some event like [midievent 176 20 1] and I succeed to turned on/off the arpeggiator toggle in the gui. So the plugin understand midievent, but if I can't control the presets list, maybe it's because there's no CC for that.
    • May 23 2011 | 10:03 am
      And since saving presets in .fxb and .fxp doesn't work, as saving the parameters values in a coll, I think it's just impossible.