I will keep testing. At least you solved the problem if slow patch changes.
Thank you.
Statistics: Posted by seamus — 17 Oct 2012, 02:03
]]>
sure that it doesn't make any confusion between differents vst's ?
Statistics: Posted by joffo78 — 17 Oct 2012, 01:25
]]>
the presets are getting mixed up between these two patches. why is that?
Statistics: Posted by seamus — 16 Oct 2012, 22:44
]]>
here is one.
i will upload another
Statistics: Posted by seamus — 16 Oct 2012, 22:42
]]>
Your setup solves the problem of the changing presets being too slow. thank you
I do have another problem.
I have used your template to create some new patches for my vsts. ONe problem i have now is that the 256 preset sub patch sometimes loads from the wrong patch.
lets say synth 1
in the presets i have
synth 1 sound 1
synth 1 sound 2
then lets say another patch called synth 2
with different patches
synth 2 sound 1
sometimes when i change a conductor preset usine loads the wrong preset manager into the vst.
i dont know how it is doing this!
i will upload a couple of the patches so maybe someone can tell me why this happens.
I tried naming the preset manager inside the patch something different for each but its still a problem
Statistics: Posted by seamus — 16 Oct 2012, 22:40
]]>
synthnsbyjoffo
in my version only one knob is recalled by conductor.
in this way there's no problem execpt curiously the script witch recall preset create a smooth transition between presets.
I resolved this problem with a stop module on the knob.
You can try it but you will to upgrade your vst module because as i hadn't it usine replace there by empty modules.
Statistics: Posted by joffo78 — 15 Oct 2012, 13:48
]]>
i have uploaded a typical patch from the way I have been trying to add presets to vst's which are then recalled by the conductor.
I think your method should work better. Its nice to see the presets in Usine and then quickly call them up with the conductor.
I suppose I need to reconfigure all my patches with your method Joffo. I was having some trouble with the way I have the preset manager used. Sometimes preset managers from different patches would get confused and show up in the wrong patch. Yikes!
Im going to try and use your method and report back.
thanks!
Statistics: Posted by seamus — 15 Oct 2012, 07:55
]]>
I think your trouble came from a conflict between parameters saved in conductor, in the vst preset and preset manager in the same time.
I tried to find a solution for you :
recall
instead of recalling preset manager directly by the conductor, i put it in a sub patch with the vst that can't be recalled by the conductor.
only one knob (not in the subpatch) that recall the num of memroies is recalled by the conductor . In this way is if you recalled manualy the preset manager et so there are no problems.
why do you need 4 preset manager ? Have you tried the 256 preset manager made by 23fx23 ? I use it in my patch.
Does it work for you ?
Statistics: Posted by joffo78 — 14 Oct 2012, 11:32
]]>
here is how my conductor is looking.
I tried changing the bloc size and refresh speed but it didnt help
bloc size is 32
refresh speed is ultra fast 1ms
Statistics: Posted by seamus — 13 Oct 2012, 19:35
]]>
I have a patch with FM8 inside it. I have 4 preset managers that have sounds stored in them.
each preset manager is set to "recall by conductor"
My controller sends out program change messages to the conductor and i also use the arrow buttons on the conductor to advance or decrease by one with a midi foot pedal attached with midi learn.
sometimes there is quite a delay and sometimes the patch doesnt recall the vst settings properly. Sometimes the vst wont change settings at all and i have to try a couple times.
any tips?
Statistics: Posted by seamus — 13 Oct 2012, 19:19
]]>