Re: Observation - midi event list

[Chi Kim]

The problem is it would be extremely hard to track down this kind of 
things because so many variables.
It  could be because of MacOS, VoiceOver, Keyboard Maestro, Pro Tools, 
AppleScripte Engine, some other processors in your computers, or even 
possibly hardware difference, and so on.
For example, Microsoft Teams kicks the fan really high and drains the 
battery like crazy in some cases on Mac, and it has been a few years 
since literally hundreds of people have been complaining about this all 
over the internet. Several possible solutions have been proposed by 
different people, but Microsoft wasn't able to fix it despite the 
popular demand during Pandemic.

Unfortunately I don't have a bandwidth to tackle this.

100ms delay is not bad when you using it, and it only applies when you 
use the monitor. I think it's a good compromise.


Having said that, let me know if you find something.


Chi


On 2/10/2021 9:31 AM, Martin (Punky) Sopart wrote:

Hello Chi!

So wouldn't it be better to investigate why your system and my two ones react 
so different, before slowing down the macros?

Best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Chi Kim
Sent: Wednesday, February 10, 2021 4:43 AM
To: ptaccess@googlegroups.com
Subject: Re: Observation - midi event list

The temperature did increase, but no, nothing like above 100 degrees. It
went from around 75 to around 85.

Also fan only increased only by like -50 rpm higher, I didn't hear much
difference.

Hopefully the new build works better on your system.


Chi


On 2/9/2021 6:24 AM, Martin (Punky) Sopart wrote:

Hello Chi!

Thanks for helping here...

Did I get you right, that you do not have this temperature behavior on your

system?

Best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Chi Kim
Sent: Monday, February 8, 2021 7:12 PM
To: ptaccess@googlegroups.com
Subject: Re: Observation - midi event list

Hi Martin,


Here's the build with a 100ms delay.

https://github.com/flotools/flotools/archive/master.zip

It's not signed, so you need to bypass the MacOS gatekeeper.


Chi


On 2/8/2021 12:49 PM, Chi Kim wrote:

Hi Martin and Slau,


On my system, temperature rises by about 10 degrees.

Now, the script constantly monitors the control for any change without
breathing.

I could insert a 100ms long breath before every check. Then the
temperature rises by about 5 degrees, but you'll notice 200ms delay
before the speech output.

Would that be acceptable?

Also I guess we need to think about doing the same thing to other
monitors such as plugin monitor, level meter monitor, and so on.


Chi




On 1/19/2021 4:54 AM, Martin (Punky) Sopart wrote:

Hello Slau!

Yes, I can remember something like that when using the Plug-in
Monitor, but not that extreme when doing nothing and watching the

cpu

temperature rises to 100 degrees Celsius.
Maybe the todays faster cpus and memory or the newer versions of
Keyboard Maestro causes that.

Thanks and best! / Martin

-Original Message-
From: ptaccess@googlegroups.com 

On

Behalf Of Slau Halatyn
Sent: Monday, January 18, 2021 10:59 PM
To: PTAccess List 
Subject: Re: Observation - midi event list

Hi Martin,

We’ve changed nothing about that feature so it has probably always

been

the case. In fact, the same thing happens when the Plug-in Monitor is
engaged. Flo Tools is constantly scanning for any changes and the
CPU starts
to rev up it appears. Chi’s going to look into this to see if
there’s anything we
can do to improve the behavior.
slau



On Jan 18, 2021, at 12:59 AM, Martin (Punky) Sopart

 wrote:

Hello all!

Yesterday I came back to some midi stuff in Pro Tools and realized
that my
Mac starts cooling very much, when using the Flo Tools feature to

e.g.

automatically announce a notes pitch.
Even in "stop mode" and doing really nothing the temperature rises

and

rises...
Setting Flo Tools to "no report" again normalizes the behaviour.

Has this always been the case? Don't think so.

Current Pro Tools and Keyboard Maestro under Catalina 10.15.7.
Same when using the Keyboard Maestro version before the last

one.

Doublicated on two different Mac Books Pro.

Thanks and best! / Martin



--
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.

To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/00a401d6ed5f%2408c0afd0%2

41a420f70%24%40cakewalker.de.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/9D227B37-B3C7-4BED-

A0D3-

B6

Re: Observation - midi event list

[Chi Kim]

The temperature did increase, but no, nothing like above 100 degrees. It 
went from around 75 to around 85.


Also fan only increased only by like -50 rpm higher, I didn't hear much 
difference.


Hopefully the new build works better on your system.


Chi


On 2/9/2021 6:24 AM, Martin (Punky) Sopart wrote:

Hello Chi!

Thanks for helping here...

Did I get you right, that you do not have this temperature behavior on your 
system?

Best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Chi Kim
Sent: Monday, February 8, 2021 7:12 PM
To: ptaccess@googlegroups.com
Subject: Re: Observation - midi event list

Hi Martin,


Here's the build with a 100ms delay.

https://github.com/flotools/flotools/archive/master.zip

It's not signed, so you need to bypass the MacOS gatekeeper.


Chi


On 2/8/2021 12:49 PM, Chi Kim wrote:

Hi Martin and Slau,


On my system, temperature rises by about 10 degrees.

Now, the script constantly monitors the control for any change without
breathing.

I could insert a 100ms long breath before every check. Then the
temperature rises by about 5 degrees, but you'll notice 200ms delay
before the speech output.

Would that be acceptable?

Also I guess we need to think about doing the same thing to other
monitors such as plugin monitor, level meter monitor, and so on.


Chi




On 1/19/2021 4:54 AM, Martin (Punky) Sopart wrote:

Hello Slau!

Yes, I can remember something like that when using the Plug-in
Monitor, but not that extreme when doing nothing and watching the cpu
temperature rises to 100 degrees Celsius.
Maybe the todays faster cpus and memory or the newer versions of
Keyboard Maestro causes that.

Thanks and best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Slau Halatyn
Sent: Monday, January 18, 2021 10:59 PM
To: PTAccess List 
Subject: Re: Observation - midi event list

Hi Martin,

We’ve changed nothing about that feature so it has probably always

been

the case. In fact, the same thing happens when the Plug-in Monitor is
engaged. Flo Tools is constantly scanning for any changes and the
CPU starts
to rev up it appears. Chi’s going to look into this to see if
there’s anything we
can do to improve the behavior.
slau



On Jan 18, 2021, at 12:59 AM, Martin (Punky) Sopart

 wrote:

Hello all!

Yesterday I came back to some midi stuff in Pro Tools and realized
that my
Mac starts cooling very much, when using the Flo Tools feature to e.g.
automatically announce a notes pitch.
Even in "stop mode" and doing really nothing the temperature rises

and

rises...
Setting Flo Tools to "no report" again normalizes the behaviour.

Has this always been the case? Don't think so.

Current Pro Tools and Keyboard Maestro under Catalina 10.15.7.
Same when using the Keyboard Maestro version before the last one.
Doublicated on two different Mac Books Pro.

Thanks and best! / Martin



--
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.

To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/00a401d6ed5f%2408c0afd0%2

41a420f70%24%40cakewalker.de.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/9D227B37-B3C7-4BED-

A0D3-

B6D4185672C1%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046CB7E68726E
983ECA8E8ECE8F9%40MN2PR05MB6046.namprd05.prod.outlook.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046F96AAB7CA2F576799D4BCE8D9%40MN2PR05MB6046.namprd05.prod.outlook.com.

Re: Observation - midi event list

[Chi Kim]

Hi Martin,


Here's the build with a 100ms delay.

https://github.com/flotools/flotools/archive/master.zip

It's not signed, so you need to bypass the MacOS gatekeeper.


Chi


On 2/8/2021 12:49 PM, Chi Kim wrote:

Hi Martin and Slau,


On my system, temperature rises by about 10 degrees.

Now, the script constantly monitors the control for any change without 
breathing.


I could insert a 100ms long breath before every check. Then the 
temperature rises by about 5 degrees, but you'll notice 200ms delay 
before the speech output.


Would that be acceptable?

Also I guess we need to think about doing the same thing to other 
monitors such as plugin monitor, level meter monitor, and so on.



Chi




On 1/19/2021 4:54 AM, Martin (Punky) Sopart wrote:

Hello Slau!

Yes, I can remember something like that when using the Plug-in 
Monitor, but not that extreme when doing nothing and watching the cpu 
temperature rises to 100 degrees Celsius.
Maybe the todays faster cpus and memory or the newer versions of 
Keyboard Maestro causes that.


Thanks and best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Slau Halatyn
Sent: Monday, January 18, 2021 10:59 PM
To: PTAccess List 
Subject: Re: Observation - midi event list

Hi Martin,

We’ve changed nothing about that feature so it has probably always been
the case. In fact, the same thing happens when the Plug-in Monitor is
engaged. Flo Tools is constantly scanning for any changes and the 
CPU starts
to rev up it appears. Chi’s going to look into this to see if 
there’s anything we

can do to improve the behavior.
slau



On Jan 18, 2021, at 12:59 AM, Martin (Punky) Sopart

 wrote:

Hello all!

Yesterday I came back to some midi stuff in Pro Tools and realized 
that my

Mac starts cooling very much, when using the Flo Tools feature to e.g.
automatically announce a notes pitch.
Even in "stop mode" and doing really nothing the temperature rises and
rises...
Setting Flo Tools to "no report" again normalizes the behaviour.

Has this always been the case? Don't think so.

Current Pro Tools and Keyboard Maestro under Catalina 10.15.7.
Same when using the Keyboard Maestro version before the last one.
Doublicated on two different Mac Books Pro.

Thanks and best! / Martin



--
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.

To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/00a401d6ed5f%2408c0afd0%2
41a420f70%24%40cakewalker.de.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/9D227B37-B3C7-4BED-A0D3-
B6D4185672C1%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/MN2PR05MB6046CB7E68726E983ECA8E8ECE8F9%40MN2PR05MB6046.namprd05.prod.outlook.com.

Re: Observation - midi event list

[Chi Kim]

Hi Martin and Slau,


On my system, temperature rises by about 10 degrees.

Now, the script constantly monitors the control for any change without 
breathing.


I could insert a 100ms long breath before every check. Then the 
temperature rises by about 5 degrees, but you'll notice 200ms delay 
before the speech output.


Would that be acceptable?

Also I guess we need to think about doing the same thing to other 
monitors such as plugin monitor, level meter monitor, and so on.



Chi




On 1/19/2021 4:54 AM, Martin (Punky) Sopart wrote:

Hello Slau!

Yes, I can remember something like that when using the Plug-in Monitor, but not 
that extreme when doing nothing and watching the cpu temperature rises to 100 
degrees Celsius.
Maybe the todays faster cpus and memory or the newer versions of Keyboard 
Maestro causes that.

Thanks and best! / Martin

-Original Message-
From: ptaccess@googlegroups.com  On
Behalf Of Slau Halatyn
Sent: Monday, January 18, 2021 10:59 PM
To: PTAccess List 
Subject: Re: Observation - midi event list

Hi Martin,

We’ve changed nothing about that feature so it has probably always been
the case. In fact, the same thing happens when the Plug-in Monitor is
engaged. Flo Tools is constantly scanning for any changes and the CPU starts
to rev up it appears. Chi’s going to look into this to see if there’s anything 
we
can do to improve the behavior.
slau



On Jan 18, 2021, at 12:59 AM, Martin (Punky) Sopart

 wrote:

Hello all!

Yesterday I came back to some midi stuff in Pro Tools and realized that my
Mac starts cooling very much, when using the Flo Tools feature to e.g.
automatically announce a notes pitch.
Even in "stop mode" and doing really nothing the temperature rises and
rises...
Setting Flo Tools to "no report" again normalizes the behaviour.

Has this always been the case? Don't think so.

Current Pro Tools and Keyboard Maestro under Catalina 10.15.7.
Same when using the Keyboard Maestro version before the last one.
Doublicated on two different Mac Books Pro.

Thanks and best! / Martin



--
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.

To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/00a401d6ed5f%2408c0afd0%2
41a420f70%24%40cakewalker.de.

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/9D227B37-B3C7-4BED-A0D3-
B6D4185672C1%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/MN2PR05MB604690330E4AAD6398D0519FCE8F9%40MN2PR05MB6046.namprd05.prod.outlook.com.

Just Bought SSL2+!

[Chi Kim]

Hi All,

Sorry for cross posting, but I thought some of you might be interested.
I just bought SSL2+ audio interface for $279, and it's very accessible.
When I walked by SSL booth at NAMM this year with my friend, he pointed 
it out, but we didn't really pay attention because SSL gears are pretty 
pricy.
Then when I wanted to get one, it was out of stock everywhere. Now it 
seems like a lot of places have them in stock.
They are also giving $880 worth of ssl plugins for free as long as you 
register your unit this year.
Originally they give VocalStrip and DrumStrip, but they're adding X-Comp 
and FlexVerb as holiday promotion. Also You get 6 months free trial for 
all SSL native plugins.
First, the unit has knobs and buttons. There is no touch pads or multi 
purpose encoders.
It also worked out of the box on Mac without any installation. Obviously 
you need to install the plugins if you want to use them, and they are 
authorized by iLok.

All the controls are on the top of the unit.
1. Eight buttons to engage 4k, 48v, high-z, and line for each input
You can feel if a button is pressed/released.
2. Two knobs to control gain for each input
3. Two knobs for seperate headphone levels
4. Knob for main output
5. Knob for direct monitor mix
6. Button to engage two inputs in stereo mode
7. Button to seperate output channel 1-2 from 3-4
All the connections are in the back.
1. Two xlr/1/4 combo connection for inputs
2. 1/4 Main l/r
3. Two rca connections for channel 1-2, 3-4
4. Two headphone outs
5. Midi in/out
6. USB-c port
They give you an usb-c to usb-c cable, and an usb-c to usb-a cable.
As far as performance, I was able to play a project with 16 audio 
tracks, full String sections from Spitfire BBC Pro (Violins A, Violins 
B, Violas, Celli, Basses) and Embertone Concert D.
Those sample libraries are extremely resource intensive, but I was able 
to play without glitch at 128 samples latency on both Pro Tools and Logic.
I haven't had a chance to use their plugins extensively yet, but From a 
brief glance, I was able to find all the parameters I needed with 
VoiceOver. To choose a preset, I needed to rely on VOCR.
As far as sound, they are not Apollo or Apogee, but the preamps are 
pretty clean. The 4k switch is not a magic, but has a nice touch. You 
can find better reviews from people who have used more extensively.
If you've been thinking about picking up a portable audio interface, it 
seems a pretty solid choice especially for the price!

Happy to answer any question.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/MN2PR05MB60466300DC92D7789331F773CEC90%40MN2PR05MB6046.namprd05.prod.outlook.com.

Re: How do y'all use Mac with touch screen function keys

[Chi Kim]

If you have the virtual extended keyboard, you can use

fn+1,2,3,4: f1,2,3,4

fn+q,w,e,r = f5,6,7,8

  fn+a,s,d,f = f9,10,11,12

fn+z,x,c,v = f16,17,18,19



On 12/2/2020 11:43 PM, Dammie Onafeko wrote:

Thanks Steeve! I'll consult the VO documentation when time permits me.
But for now, an external key board comes in handy. I don't need to
read anything. Greatly appreciate. God bless.

Best,

Dammie

On 12/2/20, Steve Martin  wrote:

VO functions can be done with the number row and the FN key. Also stuff like
the volume and turning Voiceober on/off have shortcuts that doesn’t rely on
the TouchBar. You should consult the VoiceOver documentation for details on
using a TouchBar  Mac as a VoiceOver user.
Or you can plug in a USB or bluetooth keyboard.



On Dec 2, 2020, at 10:21 PM, Dammie Onafeko 
wrote:

Evening guys! Quick question. My work just presents me with this Mac
that has a touch screen function keys, and I'm having issues with it.
How do you use a Mac like this? Please help!

Warm regards,

Dammie

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/CAN%3Dh5d-YM3yAYgMMbwuyWX1xmNjs0J%3Dd8DG1eZkFtx%2B%2BFSPkPg%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/70310FA3-ECDE-4D13-8E32-6A067CAACDE6%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB604169C8137C462ECE4278A4CEF20%40DM6PR05MB6041.namprd05.prod.outlook.com.

Re: 2 problems with ks888 mk2.

[Chi Kim]

I meant Pro Tools update, not OS update might put the Facebook plugins 
back in.


I have no idea if anything has to do with this, but I don't think Pro 
Tools officially support 10.15.6.




On 8/17/2020 3:29 AM, dingram...@earthlink.net wrote:
Hi, how are you? What you suggested had already been done in terms of 
removing anything that had fb in the title.  I wonder that after 
updating the os from Catalina 10.15.5 to Catalina 10.15.6 would bring 
back things that had already been deleted? I just thaught that I would 
ask.  I Don't remember having the problem where the ks88 mk2 is not 
being recognized by the mac mini.  That has never happened befor.  I 
don't know what else it could be but after the recognizing of the ks88 
mk2 is restored then i'll be able to check for firmware updates.  
Another question is can I try to install firmware updates using my 
windows computer?  at least this way they are installed.


-Original Message-
From: Chi Kim
Sent: Aug 16, 2020 10:03 PM
To: ptaccess@googlegroups.com
Subject: Re: 2 problems with ks888 mk2.

Have you try deleting FaceBook 360 plugins?

For some users, Facebook plugins that come with Pro Tools
interfere with Accessibility for Komplete Kontrol.

You can find them in /Library/Application Support/Avid/Audio/Plug-Ins.

Delete everything that starts with FB360.

Or you can move them to Plug-Ins (Unused) folder if you don't want
Pro Tools to reinstall when you update.


On 8/16/2020 12:08 PM, Phil Muir wrote:


I wonder if you're running the latest firmware on that keyboard?

On 16 August 2020 09:52:31  wrote:


Hi list members, I'd like to know if anyone else has had the
following problems with ks88 mk2?  1.  The ks88 mk2 is not being
recognized by the mac mini.  2. When I try to turn on
accessibility by pressing both the shift+mix buttons at the same
time nothing happens.  these are the current problems that I'm
experiencing but I've also read in ni support that other people
have had the same problems.  I've even tried to turn off the
ks88 and turn it back on again but still nothing.  I even tried
to arm a track in pro tools but nothing.  I'm not sure what the
problem is but I didn't find any solution that I thaught could
solve at least one of the problems.  May be someone may be able
to do a remote session just to see what i'm talking about.  P.S.
I also would like to ask if I should try to use the ks88 on a
windows system just to see what happens?  I'm not sure if it
would fix the not being recognized by my mac mini but I just
thaught I would ask.  Thank you for any information that you
might have that could solve both of these problems.

-- 
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.
To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/1196610506.59.1597567946247%40wamui-cinderella.atl.sa.earthlink.net.

-- 
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
<mailto:ptaccess+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/173f807ce80.27de.db423894e9b0bc6221d01044e43225ea%40accessibilitytraining.co.uk

<https://groups.google.com/d/msgid/ptaccess/173f807ce80.27de.db423894e9b0bc6221d01044e43225ea%40accessibilitytraining.co.uk?utm_medium=email_source=footer>.
-- 
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
<mailto:ptaccess+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/DM6PR05MB581701547BE3FC033FA9E741CE5F0%40DM6PR05MB5817.namprd05.prod.outlook.com

<https://groups.google.com/d/msgid/ptaccess/DM6PR05MB581701547BE3FC033FA9E741CE5F0%40DM6PR05MB5817.namprd05.prod.outlook.com?utm_medium=email_source=footer>.

--
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 
<mailto:ptaccess+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/312580586.28.1597649387541%40wamui-albus.atl.sa.earthlink.net 
<http

Re: 2 problems with ks888 mk2.

[Chi Kim]

Have you try deleting FaceBook 360 plugins?

For some users, Facebook plugins that come with Pro Tools interfere with 
Accessibility for Komplete Kontrol.


You can find them in /Library/Application Support/Avid/Audio/Plug-Ins.

Delete everything that starts with FB360.

Or you can move them to Plug-Ins (Unused) folder if you don't want Pro 
Tools to reinstall when you update.



On 8/16/2020 12:08 PM, Phil Muir wrote:


I wonder if you're running the latest firmware on that keyboard?

On 16 August 2020 09:52:31  wrote:

Hi list members, I'd like to know if anyone else has had the 
following problems with ks88 mk2?  1.  The ks88 mk2 is not being 
recognized by the mac mini.  2.  When I try to turn on accessibility 
by pressing both the shift+mix buttons at the same time nothing 
happens.  these are the current problems that I'm experiencing but 
I've also read in ni support that other people have had the same 
problems.  I've even tried to turn off the ks88 and turn it back on 
again but still nothing.  I even tried to arm a track in pro tools 
but nothing.  I'm not sure what the problem is but I didn't find any 
solution that I thaught could solve at least one of the problems.  
May be someone may be able to do a remote session just to see what 
i'm talking about.  P.S. I also would like to ask if I should try to 
use the ks88 on a windows system just to see what happens?  I'm not 
sure if it would fix the not being recognized by my mac mini but I 
just thaught I would ask.  Thank you for any information that you 
might have that could solve both of these problems.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/1196610506.59.1597567946247%40wamui-cinderella.atl.sa.earthlink.net.



--
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 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/173f807ce80.27de.db423894e9b0bc6221d01044e43225ea%40accessibilitytraining.co.uk 
.


--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB581701547BE3FC033FA9E741CE5F0%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Plugsounds > Apology: all is fine

[Chi Kim]

Hi Katie,


I deleted the old presets for plugsounds that Slau started, and updated 
with new one that now has complete 1,647 presets.



Chi


On 7/7/2020 3:46 PM, Katie Zodrow wrote:

Hi Chris it’s Katie.
I just turned on my Mac and Dropbox is currently updating my files. Yep, I 
noticed a bunch of files were deleted from my Dropbox a few minutes ago. I’m 
not on the PT What’s App group and wanted to know what files were removed?
Thanks.
Katie


On Jul 7, 2020, at 11:35 AM, Christopher Gilland  wrote:

Didn't mean to freak out anyone if I did in my last message to the list. All's 
fine with the PT Access Dropbox folder. We figured out the issue, and it was 
completely legit. See the Whatsapp group if you want more info. Otherwise, 
please accept my apology, and disregard.


Chris.

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/465de732-7bf8-d15a-fedf-c7f144633af6%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB58172D3635CE126ECC678FCECE670%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Flo Tools 2020.3 is out

[Chi Kim]

For curiosity, I ran the download link through virustotal.com. It 
doesn't have Avast, but it passed all 80 engines.

https://www.virustotal.com/gui/url/bd2b778837b61c6b57beebbbe63b782077b0231714759df0437314ddc3d5d213/detection

The installer is also notarized for distribution by Apple which includes 
malwarescan.


It's probably a false positive from Avast.


Chi


On 5/25/2020 3:08 AM, JennyK Productions wrote:

Hi
I'm using Avast security. A can't seem to find any info about it and I 
can't disable it. I'm getting a bit frustrated.

maybe coffee will help.
:)
J


On Sunday, May 24, 2020 at 7:41:25 PM UTC-4, Rocco Fiorentino wrote:

Hi jenny,

Thanks so Much for letting us know about this. If you can tell me
what software that error was generated from, or as Slau said, if
you have a specific antivirus installed, I can take a look into it
further. Feel free to message me off list as well if you’d like.
Best,
Rocco

Sent from my iPhone


On May 24, 2020, at 6:30 PM, JennyK Productions
 wrote:


Hi. I'm new here and just in the possible transition from Logic
to Pro tools. I'll be running kb maestro trial and the PT trial
to see if it's something for me. But when I try to extract the
this latest version of Flo tools from flotools.org
, I get this from my mac : "We've moved
.BC.T_kb8eQ8 to your Virus Chest because it was infected with
MacOS:Bundlore-FC [Adw].

I'm quite weirded out by that and obviously can't install
flotools. . Any thoughts?
Thoughts?
Jenny


On Saturday, April 4, 2020 at 4:58:27 PM UTC-4, Slau Halatyn wrote:

Just an FYI that last night the latest version of Flo Tools,
version 2020.3 compatible with Pro Tools 2020.3, was
released. Catalina really clamped down on a few things with
the installer and a few people had problems running the
installer so we had a number of things to fix so that the
installation ran smoothly. Any users who have not yet
downloaded the installer or downloaded it before yesterday
should re-download the installer from FloTools.org whenever
you can.

Cheers!

-- 
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 ptac...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/ptaccess/ba2b8d60-5163-4746-b081-e6121150f96d%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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/28039566-fdc2-4d92-95d0-3c1ea69c8931%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB58173EE0F0BA1DDA05FEFD5CCEB30%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Flo Tools Observations

[Chi Kim]

Keyboard Maestro Engine consumes only about 60mb, so it shouldn't hardly 
impact your memory.


You can check in your activity monitor.

Go to Applications, Utilities, Activity monitor

Then choose memory view tab from toolbar.

From there you can also find out what's hogging your memory.


Chi


On 4/22/2020 6:38 AM, Toby Davey wrote:

Hi Slau,
Thought it would be easier writing an email rather than a long voice 
message in the WatsApp group.
One first quick question - Does Flo Tools with KM eat up a bit of 
memory when they are running alongside PT as my MacBook Pro only has 
8GB of Ram?
I had some strange things happening last night when trying to see what 
was going on with FT, KM and PT, I had some alerts about low memory 
pop up a few times and I closed all programmes apart from PT, KM and 
EU that was running in the background, did a couple of re boots of my 
MacBook which did seem to stop the low memory alerts popping up.
When I did launch PT and when FT kicked in I did get an audio alerts 
to say that ‘I needed to check that in VO utilities that the tick box 
had to be ticked to allow VO to access programmes on my Mac’, very 
strange as I have never unticked this tick box in VO.
I checked to see if any system alerts were running as you suggested 
but nothing apart from one for ‘Applications running in KM.  Which I 
don’t think is actually a pop up just something that is running in the 
background.
Had another go with PT and FT in the Edit window but still could not 
get it to work.
Decided to leave it for the night and sleep on it and have another go 
this morning.

So this morning started again, booting up my MacBook, etc.
Still not able to get FT to work in the Edit window.
Decided to launch the FT installer again just in case something was 
missing from the install.  The install launched all OK.  When 
Launching PT again, I had a FT audio alert about the VO tick box again 
for allowing VO to access programmes on my Mac, went into VO 
utilities, tick box as usual was ticked to allow VO to access 
programmes on my Mac, decided to un tick it and then re tick it just 
in case.
When I got into PT I went through the same procedure that you did in 
your audio demo.  In your demo it sounded like when you were on the 
level metre before activating FT inspector that the level was read out 
automatically when you were playing the track.  I did not initially 
get any level metre reading out with VO, but when I used  VO and the 
arrow keys VO did read out the levels, not sure if that was what you 
were doing or whether the levels were being read out automatically 
when you were on the level metre.
Stopped interacting with the track, turned the inspector on and did 
the same as you did in your demo but still no FT read out when 
inspector was on and pressing ‘L’.
So I decided to go into the Mix window to check to see if FT was 
reading out the level metres in the Mix window and yes all seemed to 
be fine in the Mix window like before.
Now this is the strange bit as when I went back into the Edit window 
and did as before I was now able to get FT to read out the level metre 
readings with inspector on and pressing ‘L’, etc.
I then decided to exit out of PT shut down my MacBook and re boot and 
try this all again to see if wen I am in PT and first go to the Mix 
window and then into the Edit window will FT work again.
Yep and surprise, surprise it did work again but only in the Edit 
window if i go into the Mix window first and then back into the Edit 
window.

All very strange!
I did notice in your demo that when you went from the bottom of the 
Edit window and did a read to the left that you went straight from the 
50 to the ’track list show / hide’ button and currently in the Edit 
window of PT on my MacBook I go from 50 and then there are buttons for 
 ’show / hide clip list’, ’show / hide docked midi editor’ and then 
’show / hide track list’, not sure if this has any affect on the issue.
Not totally sure if or how to remove those extra buttons and whether 
they might be affecting things but might be worth me having a look.
not sure if it might be a memory / processor issue but I would have 
not thought that FT would be using up quite so much processor / memory 
just to read out the metre levels but maybe with having KM running it 
is using more processor and memory when performing tasks but the Mix / 
Edit window thing as above would rule that out maybe.

Cheers
Toby

On 21 Apr 2020, at 14:23, Slau Halatyn > wrote:


Hi Toby,
Actually, even in the minimal view, the level meter will be there. I 
left a message on the PT WhatsApp group demonstrating exactly how it 
should work for you. Hope that helps. Let me know if you get it to work.

Cheers,
Slau


On Apr 21, 2020, at 7:23 AM, Toby Davey > wrote:


Hi Slau,
As usual thanks so much for your words of wisdom.  I did listen to 
your demo of the edit window and fully get that VO is seeing things 

Re: What could make FlowTools not see signals

[Chi Kim]

Try

select that track only and choose show only selected track from track 
list popup.


Also recheck all the settings again from the Flo Tools manual.

By the way, it's probably not Flo tools. It's probably because the level 
is hidden from the screen.


If you manually navigate to the level with just VoiceOver, VoiceOver 
won't probably see the value either.



Chi


On 4/17/2020 11:31 AM, Dammie Onafeko wrote:

Hi Mike:

Thanks for the suggestion. Is there any other thing I need to ensure
before double tapping T or fterwards? I did exactly what you
suggested, but it's still saying no signal. If there be mor
suggestions, I'd greatly appreciate. Thanks a lot!

Best,

Dammie

On 4/17/20, Michael Holmes  wrote:

You can fix that by double tapping t and choosing scroll into view  As
long as the view options are optimized for Flo Tools, that should do the
trick!


On Apr 17, 2020, at 04:30, Dammie Onafeko  wrote:

Hi guys:

Top of the day to you all. I don't know what to do. I'm working on a
session and I'm trying to check the level of the tracks  to apply
compressor on them. But when I push L on the tracks, all I hear is no
signal. I confirmed that I'm on a track with signal by muting the
track and unmuting it just to make sure. Does anyone have an idea of
what I might pushed to make FlowTools not to see the signal? I'd
greatly appreciate your support. Thanks!

Best,

Dammie

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/CAN%3Dh5d_B6e7R93MvGiNEhoo3vMf0wdggpZfro7%2B%2BDoDSFd%3DW6Q%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/82678224-3812-499C-B063-9B8CB9FB8B3A%40gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB581781D070FB04E083F378EDCED90%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Anybody using the Valhalla vintage reverb plug-in in ProTools?

[Chi Kim]

Yes, PreSonus rep said "Automation with the FaderPort v2 is relegated to 
volume automations," but FaderPorts 8 and 16 supports plugin automation.

On Saturday, March 28, 2020 at 4:30:58 PM UTC-4, TheOreoMonsteEr wrote:
>
> Is that still the case with V2? PreSonus did update the single FaderPort 
> after the FaderPort 8 and 16 came out. 
>
>
> > On Mar 28, 2020, at 4:08 PM, Slau Halatyn  > wrote: 
> > 
> > The thing about the single Faderport is that it doesn't support plug-in 
> automation control, kind of a dealbreaker for most. 
> > 
> > 
> >> On Mar 28, 2020, at 3:33 PM, TheOreoMonster  > wrote: 
> >> 
> >> From everything I have seen the FaderPort 8 is the least expensive 
> option for ProTools users. However people may  want to look into how 
> compatible the FaderPort is with ProTOols if a single fader is sufficient, 
> as it’s considerably less expensive. 
> >> 
> >>> On Mar 28, 2020, at 2:14 PM, Slau Halatyn  > wrote: 
> >>> 
> >>> Hi Charles, 
> >>> I've never been in the market for a compact control surface and I 
> don't follow too closely what's available currently. It seems like the 
> Presonus Faderport 8 is fairly popular and has a true fader flip mode which 
> is quite helpful. Apart from that, it gets pretty expensive very quickly. 
> Perhaps some others may have more suggestions. 
> >>> Slau 
> >>> 
> >>> 
>  On Mar 28, 2020, at 1:54 PM, Charles  > wrote: 
>  
>  Slau 
>  
>  Thank you very much for that info. That is too bad. Since you 
> mentioned control surfaces, is there one that you can recommend for someone 
> who just works by himself at home? 
>  
>  Sent from my iPhone 
>  
> > On Mar 28, 2020, at 1:37 PM, Slau Halatyn  > wrote: 
> > 
> > Unfortunately, all Valhalla plug-ins are written in the JUCE 
> platform which, depending on how the developer authors things, can lead to 
> parameters not responding to the accessibility API. With a control surface, 
> everything works fine but not with VoiceOver. I know the developer and will 
> reach out to see if he can do anything about it for future releases. 
> > Slau 
> > 
> > 
> >> On Mar 28, 2020, at 12:45 PM, Charles  > wrote: 
> >> 
> >> I have just installed the Valhalla vintage rebirth and the Valhalla 
> delay plug-ins. I am using the latest version of ProTools and Mac OS X 15. 
> Though I am able to see all the parameters, I’m not able to change any of 
> them. Is anybody able to use the Valhalla plug-ins in ProTools? 
> >> 
> >> Sent from my iPhone 
> >> 
> >> -- 
> >> 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 ptac...@googlegroups.com . 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/MN2PR22MB195208988B665FE0B1E72CDEBBCD0%40MN2PR22MB1952.namprd22.prod.outlook.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 ptac...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/CC8AC63F-642A-4336-9E3A-82E20EC2D57F%40gmail.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 ptac...@googlegroups.com . 
>  To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/MN2PR22MB1952F76B27CAFBDED99259A1BBCD0%40MN2PR22MB1952.namprd22.prod.outlook.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 ptac...@googlegroups.com . 
> >>> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/8EB23231-4F13-40C6-BEB2-8C0840267322%40gmail.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 ptac...@googlegroups.com . 
> >> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/735DCAB6-2724-4F33-84C4-F7CF6026EA3A%40gmail.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 ptac...@googlegroups.com . 
> > To view this discussion on the web visit 
> 

Re: VOCR and iMac 27

[Chi Kim]

Hey Jesse,


I assuming you're using Tesseract version since you can't run Pro Tools on 
Catalina.

The result of VOCR depends on the what Tesseract gives, so there isn't really 
much you can do in order to improve.

The new VOCR has better result from using the OCR engine from built-into 
Catalina.

Hopefully when Pro Tools becomes compatible with Catalina, more people could 
take advantage of it.

Also sometimes turning off VoiceOver visuals with vo+command+f11 helps.

VoiceOver cursor indicator and captions panels get overlaid on top of a window, 
so it can interfere with the screenshot.

Lastly, there's a chance that there isn't many words on the screen.

The interface could be consist of just icons, sliders, and knobs instead of 
words.

Thus, you might be reading what Tesseract is trying to make words out of 
pictures that are not actual words.


Chi



On 10/18/2019 5:05 PM, Jesse Kragiel wrote:
Hi! I'm super late to the VOCR party, and I'm ashamed of that. I'm running a 27 
inch iMac 5K and VOCR is hit and miss inside of plugin windows such as Waves 
stuff. Am I doing something wrong, or is this just the nature of the beast? 
Where it works, it's amazing, but where it doesn't, it speaks gibberish. Any 
suggestions to optimize things better?
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/62852340-6667-49bd-aee6-8d0e4ad81c70%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817A780B2EBF069835F4B2DCE6F0%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Flogic, Subject Changed from New VOCR On Catalina

[Chi Kim]

Hi Jay,


I just changed your subject because it isn't related to VOCR.

You can download Flogic here.

https://github.com/chigkim/Flogic/archive/master.zip

You can find some tutorials here.

http://accessmtech.com/index.php?title=Category:Logic_Pro

However, Flogic doesn't work on latest logic anymore due to many changes 
that Apple made for their UI elements.

I believe you have to use old Logic 10.4.3.

I have plan to update at some point, but unfortunately too many things 
to do, too little time.

I need to clone myself. :)


Chi


On 10/8/2019 7:28 AM, Jay Paschal wrote:
> Hi Chi, i’m interested in installing your flow logic to my system; what is 
> your website and do you have any tutorial videos? Thank you
>
> “Be who you desire & desire who you wish to be”Sent from my iPhone
>
>> On Oct 8, 2019, at 7:03 AM, Chi Kim  wrote:
>>
>> HI All,
>>
>> Sorry for cross-posting, but I'm just writing to let everyone know that
>> I just released a new experimental VOCR.
>> If you haven't heard VOCR, it's an app that lets you take screenshot of
>> your mac screen, apply OCR, navigate the result, and move the mouse.
>> It's similar to JAWS and NVDA feature.
>> MacOS Catalina finally included the OCR capability in their VisionKit
>> that take advantage of machine learning.
>> In my opinion, it is much faster and accurate than Tesseract that
>> previous VOCR utilized, and you don't have to deal with terminal.
>> Because the tight security in Catalina, there are multiple steps for the
>> initial setup. You can read the instruction below.
>> https://github.com/chigkim/VOCR/tree/VK
>> Here's the link to download.
>> https://github.com/chigkim/VOCR/releases/download/v0.1.0-alpha.1/VOCR.v0.1.0-alpha.1.zip
>> This is highly experimental, so use at own your risk!
>> Lastly, this kind of feature should be really built in to VoiceOver in
>> my opinion. If you know anyone at Apple, let them know.
>> Enjoy,
>>
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/DM6PR05MB58176B1A002B6242821C4B80CE9A0%40DM6PR05MB5817.namprd05.prod.outlook.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817B56C67C37F734454F344CE9A0%40DM6PR05MB5817.namprd05.prod.outlook.com.

New VOCR On Catalina

[Chi Kim]

HI All,

Sorry for cross-posting, but I'm just writing to let everyone know that 
I just released a new experimental VOCR.
If you haven't heard VOCR, it's an app that lets you take screenshot of 
your mac screen, apply OCR, navigate the result, and move the mouse. 
It's similar to JAWS and NVDA feature.
MacOS Catalina finally included the OCR capability in their VisionKit 
that take advantage of machine learning.
In my opinion, it is much faster and accurate than Tesseract that 
previous VOCR utilized, and you don't have to deal with terminal.
Because the tight security in Catalina, there are multiple steps for the 
initial setup. You can read the instruction below.
https://github.com/chigkim/VOCR/tree/VK
Here's the link to download.
https://github.com/chigkim/VOCR/releases/download/v0.1.0-alpha.1/VOCR.v0.1.0-alpha.1.zip
This is highly experimental, so use at own your risk!
Lastly, this kind of feature should be really built in to VoiceOver in 
my opinion. If you know anyone at Apple, let them know.
Enjoy,

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB58176B1A002B6242821C4B80CE9A0%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Cannot - The checkbox labeled "Allow VoiceOver to be controlled with AppleScript" in the General pane of VoiceOver Utility should be checked.

[Chi Kim]

Hi,


I've talked to Apple Accessibility team about this before. We tried many 
different things including creating and login into a new admin account, but we 
weren't able to fix it.

Eventually upgrading to Mojave fixed itself.


Chi


On 9/5/2019 6:55 PM, Matthew Hegge wrote:
macOS High Sierra is not allowing to check this box. It looks like I can, then 
when I check it, it then unchecks and becomes greyed out until I restart the 
VoiceOver Utility. Still , does not allow this to be checked.
--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/68626641-ea18-47af-b059-ddd642c77cb6%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817B5FAEC0AEB0EBD7E35C2CEB20%40DM6PR05MB5817.namprd05.prod.outlook.com.

Flo Tools Now Installs in KM 9.0.2 Without a Problem.

[Chi Kim]

Hi All,


The bug that caused every macro in Flo Tools to be imported as its own 
group is now fixed in Km 9.0.2.

You should be able to install Flo Tools without a problem now.


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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817EB13ACA3B61236228738CEB20%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0

[Chi Kim]

A couple of weeks ago. Yes, you can.


Chi


On 8/22/2019 10:02 AM, Martin (Punky) Sopart wrote:
> Hello Chi!
>
> When did you? I checked last week...
> Could I download now and overinstall?
>
> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Chi Kim
>> Sent: Thursday, August 22, 2019 3:44 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>>
>> Hi Martin,
>>
>>
>> I reverted back, because it takes too long up to 2 minutes in some cases.
>>
>>
>> Chi
>>
>>
>> On 8/21/2019 4:10 AM, Martin (Punky) Sopart wrote:
>>> Hello Chi!
>>>
>>> Didn't you change the current version of VOCR in that way, that the screen
>> size no longer has to be entered in the OCR FrontWindow macros name?
>>> Only the documentation isn't updated so far.
>>>
>>> Best! / Martin
>>>> -Original Message-
>>>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>>>> On Behalf Of Chi Kim
>>>> Sent: Wednesday, August 21, 2019 6:29 AM
>>>> To: ptaccess@googlegroups.com
>>>> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>>>>
>>>> Unfortunately it's trial and error in that case.
>>>>
>>>> Start with 11 and increase by 1. The smaller the number, the more it has
>>>> to enlarge the image.
>>>>
>>>> If you enlarge too much, it gets pixelated and blurred. If you don't
>>>> enlarge enough, the image has less density, and each letter is
>>>> represented with fewer pixels.
>>>>
>>>> You just have to find the right balance where you get the best result.
>>>>
>>>>
>>>> Chi
>>>>
>>>>
>>>> On 8/20/2019 7:15 PM, ruivilarinhomusic wrote:
>>>>> Hi Chi,
>>>>> I just instal it and tested with good results. What a great handy
>>>>> tool, thanks a lot for that.
>>>>> Although, I didnt renamed the front OCR makro because I dont quite
>>>>> know the anser, I mean, what should I write concerning a Mac Pro using
>>>>> a HDMI adaptor display here?
>>>>> Best, Rui
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> - Original Message - From: "Chi Kim" 
>>>>> To: 
>>>>> Sent: Tuesday, August 20, 2019 10:41 AM
>>>>> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> KM 9 has a bug where if you import macros, some macros get imported
>>>> into
>>>>>> its own group. For example, if you install Flo Tools, this will create
>>>>>> 800 something groups, and it will be hard to get rid of all of those.
>>>>>>
>>>>>> This happens to other macros not just Flo Tools. What's even more
>>>>>> confusing is that this only happens to some macros, not all macros, and
>>>>>> I'm not sure what's causing it.
>>>>>>
>>>>>> As far as I know, it's not installers' bug because even if you just open
>>>>>> the exported macro file without an installer, it has the same effect.
>>>>>>
>>>>>> Peter is busy squashing other bugs in KM9, but he promised to look at it
>>>>>> as soon as he can. If he finds the fix, it'll be included in the next
>>>>>> release.
>>>>>>
>>>>>> If you like, you can purchase the KM9 update for the promotion rate,
>> but
>>>>>> don't install it yet.
>>>>>>
>>>>>> Stay tuned,
>>>>>>
>>>>>>
>>>>>> Chi
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 8/19/2019 4:36 AM, Martin (Punky) Sopart wrote:
>>>>>>> Hello Rui!
>>>>>>>
>>>>>>> Do not install VOCR or Flo Tools on top of Keyboard Maestro 9.
>>>>>>> I did and have to use Timemachine :-)
>>>>>>>
>>>>>>> I think that we have to wait for new KM9 ready installers of VOCR
>>>>>>> and Flo Tools.
>

Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0

[Chi Kim]

Hi Martin,


I reverted back, because it takes too long up to 2 minutes in some cases.


Chi


On 8/21/2019 4:10 AM, Martin (Punky) Sopart wrote:
> Hello Chi!
>
> Didn't you change the current version of VOCR in that way, that the screen 
> size no longer has to be entered in the OCR FrontWindow macros name?
>
> Only the documentation isn't updated so far.
>
> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Chi Kim
>> Sent: Wednesday, August 21, 2019 6:29 AM
>> To: ptaccess@googlegroups.com
>> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>>
>> Unfortunately it's trial and error in that case.
>>
>> Start with 11 and increase by 1. The smaller the number, the more it has
>> to enlarge the image.
>>
>> If you enlarge too much, it gets pixelated and blurred. If you don't
>> enlarge enough, the image has less density, and each letter is
>> represented with fewer pixels.
>>
>> You just have to find the right balance where you get the best result.
>>
>>
>> Chi
>>
>>
>> On 8/20/2019 7:15 PM, ruivilarinhomusic wrote:
>>> Hi Chi,
>>> I just instal it and tested with good results. What a great handy
>>> tool, thanks a lot for that.
>>> Although, I didnt renamed the front OCR makro because I dont quite
>>> know the anser, I mean, what should I write concerning a Mac Pro using
>>> a HDMI adaptor display here?
>>> Best, Rui
>>>
>>>
>>>
>>>
>>>
>>> - Original Message - From: "Chi Kim" 
>>> To: 
>>> Sent: Tuesday, August 20, 2019 10:41 AM
>>> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>>>
>>>
>>>> Hi,
>>>>
>>>>
>>>> KM 9 has a bug where if you import macros, some macros get imported
>> into
>>>> its own group. For example, if you install Flo Tools, this will create
>>>> 800 something groups, and it will be hard to get rid of all of those.
>>>>
>>>> This happens to other macros not just Flo Tools. What's even more
>>>> confusing is that this only happens to some macros, not all macros, and
>>>> I'm not sure what's causing it.
>>>>
>>>> As far as I know, it's not installers' bug because even if you just open
>>>> the exported macro file without an installer, it has the same effect.
>>>>
>>>> Peter is busy squashing other bugs in KM9, but he promised to look at it
>>>> as soon as he can. If he finds the fix, it'll be included in the next
>>>> release.
>>>>
>>>> If you like, you can purchase the KM9 update for the promotion rate, but
>>>> don't install it yet.
>>>>
>>>> Stay tuned,
>>>>
>>>>
>>>> Chi
>>>>
>>>>
>>>>
>>>>
>>>> On 8/19/2019 4:36 AM, Martin (Punky) Sopart wrote:
>>>>> Hello Rui!
>>>>>
>>>>> Do not install VOCR or Flo Tools on top of Keyboard Maestro 9.
>>>>> I did and have to use Timemachine :-)
>>>>>
>>>>> I think that we have to wait for new KM9 ready installers of VOCR
>>>>> and Flo Tools.
>>>>>
>>>>> Best! / Martin
>>>>>> -Original Message-
>>>>>> From: ptaccess@googlegroups.com
>> [mailto:ptaccess@googlegroups.com]
>>>>>> On Behalf Of ruivilarinhomusic
>>>>>> Sent: Monday, August 19, 2019 4:09 AM
>>>>>> To: ProToolsAccessList 
>>>>>> Subject: VOCR with Keyboard Maestro 9.0
>>>>>>
>>>>>> Hi,
>>>>>> I hope all are doing ok.
>>>>>> I finally decided to instal VOCR. Is it  working fine with the
>>>>>> Keyboard Maestro
>>>>>> 9.0? Can i upgrade?
>>>>>> Using HighSierra here.
>>>>>>
>>>>>>
>>>>>> Is that updated? Download VOCR at:
>>>>>> https://github.com/chigkim/VOCR/archi...
>>>>>> Getting Started:
>>>>>> https://github.com/chigkim/vocr
>>>>>>
>>>>>> Thanks in advance any tip or suggestion !
>>>>>> Rui Vilarinho
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>&

Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0

[Chi Kim]

Unfortunately it's trial and error in that case.

Start with 11 and increase by 1. The smaller the number, the more it has 
to enlarge the image.

If you enlarge too much, it gets pixelated and blurred. If you don't 
enlarge enough, the image has less density, and each letter is 
represented with fewer pixels.

You just have to find the right balance where you get the best result.


Chi


On 8/20/2019 7:15 PM, ruivilarinhomusic wrote:
> Hi Chi,
> I just instal it and tested with good results. What a great handy 
> tool, thanks a lot for that.
> Although, I didnt renamed the front OCR makro because I dont quite 
> know the anser, I mean, what should I write concerning a Mac Pro using 
> a HDMI adaptor display here?
> Best, Rui
>
>
>
>
>
> ----- Original Message - From: "Chi Kim" 
> To: 
> Sent: Tuesday, August 20, 2019 10:41 AM
> Subject: Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0
>
>
>> Hi,
>>
>>
>> KM 9 has a bug where if you import macros, some macros get imported into
>> its own group. For example, if you install Flo Tools, this will create
>> 800 something groups, and it will be hard to get rid of all of those.
>>
>> This happens to other macros not just Flo Tools. What's even more
>> confusing is that this only happens to some macros, not all macros, and
>> I'm not sure what's causing it.
>>
>> As far as I know, it's not installers' bug because even if you just open
>> the exported macro file without an installer, it has the same effect.
>>
>> Peter is busy squashing other bugs in KM9, but he promised to look at it
>> as soon as he can. If he finds the fix, it'll be included in the next
>> release.
>>
>> If you like, you can purchase the KM9 update for the promotion rate, but
>> don't install it yet.
>>
>> Stay tuned,
>>
>>
>> Chi
>>
>>
>>
>>
>> On 8/19/2019 4:36 AM, Martin (Punky) Sopart wrote:
>>> Hello Rui!
>>>
>>> Do not install VOCR or Flo Tools on top of Keyboard Maestro 9.
>>> I did and have to use Timemachine :-)
>>>
>>> I think that we have to wait for new KM9 ready installers of VOCR 
>>> and Flo Tools.
>>>
>>> Best! / Martin
>>>> -Original Message-
>>>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>>>> On Behalf Of ruivilarinhomusic
>>>> Sent: Monday, August 19, 2019 4:09 AM
>>>> To: ProToolsAccessList 
>>>> Subject: VOCR with Keyboard Maestro 9.0
>>>>
>>>> Hi,
>>>> I hope all are doing ok.
>>>> I finally decided to instal VOCR. Is it  working fine with the 
>>>> Keyboard Maestro
>>>> 9.0? Can i upgrade?
>>>> Using HighSierra here.
>>>>
>>>>
>>>> Is that updated? Download VOCR at:
>>>> https://github.com/chigkim/VOCR/archi...
>>>> Getting Started:
>>>> https://github.com/chigkim/vocr
>>>>
>>>> Thanks in advance any tip or suggestion !
>>>> Rui Vilarinho
>>>>
>>>> -- 
>>>> 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
>>>> <mailto:ptaccess+unsubscr...@googlegroups.com> .
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/ptaccess/BA3C624F20964A3DA407FA09
>>>> 9034D852%40LG
>>>> <https://groups.google.com/d/msgid/ptaccess/BA3C624F20964A3DA407FA0
>>>> 99034D852%40LG?utm_medium=email_source=footer> .
>>>
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817739FEA7D4A7E39E74A77CEAB0%40DM6PR05MB5817.namprd05.prod.outlook.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB58175171C7605D9F69DCADD3CEAA0%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: Stay Away from KM9: VOCR with Keyboard Maestro 9.0

[Chi Kim]

Hi,


KM 9 has a bug where if you import macros, some macros get imported into 
its own group. For example, if you install Flo Tools, this will create 
800 something groups, and it will be hard to get rid of all of those.

This happens to other macros not just Flo Tools. What's even more 
confusing is that this only happens to some macros, not all macros, and 
I'm not sure what's causing it.

As far as I know, it's not installers' bug because even if you just open 
the exported macro file without an installer, it has the same effect.

Peter is busy squashing other bugs in KM9, but he promised to look at it 
as soon as he can. If he finds the fix, it'll be included in the next 
release.

If you like, you can purchase the KM9 update for the promotion rate, but 
don't install it yet.

Stay tuned,


Chi




On 8/19/2019 4:36 AM, Martin (Punky) Sopart wrote:
> Hello Rui!
>
> Do not install VOCR or Flo Tools on top of Keyboard Maestro 9.
> I did and have to use Timemachine :-)
>
> I think that we have to wait for new KM9 ready installers of VOCR and Flo 
> Tools.
>
> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of ruivilarinhomusic
>> Sent: Monday, August 19, 2019 4:09 AM
>> To: ProToolsAccessList 
>> Subject: VOCR with Keyboard Maestro 9.0
>>
>> Hi,
>> I hope all are doing ok.
>> I finally decided to instal VOCR. Is it  working fine with the Keyboard 
>> Maestro
>> 9.0? Can i upgrade?
>> Using HighSierra here.
>>
>>
>> Is that updated? Download VOCR at:
>> https://github.com/chigkim/VOCR/archi...
>> Getting Started:
>> https://github.com/chigkim/vocr
>>
>> Thanks in advance any tip or suggestion !
>> Rui Vilarinho
>>
>> --
>> 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
>>  .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/BA3C624F20964A3DA407FA09
>> 9034D852%40LG
>> > 99034D852%40LG?utm_medium=email_source=footer> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR05MB5817739FEA7D4A7E39E74A77CEAB0%40DM6PR05MB5817.namprd05.prod.outlook.com.

Re: VOCR issue - Image magic not found

[Chi Kim]

Unfortunately not really.


Chi

On 11/30/2018 5:18 PM, Steve Matzura wrote:
> On the subject of VOCR, is there a mailing list to which one can 
> subscribe, or some other service, which lets users know of new 
> releases? I just happened to be cruising Github yesterday for 
> something else and discovered VOCR had a new release on the 24th. I 
> applied it, of course.
>

-- 
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: Function Keys With Touch Bar: Changed From good USB type C audio interface that is accessible as I need to buy a new mac

[Chi Kim]

Steve and Byron, thank you for confirming it. Just making sure I'm not 
missing a setting.

Actually I don't own a touch bar, but I work with students who do.

I made a program that will let you type f1-f12 and numpad keys using fn key.

fn+1,2,34 ( on number row) to f1, 2, 3, 4

fn+q,w,e,r to f5,6,7,8

fn+a,s,d,f to f9,10,11,12

fn+7,8,9 to numpad 7,8,9

fn+u,i,o to numpad 4,5,6

fn+j,k,l to numpad 1,2,3

And so on...

Anyone interested in testing it?


Chi

On 11/25/2018 1:46 AM, Steve Martin wrote:
> Actually you may be right on that one, but you can iswitch it so that the 
> TouchBar displays the function keys by default so you don’t have to press FN 
> to get to them. That being said 1 through 4 is right above the numbers on the 
> number row so I pretty much developed muscle memory to hit those and escape
> 5 and up seem to be offset by one  so if you are a touch typist the finger 
> you would normally use to hit 6 will hit 5 on the function row.  Hopefully 
> that will make it slightly less annoying. Though given how much pro tools 
> rely on the NumPad I am surprised you are using the laptops keyboard with PT 
> enough.
>
>
>> On Nov 24, 2018, at 11:25 PM, Chi Kim  wrote:
>>
>> Hi,
>>
>>
>> Please correct me if I' wrong. There might be a setting to change this
>> behavior that I'm not aware of.
>>
>> I think you can only use fn+1,2,3,etc (on the number row) only for
>> VoiceOver function.
>>
>> In other words, you can press fn+vo+2 (on the number row) to read the
>> title of current window, but you can't press fn+2 (on the number row) to
>> toggle slip mode in Pro Tools. You have to press fn key then find f2 key
>> from the touch bar.
>>
>> Please tell me I'm wrong, because this is very annoying.
>>
>> Thanks,
>>
>>
>> Chi
>>
>>
>>
>> On 11/20/2018 5:05 PM, Steve Martin wrote:
>>> The 15” MacBook pros only have the touch bar, however when using voiceover 
>>> you can press the FN key to use the normal number keys as Function keys. 
>>> Also VO+ the minus and plus keys will turn system volume up and down so you 
>>> don’t have to mess with the touch bar to use those either.
>>>
>>>> On Nov 20, 2018, at 3:47 PM, Nick Gawronski  wrote:
>>>>
>>>> Hi, The Digital 003 uses Firewire ports and I have not managed to locate
>>>> an adapter that ports Firewire to USB type C plugs.  Do most USB
>>>> interfaces work well with an USB type C adapter cable and do any of the 15
>>>> inch Mac laptops have the function keys or just the touch bars?  I want to
>>>> minimize the amount of things I have to connect to the system for editing
>>>> but if I needed to still use the Apple keyboard with the number pad I
>>>> could do that.  Nick Gawronski
>>>> On Tue, November 20, 2018 3:36 pm, Steve Martin wrote:
>>>>> Personally I’d opt for the 15” pro over the 13” pro laptop. The 15” pros
>>>>> has the advantage of quad or 6 pro processors and discrete graphics. That
>>>>> being said, There are very few actual USB-C interfaces on the market most
>>>>> of the USB-C interfaces are really just USB 2 interfaces with a USB-C
>>>>> cable to connect easily to the new computers. Given that you have a 003,
>>>>> and if pro tools is still your main DAW why not get the appropriate
>>>>> dongles so you can continue using the 003. Otherwise I’d advise a
>>>>> Thunderbolt interface wit along with the thunderbolt to Thunderbolt 3
>>>>> dongle. The only company I can think of off hand that actually makes a
>>>>> thunderbolt 3 interface is the Universal Audio Apollo. Which is a 2 in 2
>>>>> out interface with two mic/line combo jacks for the inputs. So since
>>>>> there is no actual USB-C interfaces and thunderbolt interfaces still
>>>>> require a dongle with newer USB-c/Thuderbolt 3 computers I’d probably
>>>>> hold off a little bit longer unless you really want to get rid of your
>>>>> 003.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Nov 20, 2018, at 3:20 PM, Nick Gawronski 
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi, I was holding off buying a new audio interface until I can get a
>>>>>> new mac with the USB type C ports and am looking at the 13 inch with
>>>>>> function keys and the highest ram and SSD storage.  For my inputs I
>>>>>> would like at least 4 if not more and I would

Re: VOCR issue - Image magic not found

[Chi Kim]

Hi Juan,


Can you download the latest commit and try again?

make sure to run both the installer and the script.

Also make sure the computer doesn't go to sleep during running the 
script. It might take a while because it downloads the source codes for 
Tesseract and ImageMagick and compiles them.


Chi



On 11/26/2018 11:36 AM, Juan Pablo Culasso Alonso wrote:
> Hello,
> Just trying install VOCR but when I open the import macros after run the 
> install, a message says that: Image magic not found.
> Using OsX 10.14.
>
> Ideas?
>
> Thanks
> JP.
>

-- 
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: Function Keys With Touch Bar: Changed From good USB type C audio interface that is accessible as I need to buy a new mac

[Chi Kim]

Hi,


Please correct me if I' wrong. There might be a setting to change this 
behavior that I'm not aware of.

I think you can only use fn+1,2,3,etc (on the number row) only for 
VoiceOver function.

In other words, you can press fn+vo+2 (on the number row) to read the 
title of current window, but you can't press fn+2 (on the number row) to 
toggle slip mode in Pro Tools. You have to press fn key then find f2 key 
from the touch bar.

Please tell me I'm wrong, because this is very annoying.

Thanks,


Chi



On 11/20/2018 5:05 PM, Steve Martin wrote:
> The 15” MacBook pros only have the touch bar, however when using voiceover 
> you can press the FN key to use the normal number keys as Function keys. Also 
> VO+ the minus and plus keys will turn system volume up and down so you don’t 
> have to mess with the touch bar to use those either.
>
>> On Nov 20, 2018, at 3:47 PM, Nick Gawronski  wrote:
>>
>> Hi, The Digital 003 uses Firewire ports and I have not managed to locate
>> an adapter that ports Firewire to USB type C plugs.  Do most USB
>> interfaces work well with an USB type C adapter cable and do any of the 15
>> inch Mac laptops have the function keys or just the touch bars?  I want to
>> minimize the amount of things I have to connect to the system for editing
>> but if I needed to still use the Apple keyboard with the number pad I
>> could do that.  Nick Gawronski
>> On Tue, November 20, 2018 3:36 pm, Steve Martin wrote:
>>> Personally I’d opt for the 15” pro over the 13” pro laptop. The 15” pros
>>> has the advantage of quad or 6 pro processors and discrete graphics. That
>>> being said, There are very few actual USB-C interfaces on the market most
>>> of the USB-C interfaces are really just USB 2 interfaces with a USB-C
>>> cable to connect easily to the new computers. Given that you have a 003,
>>> and if pro tools is still your main DAW why not get the appropriate
>>> dongles so you can continue using the 003. Otherwise I’d advise a
>>> Thunderbolt interface wit along with the thunderbolt to Thunderbolt 3
>>> dongle. The only company I can think of off hand that actually makes a
>>> thunderbolt 3 interface is the Universal Audio Apollo. Which is a 2 in 2
>>> out interface with two mic/line combo jacks for the inputs. So since
>>> there is no actual USB-C interfaces and thunderbolt interfaces still
>>> require a dongle with newer USB-c/Thuderbolt 3 computers I’d probably
>>> hold off a little bit longer unless you really want to get rid of your
>>> 003.
>>>
>>>
>>>
>>>
 On Nov 20, 2018, at 3:20 PM, Nick Gawronski 
 wrote:


 Hi, I was holding off buying a new audio interface until I can get a
 new mac with the USB type C ports and am looking at the 13 inch with
 function keys and the highest ram and SSD storage.  For my inputs I
 would like at least 4 if not more and I would like the jacks to be
 combo XLR and quarter inch line in jacks.  I have been reading some
 mixed reviews on the new macs and see some good and not so good ones
 written.  As I also own a windows system and am not going to make my
 mac run both accessibility on windows 10 would be great for when I want
 to record on my windows system in good quality.  I am not into brands
 but good quality and if Pro Tools can run most of the interface like
 not using the built in effects or if they are easy to use I am ok with
 it.  Any good suggestions on what I should get?  I can probably spend
 max around $1000 on good quality hardware.  If anyone is interested in
 my Digi 003 which is in very good condition let me know I just want to
 upgrade now.  Nick Gawronski

 --
 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.

-- 
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.

Good Deal? Air Instrument Expansion Pack for $75.01

[Chi Kim]

Pluginboutique has an interesting sale. You need to buy Vacuum Pro first 
for $1.00.
https://www.pluginboutique.com/product/1-Instruments/4-Synth/1558-Vacuum-Pro-
Then you can upgrade to the full Expansion Pack by purchasing AIR 
Instrument Expansion Pack 3 COMPLETE UPGRADE for $75.01.
https://www.pluginboutique.com/product/1-Instruments/58-Inst-Bundle/2294-AIR-Instrument-Expansion-Pack-3-COMPLETE-UPGRADE-
The total will be $76.01.
Good deal?


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/d/optout.

Re: strange problem in protools

[Chi Kim]

Hi,


1. Press vo+space on the text field before you tapping with t. Also make sure 
Flo Tools inspector is off.

2. Go to View menu bar> main counter and make sure bars|beats is checked.

3. Since now your main counter is set to bars|beats, numpad 1 and 2 should move 
bar by bar. If not, open Pro Tools preference, go to operation tab, interact 
with transport, interact with numeric keypad mode, and make sure transport is 
selected.

4. Go to edit window, vo+space on Toolbar options menu button, and make sure 
transport and expanded transport are checked.


Chi

On 10/1/2018 1:38 PM, Luis Daniel Pérez wrote:
Hello friends! I'm happy with another question
It happens that I am about to create a new session to produce a song, and when 
I open it I find the first problem:
1. ProTools  do not detect the tap tempo, with the letter t.
2. The count reads me for minutes, seconds and milliseconds, and does not read 
me for bars, beats, samples or tics.
3. when I move with the 1 and 2 of the numeric keypad, it does not advance 
through bars !. and less when I move with the plus and minus sign of the 
numeric keypad for the nudge.
4. I can not edit the pre and post roll measures with f9 command and f10 command
what's going on? accidentally put another configuration that was not? I already 
tried to change it with command option f7 and f8 respectively, but nothing ... 
everything remains the same.
I hope that is solved because I can not make selections like that! confuses me 
in both the second: D
thanks for always answering all my questions
a hug
--
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: MacOS update

[Chi Kim]

Make sure to fully back up before adventuring to new MacOS. That way you can 
just restore it if you don't like it.
Other people might had different experience, but unfortunately El Capitan was 
the worst experience for me with Pro Tools. A lot of crashes and sluggishness. 
When a sited user used the same system, it never crashed, but when I use with 
VoiceOver, it frequently crashed.
I went back down to Yosemite, skipped El Capitan, and upgraded later when 
Sierra came out.

Chi

On 9/25/2018 9:19 AM, Rui Vilarinho wrote:
Hi!
1.  I just read the   Pro Tools Operating System Compatibility Chart  and it 
say that my Pro Tools 12.5.2 version is compatible with El Capitan 10.11.6.
In that case, would be safe to upgrade to El Capitan at least?

2. To  those on this list that have and use the 11rack and the MAudio ProFire 
2626 interfaces, any concerns  with the setup mention  above?

Thanks, Rui Vilarinho



- Original Message - From: "Dammie Onafeko" 

To: 
Sent: Saturday, September 22, 2018 3:36 AM
Subject: Re: MacOS update


Hey!

I'm glad to let you know that you can't upgrade your Mac OS because of
the version of your Protools. Neither Ciara nor iCiara is compatible
with your ProTools 12.5 so be careful to embrace what you have there.
Otherwise you'll have to upgrade your proTools, which will cost you at
least $300. That's my 2cents.
Dammie
.

On 9/21/18, Rui Vilarinho 
 wrote:
Hi,
My MacPro Late 2013, 3.5 gigahertz 6core intel iz5, 16 giga RAM  and so on,
still has  the OSX Yosemite 10.10.5.
My Pro Tools version still is the 12.5.2.511.
On my Apple store updates list, only  has got the MacOS High  Sierra.
Concerning the Mac Pro specks  mentioned above  can   I update to to MacOS
High  Sierra?
 Without   losing  Voice Over accessibility to  the  12.5.2.511  Pro Tools
version?
I also have concerns about the Avid 11Rack  and the  MAudio Profire 2626
interfaces, since both are discontinued peryferals. They work fine with the

specks  mencioned above though.
If the MacOS High Sierra still  isnt recommended should I update do Sierra
only?

• I   just found that exist  a Sierra MacOS  and a High Sierra MacOS!
Diferent stuff...  grin. And   I was just  away for 2 years!

Thank you in advance,
Rui Vilarinho

--
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: VOCR Update

[Chi Kim]

Hey Mike,


I'm glad that it's working out for you.

Spread the news!


Chi



On 7/12/2018 10:07 AM, Michael Holmes wrote:
> I just downloaded and installed this, and I’m amazed! I was just asking the 
> Vermont tech trainer if he knew of anything like this, and he didn’t. Thank 
> you so much, Chi!
>
>
> Mike
>
> Sent from my iPhone
>
>> On Jul 10, 2018, at 20:48, Chi Kim  wrote:
>>
>> Hi All,
>>
>>
>> There's a small minor update to VOCR.
>>
>> When you're done exploring the OCR result, pressing escape will disable
>> next/previous line/words to  free up those 4 shortcuts.
>>
>> You can just run install vocr macros app to get this feature, but you
>> might also want to run install command script and update Tesseract if
>> you haven't updated Tesseract for a while.
>>
>> The new Tesseract has a new OCR engine based on LSTM neural networks. I
>> couldn't tell much, but it's supposed to be faster and produce better
>> result.
>>
>> Lastly, don't forget to rename OCR Front Windows 27 appropriately.
>>
>> Here's the download link.
>>
>> https://github.com/chigkim/VOCR/archive/master.zip
>>
>> Enjoy,
>>
>>
>> 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/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: Flo Mouse and Flo Tools, Changed from VOCR Update

[Chi Kim]

Hi Steve,


No worries! :)


Chi


On 7/12/2018 7:32 AM, Steve Matzura wrote:
> Ya know, I read that message after I sent it, and if I could've pulled 
> it back out of the ether, I would have. Sorry for the confusion on my 
> part. I really don't know how or why I wrote that and let it out! I 
> musta been smokin' some serious trash! :-)
>
>
> On 7/11/2018 6:01 AM, Chi Kim wrote:
>> Hi Steve,
>>
>>
>> Flo Mouse and VOCR are not related, but the answer to your question 
>> is yes.
>>
>>
>> Chi
>>
>>
>>
>> On 7/11/2018 3:05 AM, Steve Matzura wrote:
>>> I remember the last thing I read about FlowTools was that FlowMouse
>>> installation was not active, and those who wanted it needed to
>>> download and install it separately. Is that still the case?
>>>
>>>
>>> On 7/10/2018 8:48 PM, Chi Kim wrote:
>>>> Hi All,
>>>>
>>>>
>>>> There's a small minor update to VOCR.
>>>>
>>>> When you're done exploring the OCR result, pressing escape will 
>>>> disable
>>>> next/previous line/words to  free up those 4 shortcuts.
>>>>
>>>> You can just run install vocr macros app to get this feature, but you
>>>> might also want to run install command script and update Tesseract if
>>>> you haven't updated Tesseract for a while.
>>>>
>>>> The new Tesseract has a new OCR engine based on LSTM neural 
>>>> networks. I
>>>> couldn't tell much, but it's supposed to be faster and produce better
>>>> result.
>>>>
>>>> Lastly, don't forget to rename OCR Front Windows 27 appropriately.
>>>>
>>>> Here's the download link.
>>>>
>>>> https://github.com/chigkim/VOCR/archive/master.zip
>>>>
>>>> Enjoy,
>>>>
>>>>
>>>> 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/d/optout.

Re: Flo Mouse and Flo Tools, Changed from VOCR Update

[Chi Kim]

Hi Steve,


Flo Mouse and VOCR are not related, but the answer to your question is yes.


Chi



On 7/11/2018 3:05 AM, Steve Matzura wrote:
> I remember the last thing I read about FlowTools was that FlowMouse 
> installation was not active, and those who wanted it needed to 
> download and install it separately. Is that still the case?
>
>
> On 7/10/2018 8:48 PM, Chi Kim wrote:
>> Hi All,
>>
>>
>> There's a small minor update to VOCR.
>>
>> When you're done exploring the OCR result, pressing escape will disable
>> next/previous line/words to  free up those 4 shortcuts.
>>
>> You can just run install vocr macros app to get this feature, but you
>> might also want to run install command script and update Tesseract if
>> you haven't updated Tesseract for a while.
>>
>> The new Tesseract has a new OCR engine based on LSTM neural networks. I
>> couldn't tell much, but it's supposed to be faster and produce better
>> result.
>>
>> Lastly, don't forget to rename OCR Front Windows 27 appropriately.
>>
>> Here's the download link.
>>
>> https://github.com/chigkim/VOCR/archive/master.zip
>>
>> Enjoy,
>>
>>
>> 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/d/optout.

VOCR Update

[Chi Kim]

Hi All,


There's a small minor update to VOCR.

When you're done exploring the OCR result, pressing escape will disable 
next/previous line/words to  free up those 4 shortcuts.

You can just run install vocr macros app to get this feature, but you 
might also want to run install command script and update Tesseract if 
you haven't updated Tesseract for a while.

The new Tesseract has a new OCR engine based on LSTM neural networks. I 
couldn't tell much, but it's supposed to be faster and produce better 
result.

Lastly, don't forget to rename OCR Front Windows 27 appropriately.

Here's the download link.

https://github.com/chigkim/VOCR/archive/master.zip

Enjoy,


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/d/optout.

Re: logic with speech podcast.

[Chi Kim]

Hi All,


This is a cross-posting.

http://accessmtech.com

I just started working on a website that will archive various informal/formal 
resources related to accessible music technology.

There are many tutorials out there individuals produced. Unfortunately those 
disappeared shortly after.

With each author's permission, the plan is to post them on Youtube or 
Soundcloud which will hopefully stay for a while.

If a tutorial is already posted theirs on Youtube or Soundcloud, I can just 
link it to the website.

Right now, I only have a couple of tutorials for Pro Tools and Logic, but I'll 
keep adding them as soon as I can.

I'll also add samplitude, reaper, Sibelius, and so on.

If you know any other resource that I should add, please let me know who to 
contact.

Thanks!


Chi



On 3/3/2018 7:22 PM, Garth Humphreys wrote:
Hi guys
I currently have a podcast hosted on Libsyn that is specific to Reaper but on 
seeing this post, wondered how people would feel about having a single podcast 
feed for any tutorials about accessible DAW. Libsyn is a dedicated media host 
and I would be happy to put the actual media files there. That way it really 
doesn’t matter how many downloads of the podcasts files there are. The actual 
website could be hosted as discussed below, but hosting podcast media files on 
a web host isn’t generally a good idea.
Separate iTunes feeds can still exist for the different categories, such as 
Reaper or Logic, but people could also subscribe to a single Accessible DAW 
podcast feed. Hopefully we could get some tutorials on other DAW as well.
Just an idea anyway.
Thanks
Garth


On 1 Mar 2018, at 6:04 am, Devin Oxman 
> wrote:

Hey Robin,
I'm new to the group, but would be happy to host the logicwithspeech site as I 
think it is a useful resource. I've got a linode instance where I host a few 
sites, and if the traffic is moderate I'd be happy to setup the site there. 
Have you any logs on the average site traffic over the months wile it was up?
Anyway, I've tweeted you as well about this so you can get back to me in either 
place.
Devin

On Tuesday, 27 February 2018 15:58:10 UTC-5, Robin Kipp wrote:
Hey all,

sorry for my late response to this thread, been pretty busy over the past few 
days and so it took me a while to catch up with the list.

Basically, I was the one hosting the website and Podcast.

All the content was hosted on my home server, using my home internet connection.

Unfortunately, due to some issues related to my ISP, I’ve had to temporarily 
take it down as of November last year.

That didn’t seem like a big deal to me at first glance, as the website really 
wasn’t getting any visits, and the few that did come in were search engine bots 
crawling the site.
However, I’m really sorry for all of you who have attempted to stream podcast 
episodes, the reason why that’s currently not working is because they are still 
cached in iTunes, but the actual files are currently no longer available to 
download.

I most definitely would love to bring it back if there’s still interest in the 
website, however I currently do not have a web hosting package with enough 
storage space.
However, I still have the archive containing all the files, as well as the 
MySQL database that are necessary in order for the website to function, plus I 
still have the domain name logicwithspeech.com 
registered.

I can try to figure out a more permanent hosting solution, but if there’s 
anybody here on this list with an active hosting package, sufficient disk space 
(around 400MB), MySQL and PHP support, I’d be happy to hand over all the 
necessary files and have the domain name transferred.

The site was entirely built using WordPress, so any web host supporting that 
would be a suitable option.

So, if anybody is interested in doing this and could provide the necessary 
resources, that would be absolutely fantastic!

Many thanks, and once again sorry to all of you who have had trouble accessing 
the site or the Podcast.

Robin
Am 27.02.2018 um 20:54 schrieb Cara Quinn :

Hey Andre et al.

this is a great interim solution but do we know why these issues are happening?

Not sure who is managing the cast on iTunes but is there anything any of us can 
do to help?

Thanks a bunch and Cheers!

Cara
---
iOS design and development - LookTel.com
---
View my Online Portfolio at:

http://www.onemodelplace.com/models/Cara-Quinn

Follow me on Twitter!

https://twitter.com/ModelCara

On Feb 27, 2018, at 12:29 PM, 'Andre Louis' via Logic Accessibility 
 wrote:

Most of these tutorials are in VO Logic Dropbox. If you want me to add your 
email to it, or if you don't have that space, I can just send the dropbox link, 
let me know.
Thanks.

- Original Message - From: "Rodrigo Poblete Venthur" 

To: 

Re: Dropbox question

[Chi Kim]

My suspicion that it's because all MacOS, Android, and iOS are Linux based.

Just speculating, but that particular folder must have either some 
character in its name not permitted in Windows, or properties that are 
not allowed in Windows.


Chi



On 3/6/2018 8:11 AM, Martin (Punky) Sopart wrote:
> Yes, but why?
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Phil Muir
>> Sent: Tuesday, March 6, 2018 1:52 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: Dropbox question
>>
>> What is fascinating about this is those folders not showing up on Windows
>> but they do also show up on Android.
>>
>>
>> On 6 March 2018 12:47:38 GMT+00:00, Chi Kim <chigook...@hotmail.com>
>> wrote:
>>
>>  Martin,
>>
>>
>>  Iphone is the correct one.
>>
>>  Accessmtech.com has all the tutorials from Dropbox under the Pro
>> Tools
>>  category.
>>
>>  Except one for iLok license manager which is under other category.
>>
>>  Chi
>>
>>  On 3/6/2018 5:17 AM, Martin (Punky) Sopart wrote:
>>
>>   Hello all!
>>
>>   When browsing the PT Access Dropbox folder with the
>> iPhone app, the first
>>   sub folder ist the one named "Demos, Tutorials etc".
>>   Doing the same under Windows, the "Demos..." sub folder is
>> not there.
>>
>>   Which version is the correct one?
>>
>>   Thanks in advance and best! / Martin
>>
>>
>>
>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>> --
>> 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
>> <mailto: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: Dropbox question

[Chi Kim]

Martin,


Iphone is the correct one.

Accessmtech.com has all the tutorials from Dropbox under the Pro Tools 
category.

Except one for iLok license manager which is under other category.

Chi

On 3/6/2018 5:17 AM, Martin (Punky) Sopart wrote:
> Hello all!
>
> When browsing the PT Access Dropbox folder with the iPhone app, the first
> sub folder ist the one named "Demos, Tutorials etc".
> Doing the same under Windows, the "Demos..." sub folder is not there.
>
> Which version is the correct one?
>
> Thanks in advance and best! / Martin
>
>

-- 
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.

Please Check Out AccessMTech.com

[Chi Kim]

Hi All,

AccessMTech.com is online. Please check it out.
http://accessmtech.com
Accessible Music Tech is a place where people can find various resources 
and share their expertise.
Besides compiling good resources in one place, another goal of this site 
is to archive resources in case of original source disappear.
I upload everything to Youtube, so they will last as long as Youtube 
survives.
Now I have about 40 tutorials up for Logic, Pro Tools, Reaper, and 
others. If you click each category, you'll see important links such as 
scripts and discussion platforms at the top, and the related tutorials 
below.
By the way, the categories, except Other, are simply listed in 
alphabetical order, and the tutorials are listed in order of their 
posted dates.
There are few tutorials in the Dropbox that I have not uploaded yet. 
They will be there shortly.
I just spend entire this weekend rushing through everything, so there 
might be some broken links or incorrect information. Please let me know 
if you find something to fix.
A few things for house keeping...
If you put a tutorial in a dropbox, please send an email to the 
appropriate list and cc accessmt...@gmail.com. I'll put it up on the 
site for people not in the Dropbox.
Since there are so many discussion platforms and website, it's 
impossible for me to keep up with everything. Please help me to improve 
the site by
1. sending me emails where to find other resources and who to contact 
for permission.
2. Let me know if you know how to manage Wordpress and want to help with 
editing and managing the web page content.
3. Let me know if there are things to fix, add, or remove.
Last but not least, a huge thanks everyone who produced the tutorials!
Enjoy,

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/d/optout.

Re: Cannot enable VoiceOver to be controlled with Apple script

[Chi Kim]

HI Christian,


Create another admin user under users and groups from system preference, 
login to the new user, run VoiceOver, and see if it'll let you check it.

If it does, that means something got messed up with current user setting.

You could also Send an email to apple accessibility, and see what they say.

Keep us posted.


Chi
On 2/14/2018 1:51 PM, Christian wrote:
> Hi all,
>
> OK, so I tried this but still no luck. Running OS High Sierra. This is really 
> annoying.
> I don’t like to reinstall everything and  startover.
> Any other tips?
> Many thanks,
> Christian
>
>> 14 feb. 2018 kl. 08:54 skrev Chi Kim <chigook...@hotmail.com>:
>>
>> If uncheck and checking it doesn't fix the issue, reset all Voiceover
>> preferences by:
>>
>> Open up voiceover utility
>>
>> go to menu bar with vo+m
>>
>> go to file menu
>>
>> Select reset all voiceover preference.
>>
>> Go back to the general category and see if it lets you check allow
>> VoiceOVer to be controlled with AppleScript
>>
>>
>> Chi
>>
>>
>>
>> On 2/13/2018 8:33 PM, Slau Halatyn wrote:
>>> This was a rare issue for a couple of people and it seemed to exist in High 
>>> Sierra but, if you uncheck and recheck the checkbox, supposedly it sorts 
>>> itself out. Perhaps it's worth a try.
>>> Slau
>>>
>> -- 
>> 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: Cannot enable VoiceOver to be controlled with Apple script

[Chi Kim]

If uncheck and checking it doesn't fix the issue, reset all Voiceover 
preferences by:

Open up voiceover utility

go to menu bar with vo+m

go to file menu

Select reset all voiceover preference.

Go back to the general category and see if it lets you check allow 
VoiceOVer to be controlled with AppleScript


Chi



On 2/13/2018 8:33 PM, Slau Halatyn wrote:
> This was a rare issue for a couple of people and it seemed to exist in High 
> Sierra but, if you uncheck and recheck the checkbox, supposedly it sorts 
> itself out. Perhaps it's worth a try.
> Slau
>

-- 
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: problems using flotools 2.3.2

[Chi Kim]

It seems like you have the inspector on.

If you have the inspector on, you won't be able to type numbers because 
they are shortcuts to check inserts.

Turn off the inspector with slash, make sure VO says inspector off.

Then try it.


Chi



On 2/12/2018 12:52 AM, John Covici wrote:
> I did run it again and no joy.  One thing I notice, when I hit the :
> character, it says 0 where it did not do that before -- but at the end
> it is not changing the value or its putting all 0's in.
>
> On Sun, 11 Feb 2018 18:22:40 -0500,
> Slau Halatyn wrote:
>> If you still have the installer for 2.3.2, run it again. It'll delete 
>> whatever is needed and install new macros from scratch. Keep us posted.
>>
>>> On Feb 11, 2018, at 6:16 PM, John Covici  wrote:
>>>
>>> It worked fine with the previous version of flotools 2.3.1, so
>>> something has changed.  Perhaps I will uninstall everything but the
>>> global group and download and reinstall.  Should I redownload the
>>> mouse ones or what is the best way to get rid of everything and
>>> reinstall?
>>>
>>> On Sun, 11 Feb 2018 18:02:48 -0500,
>>> Slau Halatyn wrote:
 Hmm… Yeah, it works for others so it's a problem on your system that could 
 be any number of things. Did you delete the macro groups mentioned in the 
 Flo Tools Read Me? Sounds like there might possibly be a problem there but 
 I'm not sure. It's the kind of thing where you have to start at the top 
 and verify that all steps were followed. Did it ever work for you? If it 
 did and now it's not, something has clearly changed and I can't begin to 
 guess what that might be.
> On Feb 11, 2018, at 3:44 PM, John Covici  wrote:
>
> That did not work with the new version of flotools, it did work if I
> disabled keyboard maestro -- very strange.
>
> On Sun, 11 Feb 2018 14:04:04 -0500,
> Slau Halatyn wrote:
>> Let's eliminate variables. If you're using an extended keyboard, press 
>> the slash key, type a value on the num pad and press Enter on the num 
>> pad. Make sure you're in the Edit window. Let's see if that works first.
>>> On Feb 11, 2018, at 2:08 AM, John Covici  wrote:
>>>
>>> Hi.  I am having a problem trying to use the new flotools 2.3.2.  When
>>> I try to enter a start value, it gives me the noise, but does not
>>> enter the value.  I hear 0 a couple of times during the entry, which I
>>> never did before.  It does not work, even if I use the / key on the
>>> numpad instead.  However, if I disable the keyboard Maestro engine I
>>> can use the / on the numpad to enter the  start time.  It did not work
>>> with pt 12.8.3 and so I downloaded 2018.1, but no joy.
>>>
>>> Thanks in advance for any suggestions.
>>>
>>> -- 
>>> Your life is like a penny.  You're going to lose it.  The question is:
>>> How do
>>> you spend it?
>>>
>>>John Covici wb2una
>>>cov...@ccs.covici.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+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.
> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
>
> John Covici wb2una
> cov...@ccs.covici.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+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.

>>> -- 
>>> Your life is like a penny.  You're going to lose it.  The question is:
>>> How do
>>> you spend it?
>>>
>>>  John Covici wb2una
>>>  cov...@ccs.covici.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 
>>> 

Re: Protools vs Logic Pro, accessibility and productivity

[Chi Kim]

Hi All,

Interesting thread!
First, let me clarify some of the things mentioned about me.
My main DAW is Logic as Slau mentioned. I'm forced to use Logic because 
my main collaborators use Logic. I also developed Flogic which is no 
where close to Flo Tools yet.
Having said that, I mainly teach Pro Tools at Berklee, and I have a 
certification for Pro Tools.
I'm mostly experienced in Logic, Pro Tools, and Sonar, but I briefly 
dabbled with Reaper and Samplitude as well.
Now, I'll just get to the point.
If you're purely talking about accessibility for DAWs in Mac, Pro Tools 
with Flo Tools is the winner without a doubt.
I can point out many reasons, but one thing I don't like about logic is 
that I have to waste time fussing with flaky user interface when using 
with VoiceOver.
Also, I think the interface for Pro Tools is much efficient for 
VoiceOver users in general. In Logic, ask someone to select 8 bars from 
bar 5 for track 1, 3, 5, and paste to track 6, 8, 10 using VoiceOver.
In short, if you have a choice, I would definitely recommend to use Pro 
Tools as main DAW, and supplement with Logic for some of its cool features.
Hope that helps.

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/d/optout.

Re: Flo Tools 2.3 is out

[Chi Kim]

Yes, I use KM8, but I test with KM7 as well. Both should work.


Chi



On 11/12/2017 12:43 PM, Martin (Punky) Sopart wrote:
> Hello Chi!
>
> Thanks for answering.
>
> When launching the 2.2 uninstaller HighSierra reported that I should move 
> this app into the trash, because it is corrupted.
> I did so and went over to the newer uninstaller of version 2.3.
> Further I deleted all FloTools macro groups in the KM editor.
>
> Do you also use the newest update of KM?
>
> Best! / Martin
>
>
> Am 12.11.2017 um 18:35 schrieb Chi Kim <chigook...@hotmail.com>:
>
> Hi Martin,
>
>
> I just followed the exact process you described on three computers
> including one with fresh High Sierra installed:
>
> Install Flo Tools 2.2
>
> Uninstall Flo Tools 2.2
>
> Install Flo Tools 2.3.0
>
> I did not get any error.
>
> I suspect that there's something going on with your particular system.
>
> I'm told that Rocco is helping you with the problem.
>
> Hopefully you can sort it out quickly.
>
> Keep us posted.
>
>
> Chi
>
>
>
> On 11/12/2017 11:49 AM, Martin (Punky) Sopart wrote:
>> Hello Slau!
>>
>> That important information should have been prompted in the uninstaller 
>> *lol* :-)
>> Perfect timing, because I have to finish my project…
>> The release date is in a few days.
>>
>> Don’t tell me, never touch a running system. I was hoping to save some time 
>> when using the new FloTools.
>>
>> Best regards and thanks for answering! / Martin
>>
>>
>> Am 12.11.2017 um 17:40 schrieb Slau Halatyn <slauhala...@gmail.com>:
>>
>> Hi Martin,
>> We're working on the problem but let me say that you should not run the 
>> uninstaller unless you are not going to install Flo Tools again. Forget the 
>> uninstaller and always just run the installer.
>> Cheers,
>> Slau
>>
>>> On Nov 12, 2017, at 10:51 AM, Martin (Punky) Sopart <m...@cakewalker.de> 
>>> wrote:
>>>
>>> And I was able to install Flo Mouse without any problem.
>>> Only the FloTools installers get that error 76.
>>>
>>> Best and sorry for all that traffic! / Martin
>>>
>>>
>>> Am 12.11.2017 um 16:45 schrieb Martin (Punky) Sopart <m...@cakewalker.de>:
>>>
>>> Hello!
>>>
>>> The FloTools-2.3 uninstaller could be executed  without any error.
>>> But all of the FloTools installers now get the error 76.
>>>
>>> What could I do to get at least an older version of FloTools running?
>>>
>>> Interesting…
>>> When trying to uncheck the checkbox for allowing to control VoiceOver via 
>>> Apple Script, the status not really changes.
>>> Maybe here  something is wrong.
>>> Running HighSierra.
>>>
>>> Best! / Martin
>>>
>>> Am 12.11.2017 um 16:11 schrieb Martin (Punky) Sopart <m...@cakewalker.de>:
>>>
>>> Hello all!
>>>
>>> I uninstalled FloTools 2.2 and started the new installer of FloTools-2.3.
>>> After accepting the first two dialogs error 76 occurs.
>>>
>>> Pro Tools 12.8.1 and the latest version of KM.
>>>
>>> Any ideas?
>>>
>>> Thanks! / Martin
>>>
>>>
>>> Am 12.11.2017 um 04:57 schrieb Slau Halatyn <slauhala...@gmail.com>:
>>>
>>> What's New in Flo Tools 2.3
>>>
>>> As always, the Flo Tools Team has been thinking of ways to make your use of 
>>> Pro Tools easier and more efficient. Often, these are simple things that 
>>> make a huge difference. Flo Tools 2.3 introduces a few such features. In 
>>> fact, they're so simple that besides  foregoing the mp3 demonstration, we 
>>> even considered releasing the new version without a "What's New" and have 
>>> our users discover the new features by surprise but then where's the fun in 
>>> that?
>>>
>>> OK, so if you'd rather be surprised by the new features, feel free to skip 
>>> the rest of these scintillating paragraphs and stumble across things on 
>>> your own but, if you want a heads up on what to expect, read on.
>>>
>>> 1. You probably remember when Pro Tools users applauded the long-overdue 
>>> built-in shortcuts for switching between playlists on selected tracks. 
>>> Shift+up or down arrow is a great time-saver, to be sure. In Flo Tools 2.3, 
>>> VoiceOver will now automatically speak the name of the newly selected 
>>> playlist. If multiple tracks are selected and playlists chan

Re: Flo Tools 2.3 is out

[Chi Kim]

Hi Martin,


I just followed the exact process you described on three computers 
including one with fresh High Sierra installed:

Install Flo Tools 2.2

Uninstall Flo Tools 2.2

Install Flo Tools 2.3.0

I did not get any error.

I suspect that there's something going on with your particular system.

I'm told that Rocco is helping you with the problem.

Hopefully you can sort it out quickly.

Keep us posted.


Chi



On 11/12/2017 11:49 AM, Martin (Punky) Sopart wrote:
> Hello Slau!
>
> That important information should have been prompted in the uninstaller *lol* 
> :-)
> Perfect timing, because I have to finish my project…
> The release date is in a few days.
>
> Don’t tell me, never touch a running system. I was hoping to save some time 
> when using the new FloTools.
>
> Best regards and thanks for answering! / Martin
>
>
> Am 12.11.2017 um 17:40 schrieb Slau Halatyn :
>
> Hi Martin,
> We're working on the problem but let me say that you should not run the 
> uninstaller unless you are not going to install Flo Tools again. Forget the 
> uninstaller and always just run the installer.
> Cheers,
> Slau
>
>> On Nov 12, 2017, at 10:51 AM, Martin (Punky) Sopart  
>> wrote:
>>
>> And I was able to install Flo Mouse without any problem.
>> Only the FloTools installers get that error 76.
>>
>> Best and sorry for all that traffic! / Martin
>>
>>
>> Am 12.11.2017 um 16:45 schrieb Martin (Punky) Sopart :
>>
>> Hello!
>>
>> The FloTools-2.3 uninstaller could be executed  without any error.
>> But all of the FloTools installers now get the error 76.
>>
>> What could I do to get at least an older version of FloTools running?
>>
>> Interesting…
>> When trying to uncheck the checkbox for allowing to control VoiceOver via 
>> Apple Script, the status not really changes.
>> Maybe here  something is wrong.
>> Running HighSierra.
>>
>> Best! / Martin
>>
>> Am 12.11.2017 um 16:11 schrieb Martin (Punky) Sopart :
>>
>> Hello all!
>>
>> I uninstalled FloTools 2.2 and started the new installer of FloTools-2.3.
>> After accepting the first two dialogs error 76 occurs.
>>
>> Pro Tools 12.8.1 and the latest version of KM.
>>
>> Any ideas?
>>
>> Thanks! / Martin
>>
>>
>> Am 12.11.2017 um 04:57 schrieb Slau Halatyn :
>>
>> What's New in Flo Tools 2.3
>>
>> As always, the Flo Tools Team has been thinking of ways to make your use of 
>> Pro Tools easier and more efficient. Often, these are simple things that 
>> make a huge difference. Flo Tools 2.3 introduces a few such features. In 
>> fact, they're so simple that besides  foregoing the mp3 demonstration, we 
>> even considered releasing the new version without a "What's New" and have 
>> our users discover the new features by surprise but then where's the fun in 
>> that?
>>
>> OK, so if you'd rather be surprised by the new features, feel free to skip 
>> the rest of these scintillating paragraphs and stumble across things on your 
>> own but, if you want a heads up on what to expect, read on.
>>
>> 1. You probably remember when Pro Tools users applauded the long-overdue 
>> built-in shortcuts for switching between playlists on selected tracks. 
>> Shift+up or down arrow is a great time-saver, to be sure. In Flo Tools 2.3, 
>> VoiceOver will now automatically speak the name of the newly selected 
>> playlist. If multiple tracks are selected and playlists change, VoiceOver 
>> will speak the name of each new playlist sequentially. Of course, you can 
>> always interrupt speech at any time with the Control key.
>>
>> 2. Along similar lines, Flo Tools 2.3 adds feedback for when the track 
>> selection changes. when using the Control+p or Control+semicolon shortcuts 
>> to move the track selection up or down, VoiceOver now automatically speaks 
>> the name of the newly selected track. Cool, no? Of course it is. You know 
>> what's even cooler? Well...
>>
>> 3. All of the cool kids know that holding down the Shift key while using 
>> Control+p or semicolon extends the selection through adjacent tracks. Well, 
>> now that VoiceOver speaks the newly selected tracks as the selection moves 
>> from track to track, when the selection is extended, VoiceOver now speaks 
>> the number of tracks being selected and says the name as they're being 
>> selected. Now, is that cool enough for you? Wait, it actually does get 
>> cooler...
>>
>> 4. Apparently there are kids who are even cooler than the aforementioned 
>> cool kids. These cooler kids are quite familiar with the Pro Tools shortcut 
>> for retracting a selection from the top or bottom of a group of selected 
>> tracks. Control+Option+p or semicolon respectively retracts the selection 
>> from the top or bottom of a series of selected tracks. If you're using 
>> Control+Option as the VoiceOver keys, remember to press Control+Option+Tab 
>> to pass through the shortcuts. Once passed through, when the selection is 
>> retracted, VoiceOver 

Re: Flotools - upgrading issues.

[Chi Kim]

If you file an issue on Github with a report for that macro, I'll check 
it out.

Readme explains how to generate a report.


Chi




On 9/2/2017 2:22 PM, Juan Pablo Culasso Alonso wrote:
> Just nothing, because the message when I resize the clips list
>
> Clips table is 96 points wide. Click and drag to resize.
>
>
> Does not come up when I press the sorcut to resize the tracklist.
> Just for clarification, the track list is vissible.
>
> Thanks,
> JP.
>> On 2 Sep 2017, at 15:14, Slau Halatyn <slauhala...@gmail.com> wrote:
>>
>> HI JP,
>> After you issue the Command+Control+Shift+t macro, exactly what are you 
>> doing after that?
>>
>> Slau
>>
>>> On Sep 2, 2017, at 1:41 PM, Juan Pablo Culasso Alonso <jpcula...@gmail.com> 
>>> wrote:
>>>
>>> Hello Chi.
>>> After uninstall flotools, delete all in keyboard maestro and reinstall 
>>> flotools again,
>>> The only macro that is not working for me now is resizing the track list.
>>> Control+shift+command+t
>>>
>>> JP
>>>> On 2 Sep 2017, at 14:31, Chi Kim <chigook...@hotmail.com> wrote:
>>>>
>>>> Juan, how does it not work. Need more information.
>>>>
>>>> As far as shortcut conflicts, it seems like you manually changed
>>>> something before.
>>>>
>>>> Flo Tools Mouse uses modifiers command+option+shift.
>>>>
>>>> All other shortcuts you mentioned use command+control_+shift, it uses
>>>> control instead of option.
>>>>
>>>> If it gives you list of commands when you execute a macro, that means
>>>> there's shortcut conflict. Keyboard Maestro doesn't know which one you
>>>> meant to execute because there are more than one commands with the same
>>>> shortcut.
>>>>
>>>> However, there shouldn't be shortcut conflict in Flo Tools unless you
>>>> changed something. I just confirmed it.
>>>>
>>>> However, if you use VOCR there is some conflicts.
>>>>
>>>>
>>>> Chi
>>>>
>>>> On 9/1/2017 6:51 PM, Juan Pablo Culasso Alonso wrote:
>>>>> Hello,
>>>>> I unistalled (again) Flotools, opened keyboard maestro, deleted the 
>>>>> residual marcos, reinstalled flotools. Now almost looks fine exceptin the 
>>>>> track resizing macro.
>>>>>
>>>>> Best,
>>>>> Juan.
>>>>>
>>>> -- 
>>>> 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.

-- 
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: Flotools - upgrading issues.

[Chi Kim]

Juan, how does it not work. Need more information.

As far as shortcut conflicts, it seems like you manually changed 
something before.

Flo Tools Mouse uses modifiers command+option+shift.

All other shortcuts you mentioned use command+control_+shift, it uses 
control instead of option.

If it gives you list of commands when you execute a macro, that means 
there's shortcut conflict. Keyboard Maestro doesn't know which one you 
meant to execute because there are more than one commands with the same 
shortcut.

However, there shouldn't be shortcut conflict in Flo Tools unless you 
changed something. I just confirmed it.

However, if you use VOCR there is some conflicts.


Chi

On 9/1/2017 6:51 PM, Juan Pablo Culasso Alonso wrote:
> Hello,
> I unistalled (again) Flotools, opened keyboard maestro, deleted the residual 
> marcos, reinstalled flotools. Now almost looks fine exceptin the track 
> resizing macro.
>
> Best,
> Juan.
>

-- 
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: SOme questions Regarding Flo tools and Protools IN general

[Chi Kim]

Ramy, it's reading minutes and seconds because your main counter is set 
to minutes seconds.

Go to view menu, main counter, and change to bars and beats.

I could be wrong, but numpad 1 and 2 will always change by either one 
bar or one second at a time depending on your main counter.

However, control+comma and control+period or numpad plus and numpad 
minus will change by your nudge value.
If you want to just navigate through by nudge value, make sure nothing 
is selected before using those commands. If something is selected, it'll 
actually move what's selected, so be careful.

Chi
On 8/17/2017 11:23 AM, Ramy Moustafa wrote:
> Hell all:
>
> After using FLo tools, I have some questions that hope I can find an answer.
> 1- with Cmd-f4, I can read the counter, but it reads it in minutes,
> can I read the counter in bars? like bar 1 beat 2 etc?
> 2- if I need to change my numpad 1 and 2, from moving by ticks to
> moving by mesures, a sited sound engineer told me that, in the edit
> window, in the edit claster, I can choose the I think Gred  view or
> something instead of slept, this means that it will move by mesures
> not by ticks or seconds.
> sorry if I can not express will but hope my question makes sense.
>
> 3- While moving between regents  inside a track, pressing tap and
> option tap is working, but some times, I press and don't know where am
> I, and don't know if I'm at the end of what, so how can I be sure that
> am at the end of my session?
> with the return key I can go to the start of the session, but to the
> end, what can I use?
>
> Thanks
>
>

-- 
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: Edits not working! Help please!

[Chi Kim]

One more thing...

Make sure insertion follows playback is not selected in edit window > Cursor 
Tool Cluster > Insertion Follows Playback.

Otherwise, you'll lose your selection during playback.


Chi
On 8/15/2017 11:22 AM, Chi Kim wrote:

Hi Jesse,


Here is a list of things to check. Go through each item and double check even 
though you checked it before.

1. Options> Link Timeline and Edit Selection

2. Options > Link k Track and and Edit Selection
3. Edit window, interact with Track, make sure wave form for audio track and 
clips for midi/instrument track is selected for track view selector.
4. Interact with Track list table and deselect and reselect the track to edit 
even though Voiceover says it's selected.
5. This part is not necessary, but solo the track you selected to make sure the 
content you want to edit is in fact on the track you selected. Also if the 
output of the track goes to a bus, you need to either solo or safe solo the aux 
track.
6. Make a selection and play edit with option+[ to make sure it play from the 
beginning of selection and stops at the end of selection automatically.
Hope that helps and keep us updated.

Chi

On 8/14/2017 11:55 PM, Jesse Kragiel wrote:
All that stuff is actually checked the way it's supposed to be. I can mute, 
solo, and do all those things in the track. If by scrubbing, you mean moving 
the shuttle, the answer is yes. I don't have a control surface, so I'm limited 
to scrubbing with the numpad. Definitely frustrating when something usually 
works until it doesn't! Lol!

Sent from my iPad

On Aug 14, 2017, at 10:54 PM, Slau Halatyn 
<slauhala...@gmail.com<mailto:slauhala...@gmail.com>> wrote:

Hi Jesse,

Truly, it could be a number of things and it's difficult to troubleshoot when 
one has to assume that a number of other things are set up correctly. For 
example, if "either "Link Timeline and Edit selection" or "Edit Selection 
Follows Track Selection" under the Options menu are not checked, it can cause a 
situation like yours. Also, if an insertion point doesn't exist within the 
track you're trying to edit (as might be the case if Edit and Track selection 
aren't linked), you could be editing an entirely different track and not be 
aware of it.

Have you tried scrubbing within the track? Is "Insertion Follows Scrub" checked 
in the Preferences? When scrubbing, do you hear audio? Are you only editing a 
single track or a few tracks at the same time? Are the tracks shown or are they 
hidden? I suppose if you saw the Track View Selector, the track would, of 
course, have to be shown but, you understand, I'm grasping at straws here…. Let 
me know.
Slau

On Aug 14, 2017, at 8:50 PM, Jesse Kragiel 
<jessekrag...@gmail.com<mailto:jessekrag...@gmail.com>> wrote:

I didn't try that. Thanks for the suggestion! I found the track view selector 
right after I posed the question. Even that didn't work. Idk what the prob with 
the file is. It's lame!

Sent from my iPhone

On Aug 14, 2017, at 8:35 PM, CHUCK REICHEL 
<soundpicturerecord...@gmail.com<mailto:soundpicturerecord...@gmail.com>> wrote:

Hi Jesse,
Have you tried to save session copy.
its under the file menu.
Thats where you export or  save session copy in.
You can check to only export selected tracks and its audio and basically  it 
exports the session to where you choose.
this save session copy in is used to  make a independent copy of the pt session 
to send out to other studios.
Then what i do is to quit pt and find that save copy in session and launch it.
Or just make a new pt session and try importing session data from that session.
Also Have you tried "committing" those tracks in that session?
BTW wave form and volume will be found in the edit window.
Talk soon
Talk soon
Chuck


On Aug 14, 2017, at 7:45 PM, Jesse Kragiel wrote:

Chuck, I've tried all those things. I've had this session at the office, and 
now trying to edit it at home. Both places have the same results.

Sent from my iPhone

On Aug 14, 2017, at 7:42 PM, CHUCK REICHEL 
<soundpicturerecord...@gmail.com<mailto:soundpicturerecord...@gmail.com>> wrote:

Hi Jesse,
I just had this happen yesterday again.
turn off VO & back on that sometimes clears up things.
Hide all the tracks then only show the tracks to edit.
What I always do if its a load of tracks is to make a group out of the tracks 
first, I use the pt default of  Mix-edit group.
When that group is active and it still don't edit relaunch the session.
If that  don't work quit pt and re launch.
Last ditch restart the box! :)
HTH
Chuck


On Aug 14, 2017, at 6:00 PM, Jesse Kragiel wrote:

Hello! I have a very mission-critical project I'm working on! When I go to make 
edits, nothing I try to delete deletes. I do it in the normal way...make a 
selection, then press the backspace key just as I always have, but nothing 
clears. If I undo the operation, it says "undo clea

Re: Edits not working! Help please!

[Chi Kim]

Hi Jesse,


Here is a list of things to check. Go through each item and double check even 
though you checked it before.

1. Options> Link Timeline and Edit Selection

2. Options > Link k Track and and Edit Selection
3. Edit window, interact with Track, make sure wave form for audio track and 
clips for midi/instrument track is selected for track view selector.
4. Interact with Track list table and deselect and reselect the track to edit 
even though Voiceover says it's selected.
5. This part is not necessary, but solo the track you selected to make sure the 
content you want to edit is in fact on the track you selected. Also if the 
output of the track goes to a bus, you need to either solo or safe solo the aux 
track.
6. Make a selection and play edit with option+[ to make sure it play from the 
beginning of selection and stops at the end of selection automatically.
Hope that helps and keep us updated.

Chi

On 8/14/2017 11:55 PM, Jesse Kragiel wrote:
All that stuff is actually checked the way it's supposed to be. I can mute, 
solo, and do all those things in the track. If by scrubbing, you mean moving 
the shuttle, the answer is yes. I don't have a control surface, so I'm limited 
to scrubbing with the numpad. Definitely frustrating when something usually 
works until it doesn't! Lol!

Sent from my iPad

On Aug 14, 2017, at 10:54 PM, Slau Halatyn 
> wrote:

Hi Jesse,

Truly, it could be a number of things and it's difficult to troubleshoot when 
one has to assume that a number of other things are set up correctly. For 
example, if "either "Link Timeline and Edit selection" or "Edit Selection 
Follows Track Selection" under the Options menu are not checked, it can cause a 
situation like yours. Also, if an insertion point doesn't exist within the 
track you're trying to edit (as might be the case if Edit and Track selection 
aren't linked), you could be editing an entirely different track and not be 
aware of it.

Have you tried scrubbing within the track? Is "Insertion Follows Scrub" checked 
in the Preferences? When scrubbing, do you hear audio? Are you only editing a 
single track or a few tracks at the same time? Are the tracks shown or are they 
hidden? I suppose if you saw the Track View Selector, the track would, of 
course, have to be shown but, you understand, I'm grasping at straws here…. Let 
me know.
Slau

On Aug 14, 2017, at 8:50 PM, Jesse Kragiel 
> wrote:

I didn't try that. Thanks for the suggestion! I found the track view selector 
right after I posed the question. Even that didn't work. Idk what the prob with 
the file is. It's lame!

Sent from my iPhone

On Aug 14, 2017, at 8:35 PM, CHUCK REICHEL 
> wrote:

Hi Jesse,
Have you tried to save session copy.
its under the file menu.
Thats where you export or  save session copy in.
You can check to only export selected tracks and its audio and basically  it 
exports the session to where you choose.
this save session copy in is used to  make a independent copy of the pt session 
to send out to other studios.
Then what i do is to quit pt and find that save copy in session and launch it.
Or just make a new pt session and try importing session data from that session.
Also Have you tried "committing" those tracks in that session?
BTW wave form and volume will be found in the edit window.
Talk soon
Talk soon
Chuck


On Aug 14, 2017, at 7:45 PM, Jesse Kragiel wrote:

Chuck, I've tried all those things. I've had this session at the office, and 
now trying to edit it at home. Both places have the same results.

Sent from my iPhone

On Aug 14, 2017, at 7:42 PM, CHUCK REICHEL 
> wrote:

Hi Jesse,
I just had this happen yesterday again.
turn off VO & back on that sometimes clears up things.
Hide all the tracks then only show the tracks to edit.
What I always do if its a load of tracks is to make a group out of the tracks 
first, I use the pt default of  Mix-edit group.
When that group is active and it still don't edit relaunch the session.
If that  don't work quit pt and re launch.
Last ditch restart the box! :)
HTH
Chuck


On Aug 14, 2017, at 6:00 PM, Jesse Kragiel wrote:

Hello! I have a very mission-critical project I'm working on! When I go to make 
edits, nothing I try to delete deletes. I do it in the normal way...make a 
selection, then press the backspace key just as I always have, but nothing 
clears. If I undo the operation, it says "undo clear" but nothing clears! The 
proper tracks are selected in the track table, but that's not helping. I've 
tried all the edit modes as well, but to no avail. Any help anyone could give 
would be appreciated. Thanks!
Jesse

--
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this 

Re: Flotools maximize mix and edit window command

[Chi Kim]

Hi Brian,


It's under Flo Tools Mouse in the readme.

"Zoom/Maximize Window: Command+Option+Shift+z"

You have to make sure mouse is on with command+slash. Then go to each 
window and press command+option+shift+z.

It's same as you vo+space on zoom. Nothing special.

Chi
On 8/15/2017 7:39 AM, Brian Howerton wrote:
> Hello folks,
> I have checked the flotools read me online for this, but can’t find this 
> command.  Thanks for the help,
> Brian
>

-- 
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: Velocity automation

[Chi Kim]

Stefan, did you mean volume automation, not velocity?

If you want to automate volume:

1. put the track into one of the automation modes that lets you 
modify/write automation data.

2. make sure volume is selected in the automation window.
3. move the volume fader using either control surface, Flo Tools, or 
Voiceover while the session is playing.
If you meant midi velocity, I can't think of ways to do automate that 
top of my head. You can change velocity for each note from event list 
window though.

Chi

On 8/11/2017 1:13 PM, Stefan Albertshauser wrote:
> Hi,
>
> How would you accomplish velocity automation? Sighted users use the pencil 
> tool. What can we do?
>
> Thanks in advance for an answer.
>
> Best
> Stefan
>

-- 
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: It's paramount! that I learn this task: Tempoing

[Chi Kim]

Go to the position where you want to insert a new tempo. Open tempo 
operation window with option numpad 2 and create a constant tempo. You 
can open it from the event operation menu as well.

Then it'll immediately jump to whatever tempo you created.

Watch out for the conductor.


Chi



On 8/8/2017 5:12 PM, Chris Smart wrote:
> so how do I insert a tempo change?
>
> At 02:48 PM 8/8/2017, you wrote:
>> I should have clarified.
>>
>> I don't need it to gradually slow down. I need it to directly go from 
>> that 84 to an immediate 64BPM. I don't need a slope/curve in the 
>> tempo, unless that's not, by curve, what you meant, at which point, 
>> my apology.
>> ---
>> Christopher Gilland
>> Co-founder of Genuine Safe Haven Ministries
>>
>> <http://www.gshministry.org>http://www.gshministry.org
>> (980) 500-9575
>> - Original Message -
>> From: <mailto:chigook...@hotmail.com>Chi Kim
>> To: <mailto:ptaccess@googlegroups.com>ptaccess@googlegroups.com
>> Sent: Tuesday, August 08, 2017 10:24 AM
>> Subject: Re: It's paramount! that I learn this task: Tempoing
>>
>> Chris, check out the tempo operation window.
>>
>> You can change the constant to different curves for tempo changes.
>>
>>
>> Chi
>>
>>
>>
>> On 8/8/2017 9:32 AM, Christopher-Mark Gilland wrote:
>>> Guys,
>>>
>>> I know this has been discussed before, but I'm seeming to not be 
>>> able to get this to work.
>>>
>>> Hopefully, one of you all can tell me step by step the process to 
>>> make this work.
>>>
>>> In ProTools, here's what we got going here.
>>>
>>> I've got the song She's Not Cryin' Anymore by Billy Ray Cyrus, which 
>>> I've arranged totally by hand from scratch.
>>>
>>> For those of you who don't know the structure of this song, it's OK. 
>>> I'm gonna explain, don't worry.
>>>
>>> The song is your basic slow country 4/4 signature song which I am 
>>> doing in the key of B mager. Don't ask why not C. That's irrelavent.
>>>
>>> Anyway, I'm doing the song with an 84BPM constant tempo. That is...
>>>
>>> Up until the very very last tag of the song. The ending where he 
>>> repeats the phrase:
>>>
>>> There's a smile upon her face, a new one takes my place, she's not 
>>> cryin' anymore.
>>>
>>> On the word any more, on more, specifically, the song ends by going 
>>> to the root chord which of corse is B, then to the 4, which is E, 
>>> then back down to a single held B chord to end the song.
>>>
>>> What happens here is once that bar hits, which is at bar 77, and 
>>> carries to the end of the song at bar 78, so basically, those last 
>>> two bars of the song, there is a retard. So, normally, again, the 
>>> song is at 84BPM. What I want is starting at bar 77, and finnishing 
>>> the whole rest of the session, I want the tempo to constantly drop 
>>> from the constant 84BPM down to 64BPM.
>>>
>>> Yes, I do have a click track in this song, and I have ProTools set 
>>> to give me a 2 bar count in. Note that this count in is not actually 
>>> recorded into the song. I'm using numpad 7 to turn on the click 
>>> track, then numpad 8 to toggle on the count in.
>>>
>>> Any help with this would be appreciated. In the long run, I'm gonna 
>>> have to teach my student how to do this. So, better I learn now, 
>>> before we get to that point, that way, I'm prepared.
>>>
>>> Chris.
>>> -- 
>>> 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 
>>> <mailto:ptaccess+unsubscr...@googlegroups.com>ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit 
>>> <https://groups.google.com/d/optout>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 
>> <mailto:ptaccess+unsubscr...@googlegroups.com>ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit 
>> <https://groups.google.com/d/optout>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 
>> <mailto:ptaccess+unsubscr...@googlegroups.com>ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit 
>> <https://groups.google.com/d/optout>https://groups.google.com/d/optout.
>
>
>
> 
> "There are two means of refuge from the miseries of life: music and 
> cats." - Albert Schweitzer

-- 
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: It's paramount! that I learn this task: Tempoing

[Chi Kim]

Chris, check out the tempo operation window.

You can change the constant to different curves for tempo changes.


Chi


On 8/8/2017 9:32 AM, Christopher-Mark Gilland wrote:
Guys,

I know this has been discussed before, but I'm seeming to not be able to get 
this to work.

Hopefully, one of you all can tell me step by step the process to make this 
work.

In ProTools, here's what we got going here.

I've got the song She's Not Cryin' Anymore by Billy Ray Cyrus, which I've 
arranged totally by hand from scratch.

For those of you who don't know the structure of this song, it's OK. I'm gonna 
explain, don't worry.

The song is your basic slow country 4/4 signature song which I am doing in the 
key of B mager. Don't ask why not C. That's irrelavent.

Anyway, I'm doing the song with an 84BPM constant tempo. That is...

Up until the very very last tag of the song. The ending where he repeats the 
phrase:

There's a smile upon her face, a new one takes my place, she's not cryin' 
anymore.

On the word any more, on more, specifically, the song ends by going to the root 
chord which of corse is B, then to the 4, which is E, then back down to a 
single held B chord to end the song.

What happens here is once that bar hits, which is at bar 77, and carries to the 
end of the song at bar 78, so basically, those last two bars of the song, there 
is a retard. So, normally, again, the song is at 84BPM. What I want is starting 
at bar 77, and finnishing the whole rest of the session, I want the tempo to 
constantly drop from the constant 84BPM down to 64BPM.

Yes, I do have a click track in this song, and I have ProTools set to give me a 
2 bar count in. Note that this count in is not actually recorded into the song. 
I'm using numpad 7 to turn on the click track, then numpad 8 to toggle on the 
count in.

Any help with this would be appreciated. In the long run, I'm gonna have to 
teach my student how to do this. So, better I learn now, before we get to that 
point, that way, I'm prepared.

Chris.
--
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: Asking once again about Meterring

[Chi Kim]

Chris,

Your friend must have something in the signal chain.
I just generated a sine wave with 0.5 amplitude on Audacity and exported to a 
wave file.
I imported into Pro Tools, and it correctly reads -6db.
I imported the same file to Reaper, and it also reads -6db.
I imported to Logic, and it reads -6db.
Audacity, Pro Tools, Logic, Reaper all read exactly at -6db.
If your curious why -6db, the math is 20*log10(0.5). It's approximately -6.02...
There should be no difference between different DAWs as far as peak meter goes.

Chi

On 7/27/2017 12:27 PM, Christopher-Mark Gilland wrote:
Sorry for the crosspost, but I'm wanting to also put this on PTAccess so we can 
approach this from both DAW angles, and to help leverage getting me the most 
responses.

Guys, I asked this question on list about 2 or 3 months ago, and quite frankly, 
I never ever got a very direct answer. Everyone who did answer, in fact, some 
of which you'd never imagine saying this on the RWP list, told me, who cares, 
just use your ears, and let them be your guide. that's not what I'm seeking 
here. I really want some true and frank answers here.

Here's the situation. I am trying to help an incredibly dear friend of mine 
start up learning audio production, and by the way, no, it's not the friend I 
said who cannot do audio worth a damn. This is someone totally different. LOL! 
This guy actually is very very very open to suggestions!

Anyway, he hasn't done anything at all when it comes to pro grade audio.

One of the things that we now are working on is microphone lead vocal gain 
staging.

What I'm trying to get him to see is that if you record into your DAW too hot, 
you'll start clipping, and even if you don't! clip the  vocal track, leave not 
enough headroom, and in the long run, you'll clip your master fader. He gets 
this concept entirely.

What we did is, he sent me a recording he did in Reaper. He sent me the stems.

First, I loaded it up actually in ProTools as it's the DAW I'm most familiar 
with. But, the point is, he sent me the unprocessed raw stems which included 
his vocal that he initially recorded in Reaper.

Here's where things went absolutely awri kurfunkity wacko jacko.

In ProTools, I interacted with the track channel strip that contains his 
vocals. Note that right now, I don't have Flowtools installed. Yes, in the long 
run, this message is ProTools related even though I'm discussing Reaper right 
now. Please please I beg you, stick with me on this!

In this track strip, I navigated one VO+right arrow passed the output volume 
fader for that track, and landed on the peek meter. I have ProTools set where 
the peek meters hold infinent until reset.

On the loudest peek of his vocal, ProTools indicates that he's peeking at -1DB. 
So, he's really really really hot! Really no headroom at all. And trust me. I 
can hear it too! It sounds God aweful! Even he! agrees it sounds terrible. How 
to fix this is another issue in and of itself, but here is the strange thing 
that I just! can't! fathom!

I imported these exact same stem wav files that were created in Reaper, 
originally, back into Reaper.

I then had him, using Osara, go into the peek meter watcher settings with 
CTRL+Shift+W. Essentially, we set both combo boxes for first and second track 
to follow current. We checked both boxes to watch the tracks. I set it to hold 
the meter until reset, which I think was the default radio button value anyway.

Finally, when level reaches, I had him set this to minus 12. My reason of 
thinking was, if he can come into the DAW from his interface at around negative 
12DB, that gives plenty of headroom, and we then could use a compressor, or 
other means later in the mixing phase to get that vocal up in the mix.

This is how I was tought to do it with ProTools, or really with any DAW, for 
that mind. Record in low, then later adjust and compensate for the gain loss. - 
Don't try starting out by going in at a really hot level.

So, anyway, I then after setting up the meter watcher in Reaper had 'em play 
the recording. Because in ProTools, he was peeking at -1DB, I was hoping! that 
the peek watcher in Reaper would pick up on this, and would automatically 
without him doing anything let him know. Well, nothing happened at all. Oh, we 
could hear the clipping all right! Oh baby could we ever! It sounded 
disgusting! But, the watcher yielded nothing!

Finally, In Reaper, I told him, Ronald, try something for me. I told him with 
the watcher set, hit W to go to the beginning of the song. Note that his vocal 
track only contained 1 item. We then hit space bar to play. As soon as his 
vocal started, I let it run for about 20 seconds, then, without pausing, I had 
him hit Alt+F9 to query the peek meter on first track. Note that actually, the 
vocal was the second track in the project, and his karaoke music was the first, 
but he was focused on the second reaper track as being selected with his arrow 
keys up and down. I had him try 

Re: flotools 2.2 question

[Chi Kim]

Steve, good to hear you're enjoying it.

Few questions...

What Pro Tools version are you using

IF the answer is yes to all the question below, can you send me the 
report? Getting started has a section on how to generate a report.

Is track list table shown?

If you select a track in the track list table, does Voiceover actually 
speaks the word "selected?"

Is your Pro Tools is in English?

Is default keyboard set to “US” in System Preferences?
Let's start from there.


Chi

On 6/21/2017 4:40 AM, Steve Sparrow wrote:
> Hi guys. just installed flo tools 2.2 and i must say i think it’s bloody 
> great. compliments to all who get this stuff happening. It just makes my job 
> so much easier.
> One question. Ever since i started using flo tools. back in version 2.0 i’ve 
> never been able to get the speak selected tracks function to work. it seems 
> the same in 2.2.  i think the command is option shift T. Is this command 
> correct, and if so is there a reason it is not working for me.
> Thanks guys.
> Steve
>

-- 
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: FloTools Not Responding to Hotkeys

[Chi Kim]

Hi Samuel

Can you press command+slash which is next to the period on English 
keyboard, and see if Voiceover says mouse on or mouse off? If it doesn't 
work, most likely Flo Tools is not installed correctly.

Also if you're not using US English keyboard layout, you should change 
in the system preference > Keyboard > Input Sources.

Chi


On 4/5/2017 4:42 AM, Samuel Wilkins wrote:
> Hello Slau, I tried that and it doesn't work.  When I tried the record 
> enable status command, but that didn't work either.  I've checked and 
> Keyboard Maestro seems to be fine.  When I installed FloTools, it said 
> please wait and then exited.  Is that what is supposed to happen?
>
>
> On 04/04/2017 12:16, Slau Halatyn wrote:
>> In the Keyboard pane of System Preferences, check the box that says
>> "Use F1, F2, etc. keys as standard function keys."
>>> On Apr 4, 2017, at 4:17 AM, Samuel Wilkins  
>>> wrote:
>>>
>>> Hello everyone,
>>> Thank you for the suggestion for looking at the Readme file for 
>>> FloTools.  I got Keyboard Maestro installed and have now installed 
>>> FloTools.  However, it is not responding to hotkeys.  I opened a 
>>> session, and tried command F1 to see whether it would work. However, 
>>> instead of telling me about selections, it tried to adjust a 
>>> brightness setting.  I've made sure that VoiceOver was set to allow 
>>> control by Apple Script and that the keyboard settings were set to 
>>> US English. I also tried using the FN key with command F1, but that 
>>> didn't work, and Neither did pressing Command F2 or F3. What could I 
>>> be doing wrong?  I'm using a Mackbook with ProTools 12.  Thank you.
>>>
>>> -- 
>>> 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: FloTools - Unarming all tracks is fixed

[Chi Kim]

Martin, glad to hear it's working out!


Chi
On 10/18/2016 3:12 AM, Martin (Punky) Sopart wrote:
> Hi Chi and list!
>
> I just wanna let you know, that now the FT scripts are working as expected on 
> both of my Macs.
> The problem was that PT 12.4.0 labels an AUX track “Auxiliary Track” and not 
> “AUX Track” like in later PT versions.
>
> Having had a good Skype session yesterday with Chi, he was able to apply this 
> PT behaviour to the FT scripts.
> Thanks again for that Chi.
>
> Best! / Martin
>

-- 
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: New Script 2

[Chi Kim]

On 10/17/2016 10:10 AM, Chi Kim wrote:
>
>
> On 10/17/2016 10:04 AM, Chi Kim wrote:
>>
>>
>> On 10/17/2016 9:42 AM, Chi Kim wrote:
>>> Here it is.
>>>
>>>
>>>
>>> On 10/16/2016 5:19 PM, Chi Kim wrote:
>>>> Martin, most likely we'll probably have to do a Skype session.
>>>>
>>>> Before we do that, can you send me your session file off list? I 
>>>> don't need any audio.
>>>>
>>>> Thanks,
>>>>
>>>> Chi
>>>> On 10/16/2016 5:00 PM, Martin (Punky) Sopart wrote:
>>>>> Hi Slau!
>>>>>
>>>>> The track list table is showen in both mix and edit windows and 
>>>>> the selection scripts work fine.
>>>>>
>>>>> Best! / Martin
>>>>>
>>>>> On Oct 16, 2016, at 10:46 PM, Slau Halatyn <slauhala...@gmail.com> 
>>>>> wrote:
>>>>>
>>>>> Hi Chi,
>>>>> I thought Martin said that both windows were open however one 
>>>>> thing did occur to me, and maybe this will have nothing to do with 
>>>>> the situation but, if the Mix window is open but its track list is 
>>>>> not shown, wouldn’t that potentially be an issue? Now that I’m 
>>>>> thinking of it, on second thought, that would affect the track 
>>>>> selection script rather than the record disarming. Hmm…
>>>>> Slau
>>>>>
>>>>>> On Oct 16, 2016, at 4:20 PM, Chi Kim <chigook...@hotmail.com> wrote:
>>>>>>
>>>>>> Martin, so double tap doesn't seem to throw an error anymore 
>>>>>> after you checking some things. For all double taps, the output 
>>>>>> is false, that's the expected output.
>>>>>>
>>>>>> Change the macro to ignore result, and see if the double tap 
>>>>>> gives you any feedback with voiceover now.
>>>>>>
>>>>>>
>>>>>> Chi
>>>>>>
>>>>>> On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
>>>>>>> Chi,
>>>>>>>
>>>>>>> to make sure, all settings are correct.
>>>>>>> I missed to check the edit toolbars in my previous mail.
>>>>>>>
>>>>>>> Here the results again with all 3 tolbars (transport, MIDI 
>>>>>>> controlers and expanded transport) checked.
>>>>>>>
>>>>>>> Single tap:
>>>>>>> /var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
>>>>>>>  
>>>>>>> execution error: Error on line 16: Error: Can't get object. (-1728)
>>>>>>>
>>>>>>> Double tap:
>>>>>>> false
>>>>>>>
>>>>>>> Best, Martin
>>>>>>>
>>>>>>> -- 
>>>>>>> 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.


iterate copy.scpt
Description: iterate copy.scpt

Re: FloTools - Unarming all tracks still not working

[Chi Kim]

On 10/17/2016 9:42 AM, Chi Kim wrote:
> Here it is.
>
>
>
> On 10/16/2016 5:19 PM, Chi Kim wrote:
>> Martin, most likely we'll probably have to do a Skype session.
>>
>> Before we do that, can you send me your session file off list? I 
>> don't need any audio.
>>
>> Thanks,
>>
>> Chi
>> On 10/16/2016 5:00 PM, Martin (Punky) Sopart wrote:
>>> Hi Slau!
>>>
>>> The track list table is showen in both mix and edit windows and the 
>>> selection scripts work fine.
>>>
>>> Best! / Martin
>>>
>>> On Oct 16, 2016, at 10:46 PM, Slau Halatyn <slauhala...@gmail.com> 
>>> wrote:
>>>
>>> Hi Chi,
>>> I thought Martin said that both windows were open however one thing 
>>> did occur to me, and maybe this will have nothing to do with the 
>>> situation but, if the Mix window is open but its track list is not 
>>> shown, wouldn’t that potentially be an issue? Now that I’m thinking 
>>> of it, on second thought, that would affect the track selection 
>>> script rather than the record disarming. Hmm…
>>> Slau
>>>
>>>> On Oct 16, 2016, at 4:20 PM, Chi Kim <chigook...@hotmail.com> wrote:
>>>>
>>>> Martin, so double tap doesn't seem to throw an error anymore after 
>>>> you checking some things. For all double taps, the output is false, 
>>>> that's the expected output.
>>>>
>>>> Change the macro to ignore result, and see if the double tap gives 
>>>> you any feedback with voiceover now.
>>>>
>>>>
>>>> Chi
>>>>
>>>> On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
>>>>> Chi,
>>>>>
>>>>> to make sure, all settings are correct.
>>>>> I missed to check the edit toolbars in my previous mail.
>>>>>
>>>>> Here the results again with all 3 tolbars (transport, MIDI 
>>>>> controlers and expanded transport) checked.
>>>>>
>>>>> Single tap:
>>>>> /var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
>>>>>  
>>>>> execution error: Error on line 16: Error: Can't get object. (-1728)
>>>>>
>>>>> Double tap:
>>>>> false
>>>>>
>>>>> Best, Martin
>>>>>
>>>>> -- 
>>>>> 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.


iterate copy.scpt
Description: iterate copy.scpt

Re: FloTools - Unarming all tracks still not working

[Chi Kim]

Here it is.



On 10/16/2016 5:19 PM, Chi Kim wrote:
> Martin, most likely we'll probably have to do a Skype session.
>
> Before we do that, can you send me your session file off list? I don't 
> need any audio.
>
> Thanks,
>
> Chi
> On 10/16/2016 5:00 PM, Martin (Punky) Sopart wrote:
>> Hi Slau!
>>
>> The track list table is showen in both mix and edit windows and the 
>> selection scripts work fine.
>>
>> Best! / Martin
>>
>> On Oct 16, 2016, at 10:46 PM, Slau Halatyn <slauhala...@gmail.com> 
>> wrote:
>>
>> Hi Chi,
>> I thought Martin said that both windows were open however one thing 
>> did occur to me, and maybe this will have nothing to do with the 
>> situation but, if the Mix window is open but its track list is not 
>> shown, wouldn’t that potentially be an issue? Now that I’m thinking 
>> of it, on second thought, that would affect the track selection 
>> script rather than the record disarming. Hmm…
>> Slau
>>
>>> On Oct 16, 2016, at 4:20 PM, Chi Kim <chigook...@hotmail.com> wrote:
>>>
>>> Martin, so double tap doesn't seem to throw an error anymore after 
>>> you checking some things. For all double taps, the output is false, 
>>> that's the expected output.
>>>
>>> Change the macro to ignore result, and see if the double tap gives 
>>> you any feedback with voiceover now.
>>>
>>>
>>> Chi
>>>
>>> On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
>>>> Chi,
>>>>
>>>> to make sure, all settings are correct.
>>>> I missed to check the edit toolbars in my previous mail.
>>>>
>>>> Here the results again with all 3 tolbars (transport, MIDI 
>>>> controlers and expanded transport) checked.
>>>>
>>>> Single tap:
>>>> /var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
>>>>  
>>>> execution error: Error on line 16: Error: Can't get object. (-1728)
>>>>
>>>> Double tap:
>>>> false
>>>>
>>>> Best, Martin
>>>>
>>>> -- 
>>>> 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.


speak record enabled tracks.scpt
Description: speak record enabled tracks.scpt

Re: Mail for Chi

[Chi Kim]

Martin, good thing you asked here. They went to my junk mail for some 
reason, but I found them now.

Talk soon.

Chi
On 10/17/2016 8:38 AM, Martin (Punky) Sopart wrote:
> Hi Chi!
>
> Did you get my two mails off list?
>
> Thanks! / Martin
>

-- 
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: Suggestion for Flo Tools

[Chi Kim]

The answer is yes, we can.

Slau, if you can come up with shortcuts for volume and pan...


Chi
On 10/16/2016 10:30 PM, Slau Halatyn wrote:
> Hi John Andre,
>
> It’s one thing to have UI automation read the status and perform the default 
> action for a control. Pressing a button or toggling, resetting, etc. is a 
> simple matter. The volume fader has no default action. It must be interacted 
> with and changed to a desired value. This isn’t possible with the Inspector. 
> Naturally, we thought of this early on. There might be a different option but 
> that would be with an entirely different system not related to Flo Tools. Chi 
> can further clarify.
> Slau
>
>> On Oct 16, 2016, at 8:59 PM, John André Lium-Netland 
>>  wrote:
>>
>> Hi,
>>
>> I can already see that Flo Tools will save me a lot of time, so while 
>> experimenting with it, I got an idea:
>>
>> Would it be possible to have a shortcut in the Flo Inspector to change the 
>> volume and pan for the focused track using the arrow keys? shift-option-up 
>> and down arrow to change volume and shift-option-left and right arrow to 
>> change pan. I have not checked if there are any shortcut conflicts here.
>>
>> 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 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: FloTools - Unarming all tracks still not working

[Chi Kim]

Martin, most likely we'll probably have to do a Skype session.

Before we do that, can you send me your session file off list? I don't 
need any audio.

Thanks,

Chi
On 10/16/2016 5:00 PM, Martin (Punky) Sopart wrote:
> Hi Slau!
>
> The track list table is showen in both mix and edit windows and the selection 
> scripts work fine.
>
> Best! / Martin
>
> On Oct 16, 2016, at 10:46 PM, Slau Halatyn <slauhala...@gmail.com> wrote:
>
> Hi Chi,
> I thought Martin said that both windows were open however one thing did occur 
> to me, and maybe this will have nothing to do with the situation but, if the 
> Mix window is open but its track list is not shown, wouldn’t that potentially 
> be an issue? Now that I’m thinking of it, on second thought, that would 
> affect the track selection script rather than the record disarming. Hmm…
> Slau
>
>> On Oct 16, 2016, at 4:20 PM, Chi Kim <chigook...@hotmail.com> wrote:
>>
>> Martin, so double tap doesn't seem to throw an error anymore after you 
>> checking some things. For all double taps, the output is false, that's the 
>> expected output.
>>
>> Change the macro to ignore result, and see if the double tap gives you any 
>> feedback with voiceover now.
>>
>>
>> Chi
>>
>> On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
>>> Chi,
>>>
>>> to make sure, all settings are correct.
>>> I missed to check the edit toolbars in my previous mail.
>>>
>>> Here the results again with all 3 tolbars (transport, MIDI controlers and 
>>> expanded transport) checked.
>>>
>>> Single tap:
>>> /var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
>>>  execution error: Error on line 16: Error: Can't get object. (-1728)
>>>
>>> Double tap:
>>> false
>>>
>>> Best, Martin
>>>
>>> -- 
>>> 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: IMPORTANT: announcing Flo Tools

[Chi Kim]

You're welcome Vinny!
I'm glad that when using Pro Tools, Voiceover users including myself can now 
focus more on interacting with music instead of constantly interacting, stop 
interacting, and frantically chasing after controls!
I still find myself doing that often just out of habit. Then I realize, wait, I 
can use Flo Tools!

Chi

On 10/16/2016 3:35 PM, Vinny Pedulla wrote:
Hi Chi,
Thank you for all your work! This is outstanding and unprecedented for us on 
the Mac as of yet…
We have been discussing this on the Roger group and there have  been many 
positive comments about how well fought out the interface is and how much more 
efficient we can be with the Scripps, but I thought I would just publicly thank 
you here  on the Pro Tools list.
I would  like to thank you and Rocco for taking the  initiative to start this 
and thank Slau for coming up with such a great key map and adding so much more 
functionality for us. This is truly a great time to be a blind musician!

Thanks again for a job well done,
Vinny
Email: vinnypedu...@gmail.com<mailto:vinnypedu...@gmail.com>

On Oct 16, 2016, at 1:37 PM, Chi Kim 
<chigook...@hotmail.com<mailto:chigook...@hotmail.com>> wrote:


Thanks Byron! I'm glad that it's working out for you.

Keep us posted if you run into any problem.

Chi

On 10/16/2016 11:18 AM, byron harden wrote:
As a blind engineer, producer, and out-right music enthusiast Flo Tools has 
dramatically increased efficiency considerably in my production workflow; 
furthermore, this well thought out, intuitive, functional, yet effective 
interface has afforded blind Pro-tools users a fighting chance of seriously 
competing as a mix and recording engineer in an industry that is exceedingly 
sighted, and lacking diversity and inclusion at the higher levels.  Chi, Rocco, 
and Slau saw it necessary that blind professionals in the audio production 
arena remain focused on what really matters, which is the work and not 
accessibility; moreover, the fact that Flo-tools cost nothing and more 
importantly is an open source interface, shows not only the blind community, 
but the entire world that someone cares, and is willing to assist in the 
advancement of this small and gifted group of individuals.  I would like to 
personally thank these three gentlemen for providing a wonderful and crucial 
solution to having a pair of eyes in the studio while navigating in Pro-tools; 
as well, congratulations on changing lives through your talents, abilities, and 
good hearts.
Temporary fix-external!
permanent fix-internal!
THE answer is always with in!
LETS love this world, it's a gift!

On Oct 15, 2016, at 3:22 PM, Chi Kim 
<chigook...@hotmail.com<mailto:chigook...@hotmail.com>> wrote:


Hi All,


Thank you for all your positive excitement!

Special thanks to Rocco and Slau for making this possible!

We hope the script will help you to spend more time with music instead of 
Voiceover!


Chi

On 10/15/2016 2:43 PM, 
accessibleproto...@gmail.com<mailto:accessibleproto...@gmail.com> wrote:
Hi guys,
Thank you so much, we really appreciate the positive feedback. You can use 
keyboard maestro for 30 days before purchase, if you want to see how the 
Scripps work for you. All links and instructions can be found under the getting 
started page of the flo tools website

Sent from my iPhone

On Oct 15, 2016, at 10:35 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I'm sorry I missed that message, Slau. Shruggs. Alas, I'll go have a look.

Sigh...

Chris.
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 11:27 AM
Subject: Re: IMPORTANT: announcing Flo Tools

Follow the links on the Flo Tools site to take you to Stairways to purchase 
Keyboard Maestro if you’d like to use the macros. It’s around $36. It was on 
sale for $20 about 10 days ago and I did mention that everybody should buy it 
and I said, “Trust me, you’re going to want to buy it anyway.”

On Oct 15, 2016, at 11:20 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I need help getting setup with Keyboard Maestro. Where does one get it, and, is 
it free?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Friday, October 14, 2016 6:32 PM
Subject: IMPORTANT: announcing Flo Tools

Here’s an important new development for our community. A new free product 
specifically designed for 

Re: FloTools - Unarming all tracks still not working

[Chi Kim]

Martin, so double tap doesn't seem to throw an error anymore after you checking 
some things. For all double taps, the output is false, that's the expected 
output.

Change the macro to ignore result, and see if the double tap gives you any 
feedback with voiceover now.


Chi

On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
Chi,

to make sure, all settings are correct.
I missed to check the edit toolbars in my previous mail.

Here the results again with all 3 tolbars (transport, MIDI controlers and 
expanded transport) checked.

Single tap:
/var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
 execution error: Error on line 16: Error: Can't get object. (-1728)

Double tap:
false

Best, Martin

--
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: FloTools - Unarming all tracks still not working

[Chi Kim]

Martin, it looks like the script can't get the list of tracks.

Few more things to ask to make sure.

Do you happen to be working inside edit window with mix window closed? If you 
press vo+f2 twice and open the window chooser, do you see both mix and edit 
windows?

I assume some tracks are shown, right?

If you interact with an individual track, can you find Track record enable 
button?

I can't think of anything else at the moment, but I'll keep thinking.

Chi

On 10/16/2016 2:38 PM, Martin (Punky) Sopart wrote:
Chi,

to make sure, all settings are correct.
I missed to check the edit toolbars in my previous mail.

Here the results again with all 3 tolbars (transport, MIDI controlers and 
expanded transport) checked.

Single tap:
/var/folders/1z/tbg8gscj0hl610_kf6_qc8r8gn/T/Keyboard-Maestro-Script-99EC089F-637C-46B9-8DB3-88A087ACF24C:607:725:
 execution error: Error on line 16: Error: Can't get object. (-1728)

Double tap:
false

Best, Martin

--
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: FloTools - Unarming all tracks still not working

[Chi Kim]

Yeah it looks like the particular script is failing somewhere in the 
middle since you can hear the alert tone. I need some log from you.

Open Keyboard Maestro, and check edit if it's not checked. Edit is near 
the end of the Window.

Go find macro groups scroll area and interact with it.

press vo+space on Flo Tools group.

Stop interact with Macro Groups and go to Macros scroll area and 
interact with it.

Find the macro that says "Beta: Speak Record Enabled Tracks, Disarm All 
Record Enabled Tracks" and press vo+space on it.

Press tap and it'll say image, and now you're inside Macro Edit details 
scroll area.

Find Execute Javascript for Automation Action group and interact with it.
Find Ignore result pop-up button and press vo+space to open the popup menu.
Choose display result in a window.
If you can't find the popup button, make sure the first item in there 
indicates expanded disclosure triangle. If not vo+space to expand it.
Now switch to Pro Tools, and run the command.
If it fails, keyboard Maestro should open a window, and you should be 
able to find the output text right after the label ""The output of the 
text script is."
If voiceover doesn't get focused on the output window, press vo+f2 twice 
to open window chooser, and you should be able to find keyboard maestro 
window along with edit and mix windows.
Interact with the element that says "text," and press command+a to 
select all, and command+c to copy.
After that you can press ok button to dismiss it.
Can you give me the output for both option+shift+r single tap as well as 
double tap?
When you're done you can go back to the macro edit detail scroll area, 
execute Javascript for automation, and change it to ignore result again.
Thanks,

Chi
On 10/16/2016 1:35 PM, Martin (Punky) Sopart wrote:
> Hi Chi!
>
> How I wrote in my first mail regarding this topic, all other functions for 
> all tracks are working.
> Unmuting, unsoloing and unselecting.
> Pressing the keycombination once brings the expected message and pressing it 
> twice, brings the audio signal and the message, that all tracks are unmuted, 
> -soloed or -selected.
> Only option+shift+r does nothing. Only the audio signal when pressing the key 
> combination twice.
>
> Yes, and I’m abel to arm/unarm the current inspector track with double r.
> The message is not always correct, but thats the beta thing, but when 
> checking the arm status by interacting with the track, the function works in 
> both edit and mix windows.
>
> Could I test something else?
>
> Best! & Martin
>
>

-- 
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: IMPORTANT: announcing Flo Tools

[Chi Kim]

Thanks Byron! I'm glad that it's working out for you.

Keep us posted if you run into any problem.

Chi

On 10/16/2016 11:18 AM, byron harden wrote:
As a blind engineer, producer, and out-right music enthusiast Flo Tools has 
dramatically increased efficiency considerably in my production workflow; 
furthermore, this well thought out, intuitive, functional, yet effective 
interface has afforded blind Pro-tools users a fighting chance of seriously 
competing as a mix and recording engineer in an industry that is exceedingly 
sighted, and lacking diversity and inclusion at the higher levels.  Chi, Rocco, 
and Slau saw it necessary that blind professionals in the audio production 
arena remain focused on what really matters, which is the work and not 
accessibility; moreover, the fact that Flo-tools cost nothing and more 
importantly is an open source interface, shows not only the blind community, 
but the entire world that someone cares, and is willing to assist in the 
advancement of this small and gifted group of individuals.  I would like to 
personally thank these three gentlemen for providing a wonderful and crucial 
solution to having a pair of eyes in the studio while navigating in Pro-tools; 
as well, congratulations on changing lives through your talents, abilities, and 
good hearts.
Temporary fix-external!
permanent fix-internal!
THE answer is always with in!
LETS love this world, it's a gift!

On Oct 15, 2016, at 3:22 PM, Chi Kim 
<chigook...@hotmail.com<mailto:chigook...@hotmail.com>> wrote:


Hi All,


Thank you for all your positive excitement!

Special thanks to Rocco and Slau for making this possible!

We hope the script will help you to spend more time with music instead of 
Voiceover!


Chi

On 10/15/2016 2:43 PM, 
accessibleproto...@gmail.com<mailto:accessibleproto...@gmail.com> wrote:
Hi guys,
Thank you so much, we really appreciate the positive feedback. You can use 
keyboard maestro for 30 days before purchase, if you want to see how the 
Scripps work for you. All links and instructions can be found under the getting 
started page of the flo tools website

Sent from my iPhone

On Oct 15, 2016, at 10:35 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I'm sorry I missed that message, Slau. Shruggs. Alas, I'll go have a look.

Sigh...

Chris.
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 11:27 AM
Subject: Re: IMPORTANT: announcing Flo Tools

Follow the links on the Flo Tools site to take you to Stairways to purchase 
Keyboard Maestro if you’d like to use the macros. It’s around $36. It was on 
sale for $20 about 10 days ago and I did mention that everybody should buy it 
and I said, “Trust me, you’re going to want to buy it anyway.”

On Oct 15, 2016, at 11:20 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I need help getting setup with Keyboard Maestro. Where does one get it, and, is 
it free?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Friday, October 14, 2016 6:32 PM
Subject: IMPORTANT: announcing Flo Tools

Here’s an important new development for our community. A new free product 
specifically designed for blind users of Pro Tools has been released today and 
it’s called Flo Tools. Point your browsers at
http://flotools.github.io<http://flotools.github.io/>
and get these free scripts for Pro Tools and, yes, we said, “scripts for Pro 
Tools.” You’ll need Keyboard Maestro to trigger them. These are scripts that 
perform and automate certain tasks and provide feedback through VoiceOver. 
Everything you need to know can be found at the web site. There’s a detailed 
Read Me file plus an “Intro to Flo Tools” mp3. This open source project will 
transform the way blind users use Pro Tools. Since it’s open source, other 
programmers can get involved and who knows what this might eventually lead to 
but, right now, it’s the most exciting development in Pro Tools accessibility 
this community has seen in years. Flo Tools is brought to you by Chi Kim, Rocco 
Fiorentino and Slau Halatyn.

The Flo Tools Team


--
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<mailto:ptaccess+unsubscr...@googlegroups.com>.
F

Re: FloTools - Unarming all tracks still not working

[Chi Kim]

That's strange. Few more questions...

Are you able to use the Flo Tools inspector mode to arm and disarm an 
individual track by double tapping r quickly?

Also, are you able to unmute and unsolo all shown tracks using Flo Tools?


Chi
On 10/16/2016 1:06 PM, Martin (Punky) Sopart wrote:
> Hi Chii!
>
> Thanks for assisting me.
>
> After disarming all track manually I get the expected message, when pressing 
> numpad+3.
>
> I also find the Record Enable status LED. It’s the first object inside the 
> “normal transport buttons”.
>
> When than arming  a selected track via shift+r, that LED changes to Track 
> Record Enabled.
> So everything seams to be correct.
>
> When now pressing option+shift+t, FT announces 1 selected…
> Pressing option+shift+r, does nothing.
> Pressing it twice, only brings that little sound.
> Pressing shift+r changes Track Record Enabled back to Record Enable status 
> LED again.
>
> Could this belong to Yosemite?
> Or maybe a special mouse setting?
> Or is it at least PT 12.4  non HD?
>
> Thank you! / Martin
>

-- 
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: FloTools - Unarming all tracks still not working

[Chi Kim]

Hi Martin,


Can you do a couple of tests for me?

1. Disarm all tracks manually.

Confirm by press record, and make sure you get a dialog that says no 
tracks are record enabled.

If you go to edit window > Transport view cluster > Normal Transport 
Buttons, can you find something that says "Record Enable Status LED?"

2. Then arm one track

Go to edit window > Transport view cluster > Normal Transport Buttons 
and see if you can find something that says "Track Record Enabled."

There's also button that says "Record Enable," but we're looking for 
"Track Record Enabled.

Let me know.

Thanks


Chi


On 10/16/2016 4:30 AM, Martin (Punky) Sopart wrote:
> Hi!
>
> Now in addition to ProTools I set Yousemite to English and teh region to US.
> So everything is in English now.
> But option+shift+r,r is still not working.
> Only the audiosignal for the action is sounding, but no speech message and no 
> action after that.
>
> At the moment I’m running Yosemite and PT 12.4.0.
> It is not PT HD.
>
> Thanks! / Martin
>
>
>

-- 
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: IMPORTANT: announcing Flo Tools

[Chi Kim]

Hey Julián,

That's cool that you're thinking about coming to Berklee! Let me know if 
you have any question about the school or concerns.

When you come to US in December, are you planning to stop by Boston? If 
so, let me know. Maybe we can meet.

Best luck with everythinng!


Chi
On 10/15/2016 5:24 PM, Julián Alejandro Argoti wrote:
> Hi everyone, I want to thank the SLAU, Chi, and Rocco marabilla lords
> by this tool.
> I am an amateur record and want to study at Berklee.
> In December I travel to the United States, I have to first learn
> English and then apply to Berklee.
> Not much English now but in the future I want to be able to converse
> well with you, thank you very much for allowing me to be a member of
> this list and
> to learn something from each of you.
>
> regards
> Julian Argoti
>
>
> 2016-10-15 16:12 GMT-05:00, Chi Kim <chigook...@hotmail.com>:
>> Pro Tools has memory location window.
>>
>> I can't think of the shortcut top of my head, but you should be able to find
>> under the window menu.
>>
>>
>> Chi
>> On 10/15/2016 5:04 PM, Christopher-Mark Gilland wrote:
>> I promise to look at the documentation, so please don't shun me off with an
>> RTFM answer. Tonight's gonna be really laid back lazy for me, so I plan to
>> sit down tonight and really just go through the manual. In the meantime, is
>> there a quick way that one can add/remove and see a list in a table of all
>> markers? You know, like, when you add a marker with num pad enter?
>> ---
>> Christopher Gilland
>> JAWS Certified, 2016.
>> Training Instructor.
>>
>> i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
>> Phone: (704) 256-8010.
>> - Original Message -
>> From: Chi Kim<mailto:chigook...@hotmail.com>
>> To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
>> Sent: Saturday, October 15, 2016 4:22 PM
>> Subject: Re: IMPORTANT: announcing Flo Tools
>>
>>
>> Hi All,
>>
>>
>> Thank you for all your positive excitement!
>>
>> Special thanks to Rocco and Slau for making this possible!
>>
>> We hope the script will help you to spend more time with music instead of
>> Voiceover!
>>
>>
>> Chi
>>
>> On 10/15/2016 2:43 PM,
>> accessibleproto...@gmail.com<mailto:accessibleproto...@gmail.com> wrote:
>> Hi guys,
>> Thank you so much, we really appreciate the positive feedback. You can use
>> keyboard maestro for 30 days before purchase, if you want to see how the
>> Scripps work for you. All links and instructions can be found under the
>> getting started page of the flo tools website
>>
>> Sent from my iPhone
>>
>> On Oct 15, 2016, at 10:35 AM, Christopher-Mark Gilland
>> <clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:
>>
>> I'm sorry I missed that message, Slau. Shruggs. Alas, I'll go have a look.
>>
>> Sigh...
>>
>> Chris.
>> ---
>> Christopher Gilland
>> JAWS Certified, 2016.
>> Training Instructor.
>>
>> i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
>> Phone: (704) 256-8010.
>> - Original Message -
>> From: Slau Halatyn<mailto:slauhala...@gmail.com>
>> To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
>> Sent: Saturday, October 15, 2016 11:27 AM
>> Subject: Re: IMPORTANT: announcing Flo Tools
>>
>> Follow the links on the Flo Tools site to take you to Stairways to purchase
>> Keyboard Maestro if you’d like to use the macros. It’s around $36. It was on
>> sale for $20 about 10 days ago and I did mention that everybody should buy
>> it and I said, “Trust me, you’re going to want to buy it anyway.”
>>
>> On Oct 15, 2016, at 11:20 AM, Christopher-Mark Gilland
>> <clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:
>>
>> I need help getting setup with Keyboard Maestro. Where does one get it, and,
>> is it free?
>> ---
>> Christopher Gilland
>> JAWS Certified, 2016.
>> Training Instructor.
>>
>> i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
>> Phone: (704) 256-8010.
>> - Original Message -
>> From: Slau Halatyn<mailto:slauhala...@gmail.com>
>> To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
>> Sent: Friday, October 14, 2016 6:32 PM
>> Subject: IMPORTANT: announcing Flo Tools
>>
>> Here’s an important new development for our community. A new free product
>> specifically designed for blind users of Pro Tools has

Re: IMPORTANT: announcing Flo Tools

[Chi Kim]

Pro Tools has memory location window.

I can't think of the shortcut top of my head, but you should be able to find 
under the window menu.


Chi
On 10/15/2016 5:04 PM, Christopher-Mark Gilland wrote:
I promise to look at the documentation, so please don't shun me off with an 
RTFM answer. Tonight's gonna be really laid back lazy for me, so I plan to sit 
down tonight and really just go through the manual. In the meantime, is there a 
quick way that one can add/remove and see a list in a table of all markers? You 
know, like, when you add a marker with num pad enter?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Chi Kim<mailto:chigook...@hotmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 4:22 PM
Subject: Re: IMPORTANT: announcing Flo Tools


Hi All,


Thank you for all your positive excitement!

Special thanks to Rocco and Slau for making this possible!

We hope the script will help you to spend more time with music instead of 
Voiceover!


Chi

On 10/15/2016 2:43 PM, 
accessibleproto...@gmail.com<mailto:accessibleproto...@gmail.com> wrote:
Hi guys,
Thank you so much, we really appreciate the positive feedback. You can use 
keyboard maestro for 30 days before purchase, if you want to see how the 
Scripps work for you. All links and instructions can be found under the getting 
started page of the flo tools website

Sent from my iPhone

On Oct 15, 2016, at 10:35 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I'm sorry I missed that message, Slau. Shruggs. Alas, I'll go have a look.

Sigh...

Chris.
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 11:27 AM
Subject: Re: IMPORTANT: announcing Flo Tools

Follow the links on the Flo Tools site to take you to Stairways to purchase 
Keyboard Maestro if you’d like to use the macros. It’s around $36. It was on 
sale for $20 about 10 days ago and I did mention that everybody should buy it 
and I said, “Trust me, you’re going to want to buy it anyway.”

On Oct 15, 2016, at 11:20 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I need help getting setup with Keyboard Maestro. Where does one get it, and, is 
it free?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Friday, October 14, 2016 6:32 PM
Subject: IMPORTANT: announcing Flo Tools

Here’s an important new development for our community. A new free product 
specifically designed for blind users of Pro Tools has been released today and 
it’s called Flo Tools. Point your browsers at
http://flotools.github.io<http://flotools.github.io/>
and get these free scripts for Pro Tools and, yes, we said, “scripts for Pro 
Tools.” You’ll need Keyboard Maestro to trigger them. These are scripts that 
perform and automate certain tasks and provide feedback through VoiceOver. 
Everything you need to know can be found at the web site. There’s a detailed 
Read Me file plus an “Intro to Flo Tools” mp3. This open source project will 
transform the way blind users use Pro Tools. Since it’s open source, other 
programmers can get involved and who knows what this might eventually lead to 
but, right now, it’s the most exciting development in Pro Tools accessibility 
this community has seen in years. Flo Tools is brought to you by Chi Kim, Rocco 
Fiorentino and Slau Halatyn.

The Flo Tools Team


--
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<mailto: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<mailto: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 

Re: Very very weird issue with Flotools

[Chi Kim]

Christopher, I know exactly what happened.

I think you accidentally imported twice. Thus you have every macro twice 
duplicated. You now have 240 macros instead of 120 macros. That's why you get 
pallet for every macro.

Just delete all the Flo Tools groups, and re import only once.

Let me know how it goes.

Chi
On 10/15/2016 4:52 PM, Christopher-Mark Gilland wrote:
None of them are working without that pallet coming up.

I'll try your suggestion. No worries.
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Chi Kim<mailto:chigook...@hotmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 4:14 PM
Subject: Re: Very very weird issue with Flotools


HI Christopher,


What you're describing sounds like Keyboard Maestro palate.

This could happen if one of the shortcuts got changed, and you now have ore 
than one macros that have the same shortcuts for some reason.

When you have ore than one macros assigned with the same shortcut, Keyboard 
Maestro gives you what they call palate, asking which Macro you want to fire.

I suggest to reinstall Flo Tools following the instruction on the getting 
started toward the end.

IN short, you remove both Flo Tools and Flo Tools Inspector groups, and import 
them back. Hopefully it'll fix itself.

Have you tried other commands?
Do they not work as well?

Chi

On 10/15/2016 3:40 PM, Christopher-Mark Gilland wrote:
OK, so I went ahead and got Keyboard Maestro, and have installed the scripts.

First of all, when I opened the macro file, the KM editer opened, but I didn't 
hear anything about it being successfully imported.

Thinking maybe I just didn't hear it for some reason, I went ahead and fired up 
a very very very very small test session I made the other day which basically 
has one instrument track with Ivory instantiated, nothing really impressive.

So, I selected that track with the track list table like I'd a done before 
Flotools was in the picture. I also made absolutely sure the track is showing, 
which it definitely is. My mother who is sighted even looked, and no question, 
she confirmed it is showing both in the mix, and in the edit window.

I also made sure to follow the getting started link to an exact T that is on 
the website.

Now, if I hit option+shift+W to speak shown tracks, I'm taken to this really 
really weird window. If anyone wants to hear this with audio in action, let me 
know, and I'll record it for ya.  Basically, there's an unlabeled button with 
no help tag, then if I VO+Right arrow, I get something that says application 
button, then again to the right I see speak shown tracks, then one more 
VO+right I get show track list popup.  If I VO+Space on that, the script is 
carried out, and I'm told that 1 track is shown, inst1, which by the way, would 
be exactly correct. but why am I having to do that in this weird window 
regardless what command macro I hit? Focus mode's off, etc.

Regardless which macro I try executing, I get that strange window.  The odd 
thing is, my mom doesn't actually see it popping up on the screen.  I'm not 
sure if it's some sort of a floating window, or what.  I can't hit escape to 
get out of it either.  the only way I can dismiss it is as described above by 
carrying out the command, or, if I command+tab away from the ProTools window, 
then command+tab back to it, the window goes away, until I do another macro 
command.

This is just the strangest thing!

Slau? Do you or anyone know what on earth might be going on?  This is just 
craziness!  Yes, I do have the box to let VO be controlled with Apple Script 
checked.

Could it be possible that I'm not on the most up to date setup?

I'm running El Capitan 10.11.6. Note this isn't any sort of beta. If it were, 
I'd not be discussing it here due to nDA.

As for PT, I'm on ProTools 12.4.0.294.  For Keyboard Maestro, I am on version 
7.3.

Any clues?

Chris.
--
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<mailto: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<mailto: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 
pt

Re: IMPORTANT: announcing Flo Tools

[Chi Kim]

Hi All,


Thank you for all your positive excitement!

Special thanks to Rocco and Slau for making this possible!

We hope the script will help you to spend more time with music instead of 
Voiceover!


Chi

On 10/15/2016 2:43 PM, 
accessibleproto...@gmail.com<mailto:accessibleproto...@gmail.com> wrote:
Hi guys,
Thank you so much, we really appreciate the positive feedback. You can use 
keyboard maestro for 30 days before purchase, if you want to see how the 
Scripps work for you. All links and instructions can be found under the getting 
started page of the flo tools website

Sent from my iPhone

On Oct 15, 2016, at 10:35 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I'm sorry I missed that message, Slau. Shruggs. Alas, I'll go have a look.

Sigh...

Chris.
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Saturday, October 15, 2016 11:27 AM
Subject: Re: IMPORTANT: announcing Flo Tools

Follow the links on the Flo Tools site to take you to Stairways to purchase 
Keyboard Maestro if you’d like to use the macros. It’s around $36. It was on 
sale for $20 about 10 days ago and I did mention that everybody should buy it 
and I said, “Trust me, you’re going to want to buy it anyway.”

On Oct 15, 2016, at 11:20 AM, Christopher-Mark Gilland 
<clgillan...@gmail.com<mailto:clgillan...@gmail.com>> wrote:

I need help getting setup with Keyboard Maestro. Where does one get it, and, is 
it free?
---
Christopher Gilland
JAWS Certified, 2016.
Training Instructor.

i...@gillandmarketing.com<mailto:i...@gillandmarketing.com>
Phone: (704) 256-8010.
- Original Message -
From: Slau Halatyn<mailto:slauhala...@gmail.com>
To: ptaccess@googlegroups.com<mailto:ptaccess@googlegroups.com>
Sent: Friday, October 14, 2016 6:32 PM
Subject: IMPORTANT: announcing Flo Tools

Here’s an important new development for our community. A new free product 
specifically designed for blind users of Pro Tools has been released today and 
it’s called Flo Tools. Point your browsers at
http://flotools.github.io<http://flotools.github.io/>
and get these free scripts for Pro Tools and, yes, we said, “scripts for Pro 
Tools.” You’ll need Keyboard Maestro to trigger them. These are scripts that 
perform and automate certain tasks and provide feedback through VoiceOver. 
Everything you need to know can be found at the web site. There’s a detailed 
Read Me file plus an “Intro to Flo Tools” mp3. This open source project will 
transform the way blind users use Pro Tools. Since it’s open source, other 
programmers can get involved and who knows what this might eventually lead to 
but, right now, it’s the most exciting development in Pro Tools accessibility 
this community has seen in years. Flo Tools is brought to you by Chi Kim, Rocco 
Fiorentino and Slau Halatyn.

The Flo Tools Team


--
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<mailto: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<mailto: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<mailto: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<mailto: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<mailto:ptaccess+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscr

Re: Very very weird issue with Flotools

[Chi Kim]

HI Christopher,


What you're describing sounds like Keyboard Maestro palate.

This could happen if one of the shortcuts got changed, and you now have ore 
than one macros that have the same shortcuts for some reason.

When you have ore than one macros assigned with the same shortcut, Keyboard 
Maestro gives you what they call palate, asking which Macro you want to fire.

I suggest to reinstall Flo Tools following the instruction on the getting 
started toward the end.

IN short, you remove both Flo Tools and Flo Tools Inspector groups, and import 
them back. Hopefully it'll fix itself.

Have you tried other commands?
Do they not work as well?

Chi

On 10/15/2016 3:40 PM, Christopher-Mark Gilland wrote:
OK, so I went ahead and got Keyboard Maestro, and have installed the scripts.

First of all, when I opened the macro file, the KM editer opened, but I didn't 
hear anything about it being successfully imported.

Thinking maybe I just didn't hear it for some reason, I went ahead and fired up 
a very very very very small test session I made the other day which basically 
has one instrument track with Ivory instantiated, nothing really impressive.

So, I selected that track with the track list table like I'd a done before 
Flotools was in the picture. I also made absolutely sure the track is showing, 
which it definitely is. My mother who is sighted even looked, and no question, 
she confirmed it is showing both in the mix, and in the edit window.

I also made sure to follow the getting started link to an exact T that is on 
the website.

Now, if I hit option+shift+W to speak shown tracks, I'm taken to this really 
really weird window. If anyone wants to hear this with audio in action, let me 
know, and I'll record it for ya.  Basically, there's an unlabeled button with 
no help tag, then if I VO+Right arrow, I get something that says application 
button, then again to the right I see speak shown tracks, then one more 
VO+right I get show track list popup.  If I VO+Space on that, the script is 
carried out, and I'm told that 1 track is shown, inst1, which by the way, would 
be exactly correct. but why am I having to do that in this weird window 
regardless what command macro I hit? Focus mode's off, etc.

Regardless which macro I try executing, I get that strange window.  The odd 
thing is, my mom doesn't actually see it popping up on the screen.  I'm not 
sure if it's some sort of a floating window, or what.  I can't hit escape to 
get out of it either.  the only way I can dismiss it is as described above by 
carrying out the command, or, if I command+tab away from the ProTools window, 
then command+tab back to it, the window goes away, until I do another macro 
command.

This is just the strangest thing!

Slau? Do you or anyone know what on earth might be going on?  This is just 
craziness!  Yes, I do have the box to let VO be controlled with Apple Script 
checked.

Could it be possible that I'm not on the most up to date setup?

I'm running El Capitan 10.11.6. Note this isn't any sort of beta. If it were, 
I'd not be discussing it here due to nDA.

As for PT, I'm on ProTools 12.4.0.294.  For Keyboard Maestro, I am on version 
7.3.

Any clues?

Chris.
--
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: Record on USB Hard diskUsing SSd or Sata HD wi

[Chi Kim]

Hi,


If you can't install ssd on your Mac, just getting an external ssd is 
another option.

Amazon has Samsung 850 evo 250gb internal ssd for $94, but Samsung t3 
250gb external ssd for $99.
Using my Mac, I get 423 megabytes per seconds for read and 415 megabytes 
per seconds for write on Samsung t3.
Also I wouldn't worry too much about write cycle on ssd. One test shows 
that they had to write 300tb of data on Samsung 840 evo 250gb until the 
first error, and they were still able to write 700tb of data until first 
failure.
unless I screwed up the math, 300tb is 72.63 years worth of recording in 
48kghz 24bit non-stop.
1024(bytes)*1024(kb)*1024(mb)*1024(gb)*300(tb)/48000(sr)/3(24bits)/60(seconds)/60(minutes)/24(hours)/365(days)

Chi
On 9/24/2016 11:17 AM, Phil Muir wrote:
> Or you can run a non SSD drive such as a 7200RPM mechanical drive in an
> external enclosure.  USB is indeed more than fast enough to read/write too
> although personally not using SSD for writing audio due to loss of write
> cycles on SSD drives and wouldn't personally write to internal SSD drives
> for the same reason.  Am using WD black drives here in external USB3
> enclosures and have all of my samples on the external drive as well.
>
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf
> Of Kevin Reeves
> Sent: 24 September 2016 15:54
> To: Pro Tools Access
> Subject: Re: Record on USB Hard diskUsing SSd or Sata HD wi
>
> You can buy a Samsung EVO and put it in an external USB enclosure. USB 3 is
> definitely fast enough to record to.
> Or, you can have your Samsung SSD put into your mac mini by a technician.
> This is the better way to go because having your OS and apps on an SSD will
> definitely speed up your machine.
> With an SSD, you can record to your internal drive. No need for an external.
> Hope this helps.
>
> Kevin
>

-- 
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.

Anyone Using Voiceover Feature Called Fast Searching with Pro Tools?

[Chi Kim]

Hi All,

I discovered something that might be useful for some people who don't 
know about this.
I knew about fast search feature, but I never really bothered with it 
too much even though I had it enabled. Then I played with it inside Pro 
Tools little bit. Actually I kind of like it. You can jump to different 
things really quickly.
I.E. If you're outside of channel strip, and if you press command+i, 
your voiceover will jump to inside of inserts. If you press command+v, 
Voiceover will jump to the volume fader, command s for sends, and so on.
Basically Voiceover will jump to a next element that starts with that 
letter, and If you add shift, it'll jump to a previous item that starts 
with the letter you pressed.
If you just press command+m in succession, you'll go through mute 
buttons for each track without having to stop interacting, move to a 
next track, interact with it, and move to the mute. It's really fast too!
Have fun!

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/d/optout.

Re: Native Instruments Komplete Kontrol

[Chi Kim]

Hi All,


I just heard from Andre, and he said he's planning to demo at 5pm in UK 
time.

He also said there will be an archive for people living in different 
timezone.


Chi
On 6/23/2016 1:30 PM, Carlos Taylor wrote:
> Maybe I missed it, but what time is Andre’s demonstration scheduled for?
>> On Jun 21, 2016, at 1:12 PM, Slau Halatyn  wrote:
>>
>> Some of you undoubtedly heard about the recent progress with the 
>> accessibility of Native Instruments Komplete 10 with the self-voicing aspect 
>> and the s-series controllers. Frankly, I'm somewhat surprised that there 
>> hasn't been more discussion either here or on the Logic list. 
>> Understandably, it isn't a cheap library and the additional necessary 
>> expense of the controller probably makes it something for which many folks 
>> have to budget and purchase in time. Again, however, it's curious that there 
>> hasn't been more talk of it on the list as it relates to an accessible music 
>> library. Granted, it was only officially released a few days ago so I 
>> suppose there aren't too many that have access. For those interested, Andre 
>> Louis will be doing a live Q this Saturday. You can listen through the 
>> following link:
>> http://3.onj.me:8000/komplete.m3u
>>
>> Andre's not a Pro Tools user, to the best of my knowledge, but the 
>> information is entirely relevant as the accessibility is a function of the 
>> self-voicing aspect of the software along with the S-series controller.
>>
>> I'll probably do some type of audio walk-through as it specifically relates 
>> to Pro Tools. I received the controller and software this morning. As luck 
>> would have it, starting this afternoon, I have a series of daily sessions 
>> that run all the way into July 4th weekend so I won't have any significant 
>> time to spend with the setup but I'll certainly attempt to make some 
>> progress here and there before or after sessions.
>>
>> For those who already have controllers and are considering Komplete, it 
>> might be a good idea to simply go for the smallest of the S-series which is 
>> the 25-key controller. This would facilitate all of the navigation and it 
>> would keep the cost to a minimum.
>>
>> OK, I'll post further messages as things take shape.
>>
>> Slau
>>
>> -- 
>> 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: Productivity tips?

[Chi Kim]

Hi Slau,


Here's a bug that Avid needs to fix.

When the track is armed, the armed message sent out to voice over is not 
persistent. It comes and goes away depending on when you check it.

My theory is that perhaps track record button is flashing when is selected, and 
the flashing makes the label go on and off.

Go inside a strip, arm the track, and try to keep reading the arm state by 
going left and right with Voiceover cursor. You'll get different results quite 
often. This also applies to the item chooser method you described.
This is not a Voiceover bug. It happens to UI automation as well.
Mute and Solo don't. When it's selected, it will keep saying selected no 
matter when you check it.
Would you mind confirming and adding it to the fix list when you get a chance?
Thanks,

Chi
On 6/2/2016 9:50 AM, Slau Halatyn wrote:
Hi Peter,

Glad to hear of your progress. Until someone manages to write some kind of 
scripts like JAWS had for Sonar, the use of Pro Tools will never have the same 
type of accessibility as Sonar with scripts. There's a give and take, of 
course. Pro Tools is accessible out of the box with no need for anything else, 
no scripts that break when a new update or version comes out. Sonar was 
apparently painstakingly slow at creating a slew of tracks and naming them 
quickly which is a cinch in Pro Tools. Nothing compares with the speed of 
editing in Pro Tools. But when it comes to figuring out which tracks are record 
enabled, it's not possible in PT to simply query with a keystroke. Workflow is 
a personal and perhaps quirky thing. I don't judge how other people decide to 
work but there are many options. For example, if I want to record enable the 
third and ninth track within a session, having a control surface, I simply 
press the third and ninth record buttons. Once I've done that, there's no 
question which tracks are record-enabled. For the duration of the recording, 
there will be no reason for me to query anything because I chose to record 
enable the third and ninth tracks. To further simplify things, as always, it 
helps, but it's not necessary, to hide tracks which are not being used or do 
not need to be up front and visible. In this case, I can hide all but the third 
and ninth tracks. Since tracks that are hidden cannot be in record mode, it 
greatly decreases the range of possibilities and one has only two tracks to 
deal with in the Mix or Edit windows.

Let's say you were dealing with twelve drum tracks. It's easy to group the drum 
tracks, hide all other tracks and, while selected, pressing Shift-r will 
record-enable the selected tracks. The same Shift-modified shortcuts work for 
mute and solo. There's no need to query which tracks are record-enabled 
because, if the tracks are selected and one track is enabled, they're all 
enabled and, if you're getting signal through one track, you're getting signal 
through them all.

Bringing up the Item Chooser in the Mix window and typing r e c will display 
the record buttons currently visible in the Mix window. Arrowing down the list, 
one can determine the status of the record buttons quickly. One can even rename 
the buttons to reflect which tracks they belong to. While this tends to work, 
it's not persistent between sessions because, of course, every session is a new 
file but, if you use templates, I believe it's possible to name the buttons and 
this will propagate to subsequent session files that are created from the 
template. This is theoretical and I know it works to some degree but I don't 
use that workflow myself.

An Avid control surface is a large part of the efficiency for using Pro tools 
with VoiceOver. While it's possible to use Pro Tools without a surface, I'd 
never consider doing that long-term. I sympathize with the notion of going from 
something that was more familiar and worked quickly and easily to something 
that is quite different. with analog multitracks, it was easy to tactually  
feel which record buttons were flipped up in record mode. Those were the days, 
of course. What can one do? :)

I find that I'm regularly discovering little ways of being more efficient, even 
after years of using Pro Tools. Again, what works for some, might not work as 
well for others so it's difficult to predict what might be good advice or 
confusing information. Just like anything else, I suppose, the more you use it, 
the more you'll find your path.

Cheers,

Slau

On Jun 2, 2016, at 8:46 AM, Peter Bosher 
<peter.bos...@bbc.co.uk>
 wrote:

Hi All,

After using PT in earnest for a couple of months, I’m now reasonably confident 
with basic editing and mixing, including things like inserts and sends and 
using some plug-ins, but I still find it way, way slower than using Sonar with 
Caketalking, and I’m wondering whether anyone has some tips to speed things up.

For example, if I want to know whether track 7 is muted, or check which tracks 
are 

Re: Making Kontakt somewhat usable in Pro Tools.

[Chi Kim]

Hi Kevin,

I just started this on Logic a few days ago.
Using Keyboard Maestro, I have mapped load, add library, and resolve 
missing samples mapped so far.
Fortunately, when you click those buttons, it opens the generic finder 
open dialog at least in Logic.

I haven't confirmed in PT yet.

Chi

On 1/17/2016 11:06 AM, Kevin Reeves wrote:

Ok. I'll make a note of that when I start working with this.

Thanks.

Kevin

On 1/17/2016 10:50 AM, Jean-Philippe Rykiel wrote:

dear Kevin.
The delete instrument function would be very important as well. Each 
time you load a new instrument, it will load in a subsequent channel, 
and not araise the current channel. So if you want to try different 
sounds on Channel one, you need to delete what ever is loaded in 
there first.

Hope keyboard Maestro will work, I'm concerned as well smile.
Best,
JPR

http://www.jprykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

http://www.jprykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Le 17/01/2016 16:26, Kevin Reeves a écrit :

Hey folks.

I'm a huge fan of Kontakt libraries, as they offer the greatest 
realism in sampled and modeled instruments.
However, the Kontakt player is incredibly inaccessible. I've 
wondered if there was a way to use Keyboard Maestro to click 
coordinates on the screen, much like Hotspot Clicker or Auto Hotkey 
on windows.


The topic of using Kontakt came up on the logic list. I responded 
with some ideas, which I'm posting below, as I feel it is absolutely 
relevant to the Pro Tools platform as well.


Begin Post.

I think that Kontakt could potentially be made somewhat usable in 
both logic and Pro Tools using Keyboard Maestro.
We need to do some experiments to see what variables prevent the 
mouse from clicking the correct coordinates.
The 4 main buttons that need to be mapped to key presses are as 
follows.


1. Load
2. Add to library
3. reset multi
4. close browse window, (for samples missing dialog.)
There are other important buttons in the window, but these are the 4 
most important.



There are some variables that would prevent proper coordinate 
clicking for the above mentioned buttons.
This would include window size and position, the presence of 
floating windows, screen resolution, and other things that I haven't 
yet considered.
Also, it would be interesting to see if there are challenges which 
are program dependent between logic and Pro Tools.


I just downloaded a keyboard maestro demo, and need to figure out 
how to bind a key command to a coordinate click.
Once I do that, I will get someone to assist me in starting this 
process.


If anyone has any other insights into this, I'm all ears. I'd love 
to get Kontakt working on the mac platform for us.


Kevin







--
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: EZ Keys Presets

[Chi Kim]

Hi Slau,

Thank you for letting me know. That's great.
Hopefully the person who had the same problem with preset library using 
Slate could comment on his solution.
Also hopefully it doesn't start the blaming game between companies: 
plugin developer and avid.


Chi


On 10/31/2015 10:21 AM, Slau Halatyn wrote:

Hi Chi,
Not sure about Slate but, since I saw your message, I thought I'd let 
you know that the issue of adjusting plug-in parameters for automation 
with VoiceOver is solved in the new release, version 12.3.


Slau


On Oct 31, 2015, at 12:56 AM, Chi Kim <chigook...@hotmail.com 
<mailto:chigook...@hotmail.com>> wrote:



I recall that someone also had a very similar problem with Slate plugin.
If a sighted person saves a preset into preset librarian, and if you 
try to open them, it crashes.

Does anyone know if the problem with Slate plugin got resolved?
Thanks,

Chi
On 10/30/2015 10:31 PM, Rocco Fiorentino wrote:

Hello all,

Has anyone used EZ keys in Protools? I've been trying to convert the 
inaccessible preset browser to protools library presets, but when I 
add more then 3 presets it causes protools to crash when opening any 
of the presets in the plugin. Not sure if this is a tuneTrack or 
Avid issue...any suggestions would be appreciated.

Thanks,

Rocco

--
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 
<mailto:ptaccess+unsubscr...@googlegroups.com>.

For more options, visit https://groups.google.com/d/optout.





Avast logo <https://www.avast.com/antivirus>  

This email has been checked for viruses by Avast antivirus software.
www.avast.com <https://www.avast.com/antivirus>



--
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 
<mailto: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 
<mailto:ptaccess+unsubscr...@googlegroups.com>.

For more options, visit https://groups.google.com/d/optout.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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: EZ Keys Presets

[Chi Kim]

I recall that someone also had a very similar problem with Slate plugin.
If a sighted person saves a preset into preset librarian, and if you try 
to open them, it crashes.

Does anyone know if the problem with Slate plugin got resolved?
Thanks,

Chi
On 10/30/2015 10:31 PM, Rocco Fiorentino wrote:

Hello all,

Has anyone used EZ keys in Protools? I've been trying to convert the 
inaccessible preset browser to protools library presets, but when I 
add more then 3 presets it causes protools to crash when opening any 
of the presets in the plugin. Not sure if this is a tuneTrack or Avid 
issue...any suggestions would be appreciated.

Thanks,

Rocco

--
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.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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: RME Fireface in PT

[Chi Kim]

Hi,

I used to use both Fireface and Babyface.
You can change the basic settings like buffer size and stuff, but if you 
want to work with mixer, you have to ask someone to create a preset for you.
However, the preset files are similar to xml, so you can edit them on 
text edit and load.


Chi
On 10/5/2015 11:47 AM, Poppa Bear wrote:


Thanks Nicola, I wish it was more plug and play, well, I may be 
looking at the Apogee line. I like some of their older gear, but don’t 
have any hands on experience. I also like the Universal audio stuff, 
but I have heard a lot of negative reviews about their ADAC converters.


*From:*ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] 
*On Behalf Of *Nicola Cascino

*Sent:* Monday, October 05, 2015 4:31 AM
*To:* Pro Tools Accessibility
*Subject:* Re: RME Fireface in PT

No direct experience, but i know that the Total Mixer is not 
accessible. To fix this you need to create an user presets library in 
order to recall the scenario you need time by time, of course you need 
someone that help you to do it. Consider that  via the total mixer you 
control almost all the device functionalities, such as poering the 
phantoms on, selecting the inpput and so on. Apart this, the Fireface 
is maybe the best choice in terms of price/quality in its range.  Best.


--
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.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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: Hopefully a basic, easy to solve plugin automation problem

[Chi Kim]

Hi Slau,

I believe I've written about this a few months ago. It seems like you 
can't automate plugin parameters using Voiceover.
Even if you have a control surface, it'd be nice to be able to do this 
with Voiceover without control surface for when you don't have access to 
one like when you are traveling.
This is exactly what happened to me, and a sighted person was able to 
help with a trackpad.

Hopefully it gets fixed soon.

Chi

On 8/28/2015 8:06 AM, Slau Halatyn wrote:

Actually, it's conceivable that the VoiceOver interaction isn't working for 
automation and perhaps never worked. Has anyone successfully automated a 
plug-in parameter on the list? Let me say, and I've said this before, I can't 
fathom how any VoiceOver user can begin to use Pro tools in a serious fashion 
without a control surface. I've only used automation with with control surfaces 
and, of course, it works fine. There was a similar issue of VoiceOver changing 
fader values correctly but, when faders were grouped, things didn't work 
correctly when changing levels with VoiceOver. Again, with a control surface, 
it's been a non-issue. It's possible that we're seeing the same thing here. 
Needless to say, if that's the case here, that wouldn't be fixed in the 
upcoming release because there's no time.

As I mentioned, I've never attempted any plug-in automation without a control 
surface and, clearly, none of the beta testers have ever thought to try it 
either and there was never a bug report logged on this issue if, in fact, it is 
a current issue. Someone will need to reproduce the results. I know others 
without control surfaces have had difficulties but it'll have to be replicated 
in a controlled manner and logged. I'll see if I can do that in the near future.

Slau

On Aug 28, 2015, at 7:34 AM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:


Sorry, pressed the wrong button and sent the previous email again. ProTools is 
playing with my sanity levels. Here's what I meant to send.
It seems impossible to automate plugins using the mac keyboard. My friend has 
just done it with the trackpad and it works, but doing it with Voice-Over 
completely fails.

If anyone feels saintly enough to have a go at recreating these steps and 
telling me what they experience, or helping to put me straight on this, then 
that would be great.

I put the track on autowrite, I enable the plugin control I want for 
automation. I change the control by interacting with it and using the arrow 
keys. The change occurs; I know this becuase I can hear it, and I’ve had 
sighted clarification. I then stop the project, put the track on read, and play 
the track at the point where the automation should be kicking in. Nothing 
happens. The plugin control just resets to where it was before I started, and 
there is no automation written.

My sighted friend manages to do exactly the same as I am doing only using the 
mouse to automate, and it works fine. Sickeningly, he is also able to make 
smoother changes simply with the mouse, but that’s another story.

I have the box unticked besides the auto enable plugins for automation option 
in the automation part of the mix tab in preferences.

I really don’t think ProTools wants me to have automation control over plugins. 
Surely this can’t be an accessibility issue, as it seems like a massive flaw. I 
tried this once a few months ago using PT11 and it didn’t work then either, but 
I was too busy to try anything at that time, and assumed I was diong something 
wrong.

Thanks folks. Let’s hope this isn’t another one to add the unsolved major 
problems list.


Sent from my iPhone


On 28 Aug 2015, at 03:18, Steve Martin  wrote:

do you change the automation status from write to read or something else before 
playing it back?

On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
 wrote:

OK friends, what am I doing wrong now? I’m trying to automate certain plugin 
parameters but to no avail. I insert an effect, I VO space on the automation 
enable button, I select a parameter then press on add, then OK. I set my track 
to automation write. I start playing the project and manipulating the enabled 
perimeter, and I hear the changes. Sounding good. I then play it back and there 
are no changes. All that happens is that the plugin parameter resorts back to 
the previous value that I started at.

Any help would be very welcome as I’m rather baffled.


Sent from my iPhone

--
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 

Re: Hopefully a basic, easy to solve plugin automation problem

[Chi Kim]

Great! Thanks!

Chi

On 9/4/2015 11:22 AM, Slau Halatyn wrote:

Hi Chi,

Yes, this has been logged as a bug and it's at the very top of the list for a 
subsequent update.

Cheers,

Slau

On Sep 4, 2015, at 7:13 AM, Chi Kim <chigook...@hotmail.com> wrote:


Hi Slau,

I believe I've written about this a few months ago. It seems like you can't 
automate plugin parameters using Voiceover.
Even if you have a control surface, it'd be nice to be able to do this with 
Voiceover without control surface for when you don't have access to one like 
when you are traveling.
This is exactly what happened to me, and a sighted person was able to help with 
a trackpad.
Hopefully it gets fixed soon.

Chi

On 8/28/2015 8:06 AM, Slau Halatyn wrote:

Actually, it's conceivable that the VoiceOver interaction isn't working for 
automation and perhaps never worked. Has anyone successfully automated a 
plug-in parameter on the list? Let me say, and I've said this before, I can't 
fathom how any VoiceOver user can begin to use Pro tools in a serious fashion 
without a control surface. I've only used automation with with control surfaces 
and, of course, it works fine. There was a similar issue of VoiceOver changing 
fader values correctly but, when faders were grouped, things didn't work 
correctly when changing levels with VoiceOver. Again, with a control surface, 
it's been a non-issue. It's possible that we're seeing the same thing here. 
Needless to say, if that's the case here, that wouldn't be fixed in the 
upcoming release because there's no time.

As I mentioned, I've never attempted any plug-in automation without a control 
surface and, clearly, none of the beta testers have ever thought to try it 
either and there was never a bug report logged on this issue if, in fact, it is 
a current issue. Someone will need to reproduce the results. I know others 
without control surfaces have had difficulties but it'll have to be replicated 
in a controlled manner and logged. I'll see if I can do that in the near future.

Slau

On Aug 28, 2015, at 7:34 AM, 'onlineeagle' via Pro Tools Accessibility 
<ptaccess@googlegroups.com> wrote:


Sorry, pressed the wrong button and sent the previous email again. ProTools is 
playing with my sanity levels. Here's what I meant to send.
It seems impossible to automate plugins using the mac keyboard. My friend has 
just done it with the trackpad and it works, but doing it with Voice-Over 
completely fails.

If anyone feels saintly enough to have a go at recreating these steps and 
telling me what they experience, or helping to put me straight on this, then 
that would be great.

I put the track on autowrite, I enable the plugin control I want for 
automation. I change the control by interacting with it and using the arrow 
keys. The change occurs; I know this becuase I can hear it, and I’ve had 
sighted clarification. I then stop the project, put the track on read, and play 
the track at the point where the automation should be kicking in. Nothing 
happens. The plugin control just resets to where it was before I started, and 
there is no automation written.

My sighted friend manages to do exactly the same as I am doing only using the 
mouse to automate, and it works fine. Sickeningly, he is also able to make 
smoother changes simply with the mouse, but that’s another story.

I have the box unticked besides the auto enable plugins for automation option 
in the automation part of the mix tab in preferences.

I really don’t think ProTools wants me to have automation control over plugins. 
Surely this can’t be an accessibility issue, as it seems like a massive flaw. I 
tried this once a few months ago using PT11 and it didn’t work then either, but 
I was too busy to try anything at that time, and assumed I was diong something 
wrong.

Thanks folks. Let’s hope this isn’t another one to add the unsolved major 
problems list.


Sent from my iPhone


On 28 Aug 2015, at 03:18, Steve Martin <monkeypushe...@gmail.com> wrote:

do you change the automation status from write to read or something else before 
playing it back?

On Aug 27, 2015, at 8:34 PM, 'onlineeagle' via Pro Tools Accessibility 
<ptaccess@googlegroups.com> wrote:

OK friends, what am I doing wrong now? I’m trying to automate certain plugin 
parameters but to no avail. I insert an effect, I VO space on the automation 
enable button, I select a parameter then press on add, then OK. I set my track 
to automation write. I start playing the project and manipulating the enabled 
perimeter, and I hear the changes. Sounding good. I then play it back and there 
are no changes. All that happens is that the plugin parameter resorts back to 
the previous value that I started at.

Any help would be very welcome as I’m rather baffled.


Sent from my iPhone

--
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 f

Re: Can't Automate Plugin with Voiceover

[Chi Kim]

Hi All,

I'm still having problem automating plugin. I'm wondering if anyone else 
has this problem as well.
If sighted person moves the mouse, it records the automation, but if I 
move the same knob with the Voiceover, it doesn't record the automation. 
Sighted person can see the same knob moving if I move it with Voiceover, 
and I'm told that visually there's absolutely nothing different between 
when I do it and when he does it. However, PT refuses to record the 
automation for some reason if I do it with Voiceover. I'm pretty sure 
everything is set correctly to automate plugins, because when a sighted 
person does it with mouse, it works.
This only applies to automation for plugins. I can automate track 
parameters like volume without a problem.

This is really mysterious.
Thanks for help,

Chi

On 3/29/2015 6:41 PM, Chi Kim wrote:

Hi All,

Is there way to automate a plugin parameter with Voiceover? As far as 
automation record, everything is set up correctly.
If a sighted person moves the frequency knob on 1 band EQ with mouse 
during playback, it draws an automation curve and records it. However, 
if I interact with the same parameter and change the value with 
Voiceover during the playback, it doesn't draw the curve even though 
the same knob on the screen moves.
I'm away from my control surface, so it'd be great if there's a way to 
do this with Voiceover meantime.

I'm on Mavericks with PT 11.3.1.
Thanks all,

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/d/optout.

Re: question about pro tools meters

[Chi Kim]

Brian, how Voiceover reads the meter preference might make it little 
confusing.

Visually it's set up like a table, and it might cause some confusion.
If you already know this, you can just disregard.
IN the preference, first find the peak label, from there, move Voiceover 
cursor with VO+down instead of VO+right until you find infinite radio 
button.

If it's not selected, you probably selected infinite for clip indicator.

Chi



On 3/30/2015 8:56 AM, Brian Howerton wrote:

Hello all,
I am running pro tools 12, and I had a question about the meters.  I have my 
meters set to infinite in the preferences, at first it wasn’t staying there 
when I went back in preferences to check to make sure that my settings were set 
to infinite, but I think I finally got it to stay on infinite instead of 3 
seconds.  What was happening was that it kept switching back to 3 seconds.  
Anyway, I opened up a session and I was reading the meter on the master fader, 
and it was jumping around.  It would start at like -3, and then it would jump 
up to -5 and then -6, and then it would go back down.  So my meters looked like 
they were jumping around, this doesn’t sound normal to me, so I thought I would 
bring it to the list.  I noticed in preferences that there are new meters in 
pro tools 11 and 12, do I need to switch to a different meter type to be able 
to have it behave properly?  Any help would be appreciated.  I went to my 
metering preferences and went to the track and master meters, and saw that my 
meters were set to sample peak. Do I need to change my meters to the pro tools 
classic meters in order for voiceover to read the meter properly? I saw there 
were like 4 different meters that we could change them to in there.
  Thanks so much,
Brian




--
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.

Can't Automate Plugin with Voiceover

[Chi Kim]

Hi All,

Is there way to automate a plugin parameter with Voiceover? As far as 
automation record, everything is set up correctly.
If a sighted person moves the frequency knob on 1 band EQ with mouse 
during playback, it draws an automation curve and records it. However, 
if I interact with the same parameter and change the value with 
Voiceover during the playback, it doesn't draw the curve even though the 
same knob on the screen moves.
I'm away from my control surface, so it'd be great if there's a way to 
do this with Voiceover meantime.

I'm on Mavericks with PT 11.3.1.
Thanks all,

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/d/optout.

Fuzz Wah Mod Rate Reset when Opening a Session

[Chi Kim]

Hi All,

If I change mod rate parameter on Fuzz Wah plug in, save the session, 
and reopen the session, the parameter resets back. Could someone confirm 
this behavior?
The setting sticks until I save and reopen the session, so I don't think 
it's an automation issue.
I also tried on a new blank session with just one audio track, and got 
the same result.

I use pt 11.3 on Mavericks.
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/d/optout.

Re: feedback needed for Pro Tools 12

[Chi Kim]

Hi Slau,

Just for update, Clip indicators was already set to hold for infinite, and VO 
still doesn't announces when the meter is clipped.
Anything else I should check?
Thanks for your help,

Chi

On 3/22/2015 3:17 PM, Slau Halatyn wrote:

Hi Chi,

Yep, the Click plug-in's parameters don't work well right now. That's certainly 
on the list of things to tackle. Incidentally, the parameters are accessible 
with a control surface. So, for example, to access triplets and accent values, 
etc., the encoder knobs or faders in flip mode will control those parameters 
and it's possible to save those settings as presets for future use.

The clip indicators are working fine. Make sure you have your preferences set 
to hold clip indicators and you should be good to go.

The subject of preset browsing in the plug-in window is clearly a much larger 
issue and, regardless of its accessibility, I'm not sure that it's going to 
necessarily change any time soon. Surely, it's much more of an issue for 
virtual instruments and one size doesn't fit all so I wouldn't expect Avid to 
come up with any solution that'll be right for every developer. Plug-in 
accessibility, in general, is an important issue and its model might have to 
change entirely for it to be viable for the long term. We'll all keep trying 
until we get it right.

Slau

On Mar 22, 2015, at 3:09 PM, Chi Kim chigook...@hotmail.com wrote:


Hi Slau,

The new click plugin included in pt 11 is not accessible.
Also, getting access to warp markers would be good.
I believe clip indicator is not accessible with Voiceover anymore. When the 
meter clips, Voiceover used to say clipped until you clear it, but it doesn't 
say it anymore.
Lastly, I know you specifically said no new future request, but it'd be worth 
while to briefly mention about creating a flexible database system that manages 
all the presets for all the plugin with tagging system something like Native 
Instrument Komplete. Komplete consists of many plugins with many presets (total 
17,000), but you can browse all of them in one browser and load them easily. 
This would save a lot of time for any composers/producers to find right sound 
without going through many different plugins with many different presets.
The current preset system for Pro Tools is so old style and not that flexible, 
so many developers don't even bother and create their own instead.
I'm sure this would require a lot of thought process to make it useful for 
users, and easier for plugin developers to implement. However, if Avid pulls it 
off well and markets it as a cool new feature, it would benefit everyone 
regardless sighted or blind once the developers start taking advantage of it.
Thanks for working with Avid on this important work.

Chi

On 3/16/2015 10:41 AM, Slau Halatyn wrote:

In a couple of weeks, I'm going to have a unique opportunity to sit down with a 
programmer to work on some accessibility issues in Pro Tools. Under the 
circumstances of my trip, Avid has allowed for this meeting to be scheduled 
barring any last minute crisis with the release of Pro Tools 12. This will be 
largely driven by bug submissions already within the beta system but I wanted 
to get a sense of what the user base is focused on day to day. My goal is to 
address quality-of-life issues that affect the use of Pro Tools with VoiceOver. 
For example, the way the inserts and, in particular, sends are displayed is 
simply awful. This needs to be overhauled. There are a number of such issues 
that can hopefully be taken care of in one marathon session of tweaks.

I have a clear idea of what I personally think should be addressed but I 
thought I'd take the temperature of the community. What I'm asking of the list 
is for people to enumerate 3 to 5 things that most affect their productivity 
and would like to see improved. Now, I don't mean for people to suggest a 
different method for importing files to an existing track. That's a bigger fish 
to fry and the subject of a longer term solution. These are, as I said, 
quality-of-life issues that can be addressed quickly. Also, don't bring up 
issues in version 10. We're talking existing issues in version 11. Give me your 
top 3 or top 5 items and we'll see which seem to reveal themselves as the 
biggest concerns. The sooner you get those to me, the sooner I can prepare.

Thanks,

Slau


--
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: feedback needed for Pro Tools 12

[Chi Kim]

HI Slau, thanks for the help.
Yes I'm aware of the fact that the Voiceover reads the radio buttons in 
such ways for that particular settings.

Peak on the left and and Clip indicator on the right
Then the related radio buttons below the labels.
I went to clip indicator label first then went down to make sure 
infinite is selected. It's very mysterious why it's not working.

Can you think of any other setting that might be preventing this?
Thanks,

Chi

On 3/26/2015 10:05 AM, Slau Halatyn wrote:

Hi Chi,

I've just verified that in version 11.3 the clip indicator definitely works. I'm not sure what might be 
causing your problem with the indicator. One thing I would check is that you have the correct radio button 
checked in the Metering tab of the Preferences window. The way it reads is not entirely clear at first. There 
are two columns, one for Peak and one for Clipping. If you read across, you might mistake the first column as 
immediately following the Clip text. I'm not sure if this happened to you or not but, just to be sure, I 
would check it again. Navigate to the right until you reach the first radio button that reads 3 
seconds and then continue to the second radio button that reads 3 seconds. This is the 
column that pertains to Clipping. Navigate down and you'll find the Infinite radio button and 
make sure it's check.

Hope that helps,

Slau

On Mar 26, 2015, at 5:13 AM, Chi Kim chigook...@hotmail.com wrote:


Hi Slau,

Just for update, Clip indicators was already set to hold for infinite, and VO 
still doesn't announces when the meter is clipped.
Anything else I should check?
Thanks for your help,

Chi

On 3/22/2015 3:17 PM, Slau Halatyn wrote:

Hi Chi,

Yep, the Click plug-in's parameters don't work well right now. That's certainly 
on the list of things to tackle. Incidentally, the parameters are accessible 
with a control surface. So, for example, to access triplets and accent values, 
etc., the encoder knobs or faders in flip mode will control those parameters 
and it's possible to save those settings as presets for future use.

The clip indicators are working fine. Make sure you have your preferences set 
to hold clip indicators and you should be good to go.

The subject of preset browsing in the plug-in window is clearly a much larger 
issue and, regardless of its accessibility, I'm not sure that it's going to 
necessarily change any time soon. Surely, it's much more of an issue for 
virtual instruments and one size doesn't fit all so I wouldn't expect Avid to 
come up with any solution that'll be right for every developer. Plug-in 
accessibility, in general, is an important issue and its model might have to 
change entirely for it to be viable for the long term. We'll all keep trying 
until we get it right.

Slau

On Mar 22, 2015, at 3:09 PM, Chi Kim chigook...@hotmail.com wrote:


Hi Slau,

The new click plugin included in pt 11 is not accessible.
Also, getting access to warp markers would be good.
I believe clip indicator is not accessible with Voiceover anymore. When the 
meter clips, Voiceover used to say clipped until you clear it, but it doesn't 
say it anymore.
Lastly, I know you specifically said no new future request, but it'd be worth 
while to briefly mention about creating a flexible database system that manages 
all the presets for all the plugin with tagging system something like Native 
Instrument Komplete. Komplete consists of many plugins with many presets (total 
17,000), but you can browse all of them in one browser and load them easily. 
This would save a lot of time for any composers/producers to find right sound 
without going through many different plugins with many different presets.
The current preset system for Pro Tools is so old style and not that flexible, 
so many developers don't even bother and create their own instead.
I'm sure this would require a lot of thought process to make it useful for 
users, and easier for plugin developers to implement. However, if Avid pulls it 
off well and markets it as a cool new feature, it would benefit everyone 
regardless sighted or blind once the developers start taking advantage of it.
Thanks for working with Avid on this important work.

Chi

On 3/16/2015 10:41 AM, Slau Halatyn wrote:

In a couple of weeks, I'm going to have a unique opportunity to sit down with a 
programmer to work on some accessibility issues in Pro Tools. Under the 
circumstances of my trip, Avid has allowed for this meeting to be scheduled 
barring any last minute crisis with the release of Pro Tools 12. This will be 
largely driven by bug submissions already within the beta system but I wanted 
to get a sense of what the user base is focused on day to day. My goal is to 
address quality-of-life issues that affect the use of Pro Tools with VoiceOver. 
For example, the way the inserts and, in particular, sends are displayed is 
simply awful. This needs to be overhauled. There are a number of such issues 
that can hopefully be taken care

Re: feedback needed for Pro Tools 12

[Chi Kim]

Thanks Slau, I'll keep looking around and update what I find as well.
Have a safe trip!

Chi
On 3/26/2015 8:55 PM, Slau Halatyn wrote:

Hi Chi,

I can't think of anything else at this point. I'm not sure why it's not working 
for you right now. I'll be travelling overseas tomorrow so I suppose I'll have 
plenty of time to ponder this one :)

Best,

Slau

On Mar 26, 2015, at 8:21 PM, Chi Kim chigook...@hotmail.com wrote:


HI Slau, thanks for the help.
Yes I'm aware of the fact that the Voiceover reads the radio buttons in such 
ways for that particular settings.
Peak on the left and and Clip indicator on the right
Then the related radio buttons below the labels.
I went to clip indicator label first then went down to make sure infinite is 
selected. It's very mysterious why it's not working.
Can you think of any other setting that might be preventing this?
Thanks,

Chi

On 3/26/2015 10:05 AM, Slau Halatyn wrote:

Hi Chi,

I've just verified that in version 11.3 the clip indicator definitely works. I'm not sure what might be 
causing your problem with the indicator. One thing I would check is that you have the correct radio button 
checked in the Metering tab of the Preferences window. The way it reads is not entirely clear at first. There 
are two columns, one for Peak and one for Clipping. If you read across, you might mistake the first column as 
immediately following the Clip text. I'm not sure if this happened to you or not but, just to be sure, I 
would check it again. Navigate to the right until you reach the first radio button that reads 3 
seconds and then continue to the second radio button that reads 3 seconds. This is the 
column that pertains to Clipping. Navigate down and you'll find the Infinite radio button and 
make sure it's check.

Hope that helps,

Slau

On Mar 26, 2015, at 5:13 AM, Chi Kim chigook...@hotmail.com wrote:


Hi Slau,

Just for update, Clip indicators was already set to hold for infinite, and VO 
still doesn't announces when the meter is clipped.
Anything else I should check?
Thanks for your help,

Chi

On 3/22/2015 3:17 PM, Slau Halatyn wrote:

Hi Chi,

Yep, the Click plug-in's parameters don't work well right now. That's certainly 
on the list of things to tackle. Incidentally, the parameters are accessible 
with a control surface. So, for example, to access triplets and accent values, 
etc., the encoder knobs or faders in flip mode will control those parameters 
and it's possible to save those settings as presets for future use.

The clip indicators are working fine. Make sure you have your preferences set 
to hold clip indicators and you should be good to go.

The subject of preset browsing in the plug-in window is clearly a much larger 
issue and, regardless of its accessibility, I'm not sure that it's going to 
necessarily change any time soon. Surely, it's much more of an issue for 
virtual instruments and one size doesn't fit all so I wouldn't expect Avid to 
come up with any solution that'll be right for every developer. Plug-in 
accessibility, in general, is an important issue and its model might have to 
change entirely for it to be viable for the long term. We'll all keep trying 
until we get it right.

Slau

On Mar 22, 2015, at 3:09 PM, Chi Kim chigook...@hotmail.com wrote:


Hi Slau,

The new click plugin included in pt 11 is not accessible.
Also, getting access to warp markers would be good.
I believe clip indicator is not accessible with Voiceover anymore. When the 
meter clips, Voiceover used to say clipped until you clear it, but it doesn't 
say it anymore.
Lastly, I know you specifically said no new future request, but it'd be worth 
while to briefly mention about creating a flexible database system that manages 
all the presets for all the plugin with tagging system something like Native 
Instrument Komplete. Komplete consists of many plugins with many presets (total 
17,000), but you can browse all of them in one browser and load them easily. 
This would save a lot of time for any composers/producers to find right sound 
without going through many different plugins with many different presets.
The current preset system for Pro Tools is so old style and not that flexible, 
so many developers don't even bother and create their own instead.
I'm sure this would require a lot of thought process to make it useful for 
users, and easier for plugin developers to implement. However, if Avid pulls it 
off well and markets it as a cool new feature, it would benefit everyone 
regardless sighted or blind once the developers start taking advantage of it.
Thanks for working with Avid on this important work.

Chi

On 3/16/2015 10:41 AM, Slau Halatyn wrote:

In a couple of weeks, I'm going to have a unique opportunity to sit down with a 
programmer to work on some accessibility issues in Pro Tools. Under the 
circumstances of my trip, Avid has allowed for this meeting to be scheduled 
barring any last minute crisis with the release of Pro Tools 12. This will be 
largely

Re: feedback needed for Pro Tools 12

[Chi Kim]

Hi Slau,

The new click plugin included in pt 11 is not accessible.
Also, getting access to warp markers would be good.
I believe clip indicator is not accessible with Voiceover anymore. When 
the meter clips, Voiceover used to say clipped until you clear it, but 
it doesn't say it anymore.
Lastly, I know you specifically said no new future request, but it'd be 
worth while to briefly mention about creating a flexible database system 
that manages all the presets for all the plugin with tagging system 
something like Native Instrument Komplete. Komplete consists of many 
plugins with many presets (total 17,000), but you can browse all of them 
in one browser and load them easily. This would save a lot of time for 
any composers/producers to find right sound without going through many 
different plugins with many different presets.
The current preset system for Pro Tools is so old style and not that 
flexible, so many developers don't even bother and create their own instead.
I'm sure this would require a lot of thought process to make it useful 
for users, and easier for plugin developers to implement. However, if 
Avid pulls it off well and markets it as a cool new feature, it would 
benefit everyone regardless sighted or blind once the developers start 
taking advantage of it.

Thanks for working with Avid on this important work.

Chi

On 3/16/2015 10:41 AM, Slau Halatyn wrote:

In a couple of weeks, I'm going to have a unique opportunity to sit down with a 
programmer to work on some accessibility issues in Pro Tools. Under the 
circumstances of my trip, Avid has allowed for this meeting to be scheduled 
barring any last minute crisis with the release of Pro Tools 12. This will be 
largely driven by bug submissions already within the beta system but I wanted 
to get a sense of what the user base is focused on day to day. My goal is to 
address quality-of-life issues that affect the use of Pro Tools with VoiceOver. 
For example, the way the inserts and, in particular, sends are displayed is 
simply awful. This needs to be overhauled. There are a number of such issues 
that can hopefully be taken care of in one marathon session of tweaks.

I have a clear idea of what I personally think should be addressed but I 
thought I'd take the temperature of the community. What I'm asking of the list 
is for people to enumerate 3 to 5 things that most affect their productivity 
and would like to see improved. Now, I don't mean for people to suggest a 
different method for importing files to an existing track. That's a bigger fish 
to fry and the subject of a longer term solution. These are, as I said, 
quality-of-life issues that can be addressed quickly. Also, don't bring up 
issues in version 10. We're talking existing issues in version 11. Give me your 
top 3 or top 5 items and we'll see which seem to reveal themselves as the 
biggest concerns. The sooner you get those to me, the sooner I can prepare.

Thanks,

Slau



--
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: Working with Midi Event List

[Chi Kim]

Thanks Slau,
I'll have to play little more and see why this is not consistent.
Do you have Cursor tracking on? What about mouse cursor follows 
Voiceover Cursor?

Thanks

Chi
On 2/15/2015 7:36 PM, Slau Halatyn wrote:

Hi Chi,

OK, I've finally had a chance to see what kind of behavior I'm getting in PT 
version 11.3. I opened a session with a huge number of MIDI events, twelve 
thousand in the bass track alone. When I enter a main counter value much higher 
than the current MIDI Event List displays, if I don't stop interacting with the 
event list table, VoiceOver will not see the new events even though they're 
visually displayed. If I stop interacting with the event list table and 
interact once again, VoiceOver seems to read the events correctly. I did, 
however, encounter episodes when I entered a new counter value and on the first 
instance of interacting, VoiceOver didn't seem to read the correct value but 
upon re-entering the counter value, it did read the correct value. I've had my 
assistant confirm that the behavior is somewhat inconsistent even from a visual 
perspective. Who knows… Anyway, hope that helps in some small way.

Best,

Slau

On Feb 14, 2015, at 8:55 PM, Chi Kim chigook...@hotmail.com wrote:


Thanks Slau for helping with this.
Yes, you're correct. I moved the main counter using star numbers enter. Also I 
confirmed with the hotspot on the main counter after I jumped.
I found something interesting though. If I jump by a big number of bars like 30 
50 80, it kind of works.
However, VO cursor only gets synchronized only if the event list table moves 
from bottom of the screen to top of the screen (left of close minimize zoom 
buttons) and vice versa.
You know how track list table sometimes jumps to next to the close button. It 
does that much more frequently with the event list table when you jump by big 
number. The voiceover cursor kind of gets synchronized when this happens. When 
the voiceover cursor gets synchronized, the cursor kind of gets closer to the 
bar I jumped to, instead of the exact bar. For example, if I go to bar 60, it 
might be at like bar 54.
If I move by a small number of bars like 2 or 3 bars, nothing happens. I guess 
something has to do with when the screen scrolls.
Hope I can get this sorted out soon.
Thanks again,

Chi

On 2/14/2015 12:39 PM, Slau Halatyn wrote:

Hi Chi,

Just so that we're on the same page figuratively and literally, if you start 
reading through a list of MIDI events at bar 1 and then press the asterisk on 
the numeric keypad and enter 100 and press return, if you stop interacting with 
any and all items in the MIDI Event List window and then re-interact with the 
event list itself, VoiceOver should now see a range from just before bar 100 
and onward. Of course, there needs to be enough events to populate the range of 
up to bar 100 and beyond in order for the window itself to scroll to that 
point. I'll have another look soon.

Slau

On Feb 14, 2015, at 8:55 AM, Chi Kim chigook...@hotmail.com wrote:


Thanks Slau. Let me know what you find.
Even if I manually change the main counter, unfortunately Voiceover cursor 
doesn't get updated.

Chi

On 2/13/2015 11:45 AM, Slau Halatyn wrote:

Hi chi,

I think what the problem might be is that, when a note is selected in a MIDI 
track, changing the main counter doesn't necessarily change the selection of 
the note. In other words, selected MIDI events are not the same as selecting a 
range within the timeline of a MIDI track. That said, If an edit range is 
subsequently selected, I believe the MIDI events, by default, become 
unselected. As mentioned earlier, I do think that un-interacting with the event 
list table will bring focus to the current main counter position or selected 
edit range. I'm not at the studio today so I can't verify this but I do think 
that might be the case. I'll try to take a look at this over the weekend.

HTH,

Slau

On Feb 13, 2015, at 11:12 AM, Chi Kim chigook...@hotmail.com wrote:


HI Slau and John,

Thanks so much for those suggestions.
Interacting and selecting with vo+space seems to work relyably to edit a value.
However, the synchronizing vo cursor with the current counter doesn't seem to 
work.
If I'm on the first note at bar 1, and if I move the counter using down arrow 
or other methods, the vo cursor is still at the first note on bar 1 even after 
I stop interact and start interact again with the table.
Am I missing a step?
I'm on Mavericks with pt 11.3 if it makes difference.
Thanks,

Chi
On 2/12/2015 6:33 PM, Slau Halatyn wrote:

Hi Chi,

The MIDI Event List is a little tricky but especially because VoiceOver has a 
tendency to see what's not really there and not see what's really there, if you 
know what I mean.

Let's say you've clicked on a MIDI event. The event will become highlighted 
and, if it's a note, you should hear it. Pressing the arrow down does move the 
selection to the adjacent notes. Now, let's say you entered a main counter 
value

Re: Working with Midi Event List

[Chi Kim]

Thanks Slau. Let me know what you find.
Even if I manually change the main counter, unfortunately Voiceover 
cursor doesn't get updated.


Chi

On 2/13/2015 11:45 AM, Slau Halatyn wrote:

Hi chi,

I think what the problem might be is that, when a note is selected in a MIDI 
track, changing the main counter doesn't necessarily change the selection of 
the note. In other words, selected MIDI events are not the same as selecting a 
range within the timeline of a MIDI track. That said, If an edit range is 
subsequently selected, I believe the MIDI events, by default, become 
unselected. As mentioned earlier, I do think that un-interacting with the event 
list table will bring focus to the current main counter position or selected 
edit range. I'm not at the studio today so I can't verify this but I do think 
that might be the case. I'll try to take a look at this over the weekend.

HTH,

Slau

On Feb 13, 2015, at 11:12 AM, Chi Kim chigook...@hotmail.com wrote:


HI Slau and John,

Thanks so much for those suggestions.
Interacting and selecting with vo+space seems to work relyably to edit a value.
However, the synchronizing vo cursor with the current counter doesn't seem to 
work.
If I'm on the first note at bar 1, and if I move the counter using down arrow 
or other methods, the vo cursor is still at the first note on bar 1 even after 
I stop interact and start interact again with the table.
Am I missing a step?
I'm on Mavericks with pt 11.3 if it makes difference.
Thanks,

Chi
On 2/12/2015 6:33 PM, Slau Halatyn wrote:

Hi Chi,

The MIDI Event List is a little tricky but especially because VoiceOver has a 
tendency to see what's not really there and not see what's really there, if you 
know what I mean.

Let's say you've clicked on a MIDI event. The event will become highlighted 
and, if it's a note, you should hear it. Pressing the arrow down does move the 
selection to the adjacent notes. Now, let's say you entered a main counter 
value of bar 77. What happens is that the main counter will jump to bar 77 but 
VoiceOver is still seeing the original location. What you need to do is stop 
interacting with the event list and reinteract with it and VoiceOver will read 
the correct information.

With a control surface, you can scrub and select notes and it's a quick process 
but moving around the list itself can sometimes be tedious.

When you do find the parameter you wish to edit, as John said, interact with 
the text and press Control-Option-Space bar. The contents will be selected and 
you can enter the new value. You should be aware of the following behavior:

After entering a new value, pressing Return will confirm the new value and the 
entire row of parameters becomes selected. If you don't press Return, you can 
use the left or right arrow keys to move to different parameters but VoiceOver 
doesn't seem to speak those values unless you move the voiceOver cursor. I 
haven't played around with this aspect terribly much but that's what seems to 
be the case.

Hope that helps,

Slau



On Feb 11, 2015, at 11:45 PM, Chi Kim chigook...@hotmail.com wrote:


Hi All,

What's the best way to go through midi event list?
There are couple of things that make it little difficult to navigate the table, 
and I'm not sure if there's workarounds for these problems.
1. Synchronizing the current event and the Voiceover cursor
When you fast forward and rewind, the Voiceover cursor doesn't get synchronized 
with the playback cursor.
Let's say your voiceover cursor is on the first note. When you hit play and 
stop few bars later, your voiceover cursor is still on the first note.
Only workaround I found is to select a note, and press down arrow until I find 
somewhere closer to the spot I want. If you do this, You'll hear the notes as 
you holding down the down arrow. Then you can open item chooser, search for the 
word select, and click on the first item.
This works nicely, but you can only find a spot using down arrow, and you first 
have to select a note if you want to hear as you go down. Also this means you 
have to start searching from wherever your Voiceover cursor is.
2. Editing
Can you only open the edit fields with vo+shift+space? Simulating mouse click 
with Voiceover can be pretty flaky sometimes.
According to a sited person, The mouse cursor sometimes stays at the top left 
corner and opens menu bar if you simulate mouse click with Voiceover For some 
reason. This happens if you set mouse cursor to follow voiceover and turned the 
cursor tracking on. Also, routing mouse cursor to Voiceover cursor by pressing 
vo+cmd+f5 doesn't fix either. The mouse cursor just stays on the top left.
I'd appreciate if someone could share how to deal with those issues.
Thank you for your help,

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

Re: Working with Midi Event List

[Chi Kim]

Thanks Slau for helping with this.
Yes, you're correct. I moved the main counter using star numbers enter. 
Also I confirmed with the hotspot on the main counter after I jumped.
I found something interesting though. If I jump by a big number of bars 
like 30 50 80, it kind of works.
However, VO cursor only gets synchronized only if the event list table 
moves from bottom of the screen to top of the screen (left of close 
minimize zoom buttons) and vice versa.
You know how track list table sometimes jumps to next to the close 
button. It does that much more frequently with the event list table when 
you jump by big number. The voiceover cursor kind of gets synchronized 
when this happens. When the voiceover cursor gets synchronized, the 
cursor kind of gets closer to the bar I jumped to, instead of the exact 
bar. For example, if I go to bar 60, it might be at like bar 54.
If I move by a small number of bars like 2 or 3 bars, nothing happens. I 
guess something has to do with when the screen scrolls.

Hope I can get this sorted out soon.
Thanks again,

Chi

On 2/14/2015 12:39 PM, Slau Halatyn wrote:

Hi Chi,

Just so that we're on the same page figuratively and literally, if you start 
reading through a list of MIDI events at bar 1 and then press the asterisk on 
the numeric keypad and enter 100 and press return, if you stop interacting with 
any and all items in the MIDI Event List window and then re-interact with the 
event list itself, VoiceOver should now see a range from just before bar 100 
and onward. Of course, there needs to be enough events to populate the range of 
up to bar 100 and beyond in order for the window itself to scroll to that 
point. I'll have another look soon.

Slau

On Feb 14, 2015, at 8:55 AM, Chi Kim chigook...@hotmail.com wrote:


Thanks Slau. Let me know what you find.
Even if I manually change the main counter, unfortunately Voiceover cursor 
doesn't get updated.

Chi

On 2/13/2015 11:45 AM, Slau Halatyn wrote:

Hi chi,

I think what the problem might be is that, when a note is selected in a MIDI 
track, changing the main counter doesn't necessarily change the selection of 
the note. In other words, selected MIDI events are not the same as selecting a 
range within the timeline of a MIDI track. That said, If an edit range is 
subsequently selected, I believe the MIDI events, by default, become 
unselected. As mentioned earlier, I do think that un-interacting with the event 
list table will bring focus to the current main counter position or selected 
edit range. I'm not at the studio today so I can't verify this but I do think 
that might be the case. I'll try to take a look at this over the weekend.

HTH,

Slau

On Feb 13, 2015, at 11:12 AM, Chi Kim chigook...@hotmail.com wrote:


HI Slau and John,

Thanks so much for those suggestions.
Interacting and selecting with vo+space seems to work relyably to edit a value.
However, the synchronizing vo cursor with the current counter doesn't seem to 
work.
If I'm on the first note at bar 1, and if I move the counter using down arrow 
or other methods, the vo cursor is still at the first note on bar 1 even after 
I stop interact and start interact again with the table.
Am I missing a step?
I'm on Mavericks with pt 11.3 if it makes difference.
Thanks,

Chi
On 2/12/2015 6:33 PM, Slau Halatyn wrote:

Hi Chi,

The MIDI Event List is a little tricky but especially because VoiceOver has a 
tendency to see what's not really there and not see what's really there, if you 
know what I mean.

Let's say you've clicked on a MIDI event. The event will become highlighted 
and, if it's a note, you should hear it. Pressing the arrow down does move the 
selection to the adjacent notes. Now, let's say you entered a main counter 
value of bar 77. What happens is that the main counter will jump to bar 77 but 
VoiceOver is still seeing the original location. What you need to do is stop 
interacting with the event list and reinteract with it and VoiceOver will read 
the correct information.

With a control surface, you can scrub and select notes and it's a quick process 
but moving around the list itself can sometimes be tedious.

When you do find the parameter you wish to edit, as John said, interact with 
the text and press Control-Option-Space bar. The contents will be selected and 
you can enter the new value. You should be aware of the following behavior:

After entering a new value, pressing Return will confirm the new value and the 
entire row of parameters becomes selected. If you don't press Return, you can 
use the left or right arrow keys to move to different parameters but VoiceOver 
doesn't seem to speak those values unless you move the voiceOver cursor. I 
haven't played around with this aspect terribly much but that's what seems to 
be the case.

Hope that helps,

Slau



On Feb 11, 2015, at 11:45 PM, Chi Kim chigook...@hotmail.com wrote:


Hi All,

What's the best way to go through midi event list?
There are couple of things that make

Re: Working with Midi Event List

[Chi Kim]

HI Slau and John,

Thanks so much for those suggestions.
Interacting and selecting with vo+space seems to work relyably to edit a 
value.
However, the synchronizing vo cursor with the current counter doesn't 
seem to work.
If I'm on the first note at bar 1, and if I move the counter using down 
arrow or other methods, the vo cursor is still at the first note on bar 
1 even after I stop interact and start interact again with the table.

Am I missing a step?
I'm on Mavericks with pt 11.3 if it makes difference.
Thanks,

Chi
On 2/12/2015 6:33 PM, Slau Halatyn wrote:

Hi Chi,

The MIDI Event List is a little tricky but especially because VoiceOver has a 
tendency to see what's not really there and not see what's really there, if you 
know what I mean.

Let's say you've clicked on a MIDI event. The event will become highlighted 
and, if it's a note, you should hear it. Pressing the arrow down does move the 
selection to the adjacent notes. Now, let's say you entered a main counter 
value of bar 77. What happens is that the main counter will jump to bar 77 but 
VoiceOver is still seeing the original location. What you need to do is stop 
interacting with the event list and reinteract with it and VoiceOver will read 
the correct information.

With a control surface, you can scrub and select notes and it's a quick process 
but moving around the list itself can sometimes be tedious.

When you do find the parameter you wish to edit, as John said, interact with 
the text and press Control-Option-Space bar. The contents will be selected and 
you can enter the new value. You should be aware of the following behavior:

After entering a new value, pressing Return will confirm the new value and the 
entire row of parameters becomes selected. If you don't press Return, you can 
use the left or right arrow keys to move to different parameters but VoiceOver 
doesn't seem to speak those values unless you move the voiceOver cursor. I 
haven't played around with this aspect terribly much but that's what seems to 
be the case.

Hope that helps,

Slau



On Feb 11, 2015, at 11:45 PM, Chi Kim chigook...@hotmail.com wrote:


Hi All,

What's the best way to go through midi event list?
There are couple of things that make it little difficult to navigate the table, 
and I'm not sure if there's workarounds for these problems.
1. Synchronizing the current event and the Voiceover cursor
When you fast forward and rewind, the Voiceover cursor doesn't get synchronized 
with the playback cursor.
Let's say your voiceover cursor is on the first note. When you hit play and 
stop few bars later, your voiceover cursor is still on the first note.
Only workaround I found is to select a note, and press down arrow until I find 
somewhere closer to the spot I want. If you do this, You'll hear the notes as 
you holding down the down arrow. Then you can open item chooser, search for the 
word select, and click on the first item.
This works nicely, but you can only find a spot using down arrow, and you first 
have to select a note if you want to hear as you go down. Also this means you 
have to start searching from wherever your Voiceover cursor is.
2. Editing
Can you only open the edit fields with vo+shift+space? Simulating mouse click 
with Voiceover can be pretty flaky sometimes.
According to a sited person, The mouse cursor sometimes stays at the top left 
corner and opens menu bar if you simulate mouse click with Voiceover For some 
reason. This happens if you set mouse cursor to follow voiceover and turned the 
cursor tracking on. Also, routing mouse cursor to Voiceover cursor by pressing 
vo+cmd+f5 doesn't fix either. The mouse cursor just stays on the top left.
I'd appreciate if someone could share how to deal with those issues.
Thank you for your help,

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/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.

Working with Midi Event List

[Chi Kim]

Hi All,

What's the best way to go through midi event list?
There are couple of things that make it little difficult to navigate the 
table, and I'm not sure if there's workarounds for these problems.

1. Synchronizing the current event and the Voiceover cursor
When you fast forward and rewind, the Voiceover cursor doesn't get 
synchronized with the playback cursor.
Let's say your voiceover cursor is on the first note. When you hit play 
and stop few bars later, your voiceover cursor is still on the first note.
Only workaround I found is to select a note, and press down arrow until 
I find somewhere closer to the spot I want. If you do this, You'll hear 
the notes as you holding down the down arrow. Then you can open item 
chooser, search for the word select, and click on the first item.
This works nicely, but you can only find a spot using down arrow, and 
you first have to select a note if you want to hear as you go down. Also 
this means you have to start searching from wherever your Voiceover 
cursor is.

2. Editing
Can you only open the edit fields with vo+shift+space? Simulating mouse 
click with Voiceover can be pretty flaky sometimes.
According to a sited person, The mouse cursor sometimes stays at the top 
left corner and opens menu bar if you simulate mouse click with 
Voiceover For some reason. This happens if you set mouse cursor to 
follow voiceover and turned the cursor tracking on. Also, routing mouse 
cursor to Voiceover cursor by pressing vo+cmd+f5 doesn't fix either. The 
mouse cursor just stays on the top left.

I'd appreciate if someone could share how to deal with those issues.
Thank you for your help,

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/d/optout.

Re: Configuring Click II

[Chi Kim]

Thanks Slau for confirming.
I just wanted to make sure I'm not missing something here.

Chi

On 2/5/2015 7:02 PM, Slau Halatyn wrote:

Unfortunately, the access leaves much to be desired but that will change soon 
enough.

Slau

On Feb 5, 2015, at 7:48 AM, Chi Kim chigook...@hotmail.com wrote:


Hi All,

Does anyone have any luck configuring new Click II plugin for click track on pt 
11?
Only thing I can do is to change the volume for accented and unaccented beat.
All other controls like subdivision doesn't seem to have any effect when you 
change with Voiceover.
Also, it seems there's no way to change the sound with Voiceover without 
creating presets for each.
Thanks for help,

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/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: Pro Tools Busy?

[Chi Kim]

I thought I was running PT 11.2.1, but I was on 11.2.0.
I upgraded to pt 11.2.1, and the symptom seems to be gone for now. I'll 
report back if it reappears.
For future reference, how do you initialize the preference for PT and 
Voiceover?

Thanks for help.

On 10/28/2014 7:34 AM, 'Hi' via Pro Tools Accessibility wrote:
I had the exact same problem and symptoms. I trashed the VO prefs and 
all of the PT prefs at one time. Although I believe it was the VO 
prefs I felt it would be best to start with a clean slate for both. I 
never had that problem again.

On 10/27/2014 8:45 PM, Chi Kim wrote:

I upgraded to Pro Tools 11.2.1 on Mavericks.
When I go into track list table, voiceover frequently says Pro Tools 
busy, and only way to fix is to restart VoiceOver. This happens quite 
often.

I made sure no other window is open other than mix and edit.
Does anyone have this problem, or know how to fix this?
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/d/optout.

Pro Tools Busy?

[Chi Kim]

I upgraded to Pro Tools 11.2.1 on Mavericks.
When I go into track list table, voiceover frequently says Pro Tools 
busy, and only way to fix is to restart VoiceOver. This happens quite often.

I made sure no other window is open other than mix and edit.
Does anyone have this problem, or know how to fix this?
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/d/optout.