General

Ramp Values of Switches...

Started by metamorfosis18 on .

Sign in or create an account to join the conversation.

22 posts

I found this example here which does almost what I need! I would have to maybe apply some of the coding from this one, to my previous example to make it work!!
Now thats the problem, I tried, but since I really don't understand the logic behind the coding to well, is almost imposible to get it to work by chance!!

Can anyone help merging this to examples please!

SwitchRamp2.jzml
hm I am a little confused

Ok so you want to change a fader's x value with switches, but you want the fader value to change gradually instead of instantaneous right? And then you want a knob or something to control how quickly the value changes?

Is that right or totally off?
Hey man thanks for replying, you almost got right!
instead of using a fader, I would like to use this switches to control a fader in Ableton, so I that can determine exactly the value that is being sent each time a press one of them.

So lets say I have five switches, they all send the same CC to be assign to control a fader in Ableton or any other DAW.
1st one sends a value of 0, so it should make the fader in Ableton ramp down slowly from wherever it was, to 0. (Not jump)
Second send a value of 20, lets say, so if pressed, the fader in Ableton should now ramp slowly up or down from where it is to this new value
and so on....
The last switch would be full value, lets say 127, and again if tapped, my fader in Ableton should slide up from where it was to its full level.

About the knob that you asked, I don't really need to change speeds. It could be a fixed speed, just not too fast for a smooth fade effect.
I would like to find and edit that value, of course if I feel that is to fast or slow for my purposes.

Thanks again, I hope I didn't bore you with this long explanation!! :D
ok
I made one that is not relative to size, it is the same ramp time for every change.

I used a multislider with physics on to avoid using any on frame scripts. So it is super efficient. You just have to keep it around (you can hide it somewhere) that object is called: 'timer'

So I hope you can figure it out and learn. No directions really, but I tried to keep it simple (ask for explanations if needed)


2 knobs: 1 sets number of switches and 2nd is the speed

let me know

(deleted the module because I reposted it later)
Hey I tried it but for some reason the switches don't send midi out and the fader is locked, like frozen on the iPad . Now I tried closing and opening the app again and the fader starts to go down from the top slowly and then it works. But every time I sync it with the lemur editor on laptop it happens again it does not work.
Any ideas, is this normal behavior maybe because of the coding?
If you do check it, can you help me out with the relative rate coding! :roll: I will study and analyze this example to try to understand the logic/syntax behind it!

This is brilliant work, I had been trying to do this for so long with any success, thanks a bunch man.
WAAAIIIIT
I tested it some more and it kept freezing (because value keeps going out of limits in different places)

OK I think I got it right, it's not locking for me anymore. Let me know if it works fore you

(definitely download this one, the last one had issues)