-
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
Request to have 2 new actions stated by OSARA #1183
Comments
Sure, feedback for these can be added. Would there be anything additional to translate? I think these would only report strings we already have, no? |
Would this just use postCursorMovement (i.e. just report the time change) or are you expecting something else here? |
The best would be to have the same feedback as the following 2 actions but for the beats: |
I've added feedback in PR #1184. It's marked as draft at the moment, I'll merge as soon as I see these actions are available in a stable REAPER release. A test build is available in the PR thread, use that to check this works as expected with your key map. |
Cool, I tested and everything works perfectly in English. It will remain to be tested in French with the translation. |
Hi,
The following 2 new essential actions for transport are now native in reaper728+dev1220.
Move edit cursor to start of current/previous beat
Move edit cursor to start of next beat
Is it possible to vocalize these 2 actions with OSARA and add them in the translation, in this case, I will be able to replace the 2 scripts for these actions in the ReaperAccessible KeyMap.
The 2 scripts do not work correctly when there are tempo markers in the project.
With these 2 actions, the problem is solved.
Thanks.
The text was updated successfully, but these errors were encountered: