-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key map update for June 2024 #1076
Comments
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. |
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. |
Yeah, CTRL+Alt+U makes sense. It'll probably take getting used to for anyone used to getting loudness the old way, but so will the change to what O does given I use the LFO generator more than tempo markers
… On 11 May 2024, at 20:13, ScottChesworth ***@***.***> wrote:
what do you think about #737 <#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.
—
Reply to this email directly, view it on GitHub <#1076 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAABTP3DIQUHAHCPLEWUJ3ZBZNU5AVCNFSM6AAAAABHSC53CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVHE4DAMBWGQ>.
You are receiving this because you commented.
|
* Add Time selection: Move contents of time selection to edit cursor (moving later items) to unmodified X, replacing Item: Crossfade items within time selection which we've never had feedback for and doesn't seem to be widely adopted.
* Add Time selection: Copy contents of time selection to edit cursor (moving later items) bound to unmodified C, thus removing a tempo marker action with a name that's too vague and is now redundant.
[PT] I particularly like the simple keystrokes and adding speech feedback to these two very useful actions. Since they were introduced recently, I make great use of them! Much more efficient than searching for them in the Actions list!
…--Pete
|
what do you think about #737 <#737> ?
[PT] Agreed. The dry render options are very useful. I already have them mapped to some of the unmapped “Y” + special keys. I generally use the actions to do the dry render within a selected area, but having the entire track done automatically would be even better. But if you add a hotkey for some of these options, then I can free up the “Y” hotkey combinations again for my custom actions!
One note: When highlighting all tracks for a dry render, I don’t think the Master track will produce any output. The Master track has to be done separately.
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.
[PT] That wouldn’t be bad, but could be a lot of work. 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.
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. |
Very useful and flexible functionality if you can get that all to work! That would certainly save hotkeys and/or searching through the actions list.
…--Pete
|
Well, while the calculation is running you see the standard reaper rendering progress screen, so knowing what's happening is mostly apparent. If you're calculating loudness of specific tracks or items their names also show up, the only thing I guess could be less clear if the calculation is for the time selection and not the whole project because that still just shows the names and nothing else.
… On 11 May 2024, at 22:43, ScottChesworth ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub <#1076 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABAABTONQCXIZTF3WEMFA6TZBZ7G7AVCNFSM6AAAAABHSC53CWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGAZDMOJQGE>.
You are receiving this because you commented.
|
Formatted code to conform to overall project and based on additional suggestions by @jcsteh in PR jcsteh#1073. Removed keymap entries from config and readme due to ongoing discussion about possible reassignment (see issue jcsteh#1076).
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. |
I think that the Close this project tab action mapped to ctrl+F4, could be mapped to ctrl+W, being consistent with Windows with respect to tab and shift+tab, which moves through the project tabs. |
I'd have a MIDI editor suggestion. |
In case the CC lane update makes it into a public release, could we map the action Select all CC events in last clicked lane (ID 40668) to Ctrl+Alt+A? |
I've added those MIDI editor suggestions to the top post, thanks. |
I mean... that action just won't work for users who are running 7.15 or earlier. It is what it is. I don't know what you want me to say, LOL. |
Unless you're concerned that 7.16 bindings will break 7.15 and earlier? I don't think they will. My guess is it'll just be like a binding for an action in an extension which isn't installed, which just means that binding does nothing. |
@ScottChesworth, I have suggestions for more MIDI editor changes if you don't mind.
|
@ScottChesworth, I've updated my wish list in my previous comment a bit. 🙂 |
Top comment updated, couple of questions to think on in the MIDI Editor section. Any entries with an unchecked check box at the beginning are things I'm not so sure about. |
Good idea about swapping the commands for selecting CCs as it really feels more logical, but in that case I would propose using Ctrl+Alt+Shift+A for note selection instead - consistency is key. |
Hmm I don't love the amount of Control+Alt+Shift that's creeping in here man. Multiple people have griped that they find that a tricky combination of modifiers, plus we have more users who have some difficulties around dexterity nowadays. Let's both keep thinking... |
I can definitely see that point. Anyway I hope we manage to find a solution that will result in the key map being reasonably consistent. |
I've got another one for ya. It's not that consistent, but perhaps it isn't all that bad after all: |
Another thing that just came to mind @ScottChesworth. I often run into a situation where I, either intentionally or unintentionally, unplug a MIDI device while REAPER is open. There are two ways to resolve this, I think, either restarting REAPER or opening preferences, going into the MIDI device category and hitting the Reset all MIDI devices button. Both of them are really tidious to do, and I have seen various students doing the same thing when things like these happen. Wouldn't it be more convenient to:
|
I don't think I knew there was an action for that. Neat! Will get that done. |
Another one, should add feedback for "Send all-notes-off and all-sounds-off to all MIDI outputs/plug-ins" while I'm at it. That's been on F3 forever. Resetting can go on Shift+F3. |
@Timtam, great idea. I didn't know about that action either. That one will be a game changer. |
If Shift+C gets mapped to Edit: Copy events within time selection, if any (smart copy), shouldn't Edit: Cut events within time selection, if any (smart cut) than be remapped to Shift+X? Unfortunately though, the action Edit: Paste preserving position in measure that's currently mapped to Ctrl+Shift+V can't be remapped according this same logic. Not saying that Ctrl+Shift+X or V absolutely have to be remapped - just have been wondering about this. |
Another thing I'd suggest regarding CC actions is dropping Edit: Toggle selection of all CC events under selected notes and mapping Edit: Select all CC events in time selection (even if CC lane is hidden) instead. Of course the latter action behaves different, but it allows you to do the same thing plus more since you have more precise control over which section you want to select CCs from. |
Top comment updated. This is likely what I'll build for wider testing unless there are any objections soon. Most amount of changes are in the MIDI Editor section. |
This one is in there twice: • Added "Select all CC events in last clicked lane" on Control+Alt+C. Thats all though. Still thinking about where to put the Solo in front actions though, thats the only thing open atm right? |
DOH! Fixed it, thanks. It's solo previous and next track exclusive we need new homes for, not solo in front. |
Yeah, thats the one I meant, had a decently stinky brainfart there. |
If it's OK, I'll rather comment here instead of starting a new issue. |
This issue is still open, but it should probably be closed since the PR associated with it is merged. I would suggest filing a new issue, since otherwise, this request is likely to get lost. |
@jcsteh, thanks. 😉 |
This is where we'll be discussing and tracking work on the next OSARA key map update, aiming to merge at the end of June 2024. All changes are documented in this top post, feel free to try a test build below.
Please raise any concerns or alternative suggestions in the comments. Note that we're now only considering urgent issues, as we're nearing the end of the month.
Download OSARA for Windows with June key map changes
Download OSARA for Mac with June key map changes
Main Section Additions and Changes:
Note: Cockos specifically designed these two move/copy actions to opperate with a single click, hence the rationale for assigning them to single letter shortcuts.
MIDI Editor Section Additions and Changes:
Development tasks:
The text was updated successfully, but these errors were encountered: