Vst Weird'ness

[Drnkhobo]

Hey Guys,

Ive been having some weird problems with a synth of mine. . . support isnt too interested in my problems so I thought i'd ask you peeps here.

It begins with a simple synth. I export 2 versions of it, stereo & mono.

Now, I can see them in FL Studio but ONLY the stereo vers in Cubase. . .

By the fact that FLStudio see's it and it works, then that must mean its not my code, rather something with Cubase AND my code. . .

I have been trying to figure it out but im getting nowhere.
Does anyone have an inkling why Cubase is being funny?
Has anyone had a similar problem??

Thanks !!!!

[matti]

Do you have different ID and filename on them?

[trogluddite]

Yes, matti is most likely right - some hosts use the .dll filename to recognise plugins, but others use the ID code.
Changing the filename doesn't automatically change the ID code, so if your plugins are exported from the same schematic, sometimes the host will think they are the same one.
A new random ID number usually fixes it...

VST ID.jpg (4.18 KiB) Viewed 20543 times

[Drnkhobo]

Thanks guys!!!

I think I would have gone MAD trying to figure it out !!!

I changed it and it works!

- see it helps to have a long term knowledge on these things!

[trogluddite]

Great - glad you're all fixed up!

[Drnkhobo]

Thanks guys!

Ive had some problems before with crashes but its all fixed up now

[Drnkhobo]

alright, im back.

My VST seems to be quite unhappy with the way I have been treating her & is hell bent on destroying my fun!

It seems now she likes to change knobs/sliders by herself everytime I load her up.

EG 1.

I save my project with my synth (ALL preset params are correct, I checked) with a knob at 12 o'clock. . .
I then load up my project and the knob is now at 7 o'clock. . . wtf?

I checked the default settings of the knobs and they are fine.No probs here. . .

WHY WHY WHY WHY WHY WHY ?? ?? ?? ?? ?? ?? ??

Has anyone else had these phantom movements???

Is it just me? Or should I accept that this is the way it is ?

[tektoog]

hey,
what you have to do is to save your actual working preset as a .txt file (save with preset manager) and then to load it up again before exporting to VST.
For a bank ("Save all") make your settings for each preset...once you've got them all all right... save them all also as a single preset... re-upload them, then...save the whole bank with the "save all programs" feature in the preset manager....Reload it ("Load all") in your FS project before exporting to VST.
Of course each knob(or component) in your project needs a unique parameter name: button1, button2 etc....
Also to be sure everyting is working fine, open a new project in your host,because if you use the same project, the host might load the stored paramaters of the previous session instead of your default settings...
Hope this helps....

[Drnkhobo]

Thanks Tektoog, I have done that already in FS. I meant in my DAW ( i dont think i was clear on this sorry)

I have made sure all preset names are unique and exported to VST with them all in the correct place.

It seems to the the host not loading up the correct settings for my saved projects. It loads them in default (like INIT settings) even when I saved them with different settings. . .

Is it me being stupid?

what you have to do is to save your actual working preset as a .txt file (save with preset manager) and then to load it up again before exporting to VST.

Does this have something to do with the way DAW's load parameters?

the host might load the stored paramaters of the previous session instead of your default settings...

The thing is my default settings are fine. Its when I save a Cubase/FL project with certain settings , then load it up again, the parameters have changed!!! So I have to start from scratch!

[tektoog]

The thing is my default settings are fine.

Sorry I meant the original settings of your preset...

the parameters have changed!!! So I have to start from scratch!

Well, are the changed values always the same or are they different each time?

The preset saving and reloading has to be done in FS before to export to VST. It's like a freeze... So if no triggers or commands are sent by the DAW on the openeing (in a new project), there is now reason for the values to change
To start debugging, firstly you might want to use only one preset within your preset manager, so no mistake will be made due to a preset confusion.
Also make sure that you DAW loads your plugin on midi channel 1,for example I know that Acid pro 7 tends to create new tracks in a project using channel 2 and very often I have to change the midi channel to 1... even with expererience it happens regurlarly that it takes me some time before I realize that my track uses channel 2... when I reload my project all parameters are set up according to the preset linked to channel 1... that sucks....
Do you use an afterload prim in you schematic? the changing values could also come from tricky triggers sent by the afterload prim...
Are your parameters value in the 0-1 range? other values not in this range can be not well interpreted by the host...
In brief, if any of this works for you, you might want to post your schematic so we can have a deeper look at it...