Your shopping cart is empty.

Relative behaviour in CSS vs Web-App

Submitted by Robert Büttner on Tue, 02/16/2021 - 10:44
Robert Büttner
Control Surface Studio User

I am sorry for the double post
But a question developed to a feature request.

In the Web-App you can choose from 3 different relative-control-standards.
All of them have acceleration. Eg the faster you turn the encoder, the higher are the value-jumps for each step.
This way you can fine-tune your parameter by turning the encoder slowly and make fast and big sweeps by turning it quicker.
This works by sending values that depend on the speed. EG turning it slow sends a 1, turning it faster a 2 3 4...

In CSS you can define 1 value for increment and 1 value for decrement and then you can define a general size for each step.
This creates 3 problems:

- Acceleration is not possible, as we would have to be able define more values or ranges of values.
- Most of the time you will not be able to use a relative encoder at all as most of them only send different values depending of the speed you turn them.
This leads to the parameter only reacting to a certain speed. But if you turn faster or slower it doesn't react at all.
- Even if you have an encoder that has the option to send only 1 value for increment and 1 for decrement you would loose the acceleration that is in many cases necessary to purposefully use an controller.

So please, either change the relative behavior on CSS to the way it works in the web app or add the three standards of the web-App to CSS!

Thank you!!!!

Robert

Topic Category: 

9 Responses

Comments

John C
Forum Admin
#1

Thanks Robert, I've made a note of this.
As I think I mentioned in another post the new version of Reactions should hopefully be able to cater for adding web app style / framework controls.

ManukeMat
Control Surface Studio User
#2

The workaround is to create a parameter for each speed :
Param 1 speed 1 : knob 1 relative 127 - 1 -128 steps
Param 1 speed 2 : knob 1 relative 126 -2 - 64 steps
Param 1 speed 3 : knob 1 relative 125 - 3 - 43 steps 43 (or 64 if you want the speed to be exponential)
Etc.
It work but it is a real pain to edit.

calltrel
Free User
#3

Thank you, ManukeMat !

Robert Büttner
Control Surface Studio User
#4

Yes, thank you from me too!
Even though it is tedious, it makes it really flexible, as you can control the amount of acceleration.

Perfect would be for the future to integrate this into one parameter.

ManukeMat
Control Surface Studio User
#5

There is en error in my post :
For speed 3 : it's 32 steps, not 64 to have exponential speed.
* It would ne nice to be able to edit out post to.

ManukeMat
Control Surface Studio User
#6

By the way, it would be more logical to have the step parameter the other way :
Instead of writing 128 steps to have increments and decrement of 1 , just enter 1.
Because for exemple if we want increments of 3 we have to divide 128 by 3 and it's not a integer.

calltrel
Free User
#7

Dear remotify,

I spent a slim dollars on the Pro version and had a few exhausting nights. CSS definitely has potential, but it needs a lot more pre-made presets for the standard controllers like Arturia Minilab MK2, etc. Otherwise it won't reach the mass market. You can also order such devices for a test...
What really does not go at all is the currently necessary 3-fold assignment for a single rotary, because there is currently no real Relative (lin. 2's Comp.) connection. ( And thanks again to ManukeMat for the hint)

This was also the moment where I finally wanted to return the product. I decided differently and now I want to give you the time to perfect your product even with my money, because I think the approach is promising.

But please take care of the "relative" problem as a priority. Until then I will not be able to use your tool.

John C
Forum Admin
#8

Thank you ManukeMat for the great workaround here and thanks calltrel for your feedback, your points have been noted.

Soundmonkey
Pro User
#9

I am also stuck without proper relative acceleration in CSS. In the web app I can get the knobs on my Minilab MK2 working properly but it lacks the chain targeting feature I need for the script I am trying to create.

I would love for this feature to be added soon.

ManukeMat, thank you for the workaround! I'm trying summon the patience to use that method for the 16 knobs I'm trying to map.

Thanks!
-Matt