In my wkp, I use LOADPATCH to load a new patch that hosts a vst. Then I want send it a LOAD FROM FILE DIRECT command. Problem is, in my large workspace (it works fine in a smaller test bed) it seems like there is a delay before the busses get connected, so the LOAD FROM FILE command doesn't go through, and the process stops. I already discovered I couldn't trust the 'patch loaded' flag in the load patch module, because even though the patch is loaded, there are busses not ready to send --specifically one that gives the load from file its path. So now I wait for the send buss to send out before trying to load from file.... but apparently the recieve for the load file trigger still isn't ready, and I can't figure out how to know when it will be...
Thoughts??
Thanks!
-eric
How to know when a new buss is ready to get data?
-
woodslanding
- Member
- Posts: 1327
- Contact:
How to know when a new buss is ready to get data?
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
Hi,
Maybe you could simply wait a moment then send the command to load a file through the bus, or you could have a system to check if the bus is working.
a clock send 0 or 1 through the send bus, then at the receiving end, the other patch check if values are changing within the same time frame as the clock, that means that bus is working. is bus is not working, the output of the ">0" module will go to 0. so each time your first patch will load, ">0" will go to 0 then after a while it will go to 1 .
it's a like an "active sensing" on old Midi system
Maybe you could simply wait a moment then send the command to load a file through the bus, or you could have a system to check if the bus is working.
a clock send 0 or 1 through the send bus, then at the receiving end, the other patch check if values are changing within the same time frame as the clock, that means that bus is working. is bus is not working, the output of the ">0" module will go to 0. so each time your first patch will load, ">0" will go to 0 then after a while it will go to 1 .
it's a like an "active sensing" on old Midi system
http://oli-lab.org
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces
follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social
-
woodslanding
- Member
- Posts: 1327
- Contact:
here's what I came up with... it seems to work. I just keep sending the trigger to load until I get a loaded command back from the patch.
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
Who is online
Users browsing this forum: No registered users and 8 guests
