list of parameters dare choose a distance with page up and page down

[ranetto]

Good morning everyone, I don't know if what I'm asking is possible: 1: Problem, when using effects like the fabfilter pro q 4, or synthesizers like dune 3 or others, it would be convenient to have a hotkey to switch between the various sections of the parameters, especially in fabfilter pro q 4, where to switch between a band and a second band, there are infinite parameters to scroll through. Since I realize that it is not possible to save or create something for each synth or fx, I ask you if it were possible, based on the fact that you recently added the maximum and minimum value that can be set for a parameter, in short if it were possible to add with a contextual menu in the parameter list, the number of elements that the list must skip when you page up or page down. For example, I say: I'm in the first parameter of pro q 4, which is the activation of the first band, I press the contextual in the parameter list, the contextual could be called star pageupp, then I move down to the parameter to activate the second band, then again with the contextual on the list which could be called end pagedown, at this point my page upp and page down, would travel that distance of elements, so I would find that starting from the first parameter, I would activate the first band, then a pagedown hit and I would find myself on the parameter to activate the second band, then a third pagedown hit and I would find myself on the parameter to activate the third band and so on for all the plugins. Then when I reach the other parameters this would no longer be useful but it would be a great help for mapping the sections of an effect when you are working on it. It would also be useful in the Whe diva, also in many other synthesizers or effects. What do you think? It seems to me the simplest way to simplify the use of many parameters, without having to memorize anything except for that section or further complicate that window. Thanks and let me know if you find it interesting.

[jcsteh]

That could potentially be done, but I'm not sure how practical it would be. As it currently stands, the minimum and maximum constraints are not saved; they only apply while that parameter remains selected. If you move to a different parameter or close the dialog, the constraints are lost. So, you'd need to reset the distance every time you chose a new parameter. If I understand your use case correctly, this doesn't seem like it's going to be practical in real usage.

[ranetto]

hi, i actually thought that they could only be stored for that osara session, or at least that only the last captured distances could remain stored, so, as you say they wouldn't be for everyone, but if i have 10 tracks and i'm using pro q 4 on all the tracks, until i go to change anything, those page up and page down jumps would remain stored for all ten tracks, i could also realize that those set jumps aren't optimal for another type of plugin, but almost, and so maybe when i use pro q 4 or eventide or hybrid eq, they still work better than having to scroll through all the parameters. i don't know if i managed to explain myself, it would always be better than nothing, maybe even in a synth, where i open and close the parameters window several times while i'm composing my song, i could always find a distance of parameters that with page up and page down makes me go from the filter to the envelope, or from the envelope on vca to that on vcf, etc. What do you think? I know this isn't the best solution, but I didn't want to ask for something too much work, just a little help. Thanks in advance!

[ranetto]

you're right I explained myself badly about the storage, I thought it was a storage for each reaper session, so that when you close reaper and therefore osara it is lost and not a storage until the parameter changes, sorry I corrected myself here to explain myself better

[jcsteh]

Based on your comments, this feature is not useful to you without storage. The OSARA Parameters dialog currently doesn't know how to store anything for a REAPER session, only while a parameter is focused and while the dialog remains open. Implementing that is a pretty significant amount of work, so it's not likely to happen soon. Nevertheless, this is a valid feature request, so the issue will remain open to be implemented if and when someone gets to it.