Originally, I had an inspector for every channel, and only showed the relevant one, which was pretty high overhead, but for HH3, I made a real one that sends and receives values. It's run by some complex scripts, and all the data is sent in a single array where the first element is the channel, so the data can't end up getting sent to the wrong channel. It works okay, but can't send text, and does have some wierd subtle bugs I haven't been able to track down. So I thought I'd try and simplify, and do it all with patching, which I've never been able to get to work before.
My idea is this:
I have sends and receives in separate subpatches in each channel. When I change the channel of the inspector, the busses from the old channel are turned off, and those for the new channel turned on. This has to come in a very specific order, so that data from the previous channel doesn't overwrite the data on the new channel. The order looks like this:
disable input busses on channel we are leaving
disable output busses on channel we are leaving (not sure if order of first 2 matters...)
enable output busses on newly selected channel (so new ch's data is sent to inspector)
enable input busses on new selected channel (so inspector can change new ch's values)
I set this up with a very long delay between steps 3 and 4, and I have traces in every step of the process, and here is what is happening:
Even after 2000ms delay of step 3 above, data from the new channel is not being sent out (trace shows it has been enabled) So then step 4 happens, and old data from the previous channel gets sent from the inspector (seemingly before the input buss subpatch has even been enabled!) Then the output buss finally sees a value on the channel control, and sends the (now wrong) value to the inspector!
Not sure what is going on. I've tried all sorts of things to get that output buss to 'wake up' when it is enabled, and send its value, but nothing works. The control has a value, it is hard wired to that send, and the corresponding recieve is seeing a different value..... what gives????
Thoughts? Here is my little test wkp, so you can see what's going on, as I realize it may not be all that easy to understand from reading about it.....
http://www.sensomusic.com/forums/upload ... estWKP.wkp
You can click on the buttons to change the inspector channel.... then you can change a value in the inspector control, and see that the ch value is changed. Then you can select the other channel, and watch as the data from the old channel (after 2000ms delay) gets sent to the new channel. And you can see the order of everything in the console.
For some reason, the inspector gets set to 0, even though there is no means to send a 0 to that buss...(I guess it's the response to a null event from a switch??) so you need to flip back and forth between channels once before testing, to insure everything is correctly enabled and disabled.
thanks in advance for any tips....
-ericStatistics: Posted by woodslanding — 27 Nov 2017, 05:13
]]>