Help understanding how to use VSTi’s correctly

[neufena]

I’m starting to get better at patching but one things still confuses me, how to control vsts correctly. I understand that if I create a patch with a vst in it, edit the vst’s parameters and then save the patch then the vst’s parameters will be saved. However live I use the same vsts for more than on tune and switch tune using the conductor to change the settings. However the conductor doesn’t seem to change vst parameters, just native usine ones. Should I be using vst presets and then getting the conductor to change present for each tune? If so how do I achieve this?

Thanks,

Neufena

[bsork]

You could use the preset manager module and save all the settings for the patch that way.

I'm not quite sure about the following since I haven't used the Conductor much, but I think that you'll have to connect a fader to the preset manager's num inlet since the preset manager doesn't respond to the Conductor.

[Vincent]

Hi Neufena,
you also can connect a fader or a list to the "program" inlet of your VST and store its configuration in the scene. Obviously, that will work only if some presets are stored with th VST, example: "Church front", "Church middle", "Church back", etc... in a reverb VST.

[neufena]

Thanks for the replies, using the program inlet sounds like the best way for me to go, I have to start looking into how vst presets work!

[senso]

You can use several copies of the same vsti in the same patch or wkp.
When you save/recall the patches, you reteive the vsti's in the same state you saved them.

[neufena]

Does that increase the cpu and memory load for each instance? I'm running at about 85% memory at the moment!

Thanks,

[senso]

yes, each instance is independant and has it's own place in memory.
If you don't need automation try the [ctrl]+ drag&Drop of the vst to create a lite verstion and reduce the memory load.

[martignasse]

hy,

You could use the preset manager module and save all the settings for the patch that way.

I have a question about the preset manager.

I discover taht the preset manager don't work at sub_patch level.
I explain :

I have a simple patch with a VST and a couple of fader to control it, and a preset manager to store faders values.

If i save this patch and use it has a subpatch, connecting some faders to control it at parent-patch level, the subpatch preset manager doesn't work anymore.
In fact, i believe it's because sub-patch faders to be no more fader, they become just connexions, and the active faders are at the parent-patch level.

And i don't want to use a preset manager at the parent-patch level, because it will store lot of other things that i just don't want.

What i want is that the sub-patch preset manager work and "intercept" the fader/connexion value, is it possible ?.

I hope it's clear.... and someone can help me

[senso]

yes you are right the preset can't be recalled in a subpatch.
I'm not sure I understand your problem:
what do you mean by "intercept the fader connexion"?
When you connect a wire, the target control becomes "slave" of the source, except if you use a "stop event flow module".

I can change and turn preset active in a sub patch.
Let me think about it.

[Vincent]

Hi martignasse,
I'm not sure I understand this thread... I use some preset managers in sub-patches (an sub-sub-patches), they work fine. I event use busses to recall presets with only one User Curve that can be drawn in any other track. Not very easy to store, but once stored, it works fine.
The Preset Manager does not store stuffs in sub-patches and it's an interesting feature (example: if I plug GVI in a sub-patch, GVI does not have to reload all it's instruments - some gigabytes - each time the Preset manager in the parent patch recalls a preset).
I'm sure we could find a solution to your patching without any changes in the Preset Manager module implementation. I just need to clearly understand what you need. Maybe some small screen-shots?

If your Preset Manager only stores faders position (no VST parameters), the idea would be to simply move it (and the linked faders) in the parent patch, and of course, wire your faders to the sub-patch, then to your VST.
What do you think?

[martignasse]

ok guys,

i'll try to be more explicite (can't make screenshoot at work)

1/ I make a patch, with a VST, some faders and a preset manager.
I can redirect the preset manager and faders on the interface builder.
all is ok, the preset manager work, no probleme


2/ I save this patch, and use it as a a sub-patch.
I always can redirect the preset manager to the interface builder, but no more the faders, as there become "connexion slot" off the sub-patch.
At this point, the preset manager is working, but i have no more fader on the the interface builder


3/ Has i need the faders to be in the interface builder, i connect some new faders to the sub-patch and redirect them to the interface builder.
But now, the preset manager doesn't work anymore

[martignasse]

ok,

better than screenshot, a workspace, to show you my problem :

http://mfleurent.free.fr/usine/preset problem.wkp

and a screenshot to :

[senso]

ok, clear now.
Inlets of the subpatch are "slaves". Their values are set by fader modules, so stored in the "mother patch".

What ever you do, they will stay slaves.

Try the following way to

1) you can create a new inlet in the sub patch, connected to "num" of the preset manager.
2) create a new fader in the mother patch connected to this "nun" inlet
3) Add a new preset manager in mother patch and store new "global" presets


There is another way to deal with flow in Usine

in your sub patch actually you have some thing like that

Fader Attack ----> Attack inlet of a module

Try to create the following path (insert "pass if has changed" module in the flow path)

Fader attack -----> pass if has changed -----> Attack inlet of a module

I hope it can help you

[martignasse]

ok, clear now.
Inlets of the subpatch are "slaves". Their values are set by fader modules, so stored in the "mother patch".
What ever you do, they will stay slaves.

Yep, i understood that, but i was believing that the preset manager can deal with that. In my head, if i put a preset manager in a patch, it's to have some presets at this level, and it should continu to work if this patch become a sub-patch.

1) you can create a new inlet in the sub patch, connected to "num" of the preset manager.
2) create a new fader in the mother patch connected to this "nun" inlet
3) Add a new preset manager in mother patch and store new "global" presets

I tested that, it's not solving the probleme of "global" presets, and i don't want that.

There is another way to deal with flow in Usine

in your sub patch actually you have some thing like that

Fader Attack ----> Attack inlet of a module

Try to create the following path (insert "pass if has changed" module in the flow path)

Fader attack -----> pass if has changed -----> Attack inlet of a module

I hope it can help you

This is where i found a solution, not very elegant but working well

and at sub-patch level :
The "Pass if change" modules make the preset manager working

at global patch level :
I had to make this loop with these "Pass if change" modules to be able to control the faders in the interface builder.


and the workspace :
http://mfleurent.free.fr/usine/test_soluce.wkp

So, with usine, all is possible