Can't set VSTi presets (SOLVED)

[pepperdas]

If I add a vsti and a preset for that vsti to a midi track in either reascript or the gui, as soon as I start playing the track the preset changes to the default preset of that vsti.
I can't set it to a preset and then render.
Is this a bug or something that I'm doing wrong?

[foxAsteria]

Uh, if you you're using scripts to set presets, that's probably going to override anything else you try to do. What script are you using and why don't you just set the preset from the Fx window?

[pepperdas]

This happens when I'm not using any scripts. I simply cannot import a midi file, add a vsti effect to it, then add a preset to the vsti and have the vsti keep that preset when I go to render. It always goes back to the default preset for that vsti. This has nothing to do with scripts. I'm running Reaper 5 on Windows

[ivansc]

When you say "add a preset" are you talking about selecting one from the VST`s drop down list of presets, or making a new one and presumably saving it?

And you DID mention reascript in your initial post, which I suspect is why there is now a little confusion here.

[pepperdas]

This is not a question about scripts. I'm having this issue with common vsti synths like crystal synth and Dexed. when I import a midi file to a new track using add media, add a vsti to that file and set a preset on that vsti from the drop down list, the preset moves back to the synth's default preset whenever I press play or render. I have tried this on various versions of reaper 5 and 4, all without luck. I'm using win7

[nofish]

Originally Posted by pepperdas

I simply cannot import a midi file, add a vsti effect to it, then add a preset to the vsti and have the vsti keep that preset when I go to render.

Where do these MIDI files come from ?

Downloaded from internet by chance ?
These often have program change messages inserted which can affect (change) presets.

So if so, try checking your MIDI files for program change messages and delete them.

[DarkStar]

<< Edit: too late, but already typed >>

Have a look at the imported MIDI file in the MIDI Editor / View mode: Event List.

There may be some Program Change (PC) messages that when sent to the plug-in change the preset to the first one. If so, then delete those PC messages (or change the value to select the preset you want).

Details are in the User Guide.

[pepperdas]

This was it! You guys were both right. I had generated the midi from a script, but the library I was using added a control message to the first track.
Thanks for the help, and problem solved!