-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
[ossia-max] ossia.router bug with numbers as addresses #802
Comments
i have tested and confirmed this bug on the Ossia "2022-1-25-38" build. |
hm there's still something that I don't understand: surely in servos/y2/3, "3" is supposed to be a symbol and not converted to a number, right? (the only way tomake it show up without the quotes in max). (and I don't see any other way to do it sanely: for instance imagine that you have an OSC address such as: /audio/5.1/volume that you want to route: if we convert it from floating point to string (or conversely) for instance it could end up as "5.100000000000001" or something like this due to the way FP works, so we really have to stay with symbols all the time |
(and even if Max displays |
ossia-max-2023-01-10-15-55.zip here's a test version @navid @petervanhaaften |
@navid @petervanhaaften tell me when you have tested that I close the issue :) |
thinking about it still.
The issue arises out of the fact that ossia and jamoma routers have removed
the slash from the bending of the osc addresses, thus rendering and osc
outputs such as
/3 x
into instead
“3” x
within max when parsed as such. This behaviour is inconsistent with all the
other osc routers out there (cnmat, ircam, etc) yet i guess I see why ossia
and jamoma at some point decided to remove the leading slash from their
addresses. Let’s sleep on this for a another week: since an optimal
solution doesn’t seem to exist and any solution would be a compromise of
some sort
On Thu, Jan 12, 2023 at 3:10 PM Jean-Michaël Celerier < ***@***.***> wrote:
@navid <https://github.com/navid> @petervanhaaften
<https://github.com/petervanhaaften> tell me when you have tested that I
close the issue :)
—
Reply to this email directly, view it on GitHub
<#802 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDTZMWMCFDE4PNL3WO4GDWSBQL3ANCNFSM6AAAAAARQUKGYE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
…___________________________________________
Multidisciplinary Composer | Media Alchemist | Artist-Researcher
Associate Director, Topological Media Lab
Research Associate: Matralab, Milieux, HEXAGRAM, LASG
navidnavab.com <http:https://navidnavab.com> | 514.432.6633
----------------------------------------------------------------------------
|
what about ossia.router staying like this to not break compat with existing patch, and introducing an ossia.oscrouter which would add the / |
that is a good solution.
another alternative solution could be an attribute like @leading-slash 1
(default = 0)
On Thu, Jan 12, 2023 at 4:30 PM Jean-Michaël Celerier < ***@***.***> wrote:
what about ossia.router staying like this to not break compat with
existing patch, and introducing an ossia.oscrouter which would add the /
—
Reply to this email directly, view it on GitHub
<#802 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDTZNBFKDN2YZT4REOVIDWSBZYNANCNFSM6AAAAAARQUKGYE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
…___________________________________________
Multidisciplinary Composer | Media Alchemist | Artist-Researcher
Associate Director, Topological Media Lab
Research Associate: Matralab, Milieux, HEXAGRAM, LASG
navidnavab.com <http:https://navidnavab.com> | 514.432.6633
----------------------------------------------------------------------------
|
ossia-max-2023-01-20-17-39.zip latest version with the test patch:
|
ossia-max-24-04-2023-ossia-router-optim.zip with some optimizations |
Funny behaviour happens when trying to route the following message: servos/y2/3 11.5
If i route servo/y2
then ossia.router returns:
"3" 11.5
whereas it should return:
3 11.5
however I can still route servos/y2/3
in which case the router behaves correctly and returns:
11.5
The text was updated successfully, but these errors were encountered: