Setting window views

[Chris Gilland]

Sorry if lately I'm wearing out my welcome here on list with so many message. I promise I'm gonna slow down now that I have PT working again. That said, may I bother you all with one more question? :)

I noticed when going through the PT Access guide, as I'm brushing up on a few things here and there, when I hit one of the edit view buttons like the mix view button where you then select the things to show/not show, same with the edit window in the edit toolbar etcetera, when I press either just space by itself, or VO+Space on one of the buttons, I'm unable to tell if it's enabled or disabled.

In 2022.12, on Ventura, how can I go about telling. I kind of remember that it used to be, if it was enabled, you'd hear it say comma before the name of the button. But now, that's not even working on my end.

I have all preferences and such set down to an exact T the way Slau has them set up to the end of chapter 1 in the guide, if that helps, and I'm now in the edit window trying to do this on the views where he enabled zoom controls.

Chris.

[Martin (Punky) Sopart]

Chris!

After pressen e.g. the mix window view selector button you can toggle the state by using the space bar.
On my system Flo Tools speaks the word "comma" to announce the checked state.

Does that help?

Best! / Martin

--
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 ptaccess+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/CB5226B1-3512-44A1-8F99-908CD81658E0%40gmail.com.

[Chris Gilland]

No, not really, absolutely no offense meant. It's weird as for some bizarre reason, mine isn't saying comma no matter what I do on the button. It does seem to be toggling, but comma isn't being read out.

But, I do have a question of suspition as I know most people up here probably are not using this on Ventura.

I'm using Eloquence, not Alex or the like. Could it be that somehow, Eloquence just isn't reporting the commas? Would you be willing to test for me? I'd do it, but I suffer from severe hearing loss, and most of the other voices, I have trouble understanding well enough to easily navigate. I can, and did in the past do it, but very difficultly.

Chris.

> To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/007901d95760%24963c2020%24c2b46060%24%40cakewalker.de.

[Martin (Punky) Sopart]

Chris!

Yes, it's the Eloquence.
I'm using the Siri voice 4 here.

Maybe there're some special punctuation settings for the Eloquence, don't know.

To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/AF65C857-D3E4-4601-B5AE-4D978CF06882%40gmail.com.

[Chris Gilland]

OK, that's really really good info to know. Thank you for conforming this. I suspect this is not something that could be fixed with ProTools, as it's not a PT issue to start with. It's like you said, an Eloquence thing. Well, that stinks! I mean, granted, I guess I could look manually and see if it's enabled, and if so, great, if not, then just go hit space on it and trust it's enabling. Kind of annoying, but you do what you've gotta do.

To be totally fair, Eloquence has always had some odd querks like this one, so, I definitely don't put this at all on the Avid accessibility team. It's definitely not their faults.

Chris.

> To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/007b01d95762%2479f80850%246de818f0%24%40cakewalker.de.