Load Patch behaving strangely.
Posted: 22 Oct 2022, 08:36
]I am trying to implement global patch saving for my setup, which is challenging, as it requires loading a particular patch from memory via script, and then loading a patch for it from memory.
I have the mechanism figured out, but I hit a snag. For some reason, when the LOAD trigger is sent via a different routing in this patch, the patch does not load correctly. It seems to be trying to reload over and over again, and it keeps changing size and disapparing and reappearing in the control panel. Here's what the patch looks like:
When I load the patch via the matrix mouse down, it loads just fine. But when I load it from the quicklink at the top, it has the issue. I'm searching the same commatext in both cases, for the same text string, and the resulting number is the same in both cases. All inputs to the load patch module look to be identical in both cases. Both do try to load the correct patch, but in the second case, it does not work right.
The two clues I have:
1. The patch being loaded contains a vst, REAKTOR, and in the case where it loads incorrectly, the name of the vst includes '(loop)':
Although when I use the same mechanism to load a similar patch containing Keyscape, I do not get the (loop) designation. The behaviour is otherwise identical in both cases, though.
2. The 'patch loaded' output seems to be stuck on. It sends out a 1, but no 0 afterwards. I can click the output in the inspector to turn it off manually, but it doesn't stop the re-loading behaviour. Nothing will, except cutting power to usine. And then when I look at the patch, there is nothing that looks out of order, except the loop designation, and that the Reaktor vst host module has the wrong background color. The keyscape version looks perfectly normal. And when I load via the mouse output, I get the expected 1 and 0 from the patch loaded output.
Any thoughts as to why this might happen? The actual patch is included, in case that's helpful. I'll try some substantially different approaches in the meantime to see if I can figure it out, but I thought there was a chance it might be something I just don't understand in the patching....
I have the mechanism figured out, but I hit a snag. For some reason, when the LOAD trigger is sent via a different routing in this patch, the patch does not load correctly. It seems to be trying to reload over and over again, and it keeps changing size and disapparing and reappearing in the control panel. Here's what the patch looks like:
The two clues I have:
1. The patch being loaded contains a vst, REAKTOR, and in the case where it loads incorrectly, the name of the vst includes '(loop)':
2. The 'patch loaded' output seems to be stuck on. It sends out a 1, but no 0 afterwards. I can click the output in the inspector to turn it off manually, but it doesn't stop the re-loading behaviour. Nothing will, except cutting power to usine. And then when I look at the patch, there is nothing that looks out of order, except the loop designation, and that the Reaktor vst host module has the wrong background color. The keyscape version looks perfectly normal. And when I load via the mouse output, I get the expected 1 and 0 from the patch loaded output.
Any thoughts as to why this might happen? The actual patch is included, in case that's helpful. I'll try some substantially different approaches in the meantime to see if I can figure it out, but I thought there was a chance it might be something I just don't understand in the patching....
