I've created a fader and assigned it to a control that has 4 positions. The problem is as soon as I touch the fader the control jumps from position 1 to position 4. When assigning a rotary knob on my MIDI controller I have to limit the MIDI range to 0-3 (as opposed to the default 0-127). How can I do this in Lemur?
BTW, at the moment I'm doing everything in App. I thought the 'range' value would be what I neede. But when I try to enter this as a script (range(fadername.x,0,3) I get a syntax error (texts turns red) as soon as I type 'range('. I think I'm on the right track ..... Ish! Need a bit of direction! Cheers
..... Still no joy with this in the Lemur App. Very frustrating since its staring me in the face from the Lemur Editor on the computer Where is it hiding? Is it there all?
...... Been trying this again. There doesn't seem to be a way to do this in the App, unless it's a via a script maybe. But until I find out I'm thinking the only way is via the Lemur Editor.
I am no expert, just learning too. Try putting this into Fader "value" which you get to by clicking "More..." on the first page you see when you click on the Fader in Lemur app on your iPad.
range(FaderName.x, 0, 3)
This should give a range of 0 to 3.
Also make sure you set the Precision to 0 on the same page in the Fader.
If you want to see the values in a Monitor, create a Monitor and add the same thing to "value" in the Monitor.
range(FaderName.x, 0, 3)
And again, set the Precision to 0 in the Monitor. The Monitor should move from 0 to 3 when you move the Fader.
Hope that works for you. I tested it on my iPad and it seemed to work fine.
Hey, that worked! Thanks for that. Brilliant I had tried that script before but I'd try to add it to the script area. If I show the value I can see that the full range of the fader now only goes from 0-3.
However, when mapped to the assigned parameter on the synth I can see that all 4 positions on the parameter (in this case an LFO SYNC control with 4 options/positions) are reached within the very first part of the fader movement. It's like it's showing the correct range on the fader, since adding the script, but is still transmitting 0-127! Erm. Should there be something in the 'Unit' box (directly under 'value' in Lemur). I'm so close now I can smell it
EDIT: actually the 'unit' simply displays whatever you type in there as the object value unit .... Hence the name 'Unit' I guess
..... Just tested this in the Lemur Editor. You still need to add the range script in the 'value' area in order to get the fader to display (in this case for what I'm doing) 0-3. So clearly the 'scale' thing in the editor is separate from what is defined by the range command. So the range thing works fine but I still need to find out how to change the scale in the Lemur App so that the entire length of the fader only outputs 0-3 as opposed to the default 0-127.
Just wondering, but if you have 4 settings, wouldn't a Switches work better with 4 switches and the radio function engaged? This sends a value of 0, 1, 2, 3 depending on which switch is selected. Just a thought.
Kaatza_Music wrote:Just wondering, but if you have 4 settings, wouldn't a Switches work better with 4 switches and the radio function engaged? This sends a value of 0, 1, 2, 3 depending on which switch is selected. Just a thought.
Nice idea I tried this but it didn't work either. I gave the switch 4 rows & enabled radio. But when I select the second row in the switch the parameter I'm controlling jumps to the fourth position! What I've noticed is that the 'scale' setting is also present in the MIDI mapping window of the Lemur Editor. So in order for this to work I guess I still need to define the 'scale' as 0-3, which it appears you cannot do directly in the Lemur App
Where is it hiding? Is it there all? 
