osara
osara copied to clipboard
jcsteh
start of open folder start and end of folder
Hi everyone, I'm very confused because Osara first announces the name of the end of folder track, before saying end of folder, and so when I quickly go through it I miss the end of the folders themselves: before it was different and I was much better off. Don't you also think that it would be better if Dasara first said end of folder and then possibly the name of the track that closes the folder? When you go through it quickly, hearing the words start of folder and end of folder makes it much easier. What do you think? Thanks in advance
The order changed when we introduced support for nested folders, IMO it makes sense this way now that we include the names of folders in our reports. One alternative I can do to report the end of folder sooner would be to introduce something that distinguishes between the name of the folder and the track, but that feels like a productivity hit when I'm moving through complex folder arrangements here, it means I'm waiting too long to hear the name of the track.
Hi, but the support for nested folders works well, but it would be nice if it just said end folder before the folder name, because when you quickly scroll through the tracks, if you don't give it time to hear that it's an end folder, you you take it for a normal track name, this is how it happens to me and I always have to go back to understand that it was the end of the folder, in fact to avoid this I am forced to never name the track that closes a folder so as to allow it to say end folder as first term. Do you think this makes sense?
Seems like the length of the report is problematic either way. The way it is now, you're unhappy because you don't hear the folder notification soon enough. The way you want it to be, other people would be unhappy because it will take too long to hear their track names.
We have developed 2 scripts to overcome this problem. ReaperAccessible - Main - Go to first track in folder ReaperAccessible - Main - Go to last track in folder The scripts are available here. https://reaperaccessible.fr/index.php/en-us/ In addition, you have the following 2 SWS actions: SWS: Select nearest previous folder SWS: Select nearest next folder With these 4 actions, you no longer need to wait.
First, the issue here is not about how to navigate folders, but the format of the spoken report, yes?
I'm probably in favor of hearing the End folder part first. But as @ScottChesworth says, I don't think there is a solution that will make everyone happy. Personally I solve the problem with using an empty track as both start and end of folders. It's not perfect but it does avoid this particular issue.
in fact the problem is not having an additional command to go to the beginning of a folder or to the end, on the fact that others would be unhappy not to hear the name of their tracks, I say that since the folders are usually composed by topic, that is, they act often by bus for the tracks that are contained in them, I think that in that situation it would be much more useful to know that the folder is finished, or even the subfolder, and that therefore we find ourselves navigating on a single track. When I compose a folder it is much easier for me to know more or less what it contains, what types of tracks and what they concern, while the individual ones could escape our control more easily, then if I mistakenly deleted the track at the end of the folder I would cause damage since all the traces would be nested inside, I don't know what. I had to adopt this strategy of not naming the end of a folder and therefore having an unused track but only as a frame for the folder itself. However, this creates problems for me when I work on other people's projects who clearly do not adopt this solution. Among other things, I also want to point out that as regards the beginning of the folder, the behavior of osara is not consistent with that of the end of the folder, as the track that opens the folder itself is always announced as open before announcing its name . No, do you find it inconsistent too?
Hmm yeah, the blank track workaround wouldn't be any use during collaboration on projects we didn't arrange. I hadn't considered that. If switching the order, I'd still like to shorten the report while I'm there. Question: do tracks that are starts/ends of folders need to speak their track number? I'm thinking that if they didn't speak a number, that would be another way of distinguishing them wen we're moving fast through a track list.
no I would say the number no, then for those who have enabled the track numbers they will have the possibility to hear it later by moving around
Closing as a duplicate of #907. If you disagree, please reopen and justify. Thanks.