<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1421883052675_5565">Hi list,</div><div id="yui_3_16_0_1_1421883052675_5566" dir="ltr">Any idea why clock_delay would create a delay that is rougly 2.5 times longer than what it is supposed to be?</div><div id="yui_3_16_0_1_1421883052675_5567" dir="ltr"><br></div><div id="yui_3_16_0_1_1421883052675_5568" dir="ltr">It's weird because I can send a long stream of mouse motion messages from node-webkit to Pd, and receive the response fast enough that I can't detect the latency when I move objects around on the screen. When I click a [bng], the message to change the button black is received immediately, but the message to "un-flash" the button is sent way too late. I don't think it's a problem with socket latency, but on the other hand I can't think of what I've changed on the Pd side that would mess with the clock.</div><div id="yui_3_16_0_1_1421883052675_5570" dir="ltr"><br></div><div id="yui_3_16_0_1_1421883052675_5571" dir="ltr">This is on a virtual machine running Debian testing (Jessie) 32-bit. Pd Vanilla's bng time looks fine on the same machine.</div><div id="yui_3_16_0_1_1421883052675_5583" dir="ltr"><br></div><div id="yui_3_16_0_1_1421883052675_5584" dir="ltr">-Jonathan<br></div><div id="yui_3_16_0_1_1421883052675_5411"><br></div></div></body></html>