From the original SynthMaker forum (2004–2014), with its members’ names and dates.
theod ·
Ok I spent like 4 hours today trying to figure this out and still I cant. In the following schematic the input is connected to a "switch". In the exported VST, when using the switch everything works as expected, but when the switch is automated, the "false to trigger" chain of events does not work. Am I missing something important? I really cant figure this out.
In case you need the schematic to check it out...here it is: De-glitched Selector for mono streams...
trogluddite ·
Weird one that - if your front GUI is working, then I would expect automatiion to as well.
The only thing that comes to mind is that timers are a bit funny about signals that originate from different threads - there is a well known problem where timers don't work properly if they are started by a MIDI derived trigger. Maybe something similar is happening here when it is the VST host making the change?
There is a module in the toolbox called 'De-threader' that is used to work around the MIDI & Timers problem, maybe inserting those on the start lines of the Timers will work here too?
theod ·
Yes, the front GUI is indeed working as expected - in other words, the recorded automation changes the state of the switch in the GUI. I used read out labels and saw that indeed the automated switch state IS received by the input of the schematic, but somewhere along the way it is lost. Now that you mention it, I suspect the timers are going berzeck. i will try the "de-threader" to see if that changes anything, even though I dont fully comprehend how that works.
Also, I 've been meaning to ask, what exactly is the purpose of the primitives with the symbols >>> . Reading their info, it mentions they are used to stop a change from propagating in the schematic but I cant think of a usage for them (even though I saw them used in a couple of factory modules). As I read somewhere, they let a change of a parameter through only when "requested" but this creates the question: when is a parameter requested?
Thank you very much, again, Trogluddite!
trogluddite ·
See my triggers tutorial - 'requests' are the red 'backwards' triggers in the example there. Hint - stick a trigger blocker between the top float box and the adder, then mess around entering numbers into the two float boxes! Blockers will be getting more of a mention in the next update to the tutorial!
theod ·
I am at work and already downloading it with poor internet speed, lol! I saw it last night, and it was in my plans to study it. Im sure I'll gain a lot of knowledge out of it. Will try your 'de-threader' suggestion when I get back at home and report back.
theod ·
Yup! You were spot on. Two "de-threaders" before the trigger delays, did the trick.
trogluddite ·
Ah, that's great. I wonder if this is a new problem - the MIDI one is well known, but I don't recall there being any mention of automation doing the same thing.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker