Hi Slau, As usual thanks so much for your words of wisdom. I did listen to your demo of the edit window and fully get that VO is seeing things that arn’t in the window. This might sound stupid but how do I get to see the actual level metres in the edit view window. I have checked all the things I think need to be checked when going to the view menu and going down to edit view. I can interact with the tracks in the edit view window and can see that the words level metre are there just above comments and if I interact with the audio i/o I can see more info and click on the output window and of course I get more info there. The track heights are all set to medium too.
Maybe I am missing something in the edit window. Best and thanks Toby On 21 Apr 2020, at 00:24, Slau Halatyn <[email protected]> wrote: > > Hi Toby, > Thanks for the message and kind words. Glad to hear you're putting Flo Tools > to use. > > Regarding the Inspector, it does actually work in the Edit window as well. As > long as the track heights are Medium, you can use the same commands. The > thing is, of course, you have to be focused on a track just like in the Mix > window. Of course, the track orientation is up and down rather than left to > right and it's not as easy to quickly get to the vertical orientation of the > visible tracks. To further add a caveat, VoiceOver will not see any level > meter within a track unless 1) the Edit window view is set to show meters and > 2) the tracks are visible within the timeline portion of the Edit window. As > you may recall, VoiceOver sees things that are not necessarily visible to > sighted users. Things can easily be scrolled off screen in either direction. > When that is the case, VoiceOver can navigate to the off-screen track but, > since it's technically off screen, Pro Tools doesn't generate any real-time > level information. It would sort of be a waste of graphics resources. If you > look in the Drop Box folder, I did a quick demo for Ramy regarding tracks > navigation in the Edit window. Have a listen to that and it'll illustrate > some of the navigational quirks. I didn't touch upon Flo Tools there but it's > more about the overall navigation and how to tell if something's visible or > not. > Hope that helps, > Slau > > >> On Apr 20, 2020, at 6:23 PM, Toby Davey <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> >> >> >> Thanks to all involved in putting Flo Tools together a fantastic bit of >> software making life a bit easier for all us visually impaired Pro Tools >> users. >> >> >> >> I have only recently installed Flo Tools as I was waiting for the upgrade to >> Pro Tools 2020.3 to become available here in the UK in my Avid Link and >> then waited a bit for Flo Tools 2020.3.1 to come out too. I have listened >> to Slau’s great audio introduction to Flo Tools and read through the ReadMe >> notes before installing and also have been keeping an eye on all the emails >> and WhatsApp messages about Flo Tools too. >> >> >> >> So now to my observations on Flo Tools. >> >> >> >> Firstly, this might be me, might be due to my Mac but am I right in thinking >> that the Inspector group commands such as ‘L’, ‘V’, ‘m’ etc only work in the >> Mix window? In the Edit window I can do things like double tapp ‘L’ to turn >> level metering on and off but don’t get any feedback of the levels unless I >> am in the Mix window, likewise with volume, etc. >> >> >> >> When installing I made sure that all the settings for VoiceOver, Pro Tools, >> Keyboard Maestro and even switching the keyboard to US were done per the >> instructions in the ReadMe pages. >> >> >> >> All the Flo Tools short cuts work as should be and the inspector group >> commands work as mentioned above in the Mix window. >> >> >> >> So did I miss something in the ReadMe or the great audio introduction to Flo >> Tools as I spent quite a lot of time today trying to work out why the >> inspector group commands were not working in the Edit window, going through >> old PTAccess Group emails, etc. >> >> >> >> As I say a great piece of software and thanks again for all those involved >> in Flo Tools. >> >> >> >> Cheers >> >> >> >> Toby >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ptaccess/db052c2c-72ca-4ad5-9f93-0b81de51f845%40googlegroups.com >> >> <https://groups.google.com/d/msgid/ptaccess/db052c2c-72ca-4ad5-9f93-0b81de51f845%40googlegroups.com?utm_medium=email&utm_source=footer>. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Pro Tools Accessibility" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/ptaccess/N-x6rNVjaNI/unsubscribe > <https://groups.google.com/d/topic/ptaccess/N-x6rNVjaNI/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ptaccess/A056DB72-37BD-41A1-BBC4-2C1C14E9B1C2%40gmail.com > > <https://groups.google.com/d/msgid/ptaccess/A056DB72-37BD-41A1-BBC4-2C1C14E9B1C2%40gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/AC572384-F38C-487B-8CD0-1BA350CB6496%40gmail.com.
