Max Scheduling irregular – What could be the problem?
I am having this unexplainable problem, that my Max scheduler is not being very regular.
I can test it using a metro, sending a bang to a click~ at very high speeds. Clearly there are disruptions audible, telling me the metro is not firing at a steady pace.
Does anyone have a clue where I can look to fix the problem? All suggestions welcome, thanks!
Make sure that ‘Overdrive’ is enabled in the DSP status window.
if I were you, I’d read this article: http://cycling74.com/2004/09/09/event-priority-in-max-scheduler-vs-queue/ by Joshua Kit Clayton, specially the section ‘Event Backlog and Data Rate Reduction’ and the ones that come after that.
The point is: if you generate too many events, you might flood the event processing queue in which case the timing of the events will become irregular.
If you can’t reduce data at the source, you can filter it the moment after.
"Change" and "Zl.Change" objects are great for reducing data.
I also have this, i think as an abstraction too:
It’s a 1ms gate, that closes when you change presets and you don’t want some events doubled.
Also, set-up a counter for debugging to see where message-count is high and could be reduced.
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 757.3ocyWsrbaBCEcM9qPCqc8fDuLcWWzs8GnSlNxvMXkAj7fjcRZl7uWjDD rqgD.am1M.RHt5bN2yUR7xBG2Mhm.oK5qnehbbdYgiioKcGNMscbKoOkVPkl g4lJJKAtxco8cJ3Iko+bpBPpsTEJsPHAI5dQEBWJQaf5m.TAnTLdNhxeVsU+ .TH0ePkXe911nUv3PpXO2DR+lN46KY75O2L+3lN2QUo5v7qJHUYweDdU3RDN 1akW8MBQeKHXkG5tt.I1qZijWSurLC9Ead3KXuVfbufq3zRv7puUwnEnePqp DOd7.jreaF.FupMX6p.Ys5PULA+Hn4GFpQiumATdMWP2o+nWWrPeY4Ep+ZoN CJnOaDdc1vch5WnuQ+7hzvKw2nhISQ9RtUpGIVCFhevMS899g5dkV+KGfLjR TabQ2yJTPEj0q+jLQ8kfMl.RRm95Slh9t9FouAqMobbD41puHUEKOGplrwLp S2Vud59x3YqayPALLpWF5MLCwIdcTjD1dc.JhOmhgsyncXpm2A1H659VPFJ6 akWbXxoY+lupMipmI2YnGV.M0TNNNRuXDAGMJEomjdf6Uh.yKgFDbYIT7HRn WJy3vi0S0Y0p1cQv8RYxGR4l8O7MbFudJblfGcg5YpxFJOuSYNoN1aV0wkfT RygyTGuIqKVqL12dtDawV7j7BwyWWFPSl2ZaCXXR2VK9S93FM9E6w0Bh9fk0 86QVBt.YYotvV0d6ZJRCYblQAU7kZbH+eabF7Tpinbx5apO.U365a5auxfar pXFi4rh+0eVYnit+SkJoXeUZ6LzraNpiPYfr9OmLaae7XpYAB+1f1xxx.9w6 JkwjzMEfg28myFMbBFAdNcL2R3fGAZvehvgL1r06gmRV1NQ8RQMNFbXb6Qx0 96tCnG1MQWOFLl7qdSnow.yuSljXI.osw+J7SvedNh3qgi35gGxnpXHyDO1U 6n61c.pjMwz.k5s.dPToaFszzjwsMMQzsBNvZGe3Bczdcwe.wBgSzA -----------end_max5_patcher-----------
You could also use the
[qlim] objects for data reduction, which are more lightweight both.
Forums > MaxMSP