Linking Faders: OSCalculator

i can't specifically say how you would do it in that application, but those are the osc commands to send to eos:

• create faderbank: /eos/fader/<index>/config/<amount>, "/eos/fader/1/config/10"
  this is needed so you can afterwards page through the fader pages. eos needs to know how many faders make up a fader page. unless you have sent this commd at the very beginning of each OSC session with eos, you will not be able to access faders
• fader: /eos/fader/<index>/<number>, "/eos/fader/1/5"
  this is the definition of each of your 10(?) fader positions. this isn't yet about fader pages, it just say if it's the first or third or tenth fader you physically have available
• fader name: /eos/fader/<index>/<number>/name, "/eos/fader/1/5/name"
  if there is a space to display fader labels, this will insert the label for the record target that i currently mapped to the fader in this position
  
  
• fader navigation: /eos/fader/<index>/page/<delta>, "/eos/fader/1/page/-2"
• fader page direct access: /eos/fader/<index>/page/<faderpage>, "/eos/fader/1/page/2"

Okay so I was heading down the right path but i had the wrong string for the individual fader. 

So corrected here is what i have. 

cc1 is the button the creates the fader page

cc3 is the fader.

When I hit cc1 I get this in eos:

Then when I move the fader up the 75% I get this:

It knows I'm telling it to do something but no fader movement in Eos. 

Thanks

Maybe the problem is that you send an argument with config.

Have you tried this with the faders mapped to a target? If you send a fader command to an unmapped fader, it won't move.

not sure exactly what that means. 

It's mapped to a sub that's mapped to CH01 at full. Fader works in nomad but i have no control with midi fader even though I'm getting feed back in the diagnostics. 

Your incoming OSC looks good. However you are sending a level to fader 1/10, and according to your screenshot, fader 1/10 is not mapped to a target. If you are trying to get Fader 1 (mapped to Sub 1 in your photo) to move, you need to use /eos/fader/1/1 as your address.

wow alright I'll give that a shot. I assumed 1/10 means 1 of 10. 

That worked. Thanks!

Nope. 1/10 means you've constructed a fader bank numbered 1 that has 10 faders. You can then page through them, and they will be eos's faders 1/1-10, 2/1-10, 3/1-10, but you will always call them 1/1-10. This allows you to create fader banks on multiple devices that then page separately.

Nope. 1/10 means you've constructed a fader bank numbered 1 that has 10 faders. You can then page through them, and they will be eos's faders 1/1-10, 2/1-10, 3/1-10, but you will always call them 1/1-10. This allows you to create fader banks on multiple devices that then page separately.

hello, long time after you, starting dealing with osc to eos. I followed steps to get faders active (trying with my old nanokontrol 2).

fader seems to graduate in diagnosis tab, but acts weird: i can only graduate from full to 78. do i have to give an argument, or upper and lower values?

to be precise: bringing osc fader to 1% gets eos fader full straight

bringing it back to 0 gets eos fader to 78 straight

What am i missing?

I am fairly sure fader values need to be supplied as 0.0 > 1.0, not 100%. This is fairly common for representing percentages. 0.5 = 50%.

do you mean i should enter 0.0 as lowest  and 1.0 higher? Do i need to increment arguments too?

succeded, thanks!

not fully succeded, actually when i turn fader to 0, sub remains at 1%