aliasant ·
Trigger Limit primitive is giving x2 triggers.
Not sure if its really a bug but Trogluddite got the same results as me so here's the .osm.
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
aliasant ·
Trigger Limit primitive is giving x2 triggers.
Not sure if its really a bug but Trogluddite got the same results as me so here's the .osm.
trogluddite ·
Did some testing using this little setup...
Most primitives will ignore multiple triggers if they originate from the same source - to avoid feedback etc. But it seems that either the trigger limiter or the counter will count the duplicates as seperate triggers.
aliasant ·
trogluddite wrote: Did some testing using this little setup...
Most primitives will ignore multiple triggers if they originate from the same source - to avoid feedback etc. But it seems that either the trigger limiter or the counter will count the duplicates as seperate triggers.
hehehe. That simplified it a bit. 🙂
Its odd though. I think I will have to start hunting down a gazillion of those bugged limiters in my active projects now 😠 I will simply replace them with a VST Editor primitive and a Triggerswitch Primitive.
MichaelBenjamin ·
hm, the double connected counter ran ~1.5 times faster after load, after a disconnect/reconnect they both run the same speed now and i cant get it back as it was without reloading. the trigger limiter also seemed a bit useless besides "maybe this helps getting gfx down another %", but seemingly it didnt change much and i dont know what its really good for now.
aliasant ·
MichaelBenjamin wrote: hm, the double connected counter ran ~1.5 times faster after load, after a disconnect/reconnect they both run the same speed now and i cant get it back as it was without reloading. the trigger limiter also seemed a bit useless besides "maybe this helps getting gfx down another %", but seemingly it didnt change much and i dont know what its really good for now.
It is used to stop triggers when your not watching the gui. Example when the plugin is NOT visible/Open in yor host the triggers wont go thru but when you open the gui i starts leting them thru.
mwvdlee ·
Looks like the limitter is doing absolutely nothing. It just passes on the triggers without any sign of internal logic.
aliasant ·
mwvdlee wrote: Looks like the limitter is doing absolutely nothing. It just passes on the triggers without any sign of internal logic.
Have yo tried it in a VST plug? It wont do anything in SM since anything in SM is considered "VST Editor OPEN"
I did have a discussion with Malc last year about this and I, as you, thought it should only let thru Screen refresh triggers. In my case 60 but that is not at all how it works 🙁
mwvdlee ·
aliasant wrote: mwvdlee wrote: Looks like the limitter is doing absolutely nothing. It just passes on the triggers without any sign of internal logic.
Have yo tried it in a VST plug? It wont do anything in SM since anything in SM is considered "VST Editor OPEN"
I did have a discussion with Malc last year about this and I, as you, thought it should only let thru Screen refresh triggers. In my case 60 but that is not at all how it works 🙁
Redraw Limiter Limits triggers to the same as the redraw rate. Note that this also means that triggers will not be sent when redraws are disabled due to the window being hidden in an exported plugin or during preset changes.
Seems pretty clear what it should be doing.
aliasant ·
mwvdlee wrote: aliasant wrote: mwvdlee wrote: Looks like the limitter is doing absolutely nothing. It just passes on the triggers without any sign of internal logic.
Have yo tried it in a VST plug? It wont do anything in SM since anything in SM is considered "VST Editor OPEN"
I did have a discussion with Malc last year about this and I, as you, thought it should only let thru Screen refresh triggers. In my case 60 but that is not at all how it works 🙁
Redraw Limiter Limits triggers to the same as the redraw rate. Note that this also means that triggers will not be sent when redraws are disabled due to the window being hidden in an exported plugin or during preset changes.
Seems pretty clear what it should be doing.
Exactly what I said to Malc but ......... I suggested he might want to refrase the description but I think he had his hands full at the time.
Wrote something here? To have a post removed or your name hidden, write to [email protected].