OK, Karen, I finally have a chance to give you and the list members who've used Pro Tools with OS 9 an overview of how the two systems compare in terms of accessibility.
First, I suppose it's important to point out (although it should be fairly apparent) that the same Pro Tools keyboard shortcuts that were available in Pro Tools version 5 under OS 9 are still available. In fact, there are even more shortcuts since combinations once available only in TDM systems were incorporated into LE since Pro Tools version 6.7 or so. Since outSPOKEN users couldn't migrate to version 6, this was never available until now. Some aspects of the user interface which were hidden or clumsy under OS 9 unless you were a power user, are now easily accessible in Pro Tools 8. for example, the playlist icon was never visible with outSPOKEN. A user had to simply understand that it was an invisible icon to the right of the track name in the Edit window. Not the track name in the Show/Hide list but within the scroll area that contained the record, mute and solo buttons. The icon was in a fixed position based on the relative position of the track name and, since track names in this display were limited to 8 or 9 characters or so, the icon was directly to the right. If a track name had four characters, an outSPOKEN user could move the cursor four clicks to the right and do a mouse click. This, of course, presumed that one had read the track name from left to right rather than right to left, else the cursor would be to the left of the track name and one wouldn't land on the right position to click on the playlist icon. All of what I described above makes it sound like it's incredibly complex to get to the playlist icon with outSPOKEN. Trust me, it's not. I can do it in a matter of a couple of seconds—probably faster than it would take someone to grab a mouse and move the pointer. However, to someone who wasn't using Pro tools every day and for a living, it might not even occur to them that such a thing is possible. However, with the current version, it's a simple matter of clicking on the playlist button and you're in. Another such example is the Groups List where, depending upon what was highlighted or active, one had to constantly monitor what the status was of any given group, especially in a complex editing situation where groups were being employed. Now it's an easy task and doesn't require a bunch of mousing around and checking status, etc. An area that's not yet accessible is the MIDI Event List. Now, that's a big deal, frankly. For the most part, I use MIDI fairly often but not nearly as often as someone would in a home studio situation. Most of my needs and my client's needs are covered by simple record, cut, copy and paste, perhaps a little quantization. A significant portion of the time, however, MIDI is of no significant use to me. That said, when I do need tight control of things like editing note on and off velocities, it won't be possible with the current MIDI Event List. There are certain work-arounds which I won't get into right now but will simply say they're not nearly as efficient as having an accessible event list. In a similar way, entering tempo and meter changes is a breeze but, once they're entered, it's not possible to edit them currently. In some cases, that's a deal-breaker for someone needing heavy editing of tempo maps, etc. The subject of plug-ins is interesting and somewhat complicated. When the last major work was about to be completed on the interface, we all thought plug-ins weren't going to be accessible at all until a future release. Believe me, after seeing what had already been done with the entire rest of the interface, I thought, "So what. Look at all we have to start with." Turns out, the programmer figured out a work-around that gained access to most plug-ins right out of the box by exposing automation parameters. Now, this works quite well for a ton of plug-ins but not necessarily all plug-ins. This is because, while plug-ins have automate-able parameters, they might have menu buttons which are not automate-able and, thus, are not exposed to VoiceOver. A work-around is to use something like quicKeys to create shortcuts which can even be shared among users. None of that has happened yet although I've used QK for many years, I haven't used it in OS X. I'm sure Bryan's experiments will yield some great results at some point soon. Perhaps others might get involved as well. There are still some windows that are not accessible like the Workspace window or the Disk Space window, the Universe window, among others. These are not critical and have varying degrees of importance. for example, the Workspace window is where you set the record and playback designations for given volumes on your system. In other words, you specify whether a hard drive is for playback only or recording, etc. Well, I've never had to set anything in that window until one specific instance where, for some inexplicable reason, Pro Tools wanted me to specify the information. Actually, this was even before I had a beta of the accessible version. I was using Pro Tools completely by keyboard shortcuts to playback some backing tracks at a performance. Well, luckily, I had someone look at the screen, set the parameters and we were off. since then, never had to look at that window again. Still, it's something that we should have access to in the future, just for those special occasions when things are going so smoothly and a good wrench in the gears would make life oh so much more interesting. Now, speaking of having a sighted person help, I have to say that, Pro Tools is both a very simple and very complex program. In fact, it can be anything in between as well. Thing is, the better one knows the user interface or at least how to use Pro Tools, the better off they'll be using it with VoiceOver. I've always said that one needs to read the Pro Tools Reference Guide and understand it independently of the screen reader. Secondly, one needs to know the screen reader like the back of their hand if they expect to be efficient. That said, I haven't put in enough "real world" time in on VoiceOver with Pro Tools 8 in order to feel comfortable using it in sessions with my clients. Sure, some sessions would be a breeze but, some of the more complex sessions would require me to have some procedures a little bit more, shall we say, under my fingers. I have no doubt that I'll get to that point very soon. Having said a few specific things and a few general things, it might be easier for me to answer some very specific questions about specific tasks rather than general things about what it's like to work in Pro Tools or edit in Pro Tools. Questions like that are simply too big and they can have a short or a long answer, both of which may not actually answer the question satisfactorily. Hopefully that makes sense. OK, enough for now. Slau On Jul 7, 2010, at 7:20 PM, Karen Lewellen wrote: > why thank you! > I hope you took a moment to pat yourself on the back, you have worked long > and hard for this. > > For those who have used it already though specifically with digi 002 or 003, > especially those who were hold overs from the os 9 days, > What do we lose? > Slau already said that they are not even mentioning this access as a feature, > and it is far from 100%, but do you gain more then you had in the prior > accessible structure? > Karen > On Wed, 7 Jul 2010, Slau Halatyn wrote: > >> Hi Karen, >> >> Avid doesn't do public beta cycles. This is an update to the commercial >> release of Pro Tools 8. The current version is now 8.0.4 and it's accessible >> with VoiceOver. >> >> Best, >> >> Slau >> >> On Jul 7, 2010, at 6:25 PM, Karen Lewellen wrote: >> >>> is this another beta edition? >>> Karen >>> >>> On Wed, 7 Jul 2010, Slau Halatyn wrote: >>> >>>> http://secure.digidesign.com/services/avid/kb/downloads.cfm?digiArticleId=41974&localeCode=en >>>> >>>> >>>> >> >>
