helgoboss / helgobox

Helgobox: ReaLearn & Playtime
https://www.helgoboss.org/projects/helgobox
GNU General Public License v3.0
211 stars 20 forks source link

Add possibility to declare one mapping as default mapping #159

Open helgoboss opened 3 years ago

helgoboss commented 3 years ago

It would be used as base for newly-added or learned mappings.

jackmau commented 3 years ago

very useful for shift/page functionality working on parameters, which are likely to be the same between presets

helgoboss commented 3 years ago

Should be tied to the instance then it's more flexible. Providing a global default, not sure if that's so useful.

stereokai commented 3 years ago

Should be tied to the instance then it's more flexible. Providing a global default, not sure if that's so useful.

How would a default mapping come of use in the scope of one instance? Can you please give an example?

helgoboss commented 3 years ago

Should be tied to the instance then it's more flexible. Providing a global default, not sure if that's so useful.

How would a default mapping come of use in the scope of one instance? Can you please give an example?

I think it often depends very much on the project or even ReaLearn instance which settings make good default settings.

When I opened the ticket, I was mainly thinking of soundasleeps use case (see forum) who wants to hide ReaLearn completely and do everything just via learning via ReaLearn's global REAPER actions. He would have one ReaLearn instance (e.g. in the monitoring FX chain) that's always active. At least for him, defining the default mapping in instance scope would be enough.

vonglan commented 3 years ago

very useful for shift/page functionality working on parameters, which are likely to be the same between presets

@jackmau : do you mean, during the creation of a larger set of mappings? For example, if I want "track must be selected" to be selected, or to set a certain (non-default) step size for all of them, without having to edit that field manually in all mappings?

stereokai commented 3 years ago

I was mainly thinking of soundasleeps use case (see forum)

I couldn't find the conversation on Cockos forums, but:

who wants to hide ReaLearn completely He would have one ReaLearn instance (e.g. in the monitoring FX chain) that's always active.

Isn't that the common way to use ReaLearn? (especially concerning the first point) :)

do everything just via learning via ReaLearn's global REAPER actions

A confusing sentence, but do you mean he's just using ReaLearn to control Reaper itself? (as opposed to plugins)

Thanks for clarifying

helgoboss commented 3 years ago

who wants to hide ReaLearn completely He would have one ReaLearn instance (e.g. in the monitoring FX chain) that's always active.

Isn't that the common way to use ReaLearn? (especially concerning the first point) :)

Not the way he uses it, no. He has one instance in the monitoring FX chain which is mostly empty and whenever he needs to control something, he learns a source for this instance - without opening ReaLearn but by invoking the "ReaLearn" REAPER actions.

do everything just via learning via ReaLearn's global REAPER actions

A confusing sentence, but do you mean he's just using ReaLearn to control Reaper itself? (as opposed to plugins)

Thanks for clarifying

No, ReaLearn adds actions to REAPER's action list. Check it out.

stereokai commented 3 years ago

Ah, that's very interesting in fact. Thanks for bringing that to my attention!