Increment slider by 1 or by 10

Question

Hi guys,

I have a slider with a range of 1 - 400 and two super controls that step this slider up or down by 1 tick.

I want a way to increment it by 10, or 50, or whatever, so I can make it go in small or large steps. I thought about having a second slider with 40 ticks, so the midi range would go up in steps of 10...but failed to make this work.

Any guidance please?

Comments

You have the right idea there cnurse by adjusting the ticks to force the increments to be a defined value but it's difficult to keep the increments consistent. For example when you manage to get increments of ten some times you get ten increments and other times your get nine.

It's actually a good feature to request , to allow the Max value of a super control to set increment values no matter how many ticks are set , it will solve a lot of issue regarding your request.

Hopefully Dan might consider adding a toggle button in the midi dialog properties that we can set to indicate to use the Max value in this way.

I will vote your suggestion.

---

1) you can use named ticks to handle this problem. It's a ridiculously inelegant solution, but it should work. Also the MIDI values will be pretty surprising.
2) @midicode: I would love to give you an option. To give me a better idea, can you explain what "allow the Max value of a super control to set increment values no matter how many ticks are set" means? Can you give some SIMPLE examples, please?

Thanks for talking and thinking about this, guys, and sorry the current way of working doesn't hit this case well. Let's figure this out, though...

---

When we create a super control and press it, it's sup controls get sent and at the same time the sup controls value is added by one or more depending on how many values and ticks the sub control has and at the same time it doesn't seem to matter what value the Max is set to on the super control. So I was thinking it be cool to make use of the super control's Max value by using it to indicate how much the sup control's value should be added by.

This mechanism is limited because there could be a lot of sub controls and people would want to set different step values for each sub control. it be better if we could set each sub control's step value.

---

I've just been reading on another thread where the admin explained that you can insert a document of named ticks with there values and display values in a single copy and paste operation and even append/insert at any location using the Edit Text option in the Named Ticks dialog. This means you can use any program to generate large list of values in any order whether forwards , backwards or random and then use normal increment momentary switches to select next or previous value.

---

Yes that is awesomely simple isn't it. I've found that particularly useful when copying lists of named ticks from Midi Specifications. When your device has a list of Amp Simulations for example, you can use the exact same name and spelling so everything is very consistent.

Answer 1

1-400 is irregular. You will never get in an increment of 10 in that way. If you want to have an increment of 10 the Display Min-Max range should be 0-400 and the number of ticks should be 41. Now, when 0 is selected you can still send the midi value of 1 in that case, but that you will have to change that in the Named Ticks window.

So in summary the steps in order are

Midi Min->Max is 0->400

Display Min->Max is 0->400

41 ticks

Then in the Named Ticks window in the MIDI Renum column at tick 1 you enter 1.

This will also change your Midi Min-Max automatically but that is not a problem.

Never change anything afterwards because it will start renumbering your midi values, but in that case just repeat the steps I wrote above.

Comments

Wow Using name ticks actually solved the issue , Thanks ezb for the insight.

You don't need to do anything but set the named ticks to the values you want so setting step values is a matter of inputting all the values in the named ticks of any control no matter if it's a sub control or not. It will solve short ranges that's for sure but for a long ranges it could be tedious.

Hope cnurse can make use of the named ticks implementation.

---

So I should have :

A) slider 1-400
B) momentary button super control of A increments value by 1
C) momentary button super control of A decrements value by 1
D) slider 2 has 40 named ticks with a range of 1 - 400 and is a super control of A

Is that close?

---

Not close at all. The way I see it the following is the only solution for the moment. If someone has a better solution let me know so I can learn something new. :)

A) 1 slider 1 to 400 with midi message X
B) Momentary +1 and -1 button (super controls of A)
C) 1 slider 0 to 400, 41 ticks with midi message X (and sending out midi 1 in the Midi Renum column of the named ticks)
D) Momentary +10 and -10 button (super controls of C)

---

So how do A and C synch values if they are not linked? If they are not linked doesn't that mean one could think patch 100 was selected whilst the other thinks patch 13 is selected?

---

You know what, this is so clumsy there is strong use case for a slider with integrals small step / big step controls.

We still need a slider that doesn't force a numeric value to be displayed, rather just displays the named ticks. This is really important to the look and feel of my VG99 layout.

---

There's an Easter Egg for that, which we made for popup ;)  

Change all the display values to zero. Obviously try this in a limited sandbox. The display value should disappear (slider, crossfader) or change to be a hyphen (knobs)...

Not wonderful looking but gets the job done.

Let me know if these instructions didn't work (or did)!

Thanks!

---

Why have a useful feature like that as an Easter egg? It's a bit silly not making that feature public, I did not buy this software to have to guess whether a feature exists or not. I think all features should be documented and not left to be discovered by chance.

---

1-400 is 400 values, not 401, count 1 - 10 on your fingers...you won't reach 11 :)

---

Yeah the setting all display values to 0's sure does make the layout look cleaner now that there are no numerical values displayed over the named ticks. Nice! And yeah, shouldn't be an easter egg fellas ;-)

---

Hey Chris, never saw this comment from January. Yes, it should not be an easter egg: it's a temporary fix until we can properly include it in the App. Thanks!

Answer 2

1-400 is irregular. You will never get in an increment of 10 in that way. If you want to have an increment of 10 the Display Min-Max range should be 0-400 and the number of ticks should be 41. Now, when 0 is selected you can still send the midi value of 1 in that case, but that you will have to change that in the Named Ticks window.

So in summary the steps in order are

Midi Min->Max is 0->400

Display Min->Max is 0->400

41 ticks

Then in the Named Ticks window in the MIDI Renum column at tick 1 you enter 1.

This will also change your Midi Min-Max automatically but that is not a problem.

Never change anything afterwards because it will start renumbering your midi values, but in that case just repeat the steps I wrote above.