Skip to content
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

o.slip.decode / o.route couple triggers error messages #442

Open
nesdnuma opened this issue May 31, 2024 · 1 comment
Open

o.slip.decode / o.route couple triggers error messages #442

nesdnuma opened this issue May 31, 2024 · 1 comment

Comments

@nesdnuma
Copy link

nesdnuma commented May 31, 2024

Hello,

I have a o.route object connected to an o.slip.decode object in Max 8.6.2 / MacOS Sonoma/ ARM M2 processor.

The osc-route often sends messages "o.route: received something that is neither an OSC bundle nor a message". However if I print what the o.slip.decode objets outputs, I see only "Fullpacket" messages, nothing else.

Is it an issue with o.route, o.slip.decode or the stream the latter receives?

@nesdnuma nesdnuma changed the title o.slipo.decode / osc-route wrong couple triggers error messages o.slip.decode / o.route wrong couple triggers error messages May 31, 2024
@nesdnuma nesdnuma changed the title o.slip.decode / o.route wrong couple triggers error messages o.slip.decode / o.route couple triggers error messages May 31, 2024
@nesdnuma
Copy link
Author

In between I have noticed that regular Fullpacket messages have the number 24 or 28 as first argument whereas when the error message is send the first argument is different (480 for instance).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant