]]>
]]>
I've addressed everything by number, so I don't know about addressing by name.....
Statistics: Posted by woodslanding — 22 Dec 2016, 23:40
]]>
When I double click on the sub patch, then return to the parent view, the i/o pins are correctly displayed
Now if I Wire some of the i/o pins (to show a better visual example, and to also confirm incorrect internal wiring) and drop another (or same) VST on the subpath, the internal wiring is all funky again. Once again this is not a GUI refresh issue, the sub patch wiring is definitely wrong. Each time I reload the contents of a sub patch in this fashion, the internal wiring sems to randomly change, but it is always reset after double clicking the sub patch. Does anyone else see this sort of behavior in their Usine HH setup? I am wondering if perhaps sub patches are just not intended to be used in this way or if what I am seeing is a bug of some sort..?
Also, in my digging around the concept of IML and sub patch loading / wiring I am noticing the behavior for wiring sub patch pins to be a little quirky. For example, audio inputs to a sub patch can be addressed by terminal name in IML. however audio outputs cannot? Also, in order to load a patch and wire patch i/o modules pins by terminal name, I need to send the CREATE_LINK messages in a separate message after the patch has loaded. Is I use terminal numbers instead of names, I can put the commands for both load patch and create link in the same send message module, so it seems there is a lag for terminal names access?
Also it seems strange for me that that if I insert an i/o module in the sub patch, all of the following terminal numbers are changed, so for example if the terminal number for name out in a sub patch is 11, and I add a data in module to the sub patch, name out is moved to terminal position 12, which breaks and existing IML for wiring to that pin (and no pins below bitmap in and bitmap out are addressable be terminal names at all)
What would make more sense to me and be a lot more user friendly for IML access of sub patches i/o is if all of the default i/o of an empty sub patch had fixed terminal numbers, and any additional 1/o would be be added to the bottom of the terminal index in the order added to the sub patch, and if all terminals could be accessed by name.
I'm still just learning my way around this stuff so maybe this is all normal, I am not really sure.. But maybe if there is some unusual behavior in sub patch i/o handling / IML etc it might explain why sometimes wires in patching have wiring to the wrong / no pins or error messages when i/o modules are created or renamed..
Statistics: Posted by gurulogic — 21 Dec 2016, 01:32
]]>
Statistics: Posted by gurulogic — 13 Dec 2016, 11:01
]]>
GET_VALUE VSTNAME_A PARAM_TO_GET TEMP_VARIABLE_NAME = get value from vstA param X and temp store to tempvariable
SET_VALUE VSTNAME_B PARAM_TO_SET TEMP_VARIABLE_NAME = reapply value stored in buffer to vst b param X
Statistics: Posted by 23fx23 — 13 Dec 2016, 10:54
]]>
Assuming I'm on the right track, or even close, what I'm not getting from looking through the wiki documentation is how I would assign the retrieved value to another module's value.
(Rather than spamming the forums with new topics, if I have any further IML related questions I will try to keep them here. Thanks for patience!
)Statistics: Posted by gurulogic — 13 Dec 2016, 10:44
]]>