Re: Flo Tools conflicts

2020-10-09 Thread James
8:47 AM > To: ptaccess@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. > > Regards, > > James >

RE: Flo Tools conflicts

2020-10-09 Thread Martin (Punky) Sopart
: 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. Regards, James Sent from my iPhone -- You received this message because you are subscribed to the Google Gr

Re: Flo Tools conflicts

2020-10-09 Thread James
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 wrote: > > To be fair, one can simply use Control+p or semicolon to

Re: Flo Tools conflicts

2020-10-09 Thread James
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

Re: Flo Tools conflicts

2020-10-03 Thread Slau Halatyn
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

Re: Flo Tools conflicts

2020-10-03 Thread Rory McDonald
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

Re: Flo Tools conflicts

2020-10-02 Thread James
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 wrote: > > A couple of things: > If you're having trouble with the space Bar not starting the transport, your > problem has

Re: Flo Tools conflicts

2020-10-02 Thread Slau Halatyn
t: Friday, October 02, 2020 10:33 AM > To: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com> > Subject: Re: Flo Tools conflicts > > Hi guys, > > If you have to get a project out the door to get paid just use VoiceOver and > turn off "FTools"! :) &g

Re: Flo Tools conflicts

2020-10-02 Thread Slau Halatyn
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

RE: Flo Tools conflicts

2020-10-02 Thread Martin (Punky) Sopart
Good words… From: ptaccess@googlegroups.com On Behalf Of mcdiem...@gmail.com Sent: Friday, October 2, 2020 4:44 PM To: ptaccess@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

RE: Flo Tools conflicts

2020-10-02 Thread mcdiemert
party “scripts” I’ve encountered. From: ptaccess@googlegroups.com On Behalf Of CHUCK REICHEL Sent: Friday, October 02, 2020 10:33 AM To: ptaccess@googlegroups.com Subject: Re: Flo Tools conflicts Hi guys, If you have to get a project out the door to get paid just use VoiceOver

RE: Flo Tools conflicts

2020-10-02 Thread mcdiemert
Also, did you turn the inspector on after your session loads. This is the forward slash key to the left of right shift. From: ptaccess@googlegroups.com On Behalf Of Martin (Punky) Sopart Sent: Friday, October 02, 2020 8:37 AM To: ptaccess@googlegroups.com Subject: RE: Flo Tools conflicts

Re: Flo Tools conflicts

2020-10-02 Thread CHUCK REICHEL
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’ On Oct 2, 2020, at

RE: Flo Tools conflicts

2020-10-02 Thread Martin (Punky) Sopart
Hello! Did you check the option that the Keyboard Maestro Engine is loaded at start—up? Best! / Martin From: ptaccess@googlegroups.com On Behalf Of Tom Hessels Sent: Friday, October 2, 2020 1:56 PM To: ptaccess@googlegroups.com Subject: RE: Flo Tools conflicts Hi, I have

RE: Flo Tools conflicts

2020-10-02 Thread Tom Hessels
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. Van: ptaccess@googlegroups.com