Percussa Home / Shop / Contact /

A way to toggle encoder wrap around

SSP Features and Ideas
#1

Description of feature (short and simple): I would like the ability to turn the encoder wrap-around off.

How will this feature improve the workflow or experience for all SSP users (keep it short and focused): I would like to be able to turn off the wrap around feature of the encoders. Often it is too easy to go from minimum to maximum settings (or visa versa) when adjusting with the encoders, resulting in big changes in the sound. I would like the option to just stop at the maximum or minimum range. Maybe pushing the encoder would go past these ends when wanting to. It would be nice to add acceleration to the encoders to, so if moved quickly, the data changes in coarser increments, and when moved slowly, finer smaller changes happen.

#2

ok, the following is for factory modules

there is a setting that enables/disables wraparound.

global setting : RtMM ?

there is some kind of acceleration, however, Im not sure its on every parameter, and doesn’t scale well e.g. some parameters have really wide ranges (e.g.frequencies) others quite narrow.

coarse/fine - yeah, this has been request many times, as has ‘reset’ to default value.

my modules are a bit different, as I adapted to my taste :slight_smile:

the following is for almost all parameters for consistency, however I make use-case exceptions where I deem appropriate.

  • no wraparound ( I have no access to global setting, so cannot make this ‘optional’)
  • push = reset to default
  • push n’ turn = coarse

I don’t tend to have acceleration, I found it generally unnecessary due to having coarse/fine, which I found more ‘reliable’.

also for some reason, when I implemented acceleration I didn’t really like it at all, it felt too vague, lacked precision - to the point of annoyance. ( * )

( * ) I got the feeling there was a technical ‘issue’, some kind of lag/latency - either the refresh rate on the encoder messages or the update rate of the display.

note: this was likely something to so with the plugin sdk implementation.
I didn’t dig very deeply, I just found, I didnt really like it as implemented, so removed it/ replaced with the coarse/fine (as above)

1 Like
#3

Thanks! Much appreciated. I can totally understand the reasoning behind the accelerated scrolling thing. Some list are just incredibly long. An alternative would be a next page/prev page button of some sort. I will just get used to it.

#4

the problem here it (the ‘acceleration’) is not consistent

it would be better if we had 1 encoder for regular changes, 2 encoder for small changes, 3 encoder for big changes