These are chat archives for brunchboy/afterglow

16th
Feb 2018
Joen Tolgraven
@tolgraven
Feb 16 2018 13:19
So looking a bit closer at the stacktrace I think what’s happening is that type of bang actually results in the max Atom being passed to afterglow.controllers, which obviously can't resolve it
Joen Tolgraven
@tolgraven
Feb 16 2018 13:48
And the push2 error isn't actually the midi port (which makes sense) but from libusb in .openPushDisplay, "USB error 3: Unable to claim interface 0 of Push 2 device: Access denied (insufficient permissions)". Max console errors are a bit scrambled so didn't see the full exception until I ran my regular lein setup, sorry. Any hunch? Might get in touch with ableton whether they've made any breaking changes, because I never tested running ableton+afterglow before updating I can't say whether it was actually working earlier. Happens even in live9 and with a clean set/no M4L loaded so it's definitely either something in the new firmware, or somehow related to my setup...
Actually I should get in touch with them either way since the failing to claim goes both ways and unlike Afterglow the Live log doesn't show any errors when it happens, which definitely ain't right no matter what the root cause
Joen Tolgraven
@tolgraven
Feb 16 2018 13:59
On a less aargh note, I'm looking at using libmapper for signal passing on multiple fronts in my larger project, but seems to me it'd be just as spot on for more robust OSC support in core afterglow. Has Java and max bindings and everything, looks like it's been pretty dead for a long time but just started seeing active development again in the past few months. What do you reckon?