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.

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.

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.