From the original SynthMaker forum (2004–2014), with its members’ names and dates.
matti ·
Now that i finally updated to the latest version of SM i noticed that the "redraw limiter" has been fixed. It no longer outputs extra triggers like it used to do, which is nice when you don't wan't your schematic to do unnecessary work.. But here's the problem: I can't use the "trigger div" anymore! Because when i divide for example 2, i loose the option of one lonely trigger from passing thru. It used to go thru before because the redraw limiter was generating extra triggers. I didn't think of this earlier but this "fix" has really crippled some of my clever cpu-usage lowering tricks for the graphics... I can't have a 25 or 50 fps limiter for my graphics anymore 🙁
Any ideas on this? Maybe the trigger divider could be made to let "lonely triggers" thru?
Loonie ·
It's always risky to actually take advantage of a bug. After all, how would the divider know what constitutes a 'lonely trigger'? Its job is just to divide triggers.
I think if something like this were to be implemented, it would need a parameter in which you specified a reset time, ie- after 1000 milliseconds, the trigger divide module will reset to zero and allow the next trigger through. Set that parameter to zero and it never resets. Of course, you'd then need to go through your entire schematic, setting the property of each trigger divider.
Personally, I think you might be better off just creating your own trigger divide module that can do that job, and swap out the existing trigger dividers.
Edit: Or create your own limiter that generates an extra trigger.
matti ·
Loonie wrote: It's always risky to actually take advantage of a bug. After all, how would the divider know what constitutes a 'lonely trigger'? Its job is just to divide triggers.
I think if something like this were to be implemented, it would need a parameter in which you specified a reset time, ie- after 1000 milliseconds, the trigger divide module will reset to zero and allow the next trigger through. Set that parameter to zero and it never resets. Of course, you'd then need to go through your entire schematic, setting the property of each trigger divider.
Personally, I think you might be better off just creating your own trigger divide module that can do that job, and swap out the existing trigger dividers.
Edit: Or create your own limiter that generates an extra trigger.
Yep i know what you mean. I actually did solve my problem temporarily with a timer and an extra trigger. I've solved few other problems that way too. But whatever you do by means of "hacking" something to work like it's not supposed to, it usually is much slower and buggy than what the primitives are. This is not in the Bug section because i can live with it, i just wanted to let the developers know there's some area of confusion here with the triggers. Cos the funny thing is that when there actually was a bug in the redraw limiter my graphics used to work much smoother 😀
oddson ·
It should be possible to make a module around the trigger divide that passes the first trigger and divides any others...
I'm not at my SM machine right now but I'm sure it can be done.
Maybe a mulitplexer that shifs to a trigger divide stream after a a first trigger is recieved. Then switches back bases on a timer event if the line stays quite for a certain number of MS.
oddson ·
This is what I had in mind:
trigDivPass1.osm
The multiplexer can be left out altogether if you don't mind that the trigger division will fire 1 trigger too soon (second trigger will be at n instead of n+1).
matti ·
oddson wrote: This is what I had in mind:
trigDivPass1.osm
The multiplexer can be left out altogether if you don't mind that the trigger division will fire 1 trigger too soon (second trigger will be at n instead of n+1).
Thats about the same way i fixed my problem temporarily(i only had one timer connected to the redraw limiter and so forth..). It seems to work alright. If this really is a working solution, then no problems 🙂 I'm just always a bit sceptical when doing stuff with timers..
Neat example there oddson 🙂
oddson ·
Your right to be skeptical about timers... but here the function is just to say when to stop waiting for the next trigger to divide. If the timing is out a few milliseconds it won't cause any great problem.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker