Flo Tools conflicts

53 views
Skip to first unread message

Devil Monkey

unread,
Oct 2, 2020, 1:40:25 AM10/2/20
to Pro Tools Accessibility
Hi!

I'm having trouble with what maybe is a conflict in settings somewhere between accessibility & Flo Tools but I can't be entirely sure.

Macros in Flo Tools appear to turn themselves off in some instances or appear to have no functionality at all. I've emailed Keyboard maestro who have sent me back to Flo Tools.

Additionally, when Flo Tools is engaged some of the usual keyboard functions appear to no longer work eg space bar no longer operates as start/stop & I have to use the transport controls on the control surface.

Any tips on correct settings would be greatly appreciated.

I am running latest Pro Tools on a Mac with Mojave 10.14.6

Have a great weekend

Tom Hessels

unread,
Oct 2, 2020, 7:56:27 AM10/2/20
to ptac...@googlegroups.com

Hi,

I have the same problem: when starting pro tools sometimes Flo tools dosn’t work at all.

When i take a look in Keyboard maestro i see that all flo tools macros are disabled. When i do a reinstalll of flo tools every thing works fine again.

 

Tom.

--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/a63a3056-a243-4b01-9ac0-f51f05563e85o%40googlegroups.com.

Martin (Punky) Sopart

unread,
Oct 2, 2020, 8:36:33 AM10/2/20
to ptac...@googlegroups.com

Hello!

 

Did you check the option that the Keyboard Maestro Engine is loaded at start—up?

 

Best! / Martin

CHUCK REICHEL

unread,
Oct 2, 2020, 10:33:19 AM10/2/20
to ptac...@googlegroups.com
Hi guys,

If you have to get a  project out the door to get paid just use VoiceOver and turn off "FTools"! :)
I never run in to this problem as I don't use Ftools at all.
Keeps life simpler for me! ;)
YMMV
Chuck
"God does not play dice with the universe"
"Albert Einstein’


mcdi...@gmail.com

unread,
Oct 2, 2020, 10:40:12 AM10/2/20
to ptac...@googlegroups.com

Also, did you turn the inspector on after your session loads.  This is the forward slash key to the left of right shift.

mcdi...@gmail.com

unread,
Oct 2, 2020, 10:43:39 AM10/2/20
to ptac...@googlegroups.com

Chuck, While I held off on using flo tools for several years,  Having used it for the past year and a half,  speed, and efficiency is unmatched even with standard VO, and pro tools keystrokes!   As someone who writes Jaws scripting for a living, this is the best and most well thought out  third party “scripts” I’ve encountered.

Martin (Punky) Sopart

unread,
Oct 2, 2020, 10:46:05 AM10/2/20
to ptac...@googlegroups.com

Good words…

 

From: ptac...@googlegroups.com <ptac...@googlegroups.com> On Behalf Of mcdi...@gmail.com
Sent: Friday, October 2, 2020 4:44 PM
To: ptac...@googlegroups.com
Subject: RE: Flo Tools conflicts

 

Chuck, While I held off on using flo tools for several years,  Having used it for the past year and a half,  speed, and efficiency is unmatched even with standard VO, and pro tools keystrokes!   As someone who writes Jaws scripting for a living, this is the best and most well thought out  third party “scripts” I’ve encountered.

Slau Halatyn

unread,
Oct 2, 2020, 12:08:23 PM10/2/20
to PTAccess List
A couple of things:
If you're having trouble with the space Bar not starting the transport, your problem has absolutely nothing to do with Flo Tools. There's no Flo Tools command that involves the Space bar. You need to follow all the steps that avid recommends for setting up Pro Tools to operate correctly and you further need to follow steps to configure VoiceOver and Pro Tools to work in the best possible way for you as a blind user. If you need a reference for that, here's a document that spells it all out:
Pre-Flight Checklist for Pro Tools, Mac OS and VoiceOver .html

Slau Halatyn

unread,
Oct 2, 2020, 12:22:04 PM10/2/20
to PTAccess List
Thank you, Matt, for your words of support. Years ago, I created a filter to send Chuck's messages directly to my Trash folder for various reasons and, as a result, I never see his messages unless another user responds to him and I can then see what the nonsense is about.

Speaking of JAWs and scripts, there was a time when I was strongly opposed to the idea of an essentially alternate user interface that didn't resemble what a sighted user experiences as it related to programs like Sonar. When Rocco and Chi approached me with what eventually became Flo Tools, I realized that such a scenario wasn't the case. Yes, there was the necessity of using alternate keystokes for certain things in some cases but there's no avoiding such things, as you well know. well, years later, most blind Pro Tools users are using Flo Tools and recognize its value for increased efficiency. There's no doubt that using Flo Tools is way more efficient than using Pro Tools with VoiceOver alone. Of that, there is absolutely no question. Those who stubbornly refuse to accept that deserve the inefficiency and wasted time they incur but, hey, that's their choice. 

Cheers,
Slau

James

unread,
Oct 2, 2020, 5:04:24 PM10/2/20
to ptac...@googlegroups.com
Wow!

Thanks for the list of tasks Slau! Greatly appreciated mate! Looking forward to getting this setup!

Sent from my iPhone

On 3 Oct 2020, at 2:08 am, Slau Halatyn <slauh...@gmail.com> wrote:

A couple of things:
If you're having trouble with the space Bar not starting the transport, your problem has absolutely nothing to do with Flo Tools. There's no Flo Tools command that involves the Space bar. You need to follow all the steps that avid recommends for setting up Pro Tools to operate correctly and you further need to follow steps to configure VoiceOver and Pro Tools to work in the best possible way for you as a blind user. If you need a reference for that, here's a document that spells it all 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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/FC83F45D-2F3B-466E-9FB6-9F90C82E3F4C%40gmail.com.
<Pre-Flight Checklist for Pro Tools, Mac OS and VoiceOver .html>
Further, some macros and macro groups in Keyboard Maestro are disabled by default or as a matter of course—that's the way it works. All macros and all macro groups are not supposed to be on all the time. Much like PT and VoiceOver setup, you need to follow the setup instructions carefully to make sure Flo Tools will work properly. With all of these things, there's also a bunch of settings in Security and Privacy that need to be enabled. Whatever's not covered in documentation, you can ask about here.
HTH,
Slau


On Oct 2, 2020, at 1:40 AM, Devil Monkey <devilmon...@gmail.com> wrote:

Hi!

I'm having trouble with what maybe is a conflict in settings somewhere between accessibility & Flo Tools but I can't be entirely sure.

Macros in Flo Tools appear to turn themselves off in some instances or appear to have no functionality at all. I've emailed Keyboard maestro who have sent me back to Flo Tools.

Additionally, when Flo Tools is engaged some of the usual keyboard functions appear to no longer work eg space bar no longer operates as start/stop & I have to use the transport controls on the control surface.

Any tips on correct settings would be greatly appreciated.

I am running latest Pro Tools on a Mac with Mojave 10.14.6

Have a great weekend

--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/a63a3056-a243-4b01-9ac0-f51f05563e85o%40googlegroups.com.

--
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+u...@googlegroups.com.

Rory McDonald

unread,
Oct 3, 2020, 1:30:35 PM10/3/20
to ptac...@googlegroups.com
Figured I'd add to what Matt and others have said. I fail to see how interacting with a track on the channel strip, then going right about 5 or 6 times to get to the record enable button and then stopping interacting is faster than simply double tapping R to arm said track, but to each there own I guess...

Rory

On Oct 2, 2020, at 5:04 PM, James <devilmon...@gmail.com> wrote:

Wow!

Slau Halatyn

unread,
Oct 3, 2020, 5:09:15 PM10/3/20
to PTAccess List
To be fair, one can simply use Control+p or semicolon to select a track and press Shift R to arm it. However, the process of verifying which of many non-contiguous tracks are either selected or record enabled is laughably tedious without Flo Tools. Naturally, the best case scenario is to be intimately familiar with Pro Tools and Flo Tools alike.


James

unread,
Oct 9, 2020, 2:40:06 AM10/9/20
to ptac...@googlegroups.com
Okay. I’ve followed all the instructions but some things don’t seem to be working eg double-tapping T for the track menu. No result. I noticed there was a comment regarding some macros not needing to be enabled. Specifically which ones?

Sent from my iPhone

On 4 Oct 2020, at 8:09 am, Slau Halatyn <slauh...@gmail.com> wrote:

To be fair, one can simply use Control+p or semicolon to select a track and press Shift R to arm it. However, the process of verifying which of many non-contiguous tracks are either selected or record enabled is laughably tedious without Flo Tools. Naturally, the best case scenario is to be intimately familiar with Pro Tools and Flo Tools alike.

James

unread,
Oct 9, 2020, 2:47:12 AM10/9/20
to ptac...@googlegroups.com
I’m running latest Pro Tools, Keyboard Maestro & Flo Tools. I’m using a Mac Mini (2012) which runs macOS Mojave 10.14.6 if that’s useful for you.

Regards,

James

Sent from my iPhone

On 4 Oct 2020, at 8:09 am, Slau Halatyn <slauh...@gmail.com> wrote:

To be fair, one can simply use Control+p or semicolon to select a track and press Shift R to arm it. However, the process of verifying which of many non-contiguous tracks are either selected or record enabled is laughably tedious without Flo Tools. Naturally, the best case scenario is to be intimately familiar with Pro Tools and Flo Tools alike.

Martin (Punky) Sopart

unread,
Oct 9, 2020, 3:59:11 AM10/9/20
to ptac...@googlegroups.com

Hello James!

 

Did you tryed other double tapping commands with success?

Maybe you have to change the tapping speed in the Flo Tools prefs.

 

Best! / Martin

 

 

From: ptac...@googlegroups.com <ptac...@googlegroups.com> On Behalf Of James
Sent: Friday, October 9, 2020 8:47 AM
To: ptac...@googlegroups.com
Subject: Re: Flo Tools conflicts

 

I’m running latest Pro Tools, Keyboard Maestro & Flo Tools. I’m using a Mac Mini (2012) which runs macOS Mojave 10.14.6 if that’s useful for you.

James

unread,
Oct 9, 2020, 4:08:06 AM10/9/20
to ptac...@googlegroups.com
Hi Martin!

Thanks for your reply mate! Yep. Double tapped for no result but didn’t know that I could set tapping speed in Flo Tools prefs. I’ll give that a shot. Thanks dude. Stay safe!

Best,

James

Sent from my iPhone

On 9 Oct 2020, at 6:59 pm, Martin (Punky) Sopart <ma...@cakewalker.de> wrote:


--
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+u...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages