Closed dndrks closed 1 year ago
Hmm, the only arc message being used is /ring/map
. I know the latest grids drop support for some of the older grid messages, but map
should be the favored update method on both devices, right? The only other piece of logic there is the prefix code, and the prefix handling isn't very sophisticated. Perhaps the 2016 arc firmware is a little bit more strict on prefix control; I have a couple ideas to try and will have some test builds shortly!
I may have spoken too soon, I don't think any of the things I thought to try are related to this issue at all.
Just to confirm, you get no LED feedback in either the levels or cycles app, but ansible does correctly ID the arc and enter the arc modes?
@dndrks it took some time, but I have a potential fix for this; can you try this build? https://github.com/Dewb/monome-rack/actions/runs/4842109983
oh dang! i'll give it a spin tomorrow in the workshop, but this seems like the fix -- wild re: the enumeration pattern break :/ thank you so much for your continued excellent work on this!!
SUPER! all working great using the ARM build with macOS 13.3.1! <3333
Platform/Version
Describe the bug 2016 arc (aluminum) is not redrawing with the virtual Ansible module, though it populates in the module's device selector. the unit works with other environments on the same devices, as well as a hardware Ansible.
VCV Rack logfile from macOS: log.txt from Windows: log.txt
How to Reproduce Steps to reproduce the behavior:
monome arc
in Ansible's Device Connection menuAdditional context I'll ask @tehn to bring in a 2012 walnut as well! please lmk if there's anything else i can test on this side and thank you so much for all of your incredible work bringing this to life <3