-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new monome Max package break most of the serialosc BEAP devices #120
Comments
Prefix has been part of the monome protocol forever. You can change the argument to set the prefix to whatever you want. My implementation of it is the issue here. Anyway, I'll look into it. I think what needs to happen is the beap serialosc devices need a way of setting the prefix. This could be done without disturbing the the existing UI by making the prefix an argument? |
going to hit up Dan, perhaps we can leave BEAP alone and have the default argument of monome-device.maxpat change |
yeah |
patch cables perform the role of prefix between beap modules. Maybe the silly thing is the /monome is there at all. |
I talked to Ben more about this, and I'm not sure exactly what the best move here is, but the best move is probably the simplest. I emailed Dan/Monome; let's see what Dan thinks. |
hi @sonoptik + @stretta -- hope the end of the year is treating you both well :) @sonoptik , i'm not sure why you're seeing that unexpected prefix for a fresh-instantiation of silly, but here's a compressed patch which sends the expected prefix
just to confirm, you aren't adding any extra arguments to the invocation, right? that would also set the prefix away from its default (which is set here in the JS to lmk if i'm missing anything!! |
The new Monome Max Package breaks most of the
serialosc
BEAP devicesThe old interface device was called serialosc.maxpat and the new one is called
monome-device.maxpat
- https://llllllll.co/t/monome-max-package-2023-update/62725Looks like the problem is that the new monome-device puts out a string
/monome-device/grid/key 0 0 0
where the old serialosc patch would put out/monome/grid/key 0 0 0
Some of the BEAP devices are expecting the old string and also output serialosc in the old format
I can imagine that this new string potentially breaks 1000s of Max patches out there in the wild
The text was updated successfully, but these errors were encountered: