-
Hi!
Just got a brand new Arc and noticed something that bothers me: using the apps that support arc, the encoder leave trails of illuminated leds that get "wiped" out on the next sweep. Don't know if you can visualise that so I'll make a video of the issue and post it on youtube. Anyway for watching many videos of the arc without noticing this phenomenon I think this may be an issue with the unit.
Any experienced this ?
Thanks! -
yeah it happens a lot on EDW but also on tml.
-
That usually represents a logic / timing issue in the code somewhere for a specific app. (it might be more obvious when using the new units, as the added resolution means you're sending up to 4x as many messages to communicate the same gesture)
This is one of the reasons I always use /ring/map instead of /ring/set -- it's less efficient, but by overwriting all 64 LEDs in one command, we eliminate the danger of leaving "stuck" LEDs behind.
If you're feeling brave and want to troubleshoot it on your own, I'm 99% sure this video will give you all the tools you need.
http://youtu.be/S92ljjQtsfo
(it's not a monome video, but it does show you how to address the kind of timing issue that usually comes up around here) -
gtz is correct. with the incredibly high resolution of the arc sometimes the OSC tubes get clogged and packets dropped.
many of the apps are patched in the most simple way to understand, but they're by no means the most efficient. /map is by far the best. check out the app "returns" for example.
we'll be working on more patching examples so that "pretty" arc apps will be more prevalent. -
I see this a lot in Grainstorm -- perhaps I'll poke around in the patch and see if I can make some more efficient messaging to accommodate the new arcs.
-
Happy to know it's just a software issue!
