]]>
Statistics: Posted by gurulogic — 11 Feb 2017, 01:04
]]>
]]>
I forgot about the params array trick--I've used that in Max, I'll try that too. Possible problem is that I also may take patch changes AFTER the patch has been loaded, and don't want those double-triggering....
Thanks much!
Statistics: Posted by woodslanding — 10 Feb 2017, 23:11
]]>
A couple thoughts to try, use an on init to send a very small value of say 0.0001 to the bus sending the preset change number to resend the preset number when the patch has loaded. If it is a case of the VST not being completely loaded and ready for a preset load, perhaps try a sum array connected to the VST params out to trigger the preset number send when the sum array has a value greater than 0.
Statistics: Posted by gurulogic — 10 Feb 2017, 21:22
]]>
I cannot get this to work right. the buss in sends the change before the VST is ready for it. The PM says the patch is correct, but it hasn't actually been loaded. I tried storing the buss value in a VAR, and triggering via ON INIT, but it doesn't actually trigger, perhaps because the VAR module has not been initialized when the ON INIT trigger comes.
I tried ON ACTIVATION, but that does not trigger at all in this scenario.
Thoughts???? Any tips welcome, thanks in advance.
Statistics: Posted by woodslanding — 10 Feb 2017, 20:08
]]>