Re: Possible FloTools keystroke conflict
Hello, If you are using a physical 2 button mouse you can just right click, no need to hold down control. If you are using a trackpad or a one button apple mouse, then you can hold down control when you do a regular mouse click. Regarding the menu disappearing, in those cases in other apps what I found works is to turn on quick nav then while still holding the mouse down you can use up and down arrows to read the menu items with VO. > On May 17, 2017, at 9:37 AM, Peter Bosherwrote: > > Hi again All, > > > So I tried the Oreo Monster's suggestion. When I hold down control and > right click the physical mouse, VO speaks "Menu, four items, loop audition > ...". but two questions then arise: how do I even access that menu? it > disappears when I release the mouse button, so I can't cursor up and down in > the menu. > > > Second, that menu is probably a context menu for the audition button, rather > than for the highlighted file, so the problem remains, how to action a file > that I'm auditioning with up/down arrow? > > > Perhaps there is no other way than counting as you go, and then returning > with the VO cursor. Can anybody try to replicate this process and see > whether you find a foolproof method. I feel like foolproof is the operative > word here, but the hoops we have to jump through ... > > > Best, > > > Peter > > > > On 16/05/2017 14:27, Slau Halatyn wrote: >> Hi Peter, >> OK, that makes more sense. The contextual menu approach might be helpful >> but, if anything you wish to do involves clicking or dragging, the problem >> will be that lists of files might not necessarily scroll and thus VoiceOver >> can be focused on an item that is beyond the boundaries of the workspace's >> window. I know the Page Up and Down keys do work in workspace windows. The >> trouble is knowing whether something is truly in view. This is one of the >> issues I'll be working on shortly with Avid among other things. Keep us >> posted on your progress. >> >> Slau >> >>> On May 16, 2017, at 9:18 AM, Peter Bosher >>> wrote: >>> >>> Hi Slau, and thanks to you and others for replies so far. >>> >>> >>> First, to clarify, I do actually want to route the VO cursor to the >>> keyboard cursor, so sorry if I added confusion to an already hard to >>> explain operation. >>> >>> >>> Second, the import file workaround won't do what I wanted, because as >>> somebody else pointed out, the WorkSpace is the only method which serches >>> through files on all meta-data and across many folders. >>> >>> >>> Thirdly, I'll try the OreoMonster's right-click idea and report back. >>> >>> >>> Fourthly, here's one more try at explaining the scenario. >>> >>> >>> After searching for, say, heavy rain, or whatever it might be, I have maybe >>> a hundred results from a large effects library. If I press 'audition', >>> then I can down arrow, and quickly hear the start of each file. But, when >>> I find one I need, I want to route the VO-cursor to it, so that I can use >>> VO-shift-M, which then lets me either spot it to the edit cursor, or reveal >>> it in finder. At the moment, I have to try to count down the list, and >>> then re-locate it with the VO-cursor. >>> >>> >>> The right-click method may do the trick and I'll try it ASAP, but if >>> anybody knows a simpler reliable way, please do say. >>> >>> >>> Best, >>> >>> >>> Peter >>> >>> >>> >>> >>> >>> On 15/05/2017 20:09, Slau Halatyn wrote: Hi Peter, The key combination you mention is not used by Flo Tools but, more importantly, what that combination does is the opposite of what you're saying you're trying to do. It routes VoiceOver to the keyboard focused item rather than the other way around. Hope that clears things up. Slau > On May 15, 2017, at 1:02 PM, Peter Bosher > wrote: > > Hi All, > > > I'm not sure whether this is a FloTools keystroke conflict, but in my > continuing fight to tame the workspace, which I'll explain below in case > anyone can help further, I need to route the highlight cursor to the VO > cursor. The keystroke for this should be VO-shift-F4, but when I press > that VO speaks "presets", and the routing doesn't happen. > > > Be that as it may, I've been trying for months now to find a really good > workflow for auditioning files from the workspace window. Thanks to > your suggestions so far, I'm further on than I was, so using hot-spots > helps a lot, but still, when I have a hundred or more files to audition, > what I'm trying to do is quickly hear the beginning of each file whilst > arrowing down. This works, but when I then find a file I want to use, I > can't easily use the context-menu to 'reveal in finder' for example, > because the VO-cursor doesn't follow
Re: Possible FloTools keystroke conflict
Hi again All, So I tried the Oreo Monster's suggestion. When I hold down control and right click the physical mouse, VO speaks "Menu, four items, loop audition ...". but two questions then arise: how do I even access that menu? it disappears when I release the mouse button, so I can't cursor up and down in the menu. Second, that menu is probably a context menu for the audition button, rather than for the highlighted file, so the problem remains, how to action a file that I'm auditioning with up/down arrow? Perhaps there is no other way than counting as you go, and then returning with the VO cursor. Can anybody try to replicate this process and see whether you find a foolproof method. I feel like foolproof is the operative word here, but the hoops we have to jump through ... Best, Peter On 16/05/2017 14:27, Slau Halatyn wrote: Hi Peter, OK, that makes more sense. The contextual menu approach might be helpful but, if anything you wish to do involves clicking or dragging, the problem will be that lists of files might not necessarily scroll and thus VoiceOver can be focused on an item that is beyond the boundaries of the workspace's window. I know the Page Up and Down keys do work in workspace windows. The trouble is knowing whether something is truly in view. This is one of the issues I'll be working on shortly with Avid among other things. Keep us posted on your progress. Slau On May 16, 2017, at 9:18 AM, Peter Bosherwrote: Hi Slau, and thanks to you and others for replies so far. First, to clarify, I do actually want to route the VO cursor to the keyboard cursor, so sorry if I added confusion to an already hard to explain operation. Second, the import file workaround won't do what I wanted, because as somebody else pointed out, the WorkSpace is the only method which serches through files on all meta-data and across many folders. Thirdly, I'll try the OreoMonster's right-click idea and report back. Fourthly, here's one more try at explaining the scenario. After searching for, say, heavy rain, or whatever it might be, I have maybe a hundred results from a large effects library. If I press 'audition', then I can down arrow, and quickly hear the start of each file. But, when I find one I need, I want to route the VO-cursor to it, so that I can use VO-shift-M, which then lets me either spot it to the edit cursor, or reveal it in finder. At the moment, I have to try to count down the list, and then re-locate it with the VO-cursor. The right-click method may do the trick and I'll try it ASAP, but if anybody knows a simpler reliable way, please do say. Best, Peter On 15/05/2017 20:09, Slau Halatyn wrote: Hi Peter, The key combination you mention is not used by Flo Tools but, more importantly, what that combination does is the opposite of what you're saying you're trying to do. It routes VoiceOver to the keyboard focused item rather than the other way around. Hope that clears things up. Slau On May 15, 2017, at 1:02 PM, Peter Bosher wrote: Hi All, I'm not sure whether this is a FloTools keystroke conflict, but in my continuing fight to tame the workspace, which I'll explain below in case anyone can help further, I need to route the highlight cursor to the VO cursor. The keystroke for this should be VO-shift-F4, but when I press that VO speaks "presets", and the routing doesn't happen. Be that as it may, I've been trying for months now to find a really good workflow for auditioning files from the workspace window. Thanks to your suggestions so far, I'm further on than I was, so using hot-spots helps a lot, but still, when I have a hundred or more files to audition, what I'm trying to do is quickly hear the beginning of each file whilst arrowing down. This works, but when I then find a file I want to use, I can't easily use the context-menu to 'reveal in finder' for example, because the VO-cursor doesn't follow the arrowing. That is why I was hoping to route the VO-cursor to the list, but no joy. If you're still with me, then thanks for your patience, and can you suggest any work-around or method to make this process more productive? Best, Peter -- 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/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 ptaccess+unsubscr...@googlegroups.com. 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
Re: Possible FloTools keystroke conflict
Hi Peter, OK, that makes more sense. The contextual menu approach might be helpful but, if anything you wish to do involves clicking or dragging, the problem will be that lists of files might not necessarily scroll and thus VoiceOver can be focused on an item that is beyond the boundaries of the workspace's window. I know the Page Up and Down keys do work in workspace windows. The trouble is knowing whether something is truly in view. This is one of the issues I'll be working on shortly with Avid among other things. Keep us posted on your progress. Slau > On May 16, 2017, at 9:18 AM, Peter Bosherwrote: > > Hi Slau, and thanks to you and others for replies so far. > > > First, to clarify, I do actually want to route the VO cursor to the keyboard > cursor, so sorry if I added confusion to an already hard to explain operation. > > > Second, the import file workaround won't do what I wanted, because as > somebody else pointed out, the WorkSpace is the only method which serches > through files on all meta-data and across many folders. > > > Thirdly, I'll try the OreoMonster's right-click idea and report back. > > > Fourthly, here's one more try at explaining the scenario. > > > After searching for, say, heavy rain, or whatever it might be, I have maybe a > hundred results from a large effects library. If I press 'audition', then I > can down arrow, and quickly hear the start of each file. But, when I find > one I need, I want to route the VO-cursor to it, so that I can use > VO-shift-M, which then lets me either spot it to the edit cursor, or reveal > it in finder. At the moment, I have to try to count down the list, and then > re-locate it with the VO-cursor. > > > The right-click method may do the trick and I'll try it ASAP, but if anybody > knows a simpler reliable way, please do say. > > > Best, > > > Peter > > > > > > On 15/05/2017 20:09, Slau Halatyn wrote: >> Hi Peter, >> The key combination you mention is not used by Flo Tools but, more >> importantly, what that combination does is the opposite of what you're >> saying you're trying to do. It routes VoiceOver to the keyboard focused item >> rather than the other way around. Hope that clears things up. >> Slau >> >>> On May 15, 2017, at 1:02 PM, Peter Bosher >>> wrote: >>> >>> Hi All, >>> >>> >>> I'm not sure whether this is a FloTools keystroke conflict, but in my >>> continuing fight to tame the workspace, which I'll explain below in case >>> anyone can help further, I need to route the highlight cursor to the VO >>> cursor. The keystroke for this should be VO-shift-F4, but when I press that >>> VO speaks "presets", and the routing doesn't happen. >>> >>> >>> Be that as it may, I've been trying for months now to find a really good >>> workflow for auditioning files from the workspace window. Thanks to your >>> suggestions so far, I'm further on than I was, so using hot-spots helps a >>> lot, but still, when I have a hundred or more files to audition, what I'm >>> trying to do is quickly hear the beginning of each file whilst arrowing >>> down. This works, but when I then find a file I want to use, I can't easily >>> use the context-menu to 'reveal in finder' for example, because the >>> VO-cursor doesn't follow the arrowing. That is why I was hoping to route >>> the VO-cursor to the list, but no joy. >>> >>> >>> If you're still with me, then thanks for your patience, and can you suggest >>> any work-around or method to make this process more productive? >>> >>> >>> Best, >>> >>> >>> Peter >>> >>> >>> -- >>> 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/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 ptaccess+unsubscr...@googlegroups.com. > 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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Possible FloTools keystroke conflict
Hi Slau, and thanks to you and others for replies so far. First, to clarify, I do actually want to route the VO cursor to the keyboard cursor, so sorry if I added confusion to an already hard to explain operation. Second, the import file workaround won't do what I wanted, because as somebody else pointed out, the WorkSpace is the only method which serches through files on all meta-data and across many folders. Thirdly, I'll try the OreoMonster's right-click idea and report back. Fourthly, here's one more try at explaining the scenario. After searching for, say, heavy rain, or whatever it might be, I have maybe a hundred results from a large effects library. If I press 'audition', then I can down arrow, and quickly hear the start of each file. But, when I find one I need, I want to route the VO-cursor to it, so that I can use VO-shift-M, which then lets me either spot it to the edit cursor, or reveal it in finder. At the moment, I have to try to count down the list, and then re-locate it with the VO-cursor. The right-click method may do the trick and I'll try it ASAP, but if anybody knows a simpler reliable way, please do say. Best, Peter On 15/05/2017 20:09, Slau Halatyn wrote: Hi Peter, The key combination you mention is not used by Flo Tools but, more importantly, what that combination does is the opposite of what you're saying you're trying to do. It routes VoiceOver to the keyboard focused item rather than the other way around. Hope that clears things up. Slau On May 15, 2017, at 1:02 PM, Peter Bosherwrote: Hi All, I'm not sure whether this is a FloTools keystroke conflict, but in my continuing fight to tame the workspace, which I'll explain below in case anyone can help further, I need to route the highlight cursor to the VO cursor. The keystroke for this should be VO-shift-F4, but when I press that VO speaks "presets", and the routing doesn't happen. Be that as it may, I've been trying for months now to find a really good workflow for auditioning files from the workspace window. Thanks to your suggestions so far, I'm further on than I was, so using hot-spots helps a lot, but still, when I have a hundred or more files to audition, what I'm trying to do is quickly hear the beginning of each file whilst arrowing down. This works, but when I then find a file I want to use, I can't easily use the context-menu to 'reveal in finder' for example, because the VO-cursor doesn't follow the arrowing. That is why I was hoping to route the VO-cursor to the list, but no joy. If you're still with me, then thanks for your patience, and can you suggest any work-around or method to make this process more productive? Best, Peter -- 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/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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Possible FloTools keystroke conflict
Hi Peter, The key combination you mention is not used by Flo Tools but, more importantly, what that combination does is the opposite of what you're saying you're trying to do. It routes VoiceOver to the keyboard focused item rather than the other way around. Hope that clears things up. Slau > On May 15, 2017, at 1:02 PM, Peter Bosherwrote: > > Hi All, > > > I'm not sure whether this is a FloTools keystroke conflict, but in my > continuing fight to tame the workspace, which I'll explain below in case > anyone can help further, I need to route the highlight cursor to the VO > cursor. The keystroke for this should be VO-shift-F4, but when I press that > VO speaks "presets", and the routing doesn't happen. > > > Be that as it may, I've been trying for months now to find a really good > workflow for auditioning files from the workspace window. Thanks to your > suggestions so far, I'm further on than I was, so using hot-spots helps a > lot, but still, when I have a hundred or more files to audition, what I'm > trying to do is quickly hear the beginning of each file whilst arrowing down. > This works, but when I then find a file I want to use, I can't easily use the > context-menu to 'reveal in finder' for example, because the VO-cursor doesn't > follow the arrowing. That is why I was hoping to route the VO-cursor to the > list, but no joy. > > > If you're still with me, then thanks for your patience, and can you suggest > any work-around or method to make this process more productive? > > > Best, > > > Peter > > > -- > 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/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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Possible FloTools keystroke conflict
In VO settings under the navigation category, set mouse pointer to follow VO cursor, (its set to ignore VO cursor by default). Then in The workspace when you find a file you want to import try Holding down control while clicking the mouse to bring up the standard right click menu. the > On May 15, 2017, at 1:02 PM, Peter Bosherwrote: > > Hi All, > > > I'm not sure whether this is a FloTools keystroke conflict, but in my > continuing fight to tame the workspace, which I'll explain below in case > anyone can help further, I need to route the highlight cursor to the VO > cursor. The keystroke for this should be VO-shift-F4, but when I press that > VO speaks "presets", and the routing doesn't happen. > > > Be that as it may, I've been trying for months now to find a really good > workflow for auditioning files from the workspace window. Thanks to your > suggestions so far, I'm further on than I was, so using hot-spots helps a > lot, but still, when I have a hundred or more files to audition, what I'm > trying to do is quickly hear the beginning of each file whilst arrowing down. > This works, but when I then find a file I want to use, I can't easily use the > context-menu to 'reveal in finder' for example, because the VO-cursor doesn't > follow the arrowing. That is why I was hoping to route the VO-cursor to the > list, but no joy. > > > If you're still with me, then thanks for your patience, and can you suggest > any work-around or method to make this process more productive? > > > Best, > > > Peter > > > -- > 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/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 ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Possible FloTools keystroke conflict
Hi Peter, may I suggest a different work around? You can go to import which is (Command, Shift I) then navigate to the folder you're files are in. Assuming they're all in one folder use (VO Home) to go to the top of the list or use first letter navigation for a specific file. You can then use the arrows to quickly scroll through the intros of the files as you've been doing. When you find the file you want simply press enter, Command W and enter twice. The file will now be placed on its own track provided you haven't changed any defaults. All you have to do is press (Command Shift I) again to go right back to where you were. I once had over 2000 files to go through for beds and the client wasn't sure where anything was. I had 50 correct files in the session in less than 5 minutes going through all 2000 intros. -- 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/d/optout.