Thanks a lot for listening Daniel!!
overcomplicating is not good, definitively.
I will still find my way, I'm sure and as you said that deselecting should actually only deselect one position in only the current preset, it should work much better for me. (long press for deactivate positions in ALL presets and short press for deactivation on only current preset might be interesting as well)
One can't have everything, must always fit the UI etc... so I feel totally ok
[Hold the preset in Save Mode and you go to Route mode of that preset while sequencing, in settings you can then choose to assign either randomise or edit function to preset holds.] But I am not sure about this, I will start programming it next week and see if it feels right.
interesting! (if not overcomplicating)
However with a small workaround the workflow you describe is even possible at the moment: 1. Select a routing position, 2. go to the desired setting. 3. Select other positions, 4. Flick the encoder, 5. All routing positions are set to the setting. 6. push matrix button to deselect. 7. Press Func and a new position to start again
Just make sure the encoder response is set to instant.
I still don't understand completely.
The sequence is stopped here in this scenario, I think?
I think, all in all, I use this workaround, but am I right that this only works for one preset but not if the sequence is running?
Example: positions 1-1, 2-1, 3-1 and 4-1 are my "dry signals", normally set to 99 exept one input is too loud, so I would attenuate it a little.
My sequence is running.
I want position 1-1 through all presets set to 99.
I push 1-1 and set the encoder via push and turn (in order to be faster as my sequence is running) to 99.
Now, the sequence continues. It arrives preset 2.
In order to activate and get the same value, I turn the encoder one click leftright to catch the last used value. (Respectively with value 99 I keep on turning the encoder CW)
Preset 3 arrives, I keep on turning the encoder CW to catch the value again....
This means, with every new preset, I have to catch the last value with the encoder by turning it one click left or right and back (already getting some value variations here if I'm not fast enough)
Or - for this example - Value 99 - turning the encoder continuously CW until I reached the last preset... turning turning turning....:-)
Now, 1-2, 2-2, 3-2, 4-2 goes to my reverb.
Let's say, we want every second preset to have value 23 for 1-2
I push 1-2, set value to 23 very fast before the next preset arrives, then wait one preset. Now, reaching the third preset, I have to wiggle the encoder 1 click leftright or rightleft to catch the last value and keep on going like this till I reached the last preset, always edit only every second preset.
This means, turning the encoder every second preset one click leftright/rightleft
Here, for me it's annoying to wiggle the encoder all time leftright, as I make tiny mistakes here and would just like to press the same position in the following preset which should get activated with the same value then.
So, if I made a mistake (edit a preset on accident as my sequence is running) I would deselect these positions ("zero") the next round then.
The difficulty now comes if I want to set single positions to a certain value on only some presets.
Here it gets very inaccurate fast and I have to reedit a lot, respectively it's almost impossible (as I have to dial in the correct value but already write the "dial in" into a preset this way).
So, what I do as workaround now, is to "draw a curve" over the complete sequence and all presets for that position (with pushed encoder to obtain bigger differences). In the next round then I have to deselect ("zero") all the positions I want with value 0 again, or set the encoder to 0 and always turn the encoder one click CCW when reaching the desired preset. Now, I still should do some fine adjustments but really have to stop the sequence here (that's why I meant I needed to hold the position and turn encoder in order to "freeze" this edit point as the sequence is running)
The thing is - I better have to do this when the sequence is running in order to hear the timing of the effects in relation to the changing presets