On Thu, 2011-11-17 at 10:58 -0500, Mathieu Bouchard wrote: > Le 2011-11-17 à 15:18:00, Roman Haefeli a écrit : > > > Matju directed me to the respective parts in the source code, but I was > > not able to make any sense out of it. > > I said something wrong near the end because I spoke too quick. sched_tick > is not a main loop, it's the common part between the big mainloop > (ordinary mode), the short mainloop (-batch) and the big callback > (-schedlib). > > The top of that file defines : > > #define TIMEUNITPERSEC (32.*441000.) > > which is used by users of sched_tick. > > That's 14112000 or pow(2,8)*pow(3,2)*pow(5,3)*pow(7,2). > > 44100 is pow(2,2)*pow(3,2)*pow(5,2)*pow(7,2). > > 48000 is pow(2,7)*pow(3,1)*pow(5,0)*pow(7,0).
Ah.. I was actually looking for the number 14112000, but of course I didn't look for 32. * 441000. But then, 14112000 / 5000 gives 2822.4 Hz, which would be a too high rate for GUI refresh. So, what is relation between the tick and 5000 that leads to a sane GUI refresh rate (and finally, what _is_ the GUI refresh rate)? Roman _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
