`monome_event_next` sometimes produces odd results about libmonome

[tehn]

oh i'm surprised that you got any data at all--- i thought if serialosc was running that libmonome wouldn't be able to claim the serial port again and fail. glad you spotted the issue. isms also started out with just libmonome, but moving over to using serialosc proved very nice

…

On Sun, Jun 18, 2023 at 2:18 PM Rylee Alanza Lyman ***@***.***> wrote: Ahhh, I think what is happening is that serialosc and this program are fighting, and this program is losing. If I disable serialosc, I'm no longer able to reproduce the issue. but! this is with my 2022 grid on an M1 MBP running MacOS 13.3.1. anyway, this suggests I should refactor my program to go through serialosc. — Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB4I4A3GL5YPOQNX2AZBULXL5A7JANCNFSM6AAAAAAZLAHZBA> . You are receiving this because you commented.Message ID: ***@***.***>

[tehn]

could you tell me the edition of your grid? and also the OS version and machine you're using?

have you tried a version of the above example with registered callbacks instead? this would perhaps rule out a bunch of possible culprits, narrowing it down to just the next_event implementation.

[ryleelyman]

Ahhh, I think what is happening is that serialosc and this program are fighting, and this program is losing. If I disable serialosc, I'm no longer able to reproduce the issue.

but! this is with my 2022 grid on an M1 MBP running MacOS 13.3.1.

anyway, this suggests I should refactor my program to go through serialosc.