Well, I finally got my pro tools 11.1 authorized with avid, with the help of my Sweetwater sales guy. And with a bit of experimentation, I actually was able to transfer the key onto my iLok with the license manager on Windows. If you use OCR in jaws or NVDA, you can sort of figure out where you are. It’s a bit better with Jaws. If you right click on the key you want to transfer, which will appear if you selectg “all my licenses” from the license menu, you will get a drop down menu. When you select activate, you need to highlight the destination iLOk and then press OK. YOu will get another confirmation and you need to press OK again on that and you’ll see “Processing.” Finally it should say successful. BUt it is not by any definition accessible, I just had enough tenacity to stick with it and I was nervous that I might do something wrong that would deactivate my key or something. So Pace, if you’re monitoring this list, this doesn’t mean you’re off the hook. On the mac it is totally invisible to us. GOrd On Jan 10, 2014, at 2:27 PM, Slau Halatyn <slauhala...@gmail.com> wrote:
> Hi Matt, > > It is a bit odd that none of the parameters are visible in that particular > plug-in under 10. I wouldn't have guessed at that result. Well, for now, I > suppose one could use the 4-band eQ which appears to be readable. Of course, > under version 11.1, the 7-band EQ is completely readable. Go figure… :) > > Slau > > On Jan 10, 2014, at 7:13 AM, matt diemert <mcdiem...@gmail.com> wrote: > >> Hi Slau, >> In a previous message in this thread, you mentioned that the AAX plugs >> were some what accessible in 10.3.8. I had an instance last night >> working on someones rig that was running this build, and I just pulled >> up the 7 band EQ that is standard kit in Pro Tools. When navigating >> the plug, voice over stopped at the automation settings button and >> would not go down any further in to the actual EQ settings. Was I >> doing something wrong, or, are the AAX plugs hit and miss in the >> 10.3.8 build. It's not a big deal as I can take everything home when >> we're done working, but it'd be nice to throw some basic EQ in after >> tracking something. >> Thanks. >> >> On 1/8/14, Chi Kim <chigook...@hotmail.com> wrote: >>> Thanks Slau, >>> Glad that the aax is accessible with pt10 to a certain degree. It's time >>> for me to convince school to update to Mavericks along with pt11! >>> >>> Chi >>> >>> On 1/6/2014 1:16 PM, Slau Halatyn wrote: >>>> Hi Chi, >>>> >>>> OK, I've had a chance to review and refresh my memory of the issues of 10 >>>> versus 11. Upon review, version 11 really contains all of the >>>> improvements. The only substantive improvement that version 10 has is >>>> mainly the accessibility of the counters and AAX plug-ins. Regarding the >>>> counters, that could quite possibly be because of Mavericks versus >>>> Mountain Lion. It's been 8 months since I tried version 11 on Mountain >>>> Lion and there were a load of problems, not the least of which was the >>>> counter display issue. So, with version 10.3.8, the counters are readable >>>> but, whether that's because of Mavericks or not, I can't say for sure as >>>> I've been on Mavericks since the bulk of the accessibility work started. >>>> >>>> regarding plug-ins, the AAX plug-ins are accessible for the most part in >>>> version 10 but not in the same way as they are in 11. In a pinch, I was >>>> able to use some plug-ins for an emergency after my beta license for 11 >>>> ran out. iLok License Manager not yet being accessible, my only choice at >>>> the time was to use version 10 for which I had purchased a license back >>>> before the License Manager was introduced. >>>> >>>> So, with those two mentionable improvements but not much else that I can >>>> tell at a cursory glance, the focus is really on 11. >>>> >>>> Hope that helps, >>>> >>>> Slau >>>> >>>> On Jan 6, 2014, at 12:37 PM, Chi Kim <chigook...@hotmail.com> wrote: >>>> >>>>> Hi Slau, >>>>> >>>>> Thanks for the explanation. >>>>> I was just wondering how much accessibility improvement in 11 was >>>>> included in 10.3.8 as well. >>>>> Regardless, I'm looking forward to upgrading to 11! >>>>> >>>>> Chi >>>>> >>>>> On 1/5/2014 12:27 PM, Slau Halatyn wrote: >>>>>> Hi Chi, >>>>>> >>>>>> Yes, there is a difference. The focus on accessibility in the future >>>>>> will be on version 11. There were improvements to 10.3.8 for sure but it >>>>>> was not the primary concentration. From now on, any updates to version >>>>>> 10 will be general maintenance and will not likely include significant >>>>>> improvements to accessibility. Much like bug fixes in other software, >>>>>> it's not expected that the developer will go back to previous versions >>>>>> of the software to fix the problem. The point is that it's fixed in the >>>>>> new version and that's it. In this situation, however, there are still >>>>>> people needing to use version 10 during the transition from 32 to 64 bit >>>>>> and while plug-in developers are pulling up the rear. I was surprised at >>>>>> how much was actually done in 10.3.8 to begin with. >>>>>> >>>>>> BTW, one task that is still only doable in 10 and not 11 is to create a >>>>>> custom nudge value. In 11, a VoiceOver user can only choose from the >>>>>> default values whereas in 10 they can click a button, type a value and >>>>>> be done. In neither version is the numeric value visible. Surely, it'll >>>>>> be fixed in 11 at some point but I doubt it'll be addressed in 10. >>>>>> >>>>>> Best, >>>>>> >>>>>> Slau >>>>>> >>>>>> >>>>>> On Jan 5, 2014, at 10:53 AM, Chi Kim <chigook...@hotmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> First Slau, congratulation on this milestone! Thank you for making this >>>>>>> happen! >>>>>>> Is there any difference in accessibility between pt10.3.8 vs pt11.1? >>>>>>> Thanks, >>>>>>> >>>>>>> Chi >>>>>>> >>>>>>> -- >>>>>>> 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. >>> >> >> >> -- >> Warm Regards: >> Matt Diemert >> 330-980-0046 >> >> -- >> 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.
