Hi Martin, OK, I caught a mistake in one of the numbers. The horizontal coordinate for the Output field says 83 in the text file but it should have been 183. I simply neglected to select the entire number while copying into the document. It should work now. Let me explain something, however. The text file with -1.txt is just an alternative to show that navigation of the parameters can be virtually the same as with voiceOver. The thing is, this Plug-In View includes all of the parameters that are exposed to VoiceOver but there's no need to necessarily map coordinates for things like a polarity invert because it's a simple on/off toggle and VoiceOver does a fine job of just toggling on and off. It's the edit fields we aimed to map so that, instead of moving in tiny increments, one could type a value. So, if you look inside the text file, you'll see that the parameters that haven't been mapped say 0,0 on the line where the parameter name appears. While navigating through Plug-In View, if you're in doubt as to whether something is mapped with a coordinate, with the Mouse group enabled, press Command+Option+Shift+c to have Flo Tools speak the coordinates. If it says "0,0," then you know the mouse pointer is at the top left corner of the Plug-In window rather than somewhere within the area with parameter controls. Hopefully, that makes sense. I've updated the text file in the drop Box or, if you're feeling adventurous, you can go ahead and add a 1 in front of the 83 in the line that says "Output." Cheers, Slau
> On Oct 13, 2017, at 10:07 AM, Martin (Punky) Sopart <[email protected]> > wrote: > > Hi Slau! > > Thanks for your explanation. > And the Command+J > > Going that way brings me to exact the same path.. > Sorry for sending the German words before. > > Harddrive, Users, Me, Library, Application Support, Flo Tools, Plug-in Views. > > Same result. > The Input level works, the Output level with no reaction, and the Phase > invert brings me back to the Edit Whindow. > > Best! / Martin >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Slau Halatyn >> Sent: Friday, October 13, 2017 3:54 PM >> To: [email protected] >> Subject: Re: VoiceOver slow with sPT stock EQ and Compressor/gate >> >> Hi Martin, >> No, wrong folder. From Finder, open your Home folder with >> command+Shift+h. Press Command+j to open the View preference and >> check the checkbox at the bottom to show the User Library. Close the >> windows. >> Now, Press Command+Shift+l to open your User Library. Go to the >> Application Support folder, then the Flo Tools folder, then paste the file >> inside the Plug-In Views folder. >> Let me know if that works. >> Slau >> >>> On Oct 13, 2017, at 6:27 AM, Martin (Punky) Sopart <[email protected]> >> wrote: >>> >>> Hi again! >>> >>> Is this the right folder for the txt-files? >>> Macintosh HD ▸ Benutzer ▸ Punky ▸ Library ▸ Application Support ▸ Flo >> Tools ▸ Plug-In Views >>> >>> If so, no success when clicking any parameter. >>> >>> Best! / Martin >>> >>> Am 12.10.2017 um 21:43 schrieb Slau Halatyn <[email protected]>: >>> >>> Hi John, >>> While anything is certainly possible, given that this feature was introduced >>> last year and we've never seen any problems, it's highly unlikely. Try >>> moving the contents of the Plug-In Settings folder to another location >>> temporarily and see if anything is different. Let us know what you >>> experience. >>> Slau >>> >>>> On Oct 12, 2017, at 2:54 PM, John André Lium-Netland >>>> <[email protected]> wrote: >>>> >>>> Hi, >>>> >>>> I experience that VoiceOver gets extremely slow as soon as I open the PT >>>> stock EQ and the compressor/gate plugin windows. As soon as I close >> these >>>> windows, VoiceOver acts as expected. I can open other plugin windows >> with >>>> no such issues at all. >>>> Can Flow Tools cause issues like this? >>>> >>>> Best, >>>> John André >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
