jcsteh / osara

OSARA: Open Source Accessibility for the REAPER Application
GNU General Public License v2.0
127 stars 46 forks source link

RAZOR EDIT box navigation, selection and controlling support. #509

Open vgjh2005 opened 3 years ago

vgjh2005 commented 3 years ago

Hi: Scene reaper version 6.24, that there are a new feature called razor edit has been added. It is the new and the biggest workflow change for reaper users at last. More information, please visit reaperblog youtube video at follow link: https://www.youtube.com/watch?v=q5A0lcC6J2w https://www.youtube.com/watch?v=SGrhu1aHsd8 I found some scripts about razor edit in following reapack repository: ReaTeam JSFX; https://github.com/ReaTeam/JSFX/raw/master/index.xml ACendan Scripts; https://acendan.github.io/reascripts/index.xml TJF Scripts; https://github.com/sonictim/TJF-Scripts/raw/master/index.xml FTC Tools; https://raw.githubusercontent.com/iliaspoulakis/Reaper-Tools/master/index.xml Hope for help. Thanks!

jcsteh commented 3 years ago

It's unclear to me how we would make this accessible in such a way that it improves current workflows for OSARA users. I'm not saying it's not possible; I just don't understand enough about the use cases or workflow to have any idea how to make something useful out of it. I think we may need someone with sight to try to help figure this one out.

ScottChesworth commented 3 years ago

So far as I understand it, it behaves like time selection boundaries that can be set for specific tracks, and it seems possible to have multiple selections active at a time too. Agreed, we need eyes that've used it in situ to clarify usage. I'll try to rope some in and report back over the next few days.

ScottChesworth commented 3 years ago

Assigned the help wanted label because I know we have a few folk following the reppo that have either usable or full vision. Your input on razor edit could be useful here.

pitermach commented 3 years ago

Recently someone sighted asked about this on the r/reaper subreddit and was pointed to this video from Kenny. I meant to bring this up on RWP but had other things going on, but since someone already started a discussion here I think this has some potential for us as well, assuming I understand how these work.

From that last video, it sounds to me like razor edits behave much more like a typical selection would in an editor like Goldwave, so if you want to slice out a section of audio spanning a chunk of multiple tracks, you can just make a razor edit, then hit copy and not have to worry about making sure the right items on the right tracks are selected which should take far fewer key presses, this concept may also make Reaper easier to use for someone just getting started. I don't quite understand the benefit of being able to have multiple of these at once, but I could be missing some really obvious use cases.

Either way, it looks like Reaper currently has no actions to manipulate these from the keyboard. We'd probably need actions to mark a start and end point of a razor edit, much like we can for time selections, as well as actions to nudge the left and right edges. If we get those actions, then feedback could be provided for them in Osara. To support multiple razor edits we'd probably also need actions to move the cursor between them.

That's of course all assuming I didn't just miss the point of these all together ☺️

jcsteh commented 3 years ago

My question is: in your example, is it really less keystrokes? You still have to select multiple tracks and make a time selection. After that, right now, you press alt+shift+a to select all items on selected tracks in time selection, then control+shift+c to copy. That's two keystrokes beyond the initial selection and one of those is to copy. I don't see how we could make that any more efficient for keyboard users. I guess we could add additional time selection commands specific to razor editing, which would eliminate one keystroke (alt+shift+a), but we'd then have the problem of trying to find space for extra selection commands on the key map.

vgjh2005 commented 3 years ago

Hi: Actually, Razor edit is a containner that include tracks/items/takes/envelope items. Multiple tracks/item/envelope item/region/ selection, Non-broken item editing, multiple areas move, Non-broken ripple editing. It is a huge of useful function. I just make a song backingtrack, when the request was changed, I need to re-select all the selection to output the audio files after editing again and again. Now, I will paste some useful scripts here about razor editing: Script: Create an approximate razor edit from time selection.lua Script: Move razor edit down by one track.lua Script: Move razor edit left by grid size.lua Script: Move razor edit left by one measure.lua Script: Move razor edit right by grid size.lua Script: Move razor edit right by one measure.lua Script: Move razor edit up by one track.lua Script: Resize razor edit down by one track.lua Script: Resize razor edit left by grid size.lua Script: Resize razor edit left by one measure.lua Script: Resize razor edit right by grid size.lua Script: Resize razor edit right by one measure.lua Script: Resize razor edit up by one track.lua Script: TJF Adjust Razor Edit End to Edit Cursor.lua Script: TJF Adjust Razor Edit Start to Edit Cursor.lua Script: TJF LINK Razor Edit and Item Selection.lua Script: TJF Move Edit Cursor to End of Razor Edits.lua Script: TJF Move Edit Cursor to Start of Razor Edits.lua Script: TJF Move Left Edge of Razor Edits to Edit Cursor.lua Script: TJF Move Right Edge of Razor Edits to Edit Cursor.lua Script: TJF Razor Edit-Enclose Media Items (leave selection).lua Razor edit: Enclose media items Script: acendan_Snap edit cursor to nearest razor edit edge in first selected track.lua Script: amagalma_Delete all envelope points inside Razor Edit areas.lua Script: amagalma_Remove all item fades within Razor Edit areas.lua Script: js_Razor edit - Apply LFO to razor areas by converting to temporary automation items.lua Script: js_Razor edit - Enclose selected media items and automation items in minimal razor areas.lua Razor edit: Move areas up without contents Razor edit: Move areas forwards without contents Razor edit: Move areas down without contents Razor edit: Move areas backwards without contents Thanks!

ScottChesworth commented 3 years ago

Nice collection of scripts there man. Unfortunately we don't have room for 30 additional assignments on the key map to accommodate a single feature, so this is gonna take some thinking about.

vgjh2005 commented 3 years ago

Add a razor edit mode to osara then use the normal key to control it.

jcsteh commented 3 years ago

For now, I think we need to talk less about the "how" and get really specific about use cases and why the current way of doing things is less efficient. We can talk about "how" later, but right now, we need to be super clear on the "what" and "why". So, provide example scenarios, what you're trying to achieve, how you would do it currently, and finally, how you think you'd be able to achieve it if razor edit were supported (including an example of what actions you might use). The only way we're going to get a decent user experience here is figuring out how people will actually use this.

vgjh2005 commented 3 years ago

Please think about these situation:

  1. There are lots of tracks. We need output selected tracks seperately to be mixed bassed on different request every time after editing. If we can use razor edit to save select tracks, and we don't need to redo the same works again and again.
  2. We just to copy some block to the another position, and we can use razor editing to do it without breaking item editing.
  3. We need to ripple edit some audios, and we can use razor editing to finish this work without breaking audio editing. If some change were not suitable , and we just delete the razor edit areas. Thanks!