Hi David, The problem exists across Pro Tools in general. There's really no difference between regular Pro Tools and HD. It's the same software. Certain features only appear under certain conditions but it's the same installer, same code.
HTH, Slau On Nov 13, 2012, at 5:43 PM, David Ingram wrote: > Do these problems only exist with the standard version of pro tools and the > os and voice over? Does this also happen with the hd version of pro tools? > What would happen if the hd version of pro tools was used and if mountain > lion was used with voice over. maybe if the hd version of pro tools doesn't > have this problem and it seems that more people are using the version that is > not hd then this should be fixed all across the board if you don't mind me > saying so. I don't want to spend more money on a product that doesn't > properly work with voice over? > ----- Original Message ----- From: "Slau Halatyn" <[email protected]> > To: <[email protected]> > Sent: Tuesday, November 13, 2012 2:26 PM > Subject: Re: For Slau and others: Fw: Problem with accessibility in Mountain > Lion > > > Chris, > > Again, Avid is not aware of the issue, it's someone at Apple itself saying > it's a VoiceOver issue. That, however, is irrelevant. Don't even bring up > that point. Just keep coming back with the facts. I've supplied the link > earlier but here it is again: > http://avid.force.com/pkb/articles/en_US/Download/Pro-Tools-10-3-2-Downloads > This proves that Pro Tools 10.3.2 supports Mountain Lion and they've done the > necessary work. Don't relent. Just keep coming back with it. Yes, we'll all > get canned responses but keep going at it. > > Slau > > On Nov 13, 2012, at 3:17 PM, Christopher-Mark Gilland wrote: > >> Hello. >> >> I e-mailed Apple Accessibility regarding the issue with the counters, etc. >> not properly reading, as Slau had suggested that all of us do. Below is >> their response. In my humble opinion, though I don't want to be the one to >> shoot the black horse, this is so damn typical of them. I'm so sick of >> always hearing the same templated script: "Oh, it's not our falt. The >> developer needs to work harder." It's never Apple's falt. Maybe I'm just >> real hot as there is another onpgoing accessibility issue totally unrelated >> that they absolutely refuse to cooperate on, but I'm really getting sick and >> tired, I tell you, of them apparently never ever listenning when people like >> us who need accessibility implemented always put the raw meat back on the >> developer. They like thinking they're perfect, and that nothing's ever >> their flaw until proven otherwise. So, that leads me to my question of >> writing this mail: how do we then prove it to them, that in this case, >> they're wrong? I'd trust Slau with this more than I would anyone. If he's >> talked to Avid, and Avid directly says this isn't a P T issue, but more an >> underlying issue of OSX, which based on what I'm hearing elseware, does make >> complete sense, by the way, then I'm gonna be more promed to believe him, >> than someone who's never probably used ProTools a single day of their life. >> >> Sorry for the outburst of frustration. Maybe now I! am the one being >> extremely unfair, but come on! This is ridiculous, I mean let's just be >> realistic here. This is not the first time Apple has refused to help with >> accessibility until we pushed. And who do you think it was back in 2005 >> roughly with OSX 10.4 Tiger, that convinced them to put a screen reader, >> which wound up being Voiceover into the OS directly? Oh sure, there was >> Outspoken before then, and believe me, it worked wonderfully! but, who do >> you think put the fire under their feet to get on the train, if you will? >> That's right! the N? F? B. If it wasn't for them back in the days >> threatenning a lawsuit, now granted, it never came down to that, as Apple >> unwillingly complied, but that's just it, they did it unwillingly, then >> clamed they were committed. I'm not so convinced. >> >> If you wanna know more my reasonnings, this isn't the list for it. Write me >> off list, if you want, and I'll furtyher elaberate. >> >> Anyway, scroll down below my signature, and you'll find their response.Thank >> you kindly, >> >> Thank you kindly. >> Christopher-Mark Gilland. >> Founder of CLG Productions >> >> Blog: >> http://www.clgproductions.org >> >> Podcast: >> http://clgproductions.podhoster.com >> >> E-mail: >> [email protected] >> >> IMessage/Facetime: >> [email protected] >> >> Windows Live Messenger: >> [email protected] >> >> Twitter: >> @gilland_chris >> >> Facebook: >> http://www.facebook.com/christopher.gilland >> >> Skype: >> twinklesfriend2007 >> >> Send me a fax from any standard fax machine: >> 704-697-2069 >> >> Google Voice: (Please use sparingly): >> 980-272-8570 >> >> >> ----- Original Message ----- From: <[email protected]> >> To: <[email protected]> >> Sent: Tuesday, November 13, 2012 12:19 PM >> Subject: Re: Problem with accessibility in Mountain Lion >> >> >> Hello, >> >> Thank you for your email. Apple relies on each application developer to >> properly implement the necessary components into their applications that >> allow VoiceOver to work correctly. Unfortunately AVID has not provided an >> update for ProTools that would allow their software to work correctly with >> VoiceOver in OS X 10.8 Mountain Lion. We recommend that you contact AVID >> directly to provide them feedback on the features you are finding do not >> work. >> >> Apple Accessibility >> >> Your original message: >> >> Hello. >> >> Though I understand that this issue may come across as being something you >> all do not directly support, I genuinely hope and urge you guys here at >> Apple, to at least look into the situation as best you can. I am a >> professional musician who has been relying very heavily now for at least 4 >> years on the use of ProTools from Avid in my home recording environment. >> Recently, I've expanded and now have a full fledged recording studio which I >> bring clients to every day of the week, Monday through Friday. Regarding >> accessibility, here is the situation. After much research, and after much >> working with Avid directly, all of us... myself and Avid Engineering both >> have come to the following conclusion. >> >> Under Snow Leopard and Leopard, Pro Tools' counter displays read fine but >> under Mountain Lion, they're simply identified by labels like, "Main >> Counter, numeric text," "Edit Start Time, numeric text," etc. Under Snow >> Leopard and Leopard, edit modes and tool selections are spoken properly by >> VoiceOver but, under Mountain Lion, there's no way to tell what edit mode is >> selected or which tool is selected. >> >> We know that a programmer at Avid followed Apple's own guidelines and we >> know that the exact same version of Pro Tools behaves fine under snow >> Leopard and Leopard but not so under Mountain Lion. >> >> I'd appreciate very greatly and urge you all very strongly to look into this >> matter and try to figure out why this issue is occuring. It is going to >> make the music industry for blind individuals like myself become very very >> difficult, if not impossible if we cannot find a way to get this problem >> resolved in a timely manor. >> >> Thank you kindly, >> >> Christopher-Mark Gilland. >> Founder of CLG Productions >> >> Blog: >> http://www.clgproductions.org >> >> Podcast: >> http://clgproductions.podhoster.com >> >> E-mail: >> [email protected] >> >> IMessage/Facetime: >> [email protected] >> >> Windows Live Messenger: >> [email protected] >> >> Twitter: >> @gilland_chris >> >> Facebook: >> http://www.facebook.com/christopher.gilland >> >> Skype: >> twinklesfriend2007 >> >> Send me a fax from any standard fax machine: >> 704-697-2069 >> >> Google Voice: (Please use sparingly): >> 980-272-8570 >> >> >> >
