From the original SynthMaker forum (2004–2014), with its members’ names and dates.
NothanUmber ·
Are you sure that tick 25 creates a new trigger signal 25 times per second and not per hour? Although it does what it should the update in this quantization code is way too slow...
http://home.in.tum.de/~strixner/Tick25_bug.osm
Greetings, NothanUmber
P.S.: the bug could also be in the BSwitchTrig component...
infuzion ·
Timer35 still seems to work; try the animated boucing balls: timers / animation
NothanUmber ·
Well it's working, but the response time is more in the range of several seconds than 25 times per second (Hm, can't find a Timer35 in 0.9.3w...)
Greetings, NothanUmber
malc ·
Hi NothanUmber,
I think I know what the problem is. The Ticker 25 is a Windows timer. As such it sends timing messages using the standard windows message loop. Redraw messages also use the message loop and in this case I think the redraw messages are processed first. Because there are alot of redraws the timer messages are being held up.
Try deleting all the data components that you're using to debug and see if that makes a difference - I found that it did.
There may be something we can do about the Tick25 so I'm going to try it out. I'll let you know if it works.
Incidentally, if you're just trying to quantize the pitch bend, do you really need the timer? Could you not just use integer arithmetic, divide by the quantize level, round and re-multiply say? Just a thought.
Regarding the Timer35, the Ticker 25 is the old WTimer component that was in the bouncing balls example. It was renamed and changed from a 30 triggers/sec to 25 in a later release. If you want a faster rate there is the Timer component.
Thanks for highlighting this.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker