There is no w to spek for the entire support team. If someone isn't being clear enough you can ask them for clarification.
On Feb 17, 2014, at 7:44 AM, Nick Gawronski <n...@nickgawronski.com> wrote: > Hi, I agree totally. I meant if they say to click on the blue button that > means nothing to me but if they can tell me what it is called that would be > better. Are they good at explaining things where as I know voiceover I > should be able to follow what they are saying? Nick Gawronski > > Chris Smart <csma...@cogeco.ca> wrote: > >> It's up to you to know your screen reader. (grin) >> >> At 10:28 PM 2/16/2014, you wrote: >>> Avid will never offer VoiceOver support. You'll get support just >>> like any other user but nothing having to do with VoiceOver. If >>> something isn't accessible, that's another issue that can be >>> submitted as a bug. >>> >>> >>> On Feb 16, 2014, at 10:25 PM, TheOreoMonster <monkeypushe...@gmail.com> >>> wrote: >>> >>>> My personal opinion on the matter, so long as the area in pro >>> tools is accessible, then they shouldn't need to know anything >>> about VoiceOver. I believe we should know our Operating System and >>> or screen reader well enough that we can take standard instructions >>> and translate them into things we can do with our screenreader. Yes >>> if they use vague terms then you may have to ask them to specify >>> but we should know how to navigate to a certain screen and click on >>> it without having to get specific VoiceOver instructions. Just my >>> two cents on the matter. >>>> >>>> On Feb 16, 2014, at 8:42 PM, Nick Gawronski <n...@nickgawronski.com> wrote: >>>> >>>>> Hi, How well do the Avid support people know about voiceover if >>> I should have a question on how to do something as I agree having >>> the support contract would be very nice but if they don't know how >>> to do anything with voiceover I would not rather buy it unless they >>> can give a refund if they find out they can't help me? Nick Gawronski >>>>> On 2/15/2014 3:16 PM, Slau Halatyn wrote: >>>>>> I'm not sure but I think there's 90 days of free tech support. >>> That said, when I first started using Pro Tools I signed up for a >>> yearly support contract and I think that was a great investment. It >>> might be worth looking into the current options. >>>>>> >>>>>> Slau >>>>>> >>>>>> On Feb 15, 2014, at 3:55 PM, Krister Ekstrom >>> <kris...@kristersplace.com> wrote: >>>>>> >>>>>>> Hi , i will try contacting Avid technical support hadn't tried >>> doing that. >>>>>>> /Krister >>>>>>> >>>>>>> 15 feb 2014 kl. 21:53 skrev Slau Halatyn <slauhala...@gmail.com>: >>>>>>> >>>>>>>> Hi Krister, >>>>>>>> >>>>>>>> Never heard of that. Have you contacted Avid technical support? >>>>>>>> >>>>>>>> Slau >>>>>>>> >>>>>>>> On Feb 15, 2014, at 6:37 AM, Krister Ekstrom >>> <kris...@kristersplace.com> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> Ever since i installed Pro tools 11.1 on my IMac with 1 TB >>> hard drive and 8 Gb memory i have had a strange thing happening: I >>> quit PT after a session and the crash reporter comes up saying that >>> PT unexpectedly quit. Anyone else had these problems? Can i do >>> something about this? >>>>>>>>> /Krister >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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+unsubscr...@googlegroups.com. >>>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>>> -- >>>>>>>> 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+unsubscr...@googlegroups.com. >>>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>>>> -- >>>>>>> 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+unsubscr...@googlegroups.com. >>>>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>>> -- >>>>> 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+unsubscr...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> -- >>>> 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+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> 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+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- >> 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+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
