I am loading a patch containing a vst, via the LOAD PATCH module. After the VST is loaded, I want to send the patch's PM a patch change via a buss. The VST is reaktor, and I'm using the PM to load ensembles.
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.
Send preset to VST in patch after it has been loaded
-
woodslanding
- Member
- Posts: 1327
- Contact:
Perhaps because Reaktor is a VST with potentially long load times it still needs time to finish fully loading after the patch is initialized?
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.
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.
-
woodslanding
- Member
- Posts: 1327
- Contact:
Ooh, never thought of sending a non-int value. That solves the issue of resending the same value.
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!
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!
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
-
woodslanding
- Member
- Posts: 1327
- Contact:
well, the change of preset num from X to X.1 doesn't seem to be triggering the PM to load....
Custom Ryzen 5900x MATX build, Win10, Fireface UFX, touchscreen
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Custom 2 manual midi keyboard
Usine, Kontakt, Reaktor, Synthmaster, Byome, Arturia, Soundtoys, Unify
Maybe something along the lines of this? In this example, I reset the array disp/set prior to saving, then when I reload the patch there definitely is a good pause before the A=B kicks in and triggers the increment on the fader which may be an indication of when the VST has fully activated. Worth a try anyways.

yes or sometimes i use a counter thats start on init pulse and it's end pulse actually triggs the recall
Who is online
Users browsing this forum: No registered users and 20 guests
