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.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.
I tested that, it's not solving the probleme of "global" presets, and i don't want that.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
This is where i found a solution, not very elegant but working wellThere 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
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
Statistics: Posted by martignasse — 23 Jul 2007, 22:49
]]>
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
Statistics: Posted by senso — 21 Jul 2007, 10:12
]]>
better than screenshot, a workspace, to show you my problem :
http://mfleurent.free.fr/usine/preset problem.wkp
and a screenshot to :
Statistics: Posted by martignasse — 20 Jul 2007, 18:37
]]>
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
Statistics: Posted by martignasse — 20 Jul 2007, 14:24
]]>
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?
Statistics: Posted by Vincent — 20 Jul 2007, 12:46
]]>
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.
Statistics: Posted by senso — 20 Jul 2007, 09:05
]]>
I have a question about the preset manager.You could use the preset manager module and save all the settings for the patch that way.
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
Statistics: Posted by martignasse — 19 Jul 2007, 21:04
]]>
Statistics: Posted by senso — 13 Jun 2007, 17:44
]]>
Thanks,
Statistics: Posted by neufena — 13 Jun 2007, 16:57
]]>
Statistics: Posted by senso — 13 Jun 2007, 16:49
]]>
]]>
Statistics: Posted by Vincent — 13 Jun 2007, 13:48
]]>
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.
Statistics: Posted by bsork — 13 Jun 2007, 13:39
]]>
Thanks,
Neufena
Statistics: Posted by neufena — 13 Jun 2007, 13:25
]]>