Key map update for June 2024 about osara HOT 32 OPEN

from osara.

Fitting in the theme of removing/replacing SWS related actions what do you think about #737? It will probably require some further discussion and development time but personally I think it would be useful.

from osara.

what do you think about #737?

I like it. Having dry run variants available as actions is great of course, but there's no way we can map them all. A single keystroke acting on context would be something I'd use a lot and I think could make checking loudness less intimidating for new users.
Hmm, the menu structure presenting all the available options feels like it's a bit beyond the scope of OSARA, but that could also be a gut reaction to me being horrible at writing that sort of C++ at the moment lol.
Re the key mapping, if we add this new action, what do you think about putting it on Control+Alt+U seeing as it applies to both items and tracks? That would mean switching "Item: Move items to subproject (non-destructive glue)" to Control+Shift+U instead, because generally working with items is on Control.

from osara.

from osara.

from osara.

For some people it would be nice to easily get to all of those options, but for others, they just might want to have a single keystroke to perform an action.

The people who need all the options can get to those using the actions list, they could also set up render presets if they're not comfortable with remembering all the terminology and variants.
A single keystroke that could dry run acting on context is what I'm more likely to try working on here, got a hunch that adds something new and useful. IE,

• Select the master track and hit our new action, it dry runs master for entire project length.
• If you select master and there's a time selection set, then we dry run master within time selection instead.
• Select an item and hit it, we dry run that.
• Ditto track or multiple tracks.

What I can't work out is how we'll report what's being dry run reliably. I think I see a way to speak a summary soon after the dry run has started using a recently added callLater function, but hmm, the process starting then we report what's happening seems weird to me. I do think there's something in this though, will keep thinking.

from osara.

from osara.

from osara.

while the calculation is running you see the standard reaper rendering progress screen, so knowing what's happening is mostly apparent.

On a decently powerful computer, yeah. However, I've seen plenty of machines where trying to navigate when that screen is being shown was like dancing in quicksand with a shoe full of glue.

from osara.