jcsteh
optional automatic announcement of item number when playing track
hello all.
is it possible to implement a thing, when playing track with multiple items, make it possible to announce current item number on switching.
we are splitting large audio files by sentences, and some times automatic splitting tools are failing, and we need to understand which item is corrupted and glue it, so automatic announcement of currently playing item would be very helpful in this case.
Seems like something that could be handled with a custom action. Talk me through the workflow you're looking for.
ok, i will explain in more details.
we have large track with large amount of items for example 2000-2500 items in track.
items were created after auto splitting on silences, but for some reason speaker didn't make pauses between two sentences or pause in one sentence, between words were too big and reaper splitted this specific case incorrectly.
so we know text and want to monitor where are wrong items and split them by hand or or glue them.
for this, we need to listen to the recording and pause when something bad happens.
so we go to the beginning of a track and hit play.
we want if it is possible, while playing track to automatically announce item which is currently playing, e.g. we hit play, track started to play, time came to switch to next item, so screenreader can announce number of this item.
i think i explained in details.
if you will have additional questions, i will try to explain more.
thanks
@jcsteh and @RDMurray are the chaps who would know whether this is something that could be implemented. All I can do is suggest a workflow that might meet your needs with our current features.
- Hit Control+Space to pause whenever you hear a mistake.
- Hit Shift+A to select the item under the edit cursor.
- Hit Control+Shift+Space to report the selected item. I got this down to a single keystroke with a custom action that mostly works. You're welcome to have it if that would be useful. I say "mostly works" because moving with PageUp or PageDown seems to hose track/item selection, which is an issue I've never been able to custom action my way around yet. Feels like a bug in the API tbh. @jcsteh , have you ever had any dialogue with Cockos around this issue where navigating by bar/beat causes OSARA to lose track of what's selected? I have an active thread with Justin if not, should I pop it on his table?
1. Hit Control+Space to pause whenever you hear a mistake. 2. Hit Shift+A to select the item under the edit cursor.
I think this is probably a far more effective workflow for the intent here, since not only do you know the item number, you also have it selected and can manipulate it accordingly.
@jcsteh , have you ever had any dialogue with Cockos around this issue where navigating by bar/beat causes OSARA to lose track of what's selected?
It doesn't. When you use page up/down, that changes OSARA's focus to the ruler, so now report selection reports the time selection. While REAPER has its own focus, it doesn't have focus for the ruler (only for tracks, items and envelopes), so I had to add ruler (among other things) for OSARA. Otherwise, you wouldn't be able to report the time selection, delete a time selection, etc. If you use a track or item navigation command, that will change OSARA's focus to track or item and report selection will then reflect that.
Recent OSARA implementation of fake ruler focus should make this easy to resolve with a custom action, so I'm closing the issue. @beqabeqa473 , feel free to give me a shout on [email protected] if you need help building a custom action to handle this.
@ScottChesworth, just to clarify, what do you mean by "fake ruler focus" here? I made some tweaks to focus with respect to envelopes, but I'm not sure I follow your thinking here.
That'll be because my thinking was flawed, whoops! I was thinking that the fake focus with respect to envelopes also applied to track/item selection, It doesn't yet. That would be a helpful thing to have implementd though, both in terms of maintaining better consistency and solidifying custom actions. Should I open a new issue and outline the use case for that, or is this comment enough to persuade you?
I think there's some confusion here about what that fake focus change actually did.
OSARA has always had (and always needed) a concept of fake focus. Otherwise, you wouldn't be able to report time selection, delete time selections, delete markers, etc.
The recent envelope changes just made it so that the decision as to which type of envelope to select was based on whether a track or item last had the focus. Envelope points and automation items have always set fake focus when you move to them and that remains unchanged.
So, I don't really know what you're asking for here. When an item has focus, you can use the report selection command to report it. If the ruler has focus (which it will after you navigate the timeline), report selection reports the time selection, as it should. Changing any of this would mean you won't be able to do one of those things.
Ah ok, think I understand. Seems like I got tripped up by context sensitivity. WE can only have one type of thing selected at a time with OSARA's fake focus, right? So either a track or item or whatever is selected. If I then move with the PageUp/PageDown keys, that sets OSARA's fake focus to the ruler. Comparing that to the visual UX though, when sighted folk run those actions, the track/item/whatever selection doesn't automatically change as a result. I think what I was asking for was for OSARA to retain my track/item selection along with considering the ruler, but I can see that getting pretty hairy pretty quickly.
It's important not to conflate focus and selection. When OSARA's focus changes, the selection remains untouched. So, when you "focus" the ruler, the tracks and/or items you had selected still remain selected. It's just that OSARA's context sensitive commands operate on the ruler.
I guess the question is what you want to happen from a user perspective here. What sequence of commands currently operates in a way you don't expect? What do you expect instead?