Jan M

using [rnbo.remote] to set enum params on the remote target, seemingly only works using the normalised value.

textbutton

comment

umenu

prepend

routepass

live.text

route

outlet

print

gate

deferlow

message

zl.iter

inlet

rnbo.remote

attrui

rnbo~

param

outport

Is that a bug, or am I missing something?

Here's a patch to demonstrate my issue:




Is that a bug, or am I missing something?

using [rnbo.remote] to set enum params on the remote target, seemingly only works using the normalised value.
Here's a patch to demonstrate ... 

setting-enum-params-with-rnbo-remote-bug-or-am-i-missing-something

If you attach a print after your [prepend input] objects you'll notice the one the works is using symbols. It looks like rnbo.remote only accepts symbols for enum parameters. I'll add a feature request to allow numeric indexing as well.

The reason "normalized" works in this case is because normalized parameters are numeric by design.

Actually neither of the two versions (sending numeric value or a symbol) do work on the remote target (aka RasPi)

Only the normalised value changes the parameter on the Pi. If you open up the browser interface and observe the value changes there is't probably clearer.

maybe my example wasn't clear:
Actually neither of the two versions (sending numeric value or a symbol) do work on the remote target (aka RasPi)
Only the normalised value changes the parameter on the Pi. If you open up the browser interface and observe the value changes there is't probably clearer.



I swear that the symbol version was working for me but I'll double check that.

I wonder, do the parameters change for you correctly when you use an attrui attached to rnbo.remote directly?

Hey JAN,
I swear that the symbol version was working for me but I'll double check that.
I wonder, do the parameters change for you correctly when you use an attrui attached to rnbo.remote directly?


Thanks for double checking. I tried. various times with varios patches and the behavior was consistent.

for me it started to break with RNBO 1.0.2. Before it was working as expected.

for changing with attrui: I will have to test that later tonight and let you know.

Thanks for double checking. I tried. various times with varios patches and the behavior was consistent.
for me it started to break with RNBO 1.0.2. Before it was working as expected.

 for changing with attrui: I will have to test that later tonight and let you know.

Sorry for the delay, this is indeed a bug, enum parameters aren't being updated with the correct osc types. I'll be submitting a fix and it'll go into the next release.

Hey Jan,
Sorry for the delay, this is indeed a bug, enum parameters aren't being updated with the correct osc types. I'll be submitting a fix and it'll go into the next release.


do the parameters change for you correctly when you use an attrui attached to rnbo.remote directly?

I swear that the symbol version was working for me but I'll double check that.
 I wonderhttps://essentialshoodie.co/ do the parameters change for you correctly when you use an attrui attached to rnbo.remote directly?

Setting enum params with rnbo.remote - bug or am I missing something?