Welcome to %s forums

BrainModular Users Forum

Login Register

Storing VSTs (Conductor, preset manager, conflicts...)

I need help on a Patch
Post Reply
La Tenaille
Member
Posts: 547
Location: Saint Etienne (France)
Contact:

Unread post by La Tenaille » 24 Feb 2012, 12:47

Hi,
I see that not all my VST parameters are stored with the conductor "store VST" function, so I try to find another way.
I've put preset managers back with my VST patches. But it seems I need to isolate the VST in a "not stored" sub patch in order to avoid storing conflicts ? Or I just need to disable the conductor VST function and leave my VSTs in the top patch with the PM ?
I see a "recall by conductor" on PM modules, but the effect is canceled by the "not stored" patch function, so my conclusion is that function is made to isolate the PM in a recalled patch, and not the contrary. I'm right ?
I try doing things the simplest way, so any help is welcome !
Thanks ;)

La Tenaille
Member
Posts: 547
Location: Saint Etienne (France)
Contact:

Unread post by La Tenaille » 24 Feb 2012, 22:40

After extra tests, it seems that only the tempo parameter from the IXox delay VST isn't stored :

dl link (just a dll, no install) : http://xhosxe.free.fr/VST/IxoxDelayV1.2.zip

User avatar
nay-seven
Site Admin
Posts: 5684
Location: rennes France
Contact:

Unread post by nay-seven » 24 Feb 2012, 23:32

I've made a quick test, seems you can improve this by using a Usine knob for parameters tempo1,2,3 and 4
min= 48, max =999

La Tenaille
Member
Posts: 547
Location: Saint Etienne (France)
Contact:

Unread post by La Tenaille » 25 Feb 2012, 13:09

Ok, and then the parameter will be controled and stored through the knob. But it means tuning the delay tempo "outside' the VST window.
I think I'm going to make my own delay with usine module and poly function, Ixox is quite basic.
Thanks for your help ;)

User avatar
nay-seven
Site Admin
Posts: 5684
Location: rennes France
Contact:

Unread post by nay-seven » 25 Feb 2012, 13:19

yes, the store VST function use the standard 0_1 values for VST inlet , the VST who don't use this standard create conflicts.

mat
Member
Posts: 57
Contact:

Unread post by mat » 02 May 2012, 10:33

i am working on this now, too.

strange behaviour: the conductor with "store vst" on does NOT store my reaktor ensembles, it just does nothing on them ... (5.08.004). is there a trick i dont know? (i did not use "not stored in conductor" in the vst patch)

the preset manager DOES store the vst, BUT: recalling snap interrupts sound, recalling direct in rektor is seamless, so not really live usable.

so how to make the conductor work on my reaktors properly?

EDIT:
the strange behaviour of conductor comes from "vst parameter ID" handling in reaktor, i think after some testing.
thinkpad t61, xp 32bit, 2gig ram, rme multiface // acer timelinex 3820t, win7 64bit, 4gig ram, NI komplete audio 6 // reaktor, battery, nuendo // roland hpd15

User avatar
nay-seven
Site Admin
Posts: 5684
Location: rennes France
Contact:

Unread post by nay-seven » 02 May 2012, 12:14

Yes, you have to check/declare your parameters in Reaktor , don't remember exactly how but test different ensembles , you'll find

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests