right after receiving help as for the 1.4 serialosc download, i’m back with trouble about it (:
i’ve been working on a patch on my very decent iMac (yosemite & el capitan both went well) for the better part of the past month and everything had been good. now i’ve ported the patch to my macbook pro (running 10.8.5) and i get massive lagging in OSC communication. i can verify that my patch-performance doesn’t seem to be the bottleneck: did an [uzi] test, setting all 256 pads of my monome in an isolated patch and while the max-internal execution takes roughly 2ms, the pads only slowly and sequentially light up within no less than ~1 seconds.
thanks as always for helping out! – the problem persists under serialosc 1.2
…just to check that i did everything right:
uninstalled serialosc 1.4 by deleting library/application support/monome & library/launchagents/org.monome.serialosc.plist
because i found no uninstaller and neither did “rm
/usr/local/bin/serialosc” nor “rm /usr/local/bin/serialoscd” find
just to point this out (though obviously the bottleneck is still a problem)
it’s incredibly inefficient to update a full display of LEDs with 256 OSC messages. it’s much better to use a /map message, which reduces the total payload substantially, plus reduces the negotiation of the system with individual packets vs. a couple large packets.
i’ll try to dig up some old optimization tutorials, but let me know if this makes sense at first glance. do your patches use any optimization? also, the /all OSC commands are also helpful.
but clearly we need to figure out what’s changed in the OS to create this lag.
thanks for the reminder – i am getting behind optimization step by step (being a relatively new user). i’ve read up on it and i’m aware, at least (…and the patch above was solely for testing purpose, not the way i’d figure to do it elegantly :)).
how ever, yes, just as you’re pointing out – it does appear to be some OS issue as everything is working flawless on my other mac. hope we can pin it down.