x-fader 16bit resolution in OSC

Hi Nicolas,
since your software allows controlling 16bit LED's and I almost exclusively use the OSC x-faders to move from one cue to another, it would be useful to have the same resolution here. Do you see a way in implementing that?

Hi Stebian,
it could be possible but not in a near future...

another thing, as you use OSC to control stuff, are you aware of the two first commands listed here:
getdlight.com/wiki/index.php/OSC#Syntaxe...n_4_.5B2018-02-01.5D

did you tried them?

another OSC command that I've forget to document anywhere is :
/deviceParameter/COLOUR/RED [0.0...1.0]

it works for selected devices.
in the setupI/O you can choose if /deviceParameter act as relative or absolute mode.
absolute == [0.0...1.0]
relative == -1/+1

as for 4.1.04_b10 absolute works fine, relative never do the -1... I'll fix that

and for the next beta/release, I've reworked /pad/freescale to accept float or int arguments. This message is designed to increment or decrement levels of selected channels (and so INTENSITY/DIMMER for devices)

++

That's fine. I'll go with fade times in cases of annoying visible blinking for now.

And yes, I know these commands. I still need to integrate them in the device wheels on the controller…
I use another wheel which makes use of /pad/freescale, so I will be happy about float arguments on that one.

Thank you, Nicolas!

Hi Nicolas,
did you change /pad/freescale in 4.1.04_rc1?
I doesn't work here. I was curious to check on sending floats but that did't do either. I tried /pad/freescale +0,1/-0.1

HI,
yep I did change it but apparently not in a good way...
range for float is 0.0....1.0

next week I'm on tour, I'll be able to double check on Friday...

++

Oh, I see…
When you say range for float is 0.0....1.0, do you mean absolute or relative? Can I even send /pad/freescale 0.01/-0.01 as it works for devices?

Have a good tour!

Hi,
the proposal for /pad/freescale is :
whatever value you receive you store it
-if next value is >, increment selected channels
-if next value is <, decrement selected channels

so there's no range...
tell me if it's acceptable for you?

++

Oh, it totally is!

Hi Nico,
thanks for the release.
pad/freescale works neither for ints nor floats. It did for a moment on absolute floats only and then it stopped.

Hi Stebian,
testing the /pad/freescale here with pureData and it's fine.... so there's must be something somewhere...

pureData is sending message like that:
/pad/freescale f 100 (100 is for example)
on the first time DL is receiving freescale it visually does nothing as the first value is used to set the zeroPoint.
next call by pureData is :
/pad/freescale f 101
DL now knows it should increment so selected channels are processed +1 (not +1%, but +1 in realValue).

where does it fails for you?

++

Hi Nico, I try with English...

My setup on Touch osc is an Encoder with message /pad/freescale and value range from -1 to 1

All works fine with previous version.

Maybe on the new version i need to update the value range.

and I have the same setup on Isadora.

Isadora receive midi from controlleur and send to dlight : /pad/freescale with range from -1 to 1

Can you try with a range from -32768 to 32767

For several reasons I would like to avoid the former-1/+1 range
++

Ah, I didn't know I was supposed to send an f for floats... Do i need a preceding i for integers as well? Will try again. Thanks Nico!

@celio
You probably have the same issue as me then...

@Stebian,
Are you using pureData?
The f or i is needed when using the sendtyped message to packOSC