Last week, while working on a project for custom logo design services, I faced a challenge with the plugin's UI interface. It was crucial to detect whether it was open or closed. I implemented a solution using broadcasters and listeners to bypass certain code when the UI was closed. This not only streamlined the process but also indirectly optimized my workflow, allowing me to focus more on delivering creative designs to my clients.
@Lindon Thank you for your reply. I can go back and forth between them, or repeat the same — the results are identical — if I add the text, I get one result; if I remove it, I get a different. Weird, huh?
@CyberGen fortuitously discovered that setting the ignoreNoteOn to 1 acts as a reset signal. Whenever triggered, the LFO goes back to the start of it's cycle without having to play a note. You might sometimes need to set it back to 0 immediately (depending on what's required of the LFO) but it's a good workaround. :clinking_beer_mugs:
@Christoph-Hart Thank you for your reply. I actually like that the plugin doesn't teleport somewhere…I've just seen that message 120x already. 🤪 @d-healey 🤣