Re: PT 2024.10 and VoiceOver

[Slau Halatyn]

Tracks can once again be dragged within the track list table. Other than that, 
there's nothing of note.t

> On Oct 31, 2024, at 7:37 PM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> Has anyone experienced any accessibility issues or VO related compatibility 
> problems with PT 2024.10 and Voiceover?
> 
> 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.
> To view this discussion visit 
> https://groups.google.com/d/msgid/ptaccess/DC02536E-68B3-4AEC-958C-FEE2F09ACF4B%40a-pro-studio.no.

-- 
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 visit 
https://groups.google.com/d/msgid/ptaccess/198C17B0-DD0F-4F50-8978-EB1B46C181AA%40gmail.com.

Re: ttrack hight change after splitting drum track

[Slau Halatyn]

Hi Tom,

Control+Up and Down arrow will adjust the height of a selected track. If 
multiple tracks are selected, it'll apply the change to all of the selected 
tracks. Be aware that tracks will change relative to each other. This means 
that, if various sizes are present, they will all change in tandem relative to 
each other. Therefore, it's a good idea, for example, to press Control+Up Arrow 
a bunch of times. This will ensure that the track heights all reach the biggest 
size which is "extreme." Then 3 pressess of Control+Down Arrow will bring the 
size of all selected tracks down to "medium."

The other method would be to select the tracks and, in the Edit window, 
interact with one of the selected tracks and Option+Shift+click on the first 
control and choose "medium" from the menu. Alternatively, you can also just 
Option+click to set all tracks to that height as well. If you use flo Tools, 
turn Flo Mouse on with Command+Forward Slash and you can easily perform 
modified mouse clicks which VoiceOver doesn't support natively. Pressing 
modifiers along with the Tilde key (below the escape key) will issue the mouse 
click.

HTH,
Slau


> On Sep 17, 2024, at 7:55 AM, Tom Hessels  wrote:
> 
> Hi Slau,
> Thank you! I understand this behaviour.
> Just one question: how can i change track height for more than one track at 
> once?
> Tom.
> 
>> Op 17 sep 2024, om 01:17 heeft Slau Halatyn  het 
>> volgende geschreven:
>> 
>> Hi Tom,
>> 
>> Depending on how you split the track (i.e. all notes to separate tracks), 
>> perhaps the expected behavior is to make the track height single note. 
>> Imagine if you split a drum track with 30 different notes, if they were all 
>> set to medium height, one would have to scroll up and down the Edit window 
>> constantly. Of course, this pertains to sighted users more so but, even for 
>> a screen reader user, the navigation would surely be effected. With more 
>> tracks visible in the timeline, there would be fewer instances of having to 
>> navigate left and right rather than up and down. Of course, you could always 
>> select the tracks and increase track height.
>> 
>> Slau
>> 
>> 
>>> On Sep 16, 2024, at 7:33 AM, Tom Hessels  wrote:
>>> 
>>> Hi All,
>>> After i split a drum kit in different tracks some things e.g. Typing W 
>>> don't tells me if i am in notes or clips.
>>> After some searching i find that track height has been changed. It shoult 
>>> be Medium but single Notes is ticked.
>>> Why is this and is it possible that after splitting that track height  
>>> stays medium?
>>> 
>>> Tom.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/A78CE7E2-FA68-40CD-9CF4-524B2A52CD32%40tomhessels.nl.
>> 
>> -- 
>> 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/3C102FA9-90D2-4EC5-99B6-6613C8D160C5%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/57FD5390-C5A4-44D7-8091-081C9AD053B0%40tomhessels.nl.

-- 
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/34FDB45C-79F3-4202-A0E3-7F8DFF5BBAE2%40gmail.com.

Re: ttrack hight change after splitting drum track

[Slau Halatyn]

Hi Tom,

Depending on how you split the track (i.e. all notes to separate tracks), 
perhaps the expected behavior is to make the track height single note. Imagine 
if you split a drum track with 30 different notes, if they were all set to 
medium height, one would have to scroll up and down the Edit window constantly. 
Of course, this pertains to sighted users more so but, even for a screen reader 
user, the navigation would surely be effected. With more tracks visible in the 
timeline, there would be fewer instances of having to navigate left and right 
rather than up and down. Of course, you could always select the tracks and 
increase track height.

Slau


> On Sep 16, 2024, at 7:33 AM, Tom Hessels  wrote:
> 
> Hi All,
> After i split a drum kit in different tracks some things e.g. Typing W don't 
> tells me if i am in notes or clips.
> After some searching i find that track height has been changed. It shoult be 
> Medium but single Notes is ticked.
> Why is this and is it possible that after splitting that track height  stays 
> medium?
> 
> Tom.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/A78CE7E2-FA68-40CD-9CF4-524B2A52CD32%40tomhessels.nl.

-- 
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/3C102FA9-90D2-4EC5-99B6-6613C8D160C5%40gmail.com.

Re: Pro Tools manuals

[Slau Halatyn]

Hi Martin,

I'm not sure what you mean by "no OCR please." For example, FineReaderOCR 
converts PDF files to multiple formats including html while preserving 
structure as well. I would imagine that Adobe itself uses the same protocol. I 
haven't converted any PT manuals for quite some time but I'll probably do that 
soon. I'd imagine you're probably in need of converting something other than 
the PT docs, eh?

slau


> On Jul 8, 2024, at 7:26 AM, Martin (Punky) Sopart  wrote:
> 
> Hello all!
> 
> For years now I am using the Adobe Pro export to HTML function to get quite
> good structured HTML files instead of Avid's PDFs.
> Is there maybe a bettr and cheaper solution out now for Mac OS?
> No OCR please.
> 
> Thank you and best whishes! / 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/001101dad129%24b360a290%241a21e7b0%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/17D03594-9909-4488-BECF-1602F9897835%40gmail.com.

Re: Import all member tracks in a folder

[Slau Halatyn]

Hi John,

It surely is a matter of the table not revealing the control. It's apparently a 
circular icon following the folder name that has two or three different 
appearances depending upon whether the selection includes all or none or some 
of the tracks contained within that folder. Tables of this type are a bit 
tricky to define correctly for VoiceOver. A possible workaround for now is to 
collapse folders by clicking on them, pressing Shift+F while using Command+A 
while an open folder is visible. This will set everything in the list to "New 
Track" and you can then selectively choose "None" for any closed folders you 
wish not to import.
HTH,
slau


> On Jul 3, 2024, at 12:15 PM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> In the documentation for PT 2024.6 it is mentioned that it now should be 
> possible to import all tracks that are members of a folder by simply checking 
> a checkbox beside the folder in the list in the import dialog window. But I 
> can’t find it. Still, the only way to import all member tracks in a folder is 
> to  also set each track in the folder to «New track».
> 
> Is this checkbox invisible to VoiceOver?
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/E23A0CEC-3514-42CF-B38A-013D805F4E58%40a-pro-studio.no.

-- 
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/1BD63A35-9EBC-4A93-87BE-8B3936C0A364%40gmail.com.

Re: presets i've saved not displaying in protools

[Slau Halatyn]

Glad to hear you're back on track. Cheers!

> On Jun 21, 2024, at 10:51 AM, Steve Sparrow  wrote:
> 
> Got it sorted now. We had to rebuild the plug in presets in tools. Some sort 
> of corruption in the preset settings. But working well now. New protools is 
> great. Very happy I updated.
> Steve
> 
> 
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of 
> Steve Sparrow
> Sent: Thursday, June 20, 2024 7:18 AM
> To: ptaccess@googlegroups.com
> Subject: RE: presets i've saved not displaying in protools
> 
> Hey, thanks Slau.
> Yeah, actually after further investigation I think there is a problem with 
> the plug in window in tools on my system.
> I've got my wife Karen to have a look at the screne. There are no plug in 
> presets available to choose from. When I try to sav  a setting with save as, 
> as I have always done, it is not a a valable  to find on screne, or with 
> voice over. all I have to choose from is the one setting. The one factory 
> defalt setting.
> So unless you have further ideas, I think it is a problem in my set up.
> My mac is an old one, I'm running Monterey 12.75. That's the latest OS I can 
> put on this mac.
> I've got the current version of PT, according to avid, it is complient with 
> Monterey. 
> Don't worry mate. I think it's an issue I'll need to sort. I've trashed the 
> ;preferences in tools. With PT prefs. But they didn't want to trash. So weard 
> stuff happening with this thing.
> Fun and games. Lol
> Steve
> 
> 
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Thursday, June 20, 2024 1:59 AM
> To: PTAccess List 
> Subject: Re: presets i've saved not displaying in protools
> 
> Hi steve,
> 
> there never was a problem with factory presets in Pro Tools so I’m not sure 
> what you’re thinking of. In the case of saving your own presets, you’d need 
> to choose “Save As…” from the Settings menu. If you haven’t saved any prior 
> and, if there aren’t any factory presets, Pro Tools will create a folder in 
> your Documents/Pro Tools/Plug-in Settings folder and will take on the name of 
> the plug-in. Occasionally the manufacturer name precedes the plug-in name and 
> sometimes it doesn’t. You can either double-tap VO+f2 and look at the Plug-in 
> window’s title or, alternatively, you can sort your Plug-in Settings folder 
> by date. To do this, focus on the folder and press Control+Option+Command+4. 
> By default, the newest item will be at the top of the list and that should be 
> the folder where you saved a new preset.
> 
> Hope that helps,
> Slau
> 
> 
>> On Jun 19, 2024, at 6:45 AM, Steve Sparrow  wrote:
>> 
>> Hey again guys.
>> I’ve noticed I can’t do anything with plug in presets in PT.
>> I know the stock presets were a problem in the older protools. But now I’ve 
>> upgraded to the current version of tools, I can’t see any preset at all 
>> except the factory defalts, when I’m on the library name field.  I tried 
>> saving some presets in some plug ins, and I can’t see them either. Is there 
>> something new going on here with to get access to the plug in preset 
>> settings.
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516E13D297BC1508C6B17EBE7CF2%40SY4P282MB1516.AUSP282.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/7B59D959-A141-41C8-99AF-8CFFDB7EEEB4%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/SY4P282MB1516D9336994CB5C9BD5E910E7CF2%40SY4P282MB1516.AUSP282.PROD.OUTLOOK.COM.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from t

Re: presets i've saved not displaying in protools

[Slau Halatyn]

Hi steve,

there never was a problem with factory presets in Pro Tools so I’m not sure 
what you’re thinking of. In the case of saving your own presets, you’d need to 
choose “Save As…” from the Settings menu. If you haven’t saved any prior and, 
if there aren’t any factory presets, Pro Tools will create a folder in your 
Documents/Pro Tools/Plug-in Settings folder and will take on the name of the 
plug-in. Occasionally the manufacturer name precedes the plug-in name and 
sometimes it doesn’t. You can either double-tap VO+f2 and look at the Plug-in 
window’s title or, alternatively, you can sort your Plug-in Settings folder by 
date. To do this, focus on the folder and press Control+Option+Command+4. By 
default, the newest item will be at the top of the list and that should be the 
folder where you saved a new preset.

Hope that helps,
Slau


> On Jun 19, 2024, at 6:45 AM, Steve Sparrow  wrote:
> 
> Hey again guys.
> I’ve noticed I can’t do anything with plug in presets in PT.
> I know the stock presets were a problem in the older protools. But now I’ve 
> upgraded to the current version of tools, I can’t see any preset at all 
> except the factory defalts, when I’m on the library name field.  I tried 
> saving some presets in some plug ins, and I can’t see them either. Is there 
> something new going on here with to get access to the plug in preset settings.
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516E13D297BC1508C6B17EBE7CF2%40SY4P282MB1516.AUSP282.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/7B59D959-A141-41C8-99AF-8CFFDB7EEEB4%40gmail.com.

Re: How to manually relink missing files in PT with Voiceover or VOCR?

[Slau Halatyn]

Hi John,

Unfortunately, that window has not been accessible for years. Much like some 
other dialogs in Pro Tools, I believe this window is slated to be redesigned. 
Hopefully, it becomes easier to use if necessary. That said, I haven’t had to 
use this window for at least a dozen years. I suppose it’s in part because I 
know what a pain it is to try and hunt for missing files. Yes, relocating 
missing files to the correct Audio Files folder definitely solves the issue. 
Also, using the Clip List Table’s filter to show off-line files helps identify 
what Pro Tools is looking for. Other than that, it’s probably best practice to 
make sure you don’t find yourself in need of that type of process. As they say, 
an ounce of prevention is worth a pound of cure.

Slau


> On Jun 2, 2024, at 7:03 PM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> I have tried to find a way to manually relink missing files in PT with 
> Voiceover or VOCR, but even with sighted help I have had no luck.
> 
> Does anyone have a procedure that will work?
> 
> In the «Missing files» window you can select either to find the missing files 
> manually and relink them, or have PT find them automatically. If you select 
> to do it manually, the next window does not have any buttons that will take 
> you to an ordinary open dialog where you for example could select a folder 
> where you would start to look for the files you would like to relink. 
> 
> The only solution, is to manually find the files in Finder and place them in 
> the Audio Files folder inside of your session folder, and then reload the 
> session again. PT will then look for the missing files here, and if you are 
> lucky, the missing files window will not appear. But in other situations, the 
> manual relink feature is needed also for us. So please let me know if you 
> have a solution. :)
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/05D4D15A-91C5-4F89-BF1F-A07BDFB1D8A5%40a-pro-studio.no.

-- 
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/CD57E282-34FB-4F3D-90BE-1C92F9102749%40gmail.com.

Re: protools and latest version of macosx.

[Slau Halatyn]

Bookmark this page:
https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart
Avid updates the info every time a new version of either is released.
HTH

> On May 2, 2024, at 10:43 AM, Ronald Glaser  wrote:
> 
> Ok, whatversions of pt will work on the latest version of macosx ? and if so 
> on intell macs
> 
> Has anyone had any problems loading pro tools and getting it to come up? or 
> what could be making it hang?
> 
> -- 
> 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/28aa2d64-2367-3839-ecf9-19759d5a038d%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/405AEF36-4CFF-48F3-A6E7-F0FEBC0FA07E%40gmail.com.

Re: Plugin views don't work with let/right arrow keys

[Slau Halatyn]

Hi John,

Most likely, you have the Mac OS Mission Control shortcuts for moving backward 
and forward to previous and next space enabled. Even though you might have 
followed the pre-flight checklist, sometimes this parameter gets reset by the 
system. It’s worth checking it out. Hope that helps,
slau


> On May 1, 2024, at 9:14 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> Does anyone have problems accessing to all the parameters previously 
> accessible with the plugin views feature in Flo Tools? For the plugin views I 
> have, it’s possible to arrow down to some parameters, but those only 
> accessible by arrowing left or right, is not possible to reach.
> 
> Just would like to know if this still works with Ventura and the latest 
> version of Flo Tools and Pro Tools.
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/345D2D13-EA1E-48C8-9BE1-4DCCDF4F9ED2%40a-pro-studio.no.

-- 
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/D07C3A41-ACDD-4D11-B586-4D883951A059%40gmail.com.

Re: on the subject of Sonoma compatibility

[Slau Halatyn]

Oh, I have absolutely no idea.

> On Mar 26, 2024, at 1:27 PM, Juan Pablo Culasso Alonso  
> wrote:
> 
> Hi Slau!
> 
> Do you know if the 14.4.1 solves the issue?
> Best,
> JP
> 
>> On Mar 13, 2024, at 10:01 AM, Slau Halatyn  wrote:
>> 
>> It’s easy to criticize Avid for their Sonoma support timetable. As 
>> Production Expert points out in this article, a bunch of other developers 
>> have also had issues with compatibility. For what it’s worth, the recent 
>> critical issue with VoiceOver and Sonoma has been addressed and we’ll see a 
>> fix in the next release, which will likely be released sooner rather than on 
>> the usual schedule.
>> 
>> Further, I understand that there’s a particular pain that people feel when 
>> they’re forced to buy a brand new computer and they can’t roll back the OS 
>> and sometimes there’s a gap with support for the very latest OS. It happens. 
>> That’s the way the world goes round and one simply has to accept the 
>> reality. It sucks when that happens but, the truth is, Macs last years and 
>> years and, for the most part, these issues rarely come up. I’ve own many 
>> Macs and I’ve never had this issue. That doesn’t mean that tomorrow it won’t 
>> happen to me but I am certain that I’d just deal with it. Enough said for 
>> now from me.
>> 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/BFCEE073-7CEB-48C4-95BF-E5732F6E1EC5%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/2DA5E7E2-D844-4670-81D0-FB66AFDDC363%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/FAD96E2D-F213-43A1-A4DA-75FF06EEA6AA%40gmail.com.

Re: Error message related to accessibility when pressing Default button in the I/O setup in PT2024.3 with Ventura

[Slau Halatyn]

Hi John,

I tried it with Ventura just as Martin and I’ve had no issues. I do recall that 
there was, at one time, a similar such situation where the sudden appearance of 
a dialog would yield an error like this and the workaround was to simply turn 
off VoiceOver before issuing the command, then turning VoiceOver on and things 
proceeded as normal. I don’t know why you’re specifically getting this error on 
your system but it appears not to be a general bug. I’m not sure if you have a 
current subscription but it might be a good idea to forward that error message 
to Avid’s tech support.

Slau


> On Mar 21, 2024, at 5:18 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hello agin,
> 
> This bug is more serious than I first thought. It is purely related to the 
> use of VoiceOver with PT. If VO is turned off, the bug is not there any more.
> 
> I use PT 2024.3 with last version of Ventura. If I turn off VoiceOver and let 
> an sighted assistant open PT in a session, go to the Setup/i/O dialog, and 
> press the default button in any of the tags Input/Output or Bus, PT will 
> immediately work as expected and stay open in the I/O dialog.
> 
> If we turn on VoiceOver and I press the same default button in the same 
> session by using VO-space key, PT will immediately crash, or first show the 
> error message I pasted into my previous message in this thread. The error 
> message contain words like accessibility, so it conforms that this is related 
> to VoiceOver.
> 
> However, I did yet another test. I tried to import tracks from a different 
> session by using the option-shift-I command to import session data. If I do 
> this with VoiceOver on, PT will crash immediately when I select the file I 
> would like to import from. If we do the same with VoiceOVer off, everything 
> works as expected and the tracks will be imported. The solution in this case 
> is to use Voiceover to locate the file you would like to import from, then 
> turn off VoiceOver and press return and wait for a few seconds. Then you can 
> turn on VO, select the tracks you would like to import, then turn off 
> VoiceOver again and press return a copule of times during the next minute to 
> complete the import procedure. This works as expected.
> 
> But I hope Slau or  someone else close to the accessibility team at AVID read 
> this and report the bug to AVID so it can be fixed as soon as possible.
> 
> Best,
> John André
> 
> .  
> 
> 
>> 19. mar. 2024 kl. 17:11 skrev John André Lium-Netland 
>> :
>> 
>> Hi,
>> 
>> I get an error message related to accessibility when pressing Default button 
>> in the I/O setup in PT2024.3 with Ventura. When pressing OK on this message, 
>> PT crash. Sometimes the error message does not show up, but PT still crash 
>> when I press the Default button in the I/O setup.
>> 
>> Is this a bug related to the combination of VoiceOver and PT? Any 
>> work-arounds?
>> 
>> Here is a copy of the error message:
>> 
>> Assertion in 
>> "/Users/autobld/gitlabci/PT/release/2024/r1/ProTools/DFW/Utilities/MacOS/DFW_Accessibility.MacOS.mm",
>>  line 2387.
>> 
>> (Use the Copy button to copy this message to the clipboard.)
>> 
>> 
>> 
>> 
>> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/8DBEDF32-7538-4276-922A-7678146CB048%40a-pro-studio.no.

-- 
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/0E30E85C-3FA2-43E1-9FA9-77B9D12951BE%40gmail.com.

on the subject of Sonoma compatibility

[Slau Halatyn]

It’s easy to criticize Avid for their Sonoma support timetable. As Production 
Expert points out in this article 
,
 a bunch of other developers have also had issues with compatibility. For what 
it’s worth, the recent critical issue with VoiceOver and Sonoma has been 
addressed and we’ll see a fix in the next release, which will likely be 
released sooner rather than on the usual schedule.

Further, I understand that there’s a particular pain that people feel when 
they’re forced to buy a brand new computer and they can’t roll back the OS and 
sometimes there’s a gap with support for the very latest OS. It happens. That’s 
the way the world goes round and one simply has to accept the reality. It sucks 
when that happens but, the truth is, Macs last years and years and, for the 
most part, these issues rarely come up. I’ve own many Macs and I’ve never had 
this issue. That doesn’t mean that tomorrow it won’t happen to me but I am 
certain that I’d just deal with it. Enough said for now from me.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/BFCEE073-7CEB-48C4-95BF-E5732F6E1EC5%40gmail.com.

Re: Att Slau: keyboard maestro

[Slau Halatyn]

Hi Chris,

I haven’t done anything with those macros for a while. I’m not sure when I’ll 
have time to take a look at them. when last I checked, macros worked for 
Kontakt 7 with no issues. I haven’t looked at Komplete Kontrol macros in a 
while. I’ll see if I can take a look next week. I doubt it’s something to which 
I’ll be able to devote energies any time soon.

slau

> On Mar 10, 2024, at 8:57 PM, Christopher Gilland  
> wrote:
> 
> anyone can answer this, however, I flagged Slau on this matter, as I wanted 
> to ensure that he sees this. that said, would anyone happen to know if the 
> keyboard maestro macros have been updated to support Komplete Kontrol as well 
> as Kontakt 7 full both running on the most recent version of ventura?
> 
> I know that from kk 2.x, the user interface changed drastically from what you 
> would have found in version 3.x.
> 
> the last version of the macros that I had were for KK version 2.x, and for 
> Kontakt 6 full.
> 
> I know that there's been some discussion on list about how to manually load 
> nki files using the most recent versions, in combination with vocr, but 
> despite countless times listening to Andres tutorial on how to do this, I 
> still have never been able to get his instructions to work on my end for some 
> weird reason. this is why I think the macros would be a bit more reliable in 
> my case.
> 
> 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/CADR_nrbUi0qHaP%2BoWsF_R_AsCJ2Sy%2BOseohBKfE4WpCj5r8j-g%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/CF977BB7-7EA0-4A2D-864D-D8D552F8BB82%40gmail.com.

Re: Issues installing everything

[Slau Halatyn]

Hi Ian,
For what it’s worth, the instructions on ptaccess.github.io 
 are more comprehensive and technically more 
up-to-date.
HTH,
Slau


> On Mar 7, 2024, at 10:09 AM, ianlratt...@gmail.com wrote:
> 
> Hi Mark
>  Thanks for getting back.  I wondered as I didn’t find OS 14 Sonoma in the 
> Flow Tools script.  Good news on the Pro Tools front, I redownloaded it and 
> installed again and it’s working pretty well even if not supported yet.  I’m 
> currently going through the excellent tutor on the Flow Tools site.
>  Kind regards
>  Ian
>From: ptaccess@googlegroups.com  On Behalf Of 
> Marc Mulcahy
> Sent: Thursday, March 7, 2024 2:43 PM
> To: ptaccess@googlegroups.com
> Subject: Re: Issues installing everything
>  Hi Ian,
>  Pro Tools isn't officially supported on Sinoma yet, and Flo Tools isn't yet 
> either. I patched the installer to install on Sinoma and it should go into 
> the next Flo Tools release.
>  Best,
>  Marc
>   Sent from my iPhone
> 
> 
>> On Mar 7, 2024, at 8:19 AM, Ian Rattray  wrote:
>> 
>> Hi, I'm considering swopping from PC over to Mac.   I'm very new to both 
>> Mac and Pro Tools, though I have experience of other dAWs.  I seem to have 
>> got in a real mess as I'm getting no accessibility with the Pro Tools demo, 
>> all it says is "Empty dialogue" or something like that.   and I can't seem 
>> to install Flow Tools either, I keep getting a message saying "The varable 
>> OS name is not defined - -2753".  I clicked on edit and had a scan through 
>> the script and it appears OS 14 Sonoma isn't in the list.  Hence the 
>> message.  I'm running a Mac Book Pro OS 14 Sonoma and the current version of 
>> Pro Tools.  I should also point out I've set things up as best I can 
>> according to the directions on the Flow Tools website.
>>  Any help would be very much appreciated.
>>  Best
>>  Ian
>> -- 
>> 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/ff52ae93-e292-4858-8e01-d698cd53df38n%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/9AE729FE-E3AD-45AB-AD7E-19E8514C4104%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/0a0301da70a1%24705cdab0%2451169010%24%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/16E2DC75-BAF8-4FF0-A99B-23D7A3AEBBCB%40gmail.com.

Re: Questions about clip name announcements, working with fades and track markers feature in PT

[Slau Halatyn]

Hi John,

Some responses interjected below:
On Mar 4, 2024, at 1:50 AM, 'John André Lium-Netland' via Pro Tools 
Accessibility  wrote:
> 
> Hi all,
> 
> I wish there was a accessible way to easily see each clip in the timeline and 
> view and edit fades like one can with regions in Logic.
I think we all wish for that as well. It would take a significant change to how 
the timeline is represented (or revealed) for VoiceOver to be able to access 
individual clips within the timeline. One potential solution is to do what was 
done to the rulers with tables but even that solution leaves a bit to be 
desired. I don’t see it necessarily happening any time soon as there are many 
more and bigger fish to fry, as they say.

As far as fades are concerned, they can easily be selected and edited by 
pressing Command+F. The resulting dialog is accessible and there are, of 
course, shortcuts for the various fade shapes. What isn’t accessible are the 
anchors for dragging and adjusting parabolic curves. In my 20+ years using Pro 
Tools, I’ve never felt the need for that level of fade adjustment but that’s 
just me.
> Is there a way to have Flo Tools and VoiceOver automatically announce the 
> name of a clip when selecting it with control-tab or control-option-tab?
As far as automatic announcement, it’s problematic to have anything be 
automatic. Selected clips can be announced with Flo Tools by 
pressingOption+Shift+comma. thing is, the Clips table needs to be expanded. The 
other thing is, a clip may be selected in the list without anything being 
selected in the timeline and that can be confusing. sighted users get used to 
the behavior very quickly but a blind user must verify what is and isn’t 
selected in either the timeline or the clips list so anything automatic can 
easily lead to confusion.
> Also, I have tried to find an accesible way to use the Track Marker feature 
> introduced in PT 2023.6.
To be honest with you, I haven’t wrapped my head around it yet. I can certainly 
understand the value of it but haven’t had a use case so can’t say that I’ve 
spent any significant time with it.
> Will there be an update to the tutorials for the 2023 enhancements in PT?
I hope that we can add to the guide some time soon. There certainly have been a 
few changes that should be reflected. Any such update will surely be announced 
here.
Cheers,
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/7079E6FF-E646-4313-863D-3BC0B0414730%40gmail.com.

Re: How to find the current number of audio/insrument/MIDI tracks and basic/routing folders in a PT session?

[Slau Halatyn]

Hi John,

OK, I found a solution for your issue. To perform a modified click on the 
folder icon, interact with the folder track and navigate toward the bottom 
where the name plate appears. VoiceOver speaks the name of the track and 
erroneously reports it as a pop-up button. To the left of the name plate, is 
the track type, again, erroneously labelled. If you perform an Option-click on 
this icon, it will expand or collapse all folders. remember, however, that 
nested folders retain their open/close state so you might expand the top level 
folders but have a few closed nested folders. You can repeat the process on 
nested folders and continue expanding. Once all folders have been expanded, 
Option-clicking a top-level folder will collapse and expand all folders. That’s 
the expected behavior for Pro Tools. If you close one of the nested folders, 
it’ll remember the state of that particular folder and keep it closed unless 
you specifically expand it. This memory for the open/close status extends to 
the show/hide status of tracks contained within folders. In other words, if you 
explicitly hide tracks, they will remain hidden if you show or hide and open or 
close a folder. Pro Tools remembers the state which is as it should be. Anyway, 
I just opened a session with a bunch of nested folders and tested this and, 
with the filtering of folders, the whole reporting of numbers by flo Tools 
works nicely and the Option-click works consistently as long as the control is 
visible. Don’t display all inserts and all sends if you can avoid it and 
remember that Pro Tools displays about 16 tracks per view in the Mix window. 
beyond that, you’ll need to either scroll to track to make sure it’s the first 
item on the left hand side of the window or scroll with Option+Page Up and Page 
Down.

Hope that helps,
Slau


> On Feb 2, 2024, at 5:44 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hello again, 
> 
> Since I have a lot of files placed in nested folders at least 4 levels down, 
> the option-shift-W command will only tell me the number of shown tracks of 
> that type in the folders that are open. There is a way to open all nested 
> folders, that is to option click on the folder icon, but even with Flo Mouse 
> I have not had success performing this procedure, since I do not know exactly 
> where the folder icon is in the track list.
> 
> Any suggestions? Or is there a shortcut to expand all folders in all levels?
> 
> Best,
> John André
> 
> 
>> 1. feb. 2024 kl. 16:49 skrev Slau Halatyn :
>> 
>> HI John,
>> 
>> If you use the Track List pop-up button to show only the various track 
>> types, you can very quickly use the Flo Tools Speak Shown Tracks feature by 
>> pressing Option+Shift+W and have VoiceOver speak the number of tracks shown 
>> for that type. Remember, however, that the filtering doesn’t distinguish 
>> between routing folders and basic folders. I’m not sure if there’s a limit 
>> on the number of basic folders but, if you don’t specifically need the 
>> routing and processing aspect, that might be a work-around for track number 
>> limitations. Of course, doing post-production for film and video almost 
>> requires those higher track counts.
>> 
>> Another work-around is to use an auxiliary input within a basic foder. That 
>> way, you can technically get the benefit of the routing and inserts while 
>> still being able to collapse tracks. Just a thought.
>> 
>> HTH,
>> Slau
>> 
>> 
>>> On Feb 1, 2024, at 9:14 AM, 'John André Lium-Netland' via Pro Tools 
>>> Accessibility  wrote:
>>> 
>>> Hi,
>>> 
>>> I’ve tried to find info about this elsewhere, but with no luck.
>>> 
>>> I assume there is an overview of how many audio/instrument/MIDI tracks that 
>>> currently is used in a session. Since there is a limit to how many such 
>>> tracks and folders you can have, it’s important to know. I’m working on a 
>>> big documentary project with loads of tracks and folders, and today I was 
>>> warned that I have reached the limit of routing folders. In PT Studio that 
>>> is the silly low number of 128. While in the Ultimate version the number is 
>>> 1024.
>>> 
>>> Anyways, I’d like to know how many audio/instrument/MIDI tracks I have, to 
>>> know how far I’m from the limit here.
>>> 
>>> Does anyone know where to find such an overview?
>>> 
>>> Best,
>>> John André
>>> 
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> 

Re: How to find the current number of audio/insrument/MIDI tracks and basic/routing folders in a PT session?

[Slau Halatyn]

The icon itself for the open/close state  in the track list isn’t visible to 
VoiceOver so it’s not possible to route the VoiceOver cursor to it easily.I’ll 
see if I can come up with a work-around.

> On Feb 2, 2024, at 5:44 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hello again, 
> 
> Since I have a lot of files placed in nested folders at least 4 levels down, 
> the option-shift-W command will only tell me the number of shown tracks of 
> that type in the folders that are open. There is a way to open all nested 
> folders, that is to option click on the folder icon, but even with Flo Mouse 
> I have not had success performing this procedure, since I do not know exactly 
> where the folder icon is in the track list.
> 
> Any suggestions? Or is there a shortcut to expand all folders in all levels?
> 
> Best,
> John André
> 
> 
>> 1. feb. 2024 kl. 16:49 skrev Slau Halatyn :
>> 
>> HI John,
>> 
>> If you use the Track List pop-up button to show only the various track 
>> types, you can very quickly use the Flo Tools Speak Shown Tracks feature by 
>> pressing Option+Shift+W and have VoiceOver speak the number of tracks shown 
>> for that type. Remember, however, that the filtering doesn’t distinguish 
>> between routing folders and basic folders. I’m not sure if there’s a limit 
>> on the number of basic folders but, if you don’t specifically need the 
>> routing and processing aspect, that might be a work-around for track number 
>> limitations. Of course, doing post-production for film and video almost 
>> requires those higher track counts.
>> 
>> Another work-around is to use an auxiliary input within a basic foder. That 
>> way, you can technically get the benefit of the routing and inserts while 
>> still being able to collapse tracks. Just a thought.
>> 
>> HTH,
>> Slau
>> 
>> 
>>> On Feb 1, 2024, at 9:14 AM, 'John André Lium-Netland' via Pro Tools 
>>> Accessibility  wrote:
>>> 
>>> Hi,
>>> 
>>> I’ve tried to find info about this elsewhere, but with no luck.
>>> 
>>> I assume there is an overview of how many audio/instrument/MIDI tracks that 
>>> currently is used in a session. Since there is a limit to how many such 
>>> tracks and folders you can have, it’s important to know. I’m working on a 
>>> big documentary project with loads of tracks and folders, and today I was 
>>> warned that I have reached the limit of routing folders. In PT Studio that 
>>> is the silly low number of 128. While in the Ultimate version the number is 
>>> 1024.
>>> 
>>> Anyways, I’d like to know how many audio/instrument/MIDI tracks I have, to 
>>> know how far I’m from the limit here.
>>> 
>>> Does anyone know where to find such an overview?
>>> 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/D347BF13-CE40-4DD1-870B-092C33ADD3A2%40a-pro-studio.no.
>> 
>> -- 
>> 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/41D0F6BE-11F4-4D27-A978-0604BAA890BD%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/64D7A41F-52B9-4890-B0E4-F26F62F43753%40a-pro-studio.no.

-- 
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/A86096BE-847B-4E32-8C46-7E574E7D4F92%40gmail.com.

Re: How to find the current number of audio/insrument/MIDI tracks and basic/routing folders in a PT session?

[Slau Halatyn]

HI John,

If you use the Track List pop-up button to show only the various track types, 
you can very quickly use the Flo Tools Speak Shown Tracks feature by pressing 
Option+Shift+W and have VoiceOver speak the number of tracks shown for that 
type. Remember, however, that the filtering doesn’t distinguish between routing 
folders and basic folders. I’m not sure if there’s a limit on the number of 
basic folders but, if you don’t specifically need the routing and processing 
aspect, that might be a work-around for track number limitations. Of course, 
doing post-production for film and video almost requires those higher track 
counts.

Another work-around is to use an auxiliary input within a basic foder. That 
way, you can technically get the benefit of the routing and inserts while still 
being able to collapse tracks. Just a thought.

HTH,
Slau


> On Feb 1, 2024, at 9:14 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> I’ve tried to find info about this elsewhere, but with no luck.
> 
> I assume there is an overview of how many audio/instrument/MIDI tracks that 
> currently is used in a session. Since there is a limit to how many such 
> tracks and folders you can have, it’s important to know. I’m working on a big 
> documentary project with loads of tracks and folders, and today I was warned 
> that I have reached the limit of routing folders. In PT Studio that is the 
> silly low number of 128. While in the Ultimate version the number is 1024.
> 
> Anyways, I’d like to know how many audio/instrument/MIDI tracks I have, to 
> know how far I’m from the limit here.
> 
> Does anyone know where to find such an overview?
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/D347BF13-CE40-4DD1-870B-092C33ADD3A2%40a-pro-studio.no.

-- 
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/41D0F6BE-11F4-4D27-A978-0604BAA890BD%40gmail.com.

Re: How to make VO speak current position automatically?

[Slau Halatyn]

I think there’s a way to ensure by choosing the instance from the KK controller 
but I haven’t used that method all that much. More often than not, I freeze 
tracks so when I’m creating a new instance, the keyboard will automatically 
focus the instance on the newly-created track.

> On Jan 29, 2024, at 9:25 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> Thanks a lot. A follow up question:
> I use Komplete Kontrol and a S88MK2 with Pro Tools, but find myself often 
> browsing sounds on a different KK track than the one that is record enabled. 
> Is there a proof way to make sure that I’m not loading sounds to a different 
> track than I expect? I thought that moving the record enabled track would 
> sync S88 with PT so that they focused on the same track, but that’s not 
> always the case. Is there a way that S88 can show which track is focused?
> 
> I’ll appreciate if you or anyone else have any tips here. :)
> 
> Best,
> John André
> 
> 
> 
>> 29. jan. 2024 kl. 14:34 skrev Slau Halatyn :
>> 
>> Hi John,
>> 
>> That’s a Flo Tools feature you can engage by pressing Option+Shift+Left or 
>> Right Bracket to cycle through several items like Start, end, length, pitch, 
>> attack and release velocities. If you want to turn it off,press 
>> Option+Shift+Left Bracket until you hear VoiceOver say “no report.” To 
>> engage the feature initially, use Option+Shift+Right Bracket and move to the 
>> value you wish to have automatically reported.
>> 
>> Hope that helps,
>> Slau
>> 
>> 
>>> On Jan 27, 2024, at 10:12 AM, 'John André Lium-Netland' via Pro Tools 
>>> Accessibility  wrote:
>>> 
>>> Hi,
>>> 
>>> In the excellent PT tutorial. in one of the chapters about audio editing, 
>>> Slau set VoiceOver to automatically announce when the position is changed, 
>>> so that he for example can move around without checking the position 
>>> manually all the time.
>>> 
>>> Can Slau or anyone else tell me how to make VO do that? Does he use focus 
>>> points or is there a separate function for this in FloTools?
>>> 
>>> Thanks in advance!
>>> 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/BDC20D38-1178-46AA-A511-59B415B0D405%40a-pro-studio.no.
>> 
>> -- 
>> 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/0B5F5273-81EE-471F-81A2-009438747A39%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/624A8C88-931B-4718-9EA4-B11D9907B0BC%40a-pro-studio.no.

-- 
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/87ABD7ED-AFA7-4C12-B48D-2F6B377FF832%40gmail.com.

Re: How to make VO speak current position automatically?

[Slau Halatyn]

Hi John,

That’s a Flo Tools feature you can engage by pressing Option+Shift+Left or 
Right Bracket to cycle through several items like Start, end, length, pitch, 
attack and release velocities. If you want to turn it off,press 
Option+Shift+Left Bracket until you hear VoiceOver say “no report.” To engage 
the feature initially, use Option+Shift+Right Bracket and move to the value you 
wish to have automatically reported.

Hope that helps,
Slau


> On Jan 27, 2024, at 10:12 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> In the excellent PT tutorial. in one of the chapters about audio editing, 
> Slau set VoiceOver to automatically announce when the position is changed, so 
> that he for example can move around without checking the position manually 
> all the time.
> 
> Can Slau or anyone else tell me how to make VO do that? Does he use focus 
> points or is there a separate function for this in FloTools?
> 
> Thanks in advance!
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/BDC20D38-1178-46AA-A511-59B415B0D405%40a-pro-studio.no.

-- 
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/0B5F5273-81EE-471F-81A2-009438747A39%40gmail.com.

Re: short cut for bouncing out stems

[Slau Halatyn]

Sorry, steve, I believe I meant to type Command+Option+Shift+B. So often it’s 
muscle memory governing keyboard shortcuts :)


> On Jan 9, 2024, at 8:06 PM, Steve Sparrow  wrote:
> 
> Can someone remind me of the short cut for bouncing out stems. I can’t seem 
> to get it happening.
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516E56BA75350F4683E0733E7692%40SY4P282MB1516.AUSP282.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/B7453B50-4C74-4111-B251-AF11511E4C99%40gmail.com.

Re: short cut for bouncing out stems

[Slau Halatyn]

Hi Steve,

Command+Option+shift+C will do a track bounce for each selected track. Hope 
that helps,
Slau


> On Jan 9, 2024, at 8:06 PM, Steve Sparrow  wrote:
> 
> Can someone remind me of the short cut for bouncing out stems. I can’t seem 
> to get it happening.
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516E56BA75350F4683E0733E7692%40SY4P282MB1516.AUSP282.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/EAE6AE6D-EFD3-4F0F-AD3C-88E6FABBA38A%40gmail.com.

Re: FloTools MIDI editing - why doesn't it work?

[Slau Halatyn]

Hi John,

If I’m not mistaken, we took that feature out when Pro Tools updated it’s 
method of editing MIDI with keyboard shortcuts. Also, since we added the 
velocity and pitch macros and you can use standard commands for editing length, 
moving beginnings and endings, etc., it seemed superfluous. True, it’s still a 
different matter to edit controller data but that’s a slightly different topic. 
HTH,
Slau


> On Jan 6, 2024, at 9:45 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi, since nobody responded on this question, I ‘ll try again… :).
> 
> Long ago, I think it was way back in FloTools 2.2, a way to edit MIDI notes 
> was announced. I got it to work back then, but after some time it stopped to 
> work for me. But after being so frustrated by the hard way Pro Tools works 
> with VO when it comes to MIDI editing, I remember those FloTools features. 
>> 
>> I have tried to make it work again today, but with no luck.
>> 
>> Shortcuts like control left arrow and right arrow to focus on a MIDI value 
>> ,in the MIDI event list, as well as control-command-return to edit a 
>> specific value does not work.
>> 
>> Any suggestions or advices.
>> 
>> I did try to consolidate the MIDI track first with no better result, but do 
>> I really need to do that for every track? It’s ok for me to work in the MIDI 
>> event list if I can get this to work. 
>> 
>> I do not have to be able to close the MIDI event list to be satisfied. I 
>> just want to edit easier than I currently is able to in the MIDI event list..
>> 
>> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/F58138B6-058E-4B62-BDE8-10C6EDCBC8B1%40a-pro-studio.no.

-- 
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/6E7B3565-31D8-402C-88A4-63BDD1C59FCA%40gmail.com.

RIP Ed Gray

[Slau Halatyn]

Just thought I’d let the list know that Ed Gray just passed away.

-- 
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/13C1833F-55C6-46C2-8E48-574BEFA208F2%40gmail.com.

Ed Gray

[Slau Halatyn]

I’m posting this message here to let everyone know that in the coming days we 
will lose our friend and colleague, Ed Gray. Ed has been a key figure at avid 
and, before that, Digidesign, for some 30 years. Ed was director of third-party 
partnering so he worked with all of the plug-in developers and auxiliary 
software products.

For many years, Ed has faced serious health challenges which stemmed mostly 
from diabetes. He started losing his vision about 20 years ago and has had 
essentially no useable sight for the last 10 years. His diabetes lead to kidney 
failure as well as a recent amputation of one leg just below the knee.

Despite dialysis treatments, his condition has continued to worsen. Most 
recently, he was enduring 3 treatments per week but continued to decline. He 
recently decided to stop his treatments. Doctors gave him about a week or so to 
live. He’s still with us but doesn’t have long at all.

when I spoke with him only 2 weeks ago, he hadn’t made his decision yet. As of 
a few days ago, he shared the news with friends and family. At this point, the 
community at large has learned of his situation. I’ve been in touch with him 
over the weekend and he asked me to share the news with blind Pro Tools users. 
His most recent message read:

“Slau, thank you for sending this wonderful note. It is nice to hear from you. 
I will be around for a few days next week and try to reach out to some of the 
gang but I hope you'll pass on word to the group of what is happening and tell 
them that I intentionally enjoyed working with them. I know that you and I have 
done a lot to open the door to visually impaired users to ProTools, and that 
the work, and the best moments by far are still yet to come. Love, ed.”

We’ll sorely miss him but will continue to work and honor his legacy as a 
champion of accessibility.  
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/9474D20F-F7CF-47BC-BB7D-DAB02DE506EE%40gmail.com.

Re: short cut question

[Slau Halatyn]

Hi steve,

Yeah, that’s an old version of PT that predates the code that looks for 
specific names for buttons and such. These things can change over time and 
that’s probably what’s going on. Besides, the latest version of Flo Tools 
requires a minimum Pro Tools version beyond what you’re using.

> On Oct 25, 2023, at 8:38 PM, Steve Sparrow  wrote:
> 
> I'm currently using protools, 19.5, and the latest version of flo tools. So 
> not sure if that would cause an issue. I think it did say when I installed 
> it, some things may not work correctly. I've not found anything that doesn't 
> work yet, But maybe that's one of then.
> Anyway. Thanks
> 
> 
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Thursday, October 26, 2023 8:43 AM
> To: PTAccess List 
> Subject: Re: short cut question
> 
> It’s not a Pro Tools command but rather a Flo Tools command. I don’t remember 
> when we introduced it but it’s been around for a few years.
> 
> 
>> On Oct 25, 2023, at 4:19 PM, Steve Sparrow  wrote:
>> 
>> Ok. I tried this, but it's not doing anything here. Bow ever I am using an 
>> older version of protools So maybe that is the issue. Is there anything else 
>> I need to turn on for this to work, Perhaps I should just update protools. 
>> Steve
>> 
>> 
>> -Original Message-
>> From: ptaccess@googlegroups.com  On Behalf 
>> Of Slau Halatyn
>> Sent: Thursday, October 26, 2023 12:53 AM
>> To: PTAccess List 
>> Subject: Re: short cut question
>> 
>> Hi Steve,
>> 
>> I mean all the modifiers including Command, Option, Control and Shift 
>> together and then the letter key.
>> 
>> Cheers,
>> Slau
>> 
>> 
>>> On Oct 25, 2023, at 8:25 AM, Steve Sparrow  
>>> wrote:
>>> 
>>> Hey Slau. Thanks for this. Stupid question. What is all modifiers key 
>>> stroke. I assumed you meant the shift key. But I can't get that to wor So 
>>> what is the all modifiers command.
>>> Stevek. 
>>> 
>>> -Original Message-
>>> From: ptaccess@googlegroups.com  On Behalf 
>>> Of Slau Halatyn
>>> Sent: Wednesday, October 25, 2023 2:22 PM
>>> To: PTAccess List 
>>> Subject: Re: short cut question
>>> 
>>> Hi Steve,
>>> 
>>> If you’re using Flo Tools, all modifiers plus R will render without you 
>>> having to leave the plug-in view area. All modifiers plus P will also 
>>> preview.
>>> 
>>> HTH,
>>> Slau
>>> 
>>> 
>>>> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  
>>>> wrote:
>>>> 
>>>> Hey guys, can anyone tell me if there is a short cut to get to the render 
>>>> button when working in a pluggin in the audio sweet window. For example. 
>>>> If I want to auto tune something in this way, I have to get into the 
>>>> pluggin window, make my changes, then uninteract with the pluggin window, 
>>>> and go to the render button. But is there a way of rendering while still 
>>>> in the pluggin window. It works fine this way, but it would be a time 
>>>> saver if this was possible. It could also be I’m going about things the 
>>>> wrong way here. Maybe there is a better way.
>>>> 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.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%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+un

Re: short cut question

[Slau Halatyn]

It’s not a Pro Tools command but rather a Flo Tools command. I don’t remember 
when we introduced it but it’s been around for a few years.


> On Oct 25, 2023, at 4:19 PM, Steve Sparrow  wrote:
> 
> Ok. I tried this, but it's not doing anything here. Bow ever I am using an 
> older version of protools So maybe that is the issue. Is there anything else 
> I need to turn on for this to work, Perhaps I should just update protools. 
> Steve
> 
> 
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Thursday, October 26, 2023 12:53 AM
> To: PTAccess List 
> Subject: Re: short cut question
> 
> Hi Steve,
> 
> I mean all the modifiers including Command, Option, Control and Shift 
> together and then the letter key.
> 
> Cheers,
> Slau
> 
> 
>> On Oct 25, 2023, at 8:25 AM, Steve Sparrow  wrote:
>> 
>> Hey Slau. Thanks for this. Stupid question. What is all modifiers key 
>> stroke. I assumed you meant the shift key. But I can't get that to wor So 
>> what is the all modifiers command.
>> Stevek. 
>> 
>> -Original Message-
>> From: ptaccess@googlegroups.com  On Behalf 
>> Of Slau Halatyn
>> Sent: Wednesday, October 25, 2023 2:22 PM
>> To: PTAccess List 
>> Subject: Re: short cut question
>> 
>> Hi Steve,
>> 
>> If you’re using Flo Tools, all modifiers plus R will render without you 
>> having to leave the plug-in view area. All modifiers plus P will also 
>> preview.
>> 
>> HTH,
>> Slau
>> 
>> 
>>> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  
>>> wrote:
>>> 
>>> Hey guys, can anyone tell me if there is a short cut to get to the render 
>>> button when working in a pluggin in the audio sweet window. For example. If 
>>> I want to auto tune something in this way, I have to get into the pluggin 
>>> window, make my changes, then uninteract with the pluggin window, and go to 
>>> the render button. But is there a way of rendering while still in the 
>>> pluggin window. It works fine this way, but it would be a time saver if 
>>> this was possible. It could also be I’m going about things the wrong way 
>>> here. Maybe there is a better way.
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%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/SY4P282MB1516895B5E9AC156E7BB8537E7DEA%40SY4P282MB1516.AUSP282.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/7E800F8E-D73F-45A8-9C31-5BA66A414C0E%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/SY4P282MB15167383914356CE76A55873E7DEA%40SY4P282MB1516.AUSP282.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/C920E137-80F3-4FBB-9BD2-97EF35898D8D%40gmail.com.

Re: Mac OSx 14

[Slau Halatyn]

Avid continuously tests operating systems with beta. Official support is always 
posted on their web site:
https://avidtech.my.salesforce-sites.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart
I’d recommend bookmarking.


> On Oct 25, 2023, at 2:49 PM, Ronald Glaser  wrote:
> 
> Slau,
> 
> Do you know what the status of PT is for the newest of the mac operating 
> system, is it still in testing for to be come compatable with Mac OSX 14?
> 
> -- 
> 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/a87fd1fe-6f9c-d5d0-f304-d06f64f31d8c%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/DD24201E-C56F-467A-ABEF-AF83EBBB63F8%40gmail.com.

Re: OT was short cut question

[Slau Halatyn]

Received nothing. Feel free to re-send today.

> On Oct 25, 2023, at 11:23 AM, Martin (Punky) Sopart  
> wrote:
> 
> I used that address...
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Wednesday, October 25, 2023 4:55 PM
> To: PTAccess List 
> Subject: Re: OT was short cut question
> 
> Hi Martin,
> 
> No, I never saw a message. I’ll check again but maybe use my studio address 
> if you have it. If you don’t, it’s my first name at besharpstudios.com 
> <http://besharpstudios.com/>.
> 
>> On Oct 25, 2023, at 2:19 AM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello Slau!
>> 
>> Did you get my last pm?
>> 
>> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com  On Behalf Of 
>> Slau Halatyn
>> Sent: Wednesday, October 25, 2023 6:22 AM
>> To: PTAccess List 
>> Subject: Re: short cut question
>> 
>> Hi Steve,
>> 
>> If you’re using Flo Tools, all modifiers plus R will render without you 
>> having to leave the plug-in view area. All modifiers plus P will also 
>> preview.
>> 
>> HTH,
>> Slau
>> 
>> 
>>> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  
>>> wrote:
>>> 
>>> Hey guys, can anyone tell me if there is a short cut to get to the render 
>>> button when working in a pluggin in the audio sweet window. For example. If 
>>> I want to auto tune something in this way, I have to get into the pluggin 
>>> window, make my changes, then uninteract with the pluggin window, and go to 
>>> the render button. But is there a way of rendering while still in the 
>>> pluggin window. It works fine this way, but it would be a time saver if 
>>> this was possible. It could also be I’m going about things the wrong way 
>>> here. Maybe there is a better way.
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%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/001a01da070b%2447b10870%24d7131950%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/7054C2DE-C6D8-46EE-A9BE-C02BF38C87A6%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/002c01da0757%242e314120%248a93c360%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/34996101-65A6-4100-AE3F-6C255AF53FC0%40gmail.com.

Re: OT was short cut question

[Slau Halatyn]

Hi Martin,

No, I never saw a message. I’ll check again but maybe use my studio address if 
you have it. If you don’t, it’s my first name at besharpstudios.com 
<http://besharpstudios.com/>.

> On Oct 25, 2023, at 2:19 AM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau!
> 
> Did you get my last pm?
> 
> Best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Wednesday, October 25, 2023 6:22 AM
> To: PTAccess List 
> Subject: Re: short cut question
> 
> Hi Steve,
> 
> If you’re using Flo Tools, all modifiers plus R will render without you 
> having to leave the plug-in view area. All modifiers plus P will also preview.
> 
> HTH,
> Slau
> 
> 
>> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  
>> wrote:
>> 
>> Hey guys, can anyone tell me if there is a short cut to get to the render 
>> button when working in a pluggin in the audio sweet window. For example. If 
>> I want to auto tune something in this way, I have to get into the pluggin 
>> window, make my changes, then uninteract with the pluggin window, and go to 
>> the render button. But is there a way of rendering while still in the 
>> pluggin window. It works fine this way, but it would be a time saver if this 
>> was possible. It could also be I’m going about things the wrong way here. 
>> Maybe there is a better way.
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%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/001a01da070b%2447b10870%24d7131950%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/7054C2DE-C6D8-46EE-A9BE-C02BF38C87A6%40gmail.com.

Re: short cut question

[Slau Halatyn]

Hi Steve,

I mean all the modifiers including Command, Option, Control and Shift together 
and then the letter key.

Cheers,
Slau


> On Oct 25, 2023, at 8:25 AM, Steve Sparrow  wrote:
> 
> Hey Slau. Thanks for this. Stupid question. What is all modifiers key stroke. 
> I assumed you meant the shift key. But I can't get that to wor
> So what is the all modifiers command.
> Stevek. 
> 
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Wednesday, October 25, 2023 2:22 PM
> To: PTAccess List 
> Subject: Re: short cut question
> 
> Hi Steve,
> 
> If you’re using Flo Tools, all modifiers plus R will render without you 
> having to leave the plug-in view area. All modifiers plus P will also preview.
> 
> HTH,
> Slau
> 
> 
>> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  
>> wrote:
>> 
>> Hey guys, can anyone tell me if there is a short cut to get to the render 
>> button when working in a pluggin in the audio sweet window. For example. If 
>> I want to auto tune something in this way, I have to get into the pluggin 
>> window, make my changes, then uninteract with the pluggin window, and go to 
>> the render button. But is there a way of rendering while still in the 
>> pluggin window. It works fine this way, but it would be a time saver if this 
>> was possible. It could also be I’m going about things the wrong way here. 
>> Maybe there is a better way.
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%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/SY4P282MB1516895B5E9AC156E7BB8537E7DEA%40SY4P282MB1516.AUSP282.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/7E800F8E-D73F-45A8-9C31-5BA66A414C0E%40gmail.com.

Re: short cut question

[Slau Halatyn]

Hi Steve,

If you’re using Flo Tools, all modifiers plus R will render without you having 
to leave the plug-in view area. All modifiers plus P will also preview.

HTH,
Slau


> On Oct 24, 2023, at 11:09 PM, Steve Sparrow  wrote:
> 
> Hey guys, can anyone tell me if there is a short cut to get to the render 
> button when working in a pluggin in the audio sweet window. For example. If I 
> want to auto tune something in this way, I have to get into the pluggin 
> window, make my changes, then uninteract with the pluggin window, and go to 
> the render button. But is there a way of rendering while still in the pluggin 
> window. It works fine this way, but it would be a time saver if this was 
> possible. It could also be I’m going about things the wrong way here. Maybe 
> there is a better way.
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/SY4P282MB1516241E993871B4EA20555FE7DEA%40SY4P282MB1516.AUSP282.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/03DF9D2F-3E47-4E63-B1CB-D283C48DA081%40gmail.com.

Re: Double pressing keystrokes in FloTools

[Slau Halatyn]

Behavior hasn’t changed it still works the same way. Occasionally, system 
automation experiences a glitch in the way it interprets timing between 
keystrokes. A couple of quick fixes, one of which should work:

• Quit and restart VoiceOver
•Save, quit and reopen session file.
• Open Flo Tools prefs and change the double-tap timeout
• If all else fails, reboot.

HTH,
Slau


> On Oct 12, 2023, at 4:26 PM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> Previously it was possible to double press a keystroke in FloTools for a 
> number of functions.
> 
> Double press option-shift-S would unsolo all tracks that was in solo mode. 
> Same worked for option-shift-M and all muted tracks and option-shift-R for 
> all record armed tracks. It was also possible to double press command-K to 
> toggle pre-roll on and off. Currently command-K does not do anything to 
> pre-roll either when single pressing or double pressing command-K.
> 
> Is this a bug or a change in FloTools that I haven’t been fully aware of?
> 
> Thanks,
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/854BAD13-C6C7-470E-BE4F-9BE22E4071E8%40a-pro-studio.no.

-- 
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/B4858DD0-10EA-4C63-ADE9-4C1DD5AF828C%40gmail.com.

Re: document for setting up pro tools

[Slau Halatyn]

Hi Tom,

That pre-flight checklist was superseded by chapter 1 in the guide for screen 
reader users.
https://ptaccess.github.io/

> On Aug 4, 2023, at 12:49 AM, Tom Hessels  wrote:
> 
> Hi All,
> I had to reinstall my system.
> There was a document in the dropbox map with instructions for change the 
> settings to work with pro tools.
> e.g. settings for voiceover, keyboard shurtcutsd pro tools etc.
> But i can’t find this document.
> I hope someone can help.
>  Tom.
>   
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/000801d9c68f%240e1e4cb0%242a5ae610%24%40tomhessels.nl.


-- 
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/153148AD-8453-4498-9C13-182E7838068D%40gmail.com.

Re: Looking for alternative way to install Flo Tools

[Slau Halatyn]

A new version of Flo Tools will be coming out soon. For now, use this installer 
if you have to use Ventura:
https://www.dropbox.com/s/8uyqrus1yeec4do/FloTools%20Temporary%20Installer%20%28For%20Ventura%29.zip?dl=0

HTH,
Slau


> On May 16, 2023, at 4:20 AM, Mansour Alshekhi  
> wrote:
> 
> Hi everyone,
> I'm hoping someone can help me with a problem I'm having installing Flo Tools 
> on my new Mac mini with M2 Pro chip.
> I've downloaded the latest version of Flo Tools from the official website, 
> v2022.4.0, but when I try to install it, I get the following error message:
> The variable osName is not defined. (-2753)
> I think this error message is occurring because the installer file doesn't 
> recognize the Mac OS version that I'm running, which is Mac OS Ventura 13.3.1.
> I'm wondering if anyone knows of an alternative way to install Flo Tools on 
> my Mac mini. Additionally, I'm interested in knowing if anyone is working on 
> a new project similar to Flo Tools.
> Any help would be greatly appreciated!
> note: I’m already installed Keyboard Maestro .
> Thanks,
> Mansour.
> 
> -- 
> 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/BC398BEF-3391-47ED-AB6F-6F74CCD0B389%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/349CD38D-6419-4005-ADF0-4B2B554C47D3%40gmail.com.

Re: quick question about pro tools pricing, and the nature of flow tools?

[Slau Halatyn]

Hi Karen,

The Digi 002 has long since been unsupported by Pro Tools. I'm thinking that 
might have happened some 12 years ago or more. For control surfaces, the best 
bet these days is the Avid S1, ideally paired with an Avid Dock. Each surface 
runs around $1,000 or a bit more.

Upgrade paths for Pro Tools are sometimes confusing at best. I'd highly 
recommend contacting Sweetwater and let them sort things out and explain your 
options.

Flo Tools is virtually indispensable for any serious blind user but I wouldn't 
dive into it before you familiarize yourself with the current flavor of Pro 
Tools. It has changed dramatically from the version 6 days. For starters, I'd 
go through this free online resource for blind users provided by Berklee 
College of Music:
https://ptaccess.github.io/

That should get you up to speed. Hope that helps for now,

slau


> On May 12, 2023, at 9:54 PM, Karen Lewellen  wrote:
> 
> Hi folks,
> have been a major lurker because until now I had little reason to imagine 
> updating my pro tools license.   Likewise, am unsure if I can do this, while 
> keeping the personal accommodations I require for equipment.
> Towards that end I have a couple of numbers related questions, mostly about 
> pro tools, but come to consider I will ask about a mic setup as well.
> I came to all his from studio radio, have a digi control surface in fact, 
> with very important for me physical controls..and it is  still in working 
> condition.
> Our license goes back quite a while..pro tools 6.
> leading me to the following questions.
> What is the latest Pro tools I can upgrade to  that  still supports digi 002 
> hardware?
> If the mac, or macbook pro I intend using remains at the  pre Catalina days, 
> will that impact my edition choice?
> What about flow tools?
> I am very use to, and prefer the physical aspects of mixing, again I came to 
> pro tools from an NPR type of background.
> Would I be better served paying for in-person training, I learn better this 
> way, making flow tools less  of a reasonable approach?
> lastly, leading from an analog to digital production setup  mindset, anyone 
> here ever hear of an airbox?  If so, ideas on costs?
> Thanks all the way around,
> Karen
> 
> 

-- 
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/A11376A5-B377-4DD5-BE6F-5738BC485CE5%40gmail.com.

Re: Installation error with Flotools: the variable osName is not defined (error 2753)

[Slau Halatyn]

Use this:
https://www.dropbox.com/s/8uyqrus1yeec4do/FloTools%20Temporary%20Installer%20%28For%20Ventura%29.zip?dl=0


> On May 10, 2023, at 8:27 PM, Ty Littlefield  wrote:
> 
> I have a semi related question. I thought the code for this might be in 
> github and I could do some digging to debug my own error, but the only things 
> I see in the repo are the apps and a couple HTML files. Is the code 
> publically accessible?
> Thanks,
> 
> 
> On 5/10/2023 4:50 PM, Tyler Littlefield wrote:
>> Hi all, 
>> I attempted to install Flotools on my macbook.
>> I'm running the latest from the site (Flo Tools v2022.4.0).
>> I've extracted the installer app to my desktop and ran it from that point.
>> Protools version (sorry I can't seem to get the version from the app, but I 
>> downloaded it through Avid Link today).
>> OS is Ventura v13.1 on a Macbook pro.
>> Please let me know if there is any more useful information I can provide.
>> Thanks,
>> Ty
>> 
>> -- 
>> 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/762455e6-790d-47c1-8066-83be3adc1cf1n%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/806d5ae1-1f76-634a-0c65-e821e20768f5%40tysdomain.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/62D6C560-0AC1-4D89-B2EF-637FCF72E761%40gmail.com.

Re: Flo Tools installer error #513

[Slau Halatyn]

I think you'll need to send that error message to Rocco so he can have a look. 
As far as I know, that installer should work on any Ventura version. Not sure 
how closely Rocco follows threads here so maybe give a heads up off list and 
continue discussion here afterwards?
HTH,
Slau


> On Apr 14, 2023, at 3:53 AM, 'John André Lium-Netland' via Pro Tools 
> Accessibility  wrote:
> 
> Hi,
> 
> On my iMac running Ventura 13.3.1  and PT 2023.3 , I get an error # 513  
> message when trying to run the Flo Tools temporary Ventura installer found in 
> the PT Drop Box folder. I’m told that I do not have access to save a certain 
> keyboard file in the App folder. There is an Edit button and an OK button. If 
> I press Edit I’m presented with the details in a script, if I press OK it 
> seems like the installer does not complete the installation. I have pressed 
> OK on all system access dialogs I’ve got.  Is there a more recent installer 
> that I should run? 
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/E1FA1F4A-ACF4-42D5-B418-F61428510216%40a-pro-studio.no.

-- 
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/17D4256A-5C86-4C24-9E57-B8289182AB62%40gmail.com.

Re: flowtools and macosx ventura.

[Slau Halatyn]

An installer for Ventura is in the Drop Box.

> On Mar 8, 2023, at 4:51 PM, Ronald J. Glaser  wrote:
> 
>   I have the latest version of protools installed keyboard mistro, also 
> installed I am trying to instal flowtools but I get the error message varible 
> osname not defined, I was told that there was a way to get flowtools 
> installed in the latest version of macosx?
> 
> So if anyone knows how to do this please let me know.
> 
> 
> Ron.
> 
> -- 
> 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/547DEFA5-22FD-4890-B0E0-5C27A668C7EF%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/ABEF6E99-5881-4BC0-BAAA-1B359EF186ED%40gmail.com.

Re: Need help with Flo Tools installation on Mac device

[Slau Halatyn]

Hi Marc,

Not sure if the issue is what I think it is but try this installer:


https://www.dropbox.com/s/8uyqrus1yeec4do/FloTools%20Temporary%20Installer%20%28For%20Ventura%29.zip?dl=0
FloTools Temporary Installer (For Ventura).zip
dropbox.com


> On Feb 9, 2023, at 1:27 PM, Marc San Marco  wrote:
> 
> Hello ,
> I have been trying to install Flo Tools on a MacBook Pro that is about a year 
> or two old.  However, whenever I click on the Flo Tools installer, I receive 
> a pop-up message that says "The variable osName is not defined".  
> 
> 
> 
> Has anyone else run into this issue or have any idea how to fix it so that we 
> can move forward with the Flo Tools installation process?  We have already 
> installed iLok and Keyboard Maestro and tried to follow these instructions 
>  to the best of our ability, but we 
> keep running into the "The variable osName is not defined" pop-up message.  
> We have a current 2022.4 version of Pro Tools installed on the computer and 
> are trying to download Flo Tools 2022.4
> 
> Any suggestions?
> 
> Much appreciated!
> Marc San Marco
> 
> 
> -- 
> 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/80c75879-37fd-43ae-bde1-121a9f60a7c5n%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/2ACED4B8-ECB1-4271-8C7B-7F855325DCF1%40gmail.com.

Re: OS Ventura info/advice

[Slau Halatyn]

Hi Brian,

That is the latest version and it does work in Ventura but the Ventura 
installer version is in the Drop Box. Email me off list if you don't have 
access and/or I can just attach it directly. LMK
Slau


> On Jan 4, 2023, at 12:13 PM, Brian Casey  
> wrote:
> 
> Hi all, I hope you’re all off to a good start in 2023. 
> 
> I’ve recently taken delivery of a new mac studio with a view to gradually 
> upgrading my main studio computer from my old trusty 2011 iMac. 
> 
> I’ve just installed a bunch of plugins and the latest protools, and its just 
> dawned on me the latest FloTools is 2022.4 or some such. I’m guessing this 
> won’t work on Ventura just yet? 
> 
> I’m guessing I just hold tight for now but I’d welcome any info or vague 
> estimates of when things may catch up with Ventura 
> 
> Thanks, 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/522700F9-3209-40A8-8FAD-455F18CF4C18%40wavefieldrecordings.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/BE63D837-1C3D-42AA-9521-7E5BA0CFADE9%40gmail.com.

Re: Basic question about using Boom plugin in ProTools

[Slau Halatyn]

Only the developers can do that and I suspect this is one of those things that 
would simply never be included with automation parameters.

> On Dec 27, 2022, at 1:05 PM, Chris Gilland  wrote:
> 
> OK, that's what I suspected. Is it something I could get Aira to help with 
> Team Viewer to make it automatable, or is that something done by the plugin 
> venders themselves, and out of our control.
> 
> Chris.
> 
>> On Dec 27, 2022, at 1:00 PM, Slau Halatyn  wrote:
>> 
>> Yes. Within the effects area, only parameters that can be automated are 
>> visible. So, for example, a pop-up menu would not fall under that category 
>> and would not be seen by VoiceOver.
>> 
>>> On Dec 27, 2022, at 12:22 PM, Chris Gilland  wrote:
>>> 
>>> When you say "nonautomatable", I assume that would mean the parameter 
>>> wouldn't be accessible with Voiceover? - Or, am I assuming incorrectly.
>>> 
>>> Chris.
>>> 
>>>> On Dec 27, 2022, at 10:18 AM, Slau Halatyn  wrote:
>>>> 
>>>> Although there are presets, I don't think they account for meter. There's 
>>>> probably a non-automatable element which controls meter from the Boom UI. 
>>>> Not sure if there's a feasible workaround.
>>>> 
>>>> 
>>>>> On Dec 27, 2022, at 8:37 AM, Chris Gilland  wrote:
>>>>> 
>>>>> That's the issue though.
>>>>> 
>>>>> I tried changing the time signature to 3/4 as you described, but it 
>>>>> definitely didn't change the patterns out to 3/4. Should it have?
>>>>> 
>>>>> Chris.
>>>>> 
>>>>>> On Dec 26, 2022, at 7:46 PM, Rory McDonald  wrote:
>>>>>> 
>>>>>> There are 2 things to try.  though  I must also say that I don't use 
>>>>>> boom much, so thereby can not comment on the recording of their sample 
>>>>>> patterns. On with the things to try:
>>>>>> First change your time signature from 4/4 to 3/4. You do this by hitting 
>>>>>> command 1 to go to the time operations window, and there theres 2 
>>>>>> textfields to change your signature. You should then hear patterns in 
>>>>>> 3/4 as desired.
>>>>>> Second, if this for whatever reason doesn't work, on the lower keys of 
>>>>>> your keyboard, you can play the drum samples like a standard midi drum 
>>>>>> kit. You could always create a pattern of your own doing it that way, 
>>>>>> aftr all the boom plug inself is largely inaccessible other than playing 
>>>>>> the keys on the keyboard and choosing presets. Hope this helps. 
>>>>>> 
>>>>>> Rory
>>>>>> 
>>>>>>> On Dec 27, 2022, at 1:04 PM, clgillan...@gmail.com wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> OK, I have the stock Boom plugin which comes with the installation of 
>>>>>>> ProTools.
>>>>>>>  
>>>>>>> I see the different presets, and I also see that if I hold down a note 
>>>>>>> like C4, or rather middle C, on my midi controller, as long as that 
>>>>>>> note is held, it plays the drum pattern associated with that preset.
>>>>>>>  
>>>>>>> The problem is, I’ve gone through a lot of the presets, but don’t seem 
>>>>>>> to find anything that is 3 / 4 waltz time. Everything seems to be 4 / 4.
>>>>>>>  
>>>>>>> I was curious if there is a setting somewhere within the plugin window 
>>>>>>> that would let me configure the time signature it’s using, as perhaps 
>>>>>>> when looking, I missed something which should have been fairly obvious. 
>>>>>>> Or, is it something where the patterns to choose from are pretty well 
>>>>>>> pre-fix recorded, you get what you get.
>>>>>>>  
>>>>>>> Thanks for any help.
>>>>>>>  
>>>>>>> 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

Re: Basic question about using Boom plugin in ProTools

[Slau Halatyn]

Yes. Within the effects area, only parameters that can be automated are 
visible. So, for example, a pop-up menu would not fall under that category and 
would not be seen by VoiceOver.

> On Dec 27, 2022, at 12:22 PM, Chris Gilland  wrote:
> 
> When you say "nonautomatable", I assume that would mean the parameter 
> wouldn't be accessible with Voiceover? - Or, am I assuming incorrectly.
> 
> Chris.
> 
>> On Dec 27, 2022, at 10:18 AM, Slau Halatyn  wrote:
>> 
>> Although there are presets, I don't think they account for meter. There's 
>> probably a non-automatable element which controls meter from the Boom UI. 
>> Not sure if there's a feasible workaround.
>> 
>> 
>>> On Dec 27, 2022, at 8:37 AM, Chris Gilland  wrote:
>>> 
>>> That's the issue though.
>>> 
>>> I tried changing the time signature to 3/4 as you described, but it 
>>> definitely didn't change the patterns out to 3/4. Should it have?
>>> 
>>> Chris.
>>> 
>>>> On Dec 26, 2022, at 7:46 PM, Rory McDonald  wrote:
>>>> 
>>>> There are 2 things to try.  though  I must also say that I don't use boom 
>>>> much, so thereby can not comment on the recording of their sample 
>>>> patterns. On with the things to try:
>>>> First change your time signature from 4/4 to 3/4. You do this by hitting 
>>>> command 1 to go to the time operations window, and there theres 2 
>>>> textfields to change your signature. You should then hear patterns in 3/4 
>>>> as desired.
>>>> Second, if this for whatever reason doesn't work, on the lower keys of 
>>>> your keyboard, you can play the drum samples like a standard midi drum 
>>>> kit. You could always create a pattern of your own doing it that way, aftr 
>>>> all the boom plug inself is largely inaccessible other than playing the 
>>>> keys on the keyboard and choosing presets. Hope this helps. 
>>>> 
>>>> Rory
>>>> 
>>>>> On Dec 27, 2022, at 1:04 PM, clgillan...@gmail.com wrote:
>>>>> 
>>>>> 
>>>>> OK, I have the stock Boom plugin which comes with the installation of 
>>>>> ProTools.
>>>>>  
>>>>> I see the different presets, and I also see that if I hold down a note 
>>>>> like C4, or rather middle C, on my midi controller, as long as that note 
>>>>> is held, it plays the drum pattern associated with that preset.
>>>>>  
>>>>> The problem is, I’ve gone through a lot of the presets, but don’t seem to 
>>>>> find anything that is 3 / 4 waltz time. Everything seems to be 4 / 4.
>>>>>  
>>>>> I was curious if there is a setting somewhere within the plugin window 
>>>>> that would let me configure the time signature it’s using, as perhaps 
>>>>> when looking, I missed something which should have been fairly obvious. 
>>>>> Or, is it something where the patterns to choose from are pretty well 
>>>>> pre-fix recorded, you get what you get.
>>>>>  
>>>>> Thanks for any help.
>>>>>  
>>>>> 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>.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/ptaccess/024a01d91955%249a4c0c50%24cee424f0%24%40gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/ptaccess/024a01d91955%249a4c0c50%24cee424f0%24%40gmail.com?utm_medium=email&utm_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/3AC34375-B944-4884-BC63-A24FD9CE8E67%40rogers.com
>>>>  
>&g

Re: Basic question about using Boom plugin in ProTools

[Slau Halatyn]

Although there are presets, I don't think they account for meter. There's 
probably a non-automatable element which controls meter from the Boom UI. Not 
sure if there's a feasible workaround.


> On Dec 27, 2022, at 8:37 AM, Chris Gilland  wrote:
> 
> That's the issue though.
> 
> I tried changing the time signature to 3/4 as you described, but it 
> definitely didn't change the patterns out to 3/4. Should it have?
> 
> Chris.
> 
>> On Dec 26, 2022, at 7:46 PM, Rory McDonald  wrote:
>> 
>> There are 2 things to try.  though  I must also say that I don't use boom 
>> much, so thereby can not comment on the recording of their sample patterns. 
>> On with the things to try:
>> First change your time signature from 4/4 to 3/4. You do this by hitting 
>> command 1 to go to the time operations window, and there theres 2 textfields 
>> to change your signature. You should then hear patterns in 3/4 as desired.
>> Second, if this for whatever reason doesn't work, on the lower keys of your 
>> keyboard, you can play the drum samples like a standard midi drum kit. You 
>> could always create a pattern of your own doing it that way, aftr all the 
>> boom plug inself is largely inaccessible other than playing the keys on the 
>> keyboard and choosing presets. Hope this helps. 
>> 
>> Rory
>> 
>>> On Dec 27, 2022, at 1:04 PM, clgillan...@gmail.com wrote:
>>> 
>>> 
>>> OK, I have the stock Boom plugin which comes with the installation of 
>>> ProTools.
>>>  
>>> I see the different presets, and I also see that if I hold down a note like 
>>> C4, or rather middle C, on my midi controller, as long as that note is 
>>> held, it plays the drum pattern associated with that preset.
>>>  
>>> The problem is, I’ve gone through a lot of the presets, but don’t seem to 
>>> find anything that is 3 / 4 waltz time. Everything seems to be 4 / 4.
>>>  
>>> I was curious if there is a setting somewhere within the plugin window that 
>>> would let me configure the time signature it’s using, as perhaps when 
>>> looking, I missed something which should have been fairly obvious. Or, is 
>>> it something where the patterns to choose from are pretty well pre-fix 
>>> recorded, you get what you get.
>>>  
>>> Thanks for any help.
>>>  
>>> 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/024a01d91955%249a4c0c50%24cee424f0%24%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/3AC34375-B944-4884-BC63-A24FD9CE8E67%40rogers.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/600B5727-BDE3-49AC-BFD3-8E864E90EAAF%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/08F01EFF-BC0B-4C87-B91C-AD206BDED68F%40gmail.com.

Re: Accessibility in the play ability of pedal steel by impact SoundWorks

[Slau Halatyn]

Pedal steel is very useable. It's important to read the manual to understand 
its functionality and refer to notes on key switches below

Pedal Steel Key Switches

Articulation in red keys:
Normal is B flat above highest note
Harmonic is B
Fret Position in purple keys:
Lowest is C
Medium Low is C sharp
Medium is D
Medium High is E flat
High is E
Closest is F

Upward is F sharp
Downward is G
Shortest is A flat
is A

Moving down, 1 octave below the lowest B note, Tonic goes from B down to C with 
orange keys.
Voice Mode is right below in blue keys:
Polyphonic Legato is A
Polyphonic is B flat
Harmonized Monophonic is B


> On Dec 4, 2022, at 6:56 AM, Alex Coleman  wrote:
> 
> Hello all. I was wondering if anyone has had any experience using the pedal 
> steel instrument by impact sound works, and if so, how would you rate its 
> accessibility level?
> I would assume that in order to create custom harmony mapping‘s, one might 
> need sighted assistance.
> However, I was wondering if we would be able to adjust parameters such as the 
> key of the song, and other values using KK?
> Looking forward to hearing good news from someone on this instrument. Thanks 
> again.
> 
> Alex
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/D23183BC-E3CB-4431-BB6F-E30A8262BC0C%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/0BFCA841-F1AF-4E0D-B54C-B9CD11F313D8%40gmail.com.

Re: È UN AVVOCATO ASSASSINO: #CRISTINAROSSELLO CRISTINA ROSSELLO DI FORZA ITALIA MAFIOSA #FORZAITALIA MAFIOSA E COMUNIONE E LIBERAZIONE #COMUNIONEELIBERAZIONE (DOVE TRAMA COL LAVA SOLDI MAFIOSI, #GIOV

[Slau Halatyn]

Reported as abuse and spam.

> On Dec 2, 2022, at 5:04 AM, Tom Hessels  wrote:
> 
> Hi All,
> What doe this mail here.
> Stop this please!
>  
>  
> Van: ptaccess@googlegroups.com  
> [mailto:ptaccess@googlegroups.com] Namens ENRICA PERRUCCHIETTI 
> ANTIBERLUSCONIANI PRONTIATUTTO
> Verzonden: vrijdag 2 december 2022 10:28
> Aan: Pro Tools Accessibility  >
> Onderwerp: È UN AVVOCATO ASSASSINO: #CRISTINAROSSELLO CRISTINA ROSSELLO DI 
> FORZA ITALIA MAFIOSA #FORZAITALIA MAFIOSA E COMUNIONE E LIBERAZIONE 
> #COMUNIONEELIBERAZIONE (DOVE TRAMA COL LAVA SOLDI MAFIOSI, #GIOVANNIRAIMONDI 
> GIOVANNI RAIMONDI DI MATER OLBIA SPA.
>  
> È UN AVVOCATO ASSASSINO: #CRISTINAROSSELLO CRISTINA ROSSELLO DI FORZA ITALIA 
> MAFIOSA #FORZAITALIA MAFIOSA E COMUNIONE E LIBERAZIONE #COMUNIONEELIBERAZIONE 
> (DOVE TRAMA COL LAVA SOLDI MAFIOSI, #GIOVANNIRAIMONDI GIOVANNI RAIMONDI DI 
> MATER OLBIA SPA. #MATEROLBIA SPA, EX POLICLINICO GEMELLI 
> #POLICLINICOGEMELLI, EX FACCENDIERE TRIPLA FACCIA, FACENTE MEGA DELINQUENZE 
> FINANZIARIE, VIA FAMIGLIA DI COSA NOSTRA DEI #LIGRESTI LIGRESTI, COSA SEMPRE 
> FATTA PURE, DA SUPER CRIMINALE ED ASSASSINA CRISTINA ROSSELLO 
> #CRISTINAROSSELLO STESSA)! È POLITICO BERLU$CORROTTO & KILLER: 
> #CRISTINAROSSELLO CRISTINA ROSSELLO (UNITED AT NAZI卐KILLER #CARLTONDEAL 
> CARLTON DEAL FROM SATANIST SECT "SERVE THE CITY #SERVETHECITY" AS WELL AS 
> SATANIC SATANIC SECT "THE WELL #THEWELL", AS WELL AS MURDERING KIND OF 
> FREEMASONRY #FREEMASONRY, MURDERING KIND OF ROTARY #ROTARY AND MURDERIN KIND 
> OF LIONS CLUBS #LIONSCLUBS
> https://www.thewell.be/
> https://www.servethecity.net/team/carlton-deal/
> https://www.facebook.com/carlton.deal/
> https://twitter.com/carlton_deal
> )! PER CONTO DI PEDOFILI STRAGISTI #MASSIMODORIS MASSIMO DORIS DI 
> CRIMINALISSIMA #MEDIOLANUM MEDIOLANUM, #SILVIOBERLUSCONI SILVIO BERLUSCONI, 
> #MARINABERLUSCONI MARINA BERLUSCONI, #PIERSILVIOBERLUSCONI PIERSILVIO 
> BERLUSCONI E #FEDELECONFALONIERI FEDELE CONFALONIERI, TRAMA A MORTE EROI ANTI 
> MAFIA E NAZISMO DI SOCIETÀ  DI COSA NOSTRA: #FININVEST, FININVEST, #MEDIASET 
> MEDIASET, #MFE #MEDIAFOREUROPE MFE MEDIA FOR EUROPE E #MONDADORI MONDADORI!
> 
> L'AVVOCATO PEDOFILO, LESBICONE, MASSO^NAZI卐FASCISTA, CORROTTO, LADRO E KILLER 
> CRISTINA ROSSELLO DI MAFIOSA E HITLERIANA #FORZAITALIA FORZA ITALIA E 
> DELINQUENZIALI TIPI DI MASSONERIA NEO P2ISTA ASSASSINA, ROTARY #ROTARY 
> ASSASSINO, #LIONSCLUBS LIONS CLUBS ASSASSINI, KIWANIS #KIWANIS ASSASSINI, 
> CLUB DIPLOMATIA #CLUBDIPLOMATIA ASSASSINO, CLUB CANOVA #CLUBCANOVA ASSASSINO, 
> RICICLA TANTISSIMI SOLDI MAFIOSI, VIA SUO CRIMINALISSIMO 
> #ROSSELLOFAMILYOFFICE ROSSELLO FAMILY OFFICE DI LONDRA
> http://www.cristinarossello.it/EN/rfo.html
> (IN COLLABORAZIONE CON CRIMINALISSIMO MASSONE NAZISTA E COMPLOTTARDO CARLTON 
> DEAL
> https://www.thewell.be/
> https://www.servethecity.net/team/carlton-deal/
> https://www.facebook.com/carlton.deal/
> https://twitter.com/carlton_deal)
> 
> LA LECCA FIGA DI RAGAZZINE 13 ENNI, LA VOMITEVOLE PEDOFILA ED OMICIDA 
> CRISTINA ROSSELLO #CRISTINAROSSELLO UNITA AL PEDOFILO ASSASSINO FEDELE 
> CONFALONIERI #FEDELECONFALONIERI DI #MEDIASET MEDIASET ALIAS MAFIASET O #MFE 
> ALIAS MAFIA FOR EUROPE, COMPLOTTANO A MORTE, EROI ANTI MAFIA E NAZISMO DI 
> SILVIO BERLUSCONI #SILVIOBERLUSCONI, #BERLUSCONI, NEL MONDO INTERO!
> 
> LA LECCA FIGA DI RAGAZZINE 13 ENNI, LA VOMITEVOLE PEDOFILA ED OMICIDA 
> CRISTINA ROSSELLO #CRISTINAROSSELLO PROTEGGE PURE SOLDI STRAGISTI E LATITANZE 
> DI MAFIOSI N1 AL MONDO: #MATTEOMESSINADENARO MATTEO MESSINA DENARO E 
> #GIUSEPPEMOTISI GIUSEPPE MOTISI (COPERTA DA NAZI卐LEGHISTA BERLUSCONICCHIO 
> PEDERASTA ED OMICIDA PAOLO BARRAI A DUBAI... FA PURE RIMA... CRIMINALE 
> EFFERATO #PAOLOBARRAI, IMBOSCANTESI A #DUBAI, PER NON FINIRE IN CARCERE A 
> MILANO). LA KILLER SATANICA CRISTINA ROSSELLO #CRISTINAROSSELLO, DA TANTI 
> ANNI, ORGANIZZA PURE TANTI OMICIDI MASSO^MAFIOSI DA FAR PASSARE PER FALSI 
> SUICIDI, MALORI ED INCIDENTI. LA TRUFFATRICE LECCA VAGINE DI ADOLESCENTI 
> CRISTINA ROSSELLO, LA PEDOFILA #CRISTINAROSSELLO FU ARTEFICE DEI FALLIMENTI 
> DI #FONSAI E #VENETOBANCA! NON SI SCHIFA "IL MASSONE MAXIMO" #ALBERTONAGEL 
> ALBERTO NAGEL DI #MEDIOBANCA MEDIOBANCA A TENERE IN #SPAFID SPAFID UNA 
> CRIMINALE KILLER, HITLERIANA E MAFIOSA COME CRISTINA ROSSELLO 
> #CRISTINAROSSELLO? NON SI SCHIFA #FRATELLIBRANCADISTILLERIE FRATELLI BRANCA 
> DISTILLERIE AD AVER A CHE FARE CON UNA PEDOFILA, LESBICA, NAZISTA ED OMICIDA 
> COME CRISTINA ROSSELLO #CRISTINAROSSELLO? PRESTO TANTISSIMI ALTRI DETTAGLI!
> 
> https://twitter.com/RossellosCrimes
> https://twitter.com/CRosselloUccide
> https://twitter.com/RosselloLaLecca
> https://twitter.com/CatalanoSgama
> https://twitter.com/RossellOmicida
> https://twitter.com/Rossell_Omicida
> 
> SIAMO I NUOVI PARTIGIANI DEL 2022, SALVEREMO L'ITALIA!
> 
> ED A PROPOSITO DI SUO BURATTINAIO, PEDOFILO STRAGISTA, FASCISTA, MA

Re: Weird problem with FloTools

[Slau Halatyn]

It's because the name of the element has changed and now includes the term 
"ARA" in the name. Chi needs to update the macro. Maybe I'll just change it 
myself and throw out a new macro for the next version.
slau


> On Nov 11, 2022, at 11:48 AM, accessibleproto...@gmail.com wrote:
> 
> Check that your track height is set to medium. If it's not, certain things 
> will be hidden from view, including the elasi audio state. If you don't see 
> it in the edit window, FloTools can't see it either. You can use the FloTools 
> command in any window, but the edit window is where the actual elastic audio 
> button is located.
> 
> Rocco Fiorentino
> www.musicbyrocco.com
> (609)922-3838
> 
>> On Nov 11, 2022, at 9:13 AM, Christopher Gilland  
>> wrote:
>> 
>> I have an audio track which I have recorded some vocal on. I'm now trying 
>> to enable the elastic audio plugin on that track.
>> 
>> 
>> First, I set the track's time base to ticks instead of samples, as I do want 
>> it to change when the tempo is menipulated..
>> 
>> 
>> Now, when I make absolutely certained that I'm focused on the track, not in 
>> the track list table, but the actual track itself just to be clear, I make 
>> sure the FloTools inspector is on by hitting the slash key. Then, I press E. 
>> I hear absolutely nothing spoken. If I double press the letter E to choose 
>> the algorithm, that isn't working either.
>> 
>> 
>> Do I need to be in the edit window for this to work? I tried from the mix 
>> window, but yeah. Nothing I'm doing seems to be working. All other FloTools 
>> commands work as expected.
>> 
>> 
>> Chris.
>> 
>> -- 
>> ---
>> Chris Gilland
>> 
>> Youtube: http://www.youtube.com/c/chrisgilland
>> 
>> -- 
>> 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/10d5d05c-064a-0468-e0e0-e643a0aaf9c0%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/40822A8C-A3F0-45B7-AB73-1FFA0F6FF390%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/0B3720E2-73E9-4B6B-95B9-E6B1B42A7E10%40gmail.com.

Re: Unable to reinstall Flow Tools

[Slau Halatyn]

Thanks for doing that so quickly, Rocco.

> On Oct 26, 2022, at 2:24 PM, Rocco Fiorentino  
> wrote:
> 
> Hi all,
> 
> A Flo Tools installer for Ventura is now in the Dropbox. It’s called “Flo 
> Tools Temporary installer for Ventura” :) let me know if anyone has any 
> issues installing.
> 
> Best,
> 
> Rocco
> 
> 
>> On Oct 26, 2022, at 1:14 PM, Christopher Gilland > <mailto:clgillan...@gmail.com>> wrote:
>> 
>> Yeah... That sounds like a plan. Keep us posted. Smile. NO rush.
>> 
>> 
>> 
>> BTW, I saw the other day you removed those Kontakt AAX test macros for 
>> Chris2 file out of the Dropbox. That's fine though as I do have it backed up 
>> here elsewhere.
>> 
>> 
>> 
>> Chris.
>> 
>> ---
>> Chris Gilland
>> 
>> Youtube: http://www.youtube.com/c/chrisgilland
>> On 10/26/2022 11:03 AM, Slau Halatyn wrote:
>>> I think we might do what we did once before and just post a temporary 
>>> installer in the Drop Box. stay tuned on that.
>>> Slau
>>> 
>>> 
>>>> On Oct 25, 2022, at 11:49 PM, Chris Gilland  
>>>> <mailto:clgillan...@gmail.com> wrote:
>>>> 
>>>> Yikes!
>>>> 
>>>> Thank God I didn't do what Goerge did and uninstall it then, as I too 
>>>> noticed the first time, PT didn't seem to be navigatable with Voiceover. I 
>>>> think though, Slau, it was just that odd bug where sometimes it says no 
>>>> windows, and until you restart Voiceover, you can't regain control of the 
>>>> application.
>>>> 
>>>> I wonder what on earth's making it do that by the way.
>>>> 
>>>> Anyway, thanks for letting us know about FloTools. Is there a way we could 
>>>> manually back up the macros included and then just manually import them 
>>>> without the actual installer, or is that kind of more a pain in the arse 
>>>> than it's worth?
>>>> 
>>>> I'm just trying to think how things could be backed up and restored if 
>>>> needed. Like I say, fortunately, I have an image made of my Monterey 
>>>> install, so if I absolutely had to, I could go back, but right now, I 
>>>> don't see any need to do that.
>>>> 
>>>> Chris.
>>>> 
>>>>> On Oct 25, 2022, at 11:14 PM, Slau Halatyn  
>>>>> <mailto:slauhala...@gmail.com> wrote:
>>>>> 
>>>>> Hi George,
>>>>> 
>>>>> Yeah, that's a bit unfortunate because both Pro Tools and Flo Tools do 
>>>>> not yet support Ventura. At least on the Ventura front, it's not a big 
>>>>> issue. With flo Tools, the installer simply doesn't recognize Ventura as 
>>>>> a valid OS. Hopefully, Rocco can chime in and help come up with a 
>>>>> workaround. Stay tuned.
>>>>> 
>>>>> Slau
>>>>> 
>>>>> 
>>>>>> On Oct 25, 2022, at 10:05 PM, George Bitzer  
>>>>>> <mailto:gee-...@comcast.net> wrote:
>>>>>> 
>>>>>> Hello my name is George Bitzer and I am new to Pro Tools. Maybe I 
>>>>>> shouldn't have but I upgraded to Mac OS Ventura. After doing so, after 
>>>>>> starting Pro Tools, I had to close and reopen Voiceover. I thought that 
>>>>>> the problem was Flow Tools and I uninstalled it using the uninstaller in 
>>>>>> the Flow Tools folder. When I tried to reinstall, I got the message, "OS 
>>>>>> variable name undefined." HELP!! Appologies for maybe being off topic.
>>>>>> 
>>>>>> -- 
>>>>>> 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/7d9a2353-acff-434a-90bd-6170e8157e18n%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/ptaccess/7d9a2353-acff-434a-90bd-6170e8157e18n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>>> 
>>>

Re: Unable to reinstall Flow Tools

[Slau Halatyn]

I think we might do what we did once before and just post a temporary installer 
in the Drop Box. stay tuned on that.
Slau


> On Oct 25, 2022, at 11:49 PM, Chris Gilland  wrote:
> 
> Yikes!
> 
> Thank God I didn't do what Goerge did and uninstall it then, as I too noticed 
> the first time, PT didn't seem to be navigatable with Voiceover. I think 
> though, Slau, it was just that odd bug where sometimes it says no windows, 
> and until you restart Voiceover, you can't regain control of the application.
> 
> I wonder what on earth's making it do that by the way.
> 
> Anyway, thanks for letting us know about FloTools. Is there a way we could 
> manually back up the macros included and then just manually import them 
> without the actual installer, or is that kind of more a pain in the arse than 
> it's worth?
> 
> I'm just trying to think how things could be backed up and restored if 
> needed. Like I say, fortunately, I have an image made of my Monterey install, 
> so if I absolutely had to, I could go back, but right now, I don't see any 
> need to do that.
> 
> Chris.
> 
>> On Oct 25, 2022, at 11:14 PM, Slau Halatyn  wrote:
>> 
>> Hi George,
>> 
>> Yeah, that's a bit unfortunate because both Pro Tools and Flo Tools do not 
>> yet support Ventura. At least on the Ventura front, it's not a big issue. 
>> With flo Tools, the installer simply doesn't recognize Ventura as a valid 
>> OS. Hopefully, Rocco can chime in and help come up with a workaround. Stay 
>> tuned.
>> 
>> Slau
>> 
>> 
>>> On Oct 25, 2022, at 10:05 PM, George Bitzer  wrote:
>>> 
>>> Hello my name is George Bitzer and I am new to Pro Tools. Maybe I shouldn't 
>>> have but I upgraded to Mac OS Ventura. After doing so, after starting Pro 
>>> Tools, I had to close and reopen Voiceover. I thought that the problem was 
>>> Flow Tools and I uninstalled it using the uninstaller in the Flow Tools 
>>> folder. When I tried to reinstall, I got the message, "OS variable name 
>>> undefined." HELP!! Appologies for maybe being off topic.
>>> 
>>> -- 
>>> 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/7d9a2353-acff-434a-90bd-6170e8157e18n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/ptaccess/7d9a2353-acff-434a-90bd-6170e8157e18n%40googlegroups.com?utm_medium=email&utm_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/D1887C2D-A725-47A9-8165-6E299CADD97B%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/D1887C2D-A725-47A9-8165-6E299CADD97B%40gmail.com?utm_medium=email&utm_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/8578833C-2194-4D74-B77D-852FDEB7C7AA%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/8578833C-2194-4D74-B77D-852FDEB7C7AA%40gmail.com?utm_medium=email&utm_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/C45A3B39-14FF-4D20-AB01-73EF562D4820%40gmail.com.

Re: Unable to reinstall Flow Tools

[Slau Halatyn]

Chris,
The way Pro Tools is behaving in Ventura is actually the way it should from the 
standpoint of VoiceOver. Command-clicking selects non-contiguous tracks and 
Shift-clicking (or using Shift with the Control+P/Semicolon selects consecutive 
tracks. VoiceOver users have had the unusual benefit of being able to select 
multiple tracks by purely performing the default action with VO+Space. It's the 
way the Pro Tools UI works for sighted users. We've always tried to have parity 
with sighted users and this is an example of what that involves. It might feel 
like a bug but technically it's not. BTW, you can bring up the Action Menu on a 
track and choose to "press " the track and it will simply add it to the 
selection.

Slau


> On Oct 25, 2022, at 10:26 PM, Christopher Gilland  
> wrote:
> 
> If you don't mind me asking, I don't mean to hijack your thread, so you can 
> just answer this and then we'll move on, but I'm really curious, as you're 
> the only other person I know who's outwardly admitted that they updated to 
> Ventura prior to PT being officially supported..
> 
> 
> When you have multiple tracks in the track list table at a time, what 
> happens, regardless FloTools being installed or not, if you try selecting the 
> first track in the table at the very top, then VO+down arrow to the next 
> track in the list, and then hit VO+Space? Do you find like me it's really 
> acting totally F***ed up, and is selecting that next track but not leaving 
> the other one selected as it should?
> 
> 
> I can command+click on each track to select or unselect them individually, 
> and yeah, CTRL+semi colon, and CTRL+P do work, and also adding shift with 
> those shortcuts works as well, but doing it the old fassion way by literally 
> going into the table and VO+spacing on tracks to toggle them is totally 
> totally totally! busted on my end.
> 
> 
> So far, I'm not seeming to have any other show stopping issues, but then, 
> I've not really done much with PT since upgrading yesterday, so nightmares 
> may yet to be discovered. I hope and pray not though. I do however have a 
> time machine backup, and a bootable USB drive of Monterey, so if worst comes 
> to worst, I'm not totally screwed. I'd rather not go back, but I will if I 
> absolutely absolutely must.
> 
> 
> 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/c58c13c2-4ce9-8f0d-51f1-aae77cf640bb%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/CE6FFD27-04A1-46E3-8E91-48E27474C8EA%40gmail.com.

Re: Unable to reinstall Flow Tools

[Slau Halatyn]

Hi George,

Yeah, that's a bit unfortunate because both Pro Tools and Flo Tools do not yet 
support Ventura. At least on the Ventura front, it's not a big issue. With flo 
Tools, the installer simply doesn't recognize Ventura as a valid OS. Hopefully, 
Rocco can chime in and help come up with a workaround. Stay tuned.

Slau


> On Oct 25, 2022, at 10:05 PM, George Bitzer  wrote:
> 
> Hello my name is George Bitzer and I am new to Pro Tools. Maybe I shouldn't 
> have but I upgraded to Mac OS Ventura. After doing so, after starting Pro 
> Tools, I had to close and reopen Voiceover. I thought that the problem was 
> Flow Tools and I uninstalled it using the uninstaller in the Flow Tools 
> folder. When I tried to reinstall, I got the message, "OS variable name 
> undefined." HELP!! Appologies for maybe being off topic.
> 
> -- 
> 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/7d9a2353-acff-434a-90bd-6170e8157e18n%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/D1887C2D-A725-47A9-8165-6E299CADD97B%40gmail.com.

Re: Updates: Adhere to this gentle warning

[Slau Halatyn]

Hi Chris,
You did nothing wrong at all. I was merely poking a little fun at the fact 
that, despite your disclaimer, you do tend to be overly dramatic with the 
"Chocked beyond belief" type of comment. Sorry, but wouldn't you agree that 
such a statement is just a wee bit over the top? Again, I'm just making light 
of it and I hope you can see the light-hearted humor in it. Helping is a good 
thing, of course and it's a good thing to point out the obvious sometimes. It's 
all good. Don't take offense. I'm just funnin' with you :)


> On Oct 24, 2022, at 4:20 PM, Christopher Gilland  
> wrote:
> 
> Goodness, Slau. I'm sorry! Not to be rude/overdramatic here, but I thought I 
> was doing a good thing, helping. I guess not though. Jesus Christ! Thank you 
> for the link though.
> 
> 
> 
> Chris.
> 
> ---
> Chris Gilland
> 
> Youtube: http://www.youtube.com/c/chrisgilland 
> <http://www.youtube.com/c/chrisgilland>
> On 10/24/2022 4:06 PM, Slau Halatyn wrote:
>> Chris,
>> Once your shock (beyond belief) wears off, you should consider the fact that 
>> Avid posts compatibility data on their website and Pro Tools users are used 
>> to the fact that upgrading an OS before Pro Tools supports it is not 
>> recommended, not to mention somewhat risky. People do, however, try things 
>> out on a separate machine or partition just to experiment. Brace yourself 
>> (so that you're not shocked) when the question of whether or not to upgrade 
>> to Ventura comes up for months to come and users will repeatedly be pointed 
>> toward the compatibility chart on the Avid site. When the question 
>> inevitably comes up, steel yourself and share the following link:
>> https://avid.secure.force.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart
>>  
>> <https://avid.secure.force.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart>
>> 
>> 
>> 
>>> On Oct 24, 2022, at 2:56 PM, Christopher Gilland >> <mailto:clgillan...@gmail.com>> wrote:
>>> 
>>> I'm absolutely shocked beyond belief that not a single person, not even 
>>> Slau, has written in on the list about this. as of yet. At least, not that 
>>> I've seen.
>>> 
>>> Remember that today for us Mac users is mager upgrade time. This means OS 
>>> Monterrey is getting an upgrade officially to OS 13 Ventura.
>>> 
>>> Along with this, we may even be getting the official iPadOS 16, though I'm 
>>> more here to focus on the mac.
>>> 
>>> It's important to note that the update today for Ventura is *not* a beta... 
>>> Not even a public beta. It's the official release.
>>> 
>>> That being said, however, doesn't mean that just because the update is out, 
>>> you immediately should jump for joy with excitement, "it's here, it's here,
>>> it's here, finally!"
>>> 
>>> Let me say this: During the beta cicle, neither myself nor others could say 
>>> much due to nondisclosure NDA agreements. There are probably still things 
>>> privately
>>> being tested which people are on NDA regarding; they most likely probably 
>>> can't even disclose they are! testing in the first place, so it's most 
>>> likely
>>> probably a waist of your time to ask around.
>>> 
>>> What I'd say is, check, check, check, and oh did I mention, check! And by 
>>> the way, check! OK, you get my point.
>>> 
>>> The bottom line is, will things work with Ventura? Prr'rrobbably, yes. You 
>>> should! key word, should! be fine as far as DAW's like Logic, Reaper, 
>>> ProTools,
>>> etc. But! that being said, be careful. The bigger concern is plugins and 
>>> such.
>>> 
>>> For new users just getting on the bandwaggon with all this stuff, let me be 
>>> very black and white crystal clear and maybe even a bit direct with you. 
>>> Even
>>> though this would be an official release, you still do this at your own 
>>> risk. A lot of developers haven't yet officially, and that's the key word 
>>> here,
>>> officially, declared and certified that their software is fully compatible. 
>>> I definitely don't think Avid has with ProTools.
>>> 
>>> Also note that just because a DAW launches and works in Ventura for the 
>>> most part doesn't mean it's fully compatible. Depending on your current 
>>> software,
>>> 

Re: Updates: Adhere to this gentle warning

[Slau Halatyn]

Chris,
Once your shock (beyond belief) wears off, you should consider the fact that 
Avid posts compatibility data on their website and Pro Tools users are used to 
the fact that upgrading an OS before Pro Tools supports it is not recommended, 
not to mention somewhat risky. People do, however, try things out on a separate 
machine or partition just to experiment. Brace yourself (so that you're not 
shocked) when the question of whether or not to upgrade to Ventura comes up for 
months to come and users will repeatedly be pointed toward the compatibility 
chart on the Avid site. When the question inevitably comes up, steel yourself 
and share the following link:
https://avid.secure.force.com/pkb/articles/en_US/compatibility/Pro-Tools-Operating-System-Compatibility-Chart
 




> On Oct 24, 2022, at 2:56 PM, Christopher Gilland  
> wrote:
> 
> I'm absolutely shocked beyond belief that not a single person, not even Slau, 
> has written in on the list about this. as of yet. At least, not that I've 
> seen.
> 
> Remember that today for us Mac users is mager upgrade time. This means OS 
> Monterrey is getting an upgrade officially to OS 13 Ventura.
> 
> Along with this, we may even be getting the official iPadOS 16, though I'm 
> more here to focus on the mac.
> 
> It's important to note that the update today for Ventura is *not* a beta... 
> Not even a public beta. It's the official release.
> 
> That being said, however, doesn't mean that just because the update is out, 
> you immediately should jump for joy with excitement, "it's here, it's here,
> it's here, finally!"
> 
> Let me say this: During the beta cicle, neither myself nor others could say 
> much due to nondisclosure NDA agreements. There are probably still things 
> privately
> being tested which people are on NDA regarding; they most likely probably 
> can't even disclose they are! testing in the first place, so it's most likely
> probably a waist of your time to ask around.
> 
> What I'd say is, check, check, check, and oh did I mention, check! And by the 
> way, check! OK, you get my point.
> 
> The bottom line is, will things work with Ventura? Prr'rrobbably, yes. You 
> should! key word, should! be fine as far as DAW's like Logic, Reaper, 
> ProTools,
> etc. But! that being said, be careful. The bigger concern is plugins and such.
> 
> For new users just getting on the bandwaggon with all this stuff, let me be 
> very black and white crystal clear and maybe even a bit direct with you. Even
> though this would be an official release, you still do this at your own risk. 
> A lot of developers haven't yet officially, and that's the key word here,
> officially, declared and certified that their software is fully compatible. I 
> definitely don't think Avid has with ProTools.
> 
> Also note that just because a DAW launches and works in Ventura for the most 
> part doesn't mean it's fully compatible. Depending on your current software,
> and current hardware setup, you might luck out. Things for you may work 
> flawlessly. But then, the next Joe Bird from down the street may have a 
> totally
> different setup configuration. He/She/They try installing Ventura, and it 
> wind up being an absolute utter dreadful nightmare.
> 
> If you have another secondary mac you can try things with, it would be very 
> advisable to try Ventura there before putting it on your main production 
> machine.
> Once you know that it works OK for your environment, then you could migrate 
> things over slowly little by little to your main machine. The reason
> I say slowly little by little is that if, hypothetically something does 
> break, you'll remember the last thing in steps you did, and either can undo 
> it,
> or can say, whoops, that's where things broke. Then you can evaluate, how 
> important is it really that this thing that broke really is. Is it something
> though completely broken you can tollerate, or is it a total dealbreaker. And 
> hopefully if you're smart, because it broke first on your test 
> machine/environment,
> it's not like you brought your main machine to a halt, sota speak.
> 
> If you, like me, don't have a separate system, then you really only have 3 
> options: 1, best choice, don't do it at all, just wait until things are fully
> certified to be compatible, 2. Do it, but be darn sure you have either a Time 
> Machine backup of Monterrey, or wherever you were previously, or 3, use an
> external hard disk, or find a way to partition your current disk without 
> wiping it and dule boot between the 2 OS's until you know things totally are 
> safe.
> 
> In conclusion, I'm simply just saying, be really really really careful today! 
> Just because the update is there doesn't mean you just have to have it right
> away. If it means making or breaking your job, then make it.
> 
> My mamma  always told me, if it ain't broken, don't fix it. LOL

will clean house soon

[Slau Halatyn]

Looks like I'll have to log into the mailing list to clean house of spam, etc. 
Will do that soon.

-- 
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/66DD6BD9-9249-494F-84E9-63E50CB6FDF7%40gmail.com.

Pro Tools 2022.9 is out

[Slau Halatyn]

Avid just released Pro Tools 2022.9. For detailed information about what's new 
in this version, you can download the What's New PDF from your avid account. 
Regarding accessibility, you can take a look at the new chapter 23 in the Pro 
Tools Guide for screen Reader users and listen to the demos at:
https://ptaccess.github.io/chapter23/ 

Cheers,
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/E34F49D3-ABDF-4C63-B7E6-9433A6D7B430%40gmail.com.

Re: Though not advised I'm sure, can this still technically in theory be done?

[Slau Halatyn]

When there's a problem with Pro Tools on an unsupported OS, it's not considered 
a bug. There are a couple of hundred beta testers who test future versions of 
Pro Tools with those future operating systems. Beta versions of PT might work 
fine with an unreleased OS while the release version might not. The beta team 
puts PT through its paces in ways that you'd never imagine yet, sometimes, bugs 
do appear in releases, in fact, hundreds of them. It's a never-ending process 
of crushing them.


> On Sep 16, 2022, at 6:33 AM, Nick Gawronski  wrote:
> 
> Hi, I always like to do tests like this to see how well things work as just 
> because it is not officially supported does not mean that you can not at 
> least get something done on it.  The issue is if you find a bug with Pro 
> Tools on an unofficially supported mac operating system how do you go about 
> reporting the bug so it can at least be known?  Nick Gawronski
> On 9/16/2022 12:38 AM, accessibleproto...@gmail.com wrote:
>> As long as you're in a test environment, like a separate boot drive etc, I 
>> see no harm in trying PT or any other software to see how it does. Just 
>> don't have any expectations going in :)
>> 
>> Rocco Fiorentino
>> www.musicbyrocco.com
>> (609)922-3838
>> 
>>> On Sep 15, 2022, at 6:34 PM, Chris Gilland  wrote:
>>> 
>>> Thank you. That's exactly the answer I was looking for, just a one worded 
>>> yes or no. Enough said. Consider this top it closed. I very much appreciate 
>>> the help. From someone who is at least tried.
>>> 
 On Sep 15, 2022, at 19:30, Rory McDonald  wrote:
 
 No
 
 Rory
 
>> On Sep 15, 2022, at 7:22 PM, Chris Gilland  wrote:
> So, using an M1 system, I want to make it super super clear that I am 
> not suggesting for one second that anyone do this on their primary 
> machine, in fact, I wouldn't even do it on my main production 
> workstation, but just out of curiosity, I know Protools definitely hasn't 
> yet been certified to work with Ventura. In fact, Ventura OS13 isn't even 
> out yet. It's still public beta, hince why I'd never do this on my main 
> machine, but if you have a backup to play with that if things break, 
> isn't a big deal, I'm wondering if you technically speaking could get P'T 
> to run fairly decently on that setup. I know some plugins certainly may 
> not work correctly, but I'm speaking more just PT in and of itself, 3rd 
> party plugins not withstanding.
> 
> NOt asking for much detail here, but more just a general, yes in theory 
> it would, or no, absolutely 100 percent no no no no, don't even attempt, 
> even on a test environment.
> 
> 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/60EBBF4B-A95B-4597-B9FC-9B2630DACC5B%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/DB95B196-A446-491E-AF00-2EE83C8A552A%40rogers.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/B120D3AE-4F0E-478F-88A9-8C7D9DE843C6%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/70fcd465-1ec9-e91b-a05c-3c8c18f8cd4d%40nickgawronski.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/A7EB2DCF-1FB6-4B5B-81FA-705C28DCBF97%40gmail.com.

Re: Fixed - Avid S1 question

[Slau Halatyn]

Hi Martin,

I didn't even have an opportunity to set up my units again. Glad to hear that 
it's a hardware issue and sorry to hear that it's a hardware issue :) At least, 
I'm sure, it's still under warranty and all.

Cheers,
slau


> On Aug 16, 2022, at 8:13 AM, Martin (Punky) Sopart  wrote:
> 
> Hello!
> 
> In this case a hardware issue was the bad guy.
> The page left button doesn't work at all.
> 
> Best! / Martin
> -Original Message-
> From: Martin (Punky) Sopart  
> Sent: Saturday, August 13, 2022 12:41 AM
> To: 'Stefan Albertshauser' via Pro Tools Accessibility 
> 
> Subject: Re: Avid S1 question
> 
> Hello Slau!
> 
> Thanks for answering.
> 
> The page left button has a similar bug when setting pan on a stereo track.
> The initial rotating of the desired encoder changes the left side pan, as 
> expected.
> After pressing page right the right side pan could be controlled, fine.
> Now, after pressing page left again - to control the left side pan again - 
> the encoder still changes the right side pan.
> Pressing page right another time freezes the controlling.
> 
> The page left button seams to execute something strange.
> 
> Best! / Martin
> 
> 
> On Aug 13, 2022, at 12:25 AM, Slau Halatyn  wrote:
> 
> Hi Martin,
> 
> OK, thanks for the additional info. Yeah, I would imagine it shouldn't be 
> necessary to fuss with xml files. I have my S1 and Dock stored away right now 
> but I'll try to set them up again to see if I can recreate the issue. In the 
> mean time, there are a couple of other users who might be able to try as 
> well. Stay tuned.
> Slau
> 
> 
>> On Aug 12, 2022, at 6:14 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello Slau!
>> 
>> The xml file is created by EuControl and stored at:
>> ‎⁨Macintosh HD⁩ ▸ ⁨Library⁩ ▸ ⁨Application Support⁩ ▸ ⁨Euphonix⁩ ▸ 
>> ⁨DYN_APPSETS
>> 
>> I removed it with no success.
>> 
>> Since some EuControl and Pro Tools versions you can use "Attention most 
>> recently clicked DAW area" features (EuControl, general settings).
>> Checking "plug-in" here will  make the surface following Pro Tools.
>> Just use Flo Tools double pressing the insert slot number and that's it.
>> 
>> Using the way you described will cause in the same problem.
>> Pressing page right on the S1 switches to the next 8 parameters, but page 
>> left does nothing.
>> Pressing page right again - EQ III 7 Band - freezes the controlling.
>> 
>> Best! / Martin
>> 
>> 
>> On Aug 12, 2022, at 11:54 PM, Slau Halatyn  wrote:
>> 
>> Hi Martin,
>> I'm not sure what you mean by "Pro Tools 22MAC.xml" in this case. What is 
>> that? If you're using Flo Tools to open an insert, the S1 will not follow 
>> (unless I've overlooked a completely new feature). Normally, opening an 
>> insert from the control surface will put the surface into plug-in edit mode 
>> and the Pro Tools interface will certainly follow by opening the Plug-in 
>> window and displaying the appropriate plug-in. Let's see if we can figure it 
>> out.
>> 
>> Best,
>> Slau
>> 
>> 
>>> On Aug 12, 2022, at 5:03 PM, Martin (Punky) Sopart  
>>> wrote:
>>> 
>>> Hello S1 users!
>>> 
>>> I just got a S1 surface and noticed the following:
>>> 
>>> After opening a plug-in by using Flo Tools (double press of the insert slot 
>>> number), I'm able to control the first 8 parameters
>>> Pressing "Page Right" on the S1 switches to the next 8 parameters, but 
>>> "Page Left" freezes the whole controlling.
>>> 
>>> My idea is that the  "Pro Tools 22Mac.xml" could have wrong entries.
>>> Is there a way to reset it?
>>> 
>>> Before the S1 I got an Avid Dock and my goal is to use both devices.
>>> 
>>> Thank you 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/D2FEDE7B-1BB4-4BE3-86EA-3F0B0EEB72CC%40cakewalker.de.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscrib

Re: Avid S1 question

[Slau Halatyn]

Hi Martin,

OK, thanks for the additional info. Yeah, I would imagine it shouldn't be 
necessary to fuss with xml files. I have my S1 and Dock stored away right now 
but I'll try to set them up again to see if I can recreate the issue. In the 
mean time, there are a couple of other users who might be able to try as well. 
Stay tuned.
Slau


> On Aug 12, 2022, at 6:14 PM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau!
> 
> The xml file is created by EuControl and stored at:
> ‎⁨Macintosh HD⁩ ▸ ⁨Library⁩ ▸ ⁨Application Support⁩ ▸ ⁨Euphonix⁩ ▸ 
> ⁨DYN_APPSETS
> 
> I removed it with no success.
> 
> Since some EuControl and Pro Tools versions you can use "Attention most 
> recently clicked DAW area" features (EuControl, general settings).
> Checking "plug-in" here will  make the surface following Pro Tools.
> Just use Flo Tools double pressing the insert slot number and that's it.
> 
> Using the way you described will cause in the same problem.
> Pressing page right on the S1 switches to the next 8 parameters, but page 
> left does nothing.
> Pressing page right again - EQ III 7 Band - freezes the controlling.
> 
> Best! / Martin
> 
> 
> On Aug 12, 2022, at 11:54 PM, Slau Halatyn  wrote:
> 
> Hi Martin,
> I'm not sure what you mean by "Pro Tools 22MAC.xml" in this case. What is 
> that? If you're using Flo Tools to open an insert, the S1 will not follow 
> (unless I've overlooked a completely new feature). Normally, opening an 
> insert from the control surface will put the surface into plug-in edit mode 
> and the Pro Tools interface will certainly follow by opening the Plug-in 
> window and displaying the appropriate plug-in. Let's see if we can figure it 
> out.
> 
> Best,
> Slau
> 
> 
>> On Aug 12, 2022, at 5:03 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello S1 users!
>> 
>> I just got a S1 surface and noticed the following:
>> 
>> After opening a plug-in by using Flo Tools (double press of the insert slot 
>> number), I'm able to control the first 8 parameters
>> Pressing "Page Right" on the S1 switches to the next 8 parameters, but "Page 
>> Left" freezes the whole controlling.
>> 
>> My idea is that the  "Pro Tools 22Mac.xml" could have wrong entries.
>> Is there a way to reset it?
>> 
>> Before the S1 I got an Avid Dock and my goal is to use both devices.
>> 
>> Thank you 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/D2FEDE7B-1BB4-4BE3-86EA-3F0B0EEB72CC%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/48933BC8-4837-487D-85FD-28FBE1B99791%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/A2163FF8-EEFD-4867-85D6-99DBED822492%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/18CF725D-C2AC-4894-9BEA-B898EC1FCF24%40gmail.com.

Re: Avid S1 question

[Slau Halatyn]

Hi Martin,
I'm not sure what you mean by "Pro Tools 22MAC.xml" in this case. What is that? 
If you're using Flo Tools to open an insert, the S1 will not follow (unless 
I've overlooked a completely new feature). Normally, opening an insert from the 
control surface will put the surface into plug-in edit mode and the Pro Tools 
interface will certainly follow by opening the Plug-in window and displaying 
the appropriate plug-in. Let's see if we can figure it out.

Best,
Slau


> On Aug 12, 2022, at 5:03 PM, Martin (Punky) Sopart  wrote:
> 
> Hello S1 users!
> 
> I just got a S1 surface and noticed the following:
> 
> After opening a plug-in by using Flo Tools (double press of the insert slot 
> number), I'm able to control the first 8 parameters
> Pressing "Page Right" on the S1 switches to the next 8 parameters, but "Page 
> Left" freezes the whole controlling.
> 
> My idea is that the  "Pro Tools 22Mac.xml" could have wrong entries.
> Is there a way to reset it?
> 
> Before the S1 I got an Avid Dock and my goal is to use both devices.
> 
> Thank you 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/D2FEDE7B-1BB4-4BE3-86EA-3F0B0EEB72CC%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/48933BC8-4837-487D-85FD-28FBE1B99791%40gmail.com.

Re: Some problems plz?

[Slau Halatyn]

Hi Ramy,
If you really want to be able to keep discrete Plug-in windows open to be able 
to switch between them more easily, open a plug-in and click on the target 
button. Then open the Mix window and open the other plug-in you wish to switch 
to. Now you'll have 2 plug-in windows open at the same time. If you followed my 
pre-flight checklist and set the Control+F6 shortcut in Keyboard preference 
pane, you can flip between the 2 plug-in windows with Control+F6.
HTH,
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/C744E76B-95F2-4905-A1A1-4E56FFF3B61A%40gmail.com.

Re: Some problems plz?

[Slau Halatyn]

Hi Ramy,
Again as Martin points out, use the trak selector and then the insert selector.

> On Aug 8, 2022, at 10:38 AM, Ramy Moustafa Saber  
> wrote:
> 
> Thanks so much Slau.
> COncerning Plugins, The 2 plugins that i need to toggle between are on 2 
> different tracks, so, this method will not work.
> 
> Warm Regards,
> Dr/ Ramy Moustafa Saber
> Music Producer and Sound Engineer
> Music Instructor at: Faculty of Musical Education
> Helwan University
> 
>> On Aug 8, 2022, at 4:18 PM, Slau Halatyn > <mailto:slauhala...@gmail.com>> wrote:
>> 
>> Hi Ramy,
>> Just to underline what Martin said, within the plug-in window, aside from 
>> the track selector, there's an insert selector which displays the Letter 
>> name of the insert. If you click on that, you'll get a pop-up menu and you 
>> can access all inserts from there. If there's a plug-in instantiated, the 
>> insert letter will be followed by the name of the plug-in on that insert.
>> Regarding the automation, I covered exactly this material in the most recent 
>> chapter of the PT Guide for Screen Reader Users. Hope that helps,\
>> Slau
>> 
>> 
>>> On Aug 8, 2022, at 3:01 AM, Ramy Moustafa >> <mailto:ramy.moustaf...@gmail.com>> wrote:
>>> 
>>> Hello Mr. Slau:
>>> COncerning the Target plugin:
>>> I do not want to see multible plugins opened at the same window or 
>>> something, all i need is an easy method for switching between them,so, if i 
>>> have a compressor opened, and i need to switch between it and an Eq for 
>>> instance, each time i should hit command ` to move between windows and go 
>>> and open the other one, etc, so is there an easy way for switching?
>>> 
>>> COncerning Automation:
>>> Thanks so much for your explnation, however, If you do not mind, i need 
>>> more explnation  or an audio demo please, because  can not do all you told 
>>> me.
>>> Thanks so much for your help
>>> 
>>> Warm Regards,
>>> Dr/ Ramy Moustafa Saber
>>> Music Producer and Sound Engineer
>>> Music Instructor at: Faculty of Musical Education
>>> Helwan University
>>> 
>>> 
>>>  
>>> 
>>> 
>>>> On 7 Aug 2022, at 6:39 PM, Slau Halatyn >>> <mailto:slauhala...@gmail.com>> wrote:
>>>> 
>>>> Dear Doctor Ramy,
>>>> 
>>>> My responses interspersed below:
>>>> On Aug 7, 2022, at 11:25 AM, Ramy Moustafa >>> <mailto:ramy.moustaf...@gmail.com>> wrote:
>>>>> 
>>>>> Hello all:
>>>>> While taking a small mastering course, i am facing some problems related 
>>>>> to SOme plugins and VOice over, so I will write them here, and hope you 
>>>>> can help me fixing what am facing.
>>>>> 
>>>>> 1- how can we Read inside the VU Meeter? is there an accessible VU meeter 
>>>>> plugin?
>>>> VoiceOver only sees one value for metering. It cannot read VU specifically.
>>>> 
>>>>> 2- moving between Open plugins without opening 1 by 1 each time, I tried 
>>>>> TO press on Target plugin but with no help.
>>>> By default, only one plug-in window is open at a time. I wouldn't 
>>>> recommend using more than one plug-in window because you can't see more 
>>>> than one window at a time and, since you would need to bring up the window 
>>>> Chooser and make sure the window is the target, simply selecting from the 
>>>> track selector in one window is more straight-forward.
>>>> 
>>>>> 3- how can i write Volume Automation  by section using Keyboard not 
>>>>> COntrol surface? so i need to add 1 Db volume from bar 10 to bar 20, can 
>>>>> i do this using Just my keyboard or i should use COntrol surface etc?
>>>> This is a deceptively complex question because it depends on a number of 
>>>> factors. To offer an answer that'll work under all circumstances, Make 
>>>> your selection and enter Auto Latch Trim mode and change the volume fader 
>>>> to +1 dB. Engage the transport and either let it play through the 
>>>> selection or use the Write To Selection button in the Automation window if 
>>>> it's a long section that you don't want to play all the way through.
>>>> 
>>>>> 4- When i need to load presets from the Ozone9, Pro tools always crash, 
>>>>> but when voice over is off, it wor

Re: Some problems plz?

[Slau Halatyn]

Hi Martin,
I simply pointed out that Plug-in Alliance has a number of options and reading 
the manual is key to be able to make sense of things.
Slau


> On Aug 8, 2022, at 10:32 AM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau!
> 
> Was there anything helpful on WhatsApp regarding the eq mid side question?
> 
> Thanks and best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Slau 
> Halatyn
> Sent: Sunday, August 7, 2022 6:39 PM
> To: PTAccess List 
> Subject: Re: Some problems plz?
> 
> Dear Doctor Ramy,
> 
> My responses interspersed below:
> 
> On Aug 7, 2022, at 11:25 AM, Ramy Moustafa  <mailto:ramy.moustaf...@gmail.com> > wrote:
> 
> 
> 
>   Hello all:
>   While taking a small mastering course, i am facing some problems 
> related to SOme plugins and VOice over, so I will write them here, and hope 
> you can help me fixing what am facing.
> 
>   1- how can we Read inside the VU Meeter? is there an accessible VU 
> meeter plugin?
> 
> VoiceOver only sees one value for metering. It cannot read VU specifically.
> 
> 
>   2- moving between Open plugins without opening 1 by 1 each time, I 
> tried TO press on Target plugin but with no help.
> 
> By default, only one plug-in window is open at a time. I wouldn't recommend 
> using more than one plug-in window because you can't see more than one window 
> at a time and, since you would need to bring up the window Chooser and make 
> sure the window is the target, simply selecting from the track selector in 
> one window is more straight-forward.
> 
> 
>   3- how can i write Volume Automation  by section using Keyboard not 
> COntrol surface? so i need to add 1 Db volume from bar 10 to bar 20, can i do 
> this using Just my keyboard or i should use COntrol surface etc?
> 
> This is a deceptively complex question because it depends on a number of 
> factors. To offer an answer that'll work under all circumstances, Make your 
> selection and enter Auto Latch Trim mode and change the volume fader to +1 
> dB. Engage the transport and either let it play through the selection or use 
> the Write To Selection button in the Automation window if it's a long section 
> that you don't want to play all the way through.
> 
> 
>   4- When i need to load presets from the Ozone9, Pro tools always crash, 
> but when voice over is off, it works, is there a solution?
> 
> See if others can recreate the issue and, if so, open a support ticket with 
> Izotope.
> 
> 
>   5- what is a good EQ that can do mid side technique? I tried the Ozone 
> 9 EQ, and it crashes with VOice over.
> 
> See my response on WhatsApp.
> 
> 
> 
>   Warm Regards,
>   Dr/ Ramy Moustafa Saber
>   Music Producer and Sound Engineer
>   Music Instructor at: Faculty of Musical Education
>   Helwan University
>   
>   
>   
>   
>   
> 
>  
> 
> 
>   -- 
>   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/82D82B65-3265-49F7-A19D-D58CAC1BF5B4%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/82D82B65-3265-49F7-A19D-D58CAC1BF5B4%40gmail.com?utm_medium=email&utm_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/401EC31D-9799-4599-94B5-92EDE1374B9F%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/401EC31D-9799-4599-94B5-92EDE1374B9F%40gmail.com?utm_medium=email&utm_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/00f901d8ab33%24ae41f6b0%240ac5e410%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/30F06656-A1E3-406E-9816-47EDAA8A7FF4%40gmail.com.

Re: Some problems plz?

[Slau Halatyn]

Hi Ramy,
Just to underline what Martin said, within the plug-in window, aside from the 
track selector, there's an insert selector which displays the Letter name of 
the insert. If you click on that, you'll get a pop-up menu and you can access 
all inserts from there. If there's a plug-in instantiated, the insert letter 
will be followed by the name of the plug-in on that insert.
Regarding the automation, I covered exactly this material in the most recent 
chapter of the PT Guide for Screen Reader Users. Hope that helps,\
Slau


> On Aug 8, 2022, at 3:01 AM, Ramy Moustafa  wrote:
> 
> Hello Mr. Slau:
> COncerning the Target plugin:
> I do not want to see multible plugins opened at the same window or something, 
> all i need is an easy method for switching between them,so, if i have a 
> compressor opened, and i need to switch between it and an Eq for instance, 
> each time i should hit command ` to move between windows and go and open the 
> other one, etc, so is there an easy way for switching?
> 
> COncerning Automation:
> Thanks so much for your explnation, however, If you do not mind, i need more 
> explnation  or an audio demo please, because  can not do all you told me.
> Thanks so much for your help
> 
> Warm Regards,
> Dr/ Ramy Moustafa Saber
> Music Producer and Sound Engineer
> Music Instructor at: Faculty of Musical Education
> Helwan University
> 
> 
>  
> 
> 
>> On 7 Aug 2022, at 6:39 PM, Slau Halatyn  wrote:
>> 
>> Dear Doctor Ramy,
>> 
>> My responses interspersed below:
>> On Aug 7, 2022, at 11:25 AM, Ramy Moustafa > <mailto:ramy.moustaf...@gmail.com>> wrote:
>>> 
>>> Hello all:
>>> While taking a small mastering course, i am facing some problems related to 
>>> SOme plugins and VOice over, so I will write them here, and hope you can 
>>> help me fixing what am facing.
>>> 
>>> 1- how can we Read inside the VU Meeter? is there an accessible VU meeter 
>>> plugin?
>> VoiceOver only sees one value for metering. It cannot read VU specifically.
>> 
>>> 2- moving between Open plugins without opening 1 by 1 each time, I tried TO 
>>> press on Target plugin but with no help.
>> By default, only one plug-in window is open at a time. I wouldn't recommend 
>> using more than one plug-in window because you can't see more than one 
>> window at a time and, since you would need to bring up the window Chooser 
>> and make sure the window is the target, simply selecting from the track 
>> selector in one window is more straight-forward.
>> 
>>> 3- how can i write Volume Automation  by section using Keyboard not COntrol 
>>> surface? so i need to add 1 Db volume from bar 10 to bar 20, can i do this 
>>> using Just my keyboard or i should use COntrol surface etc?
>> This is a deceptively complex question because it depends on a number of 
>> factors. To offer an answer that'll work under all circumstances, Make your 
>> selection and enter Auto Latch Trim mode and change the volume fader to +1 
>> dB. Engage the transport and either let it play through the selection or use 
>> the Write To Selection button in the Automation window if it's a long 
>> section that you don't want to play all the way through.
>> 
>>> 4- When i need to load presets from the Ozone9, Pro tools always crash, but 
>>> when voice over is off, it works, is there a solution?
>> See if others can recreate the issue and, if so, open a support ticket with 
>> Izotope.
>> 
>>> 5- what is a good EQ that can do mid side technique? I tried the Ozone 9 
>>> EQ, and it crashes with VOice over.
>> See my response on WhatsApp.
>> 
>>> 
>>> Warm Regards,
>>> Dr/ Ramy Moustafa Saber
>>> Music Producer and Sound Engineer
>>> Music Instructor at: Faculty of Musical Education
>>> Helwan University
>>> 
>>> 
>>>  
>>> 
>>> 
>>> -- 
>>> 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/82D82B65-3265-49F7-A19D-D58CAC1BF5B4%40gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/ptaccess/82D82B65-3265-49F7-A19D-D58CAC1BF5B4%40gmail.com?utm_medium=email&utm_source=footer>.
>> 

Re: Some problems plz?

[Slau Halatyn]

Dear Doctor Ramy,

My responses interspersed below:
On Aug 7, 2022, at 11:25 AM, Ramy Moustafa  wrote:
> 
> Hello all:
> While taking a small mastering course, i am facing some problems related to 
> SOme plugins and VOice over, so I will write them here, and hope you can help 
> me fixing what am facing.
> 
> 1- how can we Read inside the VU Meeter? is there an accessible VU meeter 
> plugin?
VoiceOver only sees one value for metering. It cannot read VU specifically.

> 2- moving between Open plugins without opening 1 by 1 each time, I tried TO 
> press on Target plugin but with no help.
By default, only one plug-in window is open at a time. I wouldn't recommend 
using more than one plug-in window because you can't see more than one window 
at a time and, since you would need to bring up the window Chooser and make 
sure the window is the target, simply selecting from the track selector in one 
window is more straight-forward.

> 3- how can i write Volume Automation  by section using Keyboard not COntrol 
> surface? so i need to add 1 Db volume from bar 10 to bar 20, can i do this 
> using Just my keyboard or i should use COntrol surface etc?
This is a deceptively complex question because it depends on a number of 
factors. To offer an answer that'll work under all circumstances, Make your 
selection and enter Auto Latch Trim mode and change the volume fader to +1 dB. 
Engage the transport and either let it play through the selection or use the 
Write To Selection button in the Automation window if it's a long section that 
you don't want to play all the way through.

> 4- When i need to load presets from the Ozone9, Pro tools always crash, but 
> when voice over is off, it works, is there a solution?
See if others can recreate the issue and, if so, open a support ticket with 
Izotope.

> 5- what is a good EQ that can do mid side technique? I tried the Ozone 9 EQ, 
> and it crashes with VOice over.
See my response on WhatsApp.

> 
> Warm Regards,
> Dr/ Ramy Moustafa Saber
> Music Producer and Sound Engineer
> Music Instructor at: Faculty of Musical Education
> Helwan University
> 
> 
>  
> 
> 
> -- 
> 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/82D82B65-3265-49F7-A19D-D58CAC1BF5B4%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/401EC31D-9799-4599-94B5-92EDE1374B9F%40gmail.com.

Re: S1 and Dock

[Slau Halatyn]

Hi Wes,

The little plate that comes with the S1 will readily join another S1 alongside 
but, for the Dock, Avid recommends a slight modification to two of the rubber 
feet which involves slicing about an eighth of an inch or so off the tip of the 
domed rubber. Frankly, I don't think it's at all necessary to join an S1 and 
Dock. In fact, I find it useful to keep them apart. Anyway, to each, their own, 
I suppose.
best,
Slau


> On Jul 24, 2022, at 8:38 PM, Wes Smith  wrote:
> 
> Hi.  I'm trying to get into audio mixing/engineering as a career, so I bought 
> the S1 and dock.  My question is how do I join the dock and S1 together with 
> the plate?  I know there are some magnets that came with the S1, but from wha 
> understand they are not needed.  I hope not anyway, because they accidently 
> got magnitized together and I can't get them apart LOL.  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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/9d735443-005e-42b3-9678-c98e0b3e0140n%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/D4BD8F1A-43C9-4088-87D9-BDD9FABC80A2%40gmail.com.

Re: Now that i've upgraded to the most recent versions of Pro tools and keyboard maestro, where would i find the latest version of flo tools?

[Slau Halatyn]

Hi David,

The latest version of Flo Tools can always be found at
http://www.flotools.org 
Komplete Kontrol does not require Keyboard Maestro although the macros I 
created for it do use Keyboard Maestro. All the info is in the Read Me which 
accompanies each set of macros.

HTH,
Slau



> On Jul 21, 2022, at 10:07 PM, David Ingram  wrote:
> 
> Hi  Slau, I’d like to know where can i find the latest version of  flo tools? 
>  I  ask this question because  i have the latest versions of  Pro Tools  and 
> keyboard Maestro.  I  also have a question concerning komplete kontrol and 
> keyboard maestro.  What  i’d like to know is there any difference between 
> commands for kompletekontroll using keyboard maestro.  I’m sorry for not 
> spelling your  name correctly.  I want  to thank you for the information that 
> you have provided.

-- 
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/4EF9C720-3EC0-454B-AE62-5CEDF4E5B53B%40gmail.com.

Re: I've upgraded to the most recent versions of Pro Tools and keyboard maestro, is the preflight check list the same?

[Slau Halatyn]

So, first of all, FYI, my name is spelled S l a u and I've inserted responses 
below.
On Jul 21, 2022, at 11:13 AM, David Ingram  wrote:
> 
> Hi Slaugh I’d like to know if the preflight check list is the same since i’ve 
> upgraded to the most recent version of pro tools and keyboard maestro?

Same principles apply. The guide cannot be specific for every combination of 
Pro Tools and MacOS but the basic controls are still the same.

>  I’d like to know if the preflight  check list for  Pro Tools is still going 
> to work the same even though the version of Pro tools is different, also what 
> about keyboard maestro, are there new commands or ways to use keyboard 
> maestro to work with komplete.

Keyboard Maestro is the same and there are no differences as it pertains to Flo 
Tools. I'm not sure what you are referring to specifically regarding Komplete 
Kontrol.

>  I just thaught that i would ask these questions,  Also concerning the pro 
> tools  tutorials i’d like to put them on my external drive, how would i do 
> that if i may ask.  Thank you for any information that you  might have 
> concerning these questions.
The guide is both text and audio and most easily absorbed online. If you want 
to have a local copy of the audio demonstrations, you can right-click the play 
button and download an mp3 for each demonstration.

-- 
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/078755AE-76E1-4D07-9D11-FEFC443DB290%40gmail.com.

Re: Have been away for a long time

[Slau Halatyn]

As it regards Pro Tools, you can start by visiting:
https://ptaccess.github.io 
Cheers,
slau


> On Jul 16, 2022, at 4:19 PM, Aaron Linson  wrote:
> 
> Hi all,
> So a bit of back story. I have my B.S. in music with a concentration in audio 
> production and a minor in communications from IU SouthEast graduating in 
> 2017. During that time I had limited vision able to use magnification to 
> manuver around PT itself. I tried running VO but found that PT overtook the 
> audio and didn't touch it after. Now, I've completely lost all of the vision 
> out of my only eye. I want to get back into audio production and recording. I 
> have no idea how one is supposed to do that or how it's done while listening 
> to a screen reader. 
> 
> I don't mind purchasing equipment and PT. I've tried Reaper on a windows 
> machine but find it hard to understand. I'd only record one instrument at a 
> time. Just need resources on where to start. I'm thinking of getting a 
> macbook air to start. I have mics would just need a interface and a control 
> surface. I'd like to make a living at this again. I've an idea of editing 
> podcasts as a career. Right now I'm a recruiter for AWS. 
> 
> Thanks for any help anyone can provide. 
> God bless,
> Aaron L
> 
> -- 
> 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/19929a63-62b7-4a62-89a5-b3d6a4c2635bn%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/374D1447-BEA2-47FB-843E-4BA4D3CA62EE%40gmail.com.

Pro Tools 2022.6 is out

[Slau Halatyn]

To learn what's new in Pro Tools 2022.6 from an accessibility perspective, 
check out the new Chapter 22 in the Pro Tools Guide for screen reader Users 
.

Best,
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/FEB5D6FF-A9B6-4ECE-9E75-256AFD926120%40gmail.com.

Re: Looking for some presets, if they exist

[Slau Halatyn]

Let's keep the discussion on the public list rather than replying privately.
Guitar rig 6 has sets of internal presets for, say, amp model versus cabinet 
versus effect rack. So, one could choose a preset for effects and choose an amp 
preset to try those effects through a particular amp model, etc. So it's not 
just a single preset for the entire chain.

> On Jun 26, 2022, at 12:12 PM, Christopher Gilland  
> wrote:
> 
> What do you mean by modular? I've not heard that term used in this context.
> 
> 
> Chris.
> 
> On 6/26/2022 10:26 AM, Slau Halatyn wrote:
>> Guitar Rig 6 is a different animal from version 5 so the older presets will 
>> not work at all. Further, it's modular so creating PT presets will be a 
>> monumental task if one wanted to be thorough. Whereas version 5 had some 500 
>> presets, the modular nature of version 6 means that there would need to be 
>> thousands of presets to cover various combinations.
>> 
>> 
>>> On Jun 26, 2022, at 8:22 AM, Christopher Gilland  
>>> wrote:
>>> 
>>> I looked in the PTAccess dropbox, but all I'm finding are presets for 
>>> Guitar Rig 5, not for 6.
>>> 
>>> 
>>> I'm curious though not in the Dropbox, if anyone by chance may have any 6 
>>> presets, even if all be it, not a huge amount of them, I'll gladly take 
>>> what I can get. Unfortunately, some plugins, as long as you get the folder 
>>> name exactly down to the character correct, you can sometimes trick 
>>> ProTools into still loading things and working. A good example of this is 
>>> the Click presets in the Dropbox. If you just copy those directly over to 
>>> your plugin Settings area, it's not gonna work. But, if you rename that 
>>> folder to Click 2, or whatever the exact name is of that plugin, you can 
>>> trick PT into exposing the presets and making it work. As I said, 
>>> unfortunately, that doesn't seem to work here though for GR6, which kind of 
>>> makes sense actually, as the UI is probably different enough that it 
>>> wouldn't work. I don't even see them let alone not being able to load them 
>>> once shown. So yeah, there went that idea. LOL! Ruh, row'w.. Whoops?
>>> 
>>> 
>>> 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/9d222858-948b-c911-5819-d959431a05d5%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/DC975197-8CBC-41E9-936B-67464EB7E5E8%40gmail.com.

Re: Looking for some presets, if they exist

[Slau Halatyn]

Guitar Rig 6 is a different animal from version 5 so the older presets will not 
work at all. Further, it's modular so creating PT presets will be a monumental 
task if one wanted to be thorough. Whereas version 5 had some 500 presets, the 
modular nature of version 6 means that there would need to be thousands of 
presets to cover various combinations.


> On Jun 26, 2022, at 8:22 AM, Christopher Gilland  
> wrote:
> 
> I looked in the PTAccess dropbox, but all I'm finding are presets for Guitar 
> Rig 5, not for 6.
> 
> 
> I'm curious though not in the Dropbox, if anyone by chance may have any 6 
> presets, even if all be it, not a huge amount of them, I'll gladly take what 
> I can get. Unfortunately, some plugins, as long as you get the folder name 
> exactly down to the character correct, you can sometimes trick ProTools into 
> still loading things and working. A good example of this is the Click presets 
> in the Dropbox. If you just copy those directly over to your plugin Settings 
> area, it's not gonna work. But, if you rename that folder to Click 2, or 
> whatever the exact name is of that plugin, you can trick PT into exposing the 
> presets and making it work. As I said, unfortunately, that doesn't seem to 
> work here though for GR6, which kind of makes sense actually, as the UI is 
> probably different enough that it wouldn't work. I don't even see them let 
> alone not being able to load them once shown. So yeah, there went that idea. 
> LOL! Ruh, row'w.. Whoops?
> 
> 
> 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/9d222858-948b-c911-5819-d959431a05d5%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/612FDA1C-6C9A-446F-A42D-19851C260AD2%40gmail.com.

Re: New email.

[Slau Halatyn]

Link to the guide is:
https://ptaccess.github.io
To use your new email, send a blank message from that account to 
ptaccess+subscr...@googlegroups.com 
To unsubscribe your old address, send a blank message from that account to:
ptaccess+unsubscr...@googlegroups.com 


HTH,
Slau

> On Jun 18, 2022, at 12:08 AM, Kurt Lantz  wrote:
> 
> Hello Slau. I have a new email and it is sonicgr...@gmail.com, could you 
> please use it instead of blindm...@gmail.com on the pt access google groups 
> email list. Also could you please send me the lick to the new pro Tools 
> comprehensive guide for screen readers, I can;t seem to google it. Thank you 
> very much.
> 
> -- 
> 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/BC180CF5-9268-4BD2-B4A5-A2161BED8116%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/1D22C4C2-B352-47E9-80B5-F8896408437B%40gmail.com.

Re: Don't shoot the messenger! Pweez? Houston, we've gotta small problem with bouncing.

[Slau Halatyn]

Yes, normally this wouldn't be required but, if one is having trouble, it's a 
workaround.

> On Jun 15, 2022, at 8:19 PM, John Covici  wrote:
> 
> But if you do that, won't the bounce take as long as the original
> program?
> 
> On Wed, 15 Jun 2022 16:34:04 -0400,
> Slau Halatyn wrote:
>> 
>> Track Bounce with the Offline checkbox unchecked will render everything 
>> fine. If the "Import After Bounce" checkbox in the Location area is checked, 
>> it'll come right back into the session. I did have this issue a couple of 
>> times but haven't seen it in a while.
>> 
>> 
>> 
>>> On Jun 15, 2022, at 1:11 AM, Rocco Fiorentino 
>>>  wrote:
>>> 
>>> I’ve also had this happen to me, specifically with pianos. I’m guessing it 
>>> also happens if you try to freeze that piano track or commit it too? And it 
>>> never happens if bouncing, freezing or committing are done online, right?
>>> I’ve had this issue and haven’t found a fix for it yet, incredibly 
>>> annoying. I think Slau may have had this too at one point, so curious to 
>>> see what others have done for this.
>>> 
>>> Best,
>>> 
>>> Rocco
>>> 
>>> 
>>>> On Jun 14, 2022, at 10:16 PM, Christopher Gilland  
>>>> wrote:
>>>> 
>>>> So, I've got 2 instrument tracks. One is Alecia's Keys through my Komplete 
>>>> Kontrol with the close auditorium preset I think it's called? It's 
>>>> literally like the 2nd or 3rd preset from the top, if that helps.
>>>> 
>>>> 
>>>> Then, I've got Embertone's Joshua Bell Violin on the 2nd track also with 
>>>> Komplete Kontrol. When I play in PT itself, things sounds fine. Even with 
>>>> a 2TB solid state drive, if I bounce, things are 99.9 percent there, 
>>>> but with an offline bounce, the piano arpegios I'm doing seem to be ever 
>>>> so slightly chopping off. It's not as bad as when I had my 7200RPM drive 
>>>> by far! It's way way way better than that, but it is noticeable. I tried 
>>>> changing the piano to the American Concert D through Ivory, and also had 
>>>> this issue. I even tried with the free Kawaii X Player library, and had 
>>>> it. Hammersmith Free is doing it too. The violin seems to be fine, but 
>>>> yeah, the piano is not for some reason. The odd thing is, now after moving 
>>>> things to that SSD, in Logic, it's not giving me this issue, nor is it in 
>>>> Reaper. It's only happening in PT. So, yes, I did read the guide, and go 
>>>> through the included audio. I may have missed something, as there was a 
>>>> boatload of material covered, and I'll definitely go back and review 
>>>> bouncing audio, but is there something in the bounce dialog pertaining to 
>>>> making sure it doesn't cut off tails from my audio?
>>>> 
>>>> 
>>>> Oddly, if I end with a sustained arpegio chord, even that's cutting off 
>>>> prematurely, and not fully ringing through. Yeah, both tracks are selected 
>>>> in the track list table prior to bouncing, and yes, I did make sure 
>>>> everything was selected from beginning to end. I remember having this 
>>>> issue when using PT back in the days. I just don't recall what I did to 
>>>> fix it.
>>>> 
>>>> 
>>>> 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/b29c9c1c-d4c4-4860-f7cf-3c5177694d19%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/1E2AD8AD-C1EC-4041-BA9C-7C47DDDB4578%40gmail.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" grou

Re: Don't shoot the messenger! Pweez? Houston, we've gotta small problem with bouncing.

[Slau Halatyn]

Track Bounce with the Offline checkbox unchecked will render everything fine. 
If the "Import After Bounce" checkbox in the Location area is checked, it'll 
come right back into the session. I did have this issue a couple of times but 
haven't seen it in a while.



> On Jun 15, 2022, at 1:11 AM, Rocco Fiorentino  
> wrote:
> 
> I’ve also had this happen to me, specifically with pianos. I’m guessing it 
> also happens if you try to freeze that piano track or commit it too? And it 
> never happens if bouncing, freezing or committing are done online, right?
> I’ve had this issue and haven’t found a fix for it yet, incredibly annoying. 
> I think Slau may have had this too at one point, so curious to see what 
> others have done for this.
> 
> Best,
> 
> Rocco
> 
> 
>> On Jun 14, 2022, at 10:16 PM, Christopher Gilland  
>> wrote:
>> 
>> So, I've got 2 instrument tracks. One is Alecia's Keys through my Komplete 
>> Kontrol with the close auditorium preset I think it's called? It's literally 
>> like the 2nd or 3rd preset from the top, if that helps.
>> 
>> 
>> Then, I've got Embertone's Joshua Bell Violin on the 2nd track also with 
>> Komplete Kontrol. When I play in PT itself, things sounds fine. Even with a 
>> 2TB solid state drive, if I bounce, things are 99.9 percent there, but 
>> with an offline bounce, the piano arpegios I'm doing seem to be ever so 
>> slightly chopping off. It's not as bad as when I had my 7200RPM drive by 
>> far! It's way way way better than that, but it is noticeable. I tried 
>> changing the piano to the American Concert D through Ivory, and also had 
>> this issue. I even tried with the free Kawaii X Player library, and had it. 
>> Hammersmith Free is doing it too. The violin seems to be fine, but yeah, the 
>> piano is not for some reason. The odd thing is, now after moving things to 
>> that SSD, in Logic, it's not giving me this issue, nor is it in Reaper. It's 
>> only happening in PT. So, yes, I did read the guide, and go through the 
>> included audio. I may have missed something, as there was a boatload of 
>> material covered, and I'll definitely go back and review bouncing audio, but 
>> is there something in the bounce dialog pertaining to making sure it doesn't 
>> cut off tails from my audio?
>> 
>> 
>> Oddly, if I end with a sustained arpegio chord, even that's cutting off 
>> prematurely, and not fully ringing through. Yeah, both tracks are selected 
>> in the track list table prior to bouncing, and yes, I did make sure 
>> everything was selected from beginning to end. I remember having this issue 
>> when using PT back in the days. I just don't recall what I did to fix it.
>> 
>> 
>> 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/b29c9c1c-d4c4-4860-f7cf-3c5177694d19%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/1E2AD8AD-C1EC-4041-BA9C-7C47DDDB4578%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/470EF1B6-EED4-4720-A4DA-87CE1D2F4570%40gmail.com.

Re: Is there enough USB power to do this?

[Slau Halatyn]

If it's an Apple keyboard, it's USB 2 and you can plug your iLok key into it.

> On Jun 14, 2022, at 9:42 PM, Christopher Gilland  
> wrote:
> 
> So guys,
> 
> 
> I have one of those white full sized wired USB aluminum Apple keyboards that 
> have the 2 USB ports on them. My thing is, I think, though don't quote me, 
> those ports only support USB 1.0. they might be 2.0 ports, but somehow, I 
> tend to doubt it.. I know they're extremely extremely low powered.
> 
> 
> My question is, could I probably get enough power off one of those things to 
> effectively run my iLok through one of them instead of plugging it to my 7 
> port USB hub? I'm running out of USB ports very rapidly, so figured if I 
> could take it off the hub to save a port there, it would be incredibly 
> helpful.
> 
> 
> 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/fe7cdead-1621-84b4-ecf5-8d1ab05754e8%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/568E474C-9658-4B5F-AEF3-1CFE52102D3B%40gmail.com.

Re: free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

It was a tremendous amount of work. The more you dive in, the more it will have 
had been worth the effort :)


> On Jun 13, 2022, at 1:18 PM, Vaughn Brown  wrote:
> 
> This is incredible! Thank you to everyone who worked on this time consuming 
> project. It is very much appreciated.
> 
>> On Jun 9, 2022, at 9:20 PM, Slau Halatyn > <mailto:slauhala...@gmail.com>> wrote:
>> 
>> The long-awaited  "Pro Tools Guide for screen Reader Users" is finally here! 
>> This free online resource, made possible through Berklee College of Music 
>> features a comprehensive series of tutorials aimed specifically at blind 
>> users of Pro Tools. It includes 250 audio demonstrations (totaling 20 hours) 
>> with detailed examples to accompany each topic. All of the session files 
>> used throughout this series are available too download for reference and 
>> practice.
>> 
>> Whether you're completely new to Pro Tools or already use it and want to 
>> fill in the gaps, start your journey by going to:
>> https://ptaccess.github.io <https://ptaccess.github.io/>
>> 
>> As the process of refining Pro Tools accessibility is ongoing, this online 
>> guide will continue to be updated regularly to reflect the most recent 
>> improvements to the Pro Tools user interface from the perspective of a 
>> screen reader user.
>> 
>> Thanks to Chi Kim for facilitating this project and to Berklee for 
>> entrusting me with this massive undertaking. I couldn't have done it without 
>> their support. Thanks also to Avid for making resources available during the 
>> planning, writing and recording of this project.
>> 
>> Slau Halatyn
>> 
>> 
>> 
>> -- 
>> 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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com?utm_medium=email&utm_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/810C0E4E-4590-45B3-A665-A7142A9D0234%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/810C0E4E-4590-45B3-A665-A7142A9D0234%40gmail.com?utm_medium=email&utm_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/90E83C03-134F-4C26-BE99-695C4DB38865%40gmail.com.

Re: free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

I hope it helps. Regardless of what support and documentation there is for any 
given DAW, it boils down to what one feels comfortable with. Pro Tools is not 
for everyone just as Logic and reaper are not for everyone. My hope is that 
this will help those who want but especially need to use Pro Tools. either way, 
I'm glad it's finally here.
Best,
slau


> On Jun 11, 2022, at 9:19 AM, Ronald van Rhijn  wrote:
> 
> Wow, many thanks Slau! Fantastic work. I will give Pro Tools one last attempt 
> to master it with this tutorial.
> 
> best, 
> Ronald
> 
> 
> 
> 
> 
>> Op 10 jun. 2022, om 06:20 heeft Slau Halatyn > <mailto:slauhala...@gmail.com>> het volgende geschreven:
>> 
>> The long-awaited  "Pro Tools Guide for screen Reader Users" is finally here! 
>> This free online resource, made possible through Berklee College of Music 
>> features a comprehensive series of tutorials aimed specifically at blind 
>> users of Pro Tools. It includes 250 audio demonstrations (totaling 20 hours) 
>> with detailed examples to accompany each topic. All of the session files 
>> used throughout this series are available to download for reference and 
>> practice.
>> 
>> Whether you're completely new to Pro Tools or already use it and want to 
>> fill in the gaps, start your journey by going to:
>> https://ptaccess.github.io <https://ptaccess.github.io/>
>> 
>> As the process of refining Pro Tools accessibility is ongoing, this online 
>> guide will continue to be updated regularly to reflect the most recent 
>> improvements to the Pro Tools user interface from the perspective of a 
>> screen reader user.
>> 
>> Thanks to Chi Kim for facilitating this project and to Berklee for 
>> entrusting me with this massive undertaking. I couldn't have done it without 
>> their support. Thanks also to Avid for making resources available during the 
>> planning, writing and recording of this project.
>> 
>> Slau Halatyn
>> 
>> 
>> 
>> -- 
>> 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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com?utm_medium=email&utm_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/79B20689-1081-4C96-9A4F-17E1F88B92C9%40xs4all.nl
>  
> <https://groups.google.com/d/msgid/ptaccess/79B20689-1081-4C96-9A4F-17E1F88B92C9%40xs4all.nl?utm_medium=email&utm_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/B87E1F09-123E-44F7-A13B-7F4AC5463571%40gmail.com.

Re: And the weirdness just continues! What on earth is this window?

[Slau Halatyn]

That's the Transport window. Double-tap VO+F2 to have the VoiceOver Window 
Chooser come up in a list and you can see what windows are present. Command+1 
on the numeric keypad will open and close the Transport window.

> On Jun 10, 2022, at 9:49 PM, Christopher Gilland  
> wrote:
> 
> So, if I go to the dashboard with command+n, then command+1 to the create 
> tab, and make a new session not based off a template, I obviously get thrown 
> in the session with no tracks.
> 
> 
> Now, I create either an audio or instrument track. After I do so, rather than 
> being placed in the edit window or the mix window, preferably the ladder, I'm 
> taken to this weird screen I've never seen before where it says transport 
> cluster. If I then VO+Right arrow once, I get to transport options button. 
> That's literally speaking all on the whole entire screen. Literally! aside 
> the close, zoom and minimize buttons, that's literally speaking all that's 
> there. What's strange about this is, if I then hit command+equals, it takes 
> me to the edit window, which by the way looks just fine, and if I then hit 
> command+equals again, I'm at the mix window, then I see the track strip, the 
> track list table, and everything as I should. It's just right after I first 
> create a new track and get that very first track in the session that I see 
> this weirdness. What in the hell did I do! This is just nuts crazy!! I can't 
> remember earlier today if when I first installed PT it did this or not. I'm 
> suspicious that something I did in the edit window under the toolbar options 
> may a caused this, as I was trying to get those things according to the 
> Preflight chapter configured, but since I'm not able to see what's selected 
> and what isn't... Voiceover isn't telling me, it's really really hard for me 
> to say for sure what I've done, or even it that is rellavent.
> 
> 
> 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/f74ac565-4a85-c179-6d1c-f278ffc4f578%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/B26057CA-CFFB-4EFD-8552-D2D73F399F94%40gmail.com.

Re: free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

Chapter 1 offers the Pre-Flight Checklist which doesn't require a 
demonstration. If people can't follow those instructions without an audio 
demonstration, I'm afraid they probably couldn't handle working with Pro Tools. 
I suppose it's sort of a litmus test :)
Mic was a Neumann U 47 into Millennia HV3D. I have 2 different Pro Tools 
systems and simply piped VoiceOver into another PT system along with vocal and 
the interface connected to the laptop. 


> On Jun 10, 2022, at 5:41 PM, Nick Gawronski  wrote:
> 
> Hi, I like these wonderful tutorials a lot.  One demo that I think is missing 
> is the demo on how to change the different mac and Pro Tools settings as all 
> of mine are correct but havving audio demos would be helpful for some users.  
> I like the quality of the audio content so was just wondering what audio 
> equipment and microphones did you use to record these and how did you go 
> about getting the voice over speech into the tutorials?  Nick Gawronski
> On 6/10/2022 3:21 PM, Juan Pablo Culasso Alonso wrote:
>> Slau, this guide is so beautiful.
>> Thank you so much.
>> Question, are you planing to make some apendix highlighting the advance 
>> automation and edit that protools ultimate has now eve protools studio has?
>> Thanks,
>> Juan
>> 
>>> On Jun 9, 2022, at 23:20, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> The long-awaited  "Pro Tools Guide for screen Reader Users" is finally 
>>> here! This free online resource, made possible through Berklee College of 
>>> Music features a comprehensive series of tutorials aimed specifically at 
>>> blind users of Pro Tools. It includes 250 audio demonstrations (totaling 20 
>>> hours) with detailed examples to accompany each topic. All of the session 
>>> files used throughout this series are available to download for reference 
>>> and practice.
>>> 
>>> Whether you're completely new to Pro Tools or already use it and want to 
>>> fill in the gaps, start your journey by going to:
>>> https://ptaccess.github.io <https://ptaccess.github.io/>
>>> 
>>> As the process of refining Pro Tools accessibility is ongoing, this online 
>>> guide will continue to be updated regularly to reflect the most recent 
>>> improvements to the Pro Tools user interface from the perspective of a 
>>> screen reader user.
>>> 
>>> Thanks to Chi Kim for facilitating this project and to Berklee for 
>>> entrusting me with this massive undertaking. I couldn't have done it 
>>> without their support. Thanks also to Avid for making resources available 
>>> during the planning, writing and recording of this project.
>>> 
>>> Slau Halatyn
>>> 
>>> 
>>> 
>>> -- 
>>> 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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/ptaccess/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com?utm_medium=email&utm_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/993FFCB5-D796-404E-810D-A623A8CC1305%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/993FFCB5-D796-404E-810D-A623A8CC1305%40gmail.com?utm_medium=email&utm_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/9475ade9-cace-80c2-e40c-16861f040fc9%40nickgawronski.com
>  
> <https://groups.google.com/d/msgid/ptaccess/9475ade9-cace-80c2-e40c-16861f040fc9%40nickgawronski.com?utm_medium=email&utm_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/711515FB-69E0-4FF9-8C54-DF971D58DE54%40gmail.com.

Re: free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

For the most part, I did add that stuff in Chapter 19 where I cover Manual 
Write, Write On stop and the various Write, Trim and Glide to Current commands. 
Cheers!

> On Jun 10, 2022, at 4:21 PM, Juan Pablo Culasso Alonso  
> wrote:
> 
> Slau, this guide is so beautiful.
> Thank you so much.
> Question, are you planing to make some apendix highlighting the advance 
> automation and edit that protools ultimate has now eve protools studio has?
> Thanks,
> Juan
> 
>> On Jun 9, 2022, at 23:20, Slau Halatyn > <mailto:slauhala...@gmail.com>> wrote:
>> 
>> The long-awaited  "Pro Tools Guide for screen Reader Users" is finally here! 
>> This free online resource, made possible through Berklee College of Music 
>> features a comprehensive series of tutorials aimed specifically at blind 
>> users of Pro Tools. It includes 250 audio demonstrations (totaling 20 hours) 
>> with detailed examples to accompany each topic. All of the session files 
>> used throughout this series are available to download for reference and 
>> practice.
>> 
>> Whether you're completely new to Pro Tools or already use it and want to 
>> fill in the gaps, start your journey by going to:
>> https://ptaccess.github.io <https://ptaccess.github.io/>
>> 
>> As the process of refining Pro Tools accessibility is ongoing, this online 
>> guide will continue to be updated regularly to reflect the most recent 
>> improvements to the Pro Tools user interface from the perspective of a 
>> screen reader user.
>> 
>> Thanks to Chi Kim for facilitating this project and to Berklee for 
>> entrusting me with this massive undertaking. I couldn't have done it without 
>> their support. Thanks also to Avid for making resources available during the 
>> planning, writing and recording of this project.
>> 
>> Slau Halatyn
>> 
>> 
>> 
>> -- 
>> 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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com?utm_medium=email&utm_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/993FFCB5-D796-404E-810D-A623A8CC1305%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/993FFCB5-D796-404E-810D-A623A8CC1305%40gmail.com?utm_medium=email&utm_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/66906CC3-8F1C-4AE0-821F-FC9D8DC8101B%40gmail.com.

Re: Downloading supplimental sessions

[Slau Halatyn]

It's right in the Introduction toward the end of the page.

> On Jun 10, 2022, at 4:08 PM, Christopher Gilland  
> wrote:
> 
> Where do I go to download the sessions that are often mentioned within the PT 
> Access online guide? Each chapter doesn't seem to have links to them. I 
> definitely see that I have to listen to the accompanying audio from the 
> website, which is fine, but it keeps saying refer to the xxx.ptx session 
> file. I just don't know where to get it though. For example, in chapter 3, it 
> talks about the edit modes session.
> 
> 
> 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/20a58b2e-5a39-551b-33b0-3ccf41799594%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/C28573F5-B7EB-488C-A103-AD6CC99A764A%40gmail.com.

Re: Numeric keypad absolutely 100 percent required?

[Slau Halatyn]

You can create a marker by pressing FN+Return which emulates the Enter key.

> On Jun 10, 2022, at 9:34 AM, Dammie Onafeko  wrote:
> 
> Hey Chris! It’s possible to use ProTools without a num pad keyboard. You just 
> won’t be able to do some things like creating a marker. If you can devise 
> other ways of getting to a point in the session or fast forwarding without 
> relying on using number 2 on num pad keyboard, it is doable with your laptop 
> keyboard. 
> 
> Best,
> 
> Dammie
> 
> On Fri, Jun 10, 2022 at 8:44 AM Christopher Gilland  > wrote:
> I absolutely understand completely that my experience would be way way 
> better with a full sized keyboard using a numpad, and that this would be 
> hugely hugely preferred and advised. So let me get that out of the way.
> 
> 
> That said however, is it even remotely possible to navigate and 
> effectively use ProTools without a numpad? I know I'd have to learn the 
> commands, and that they'd be a bit different, and I know about flo 
> numpad, although I really would rather just use native commands if 
> possible, but I'm just curious how many things already are mapped to 
> things on my regular keyboard? Right now, I'm not in a position due to 
> living arrangements where I easily can hook up a full sized keyboard. 
> That may change, but for the time being, I don't have an easy way to do it.
> 
> 
> This is literally speaking the only thing holding me back right now from 
> trying PT again. If you all can assure me that we can work around that, 
> all be it, maybe not the most efficiently, I get that, if we can do it 
> though, then I'll go ahead and call Sweetwater, and see what I can do to 
> reinstate my license. Otherwise, I may have to hold off, but yeah, this 
> is literally the only thing now holding me back.
> 
> 
> 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/023166cb-85a9-fe48-b517-bcae68057c21%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/CAN%3Dh5d8O2CLJSp%2BvCdCL1tJ8cQ%2B2UHB%3DOowfgZrUYKKArhSZig%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/B80DF484-D81F-4925-A431-9C2DBD43AD4E%40gmail.com.

Re: Back after a huge huge hiatus.

[Slau Halatyn]

This was launched literally this morning:

The  "Pro Tools Guide for screen Reader Users" is a free online resource made 
possible through the Berklee College of Music and features a comprehensive 
series of tutorials aimed specifically at blind users of Avid's Pro Tools 
digital audio workstation software. It includes 250 audio demonstrations 
(totaling 20 hours) with detailed examples to accompany each topic. All of the 
Pro Tools session files used throughout this series are available to download 
for reference and practice. As the process of refining Pro Tools accessibility 
is ongoing, this online guide will continue to be updated regularly to reflect 
the most recent improvements to the Pro Tools user interface from the 
perspective of a screen reader user. Whether you're new to Pro Tools or already 
use it with adaptive technology and want to expand your knowledge, start your 
journey by visiting:
https://ptaccess.github.io


> On Jun 10, 2022, at 8:37 AM, Christopher Gilland  
> wrote:
> 
> Hey guys, I'm sure a lot of you remember me, and if nothing else, probably 
> know me from the Komplete Kontrol Access list, and also the VO Logic users 
> group.
> 
> 
> I won't bore you all with much intro since most of you already do know me, 
> but I do wanna catch all of you, especially people like Kevin, Slau, and a 
> few others heavily in the PT ecosystem up with where I'm now at with things.
> 
> 
> So, it's kind of a long story, but the very condensed jist of it is, in 
> November of 2020, right after the pandemic hit, due to me being high risk as 
> far as health is concerned, I was made to stay at home and hardly at all get 
> out in public. Given that I wasn't working, this gave me a huge huge amount 
> of time on my hands to really take on learning more about audio production 
> than the time before I was able to commit.. I pretty well thought I knew what 
> I was doing when it came to audio mixing, editing, producing, etc, but boy 
> was I in for a rude awakening! I'm very humbly saying this.
> 
> 
> I decided, for some reason clear beyond me to give Reaper another try. I'd 
> struggled with it tremendously before, just getting all the ins and outs, no 
> pun intended, down pat. For whatever bizarre reason still to this day unknown 
> to me, this time, it clicked. Everything just totally fell into place and 
> made sense.
> 
> 
> The problem was, and I'll get to PT, I promise. Just stick with me... virtual 
> instruments. I had been using Xpand2 inside ProTools, along with Ivory, and 
> maybe a few more things. In Reaper, I didn't have native access, again, no 
> pun intended, to those luxuries, and therefore had to invest in something 
> else. I'd heard a lot of very good things about Native Instruments/Komplete 
> Kontrol, and so I went ahead and took the plunge and got an M32 controller 
> since I already had a full sized 88 key controller I could use for actually 
> playing. I also got a 2TB external hard drive, as I knew I'd probably need it 
> eventually.
> 
> 
> Now fast forward to April of 2021. At that time, I still had that same Mac  
> mini that Kevin Reeves tought me ProTools on back in 2012. That thing was 
> still chugalugging along. It however by then was very old. We're talking 8GB 
> ram, I5 mid 2012 and only running Mojave. I didn't even have Catalina on it, 
> as it ran too slow, barely ran Mojave efficiently. Plus, a lot of my virtual 
> instruments were bottle necking out tremendously!
> 
> 
> Given that I had gotten the full 1300 dollar stemulous check that month, I 
> put it forth to get an Orbit Reader 40, which wound up being an absolute 
> disaster, but I won't go there. The point is, I was refunded that full amount 
> from Orbit research. I then decided, you know, if I wanna get serious with 
> audio, that mac really! needs to be upgraded, case closed, what better time 
> to do it than now while I have the 1300 and can.
> 
> 
> So, I made the plunge, and got a rose gold 2020 M1 cilicon 13 inch macbook 
> air with 8GB ram, 512 internal SSD, and 8 core processor running, at that 
> time, Big Sur. We'll simply say, I will never! look back! This system is 
> incredible, and fast as a bullet!
> 
> 
> Once I got the new system, I decided to see if it would be a better 
> experience than before running Logic. Boy was it ever! It has now become for 
> the time being my primary DAW. So much so, I even stopped the monthly 
> payments to Avid for ProTools. I now strongly regret doing that, but I should 
> be able I hope to deal with that, and resubscribe to the monthly license.
> 
> 
> I have admittedly forgotten a lot about using ProTools, but I know that I'll 
> pick it back up incredibly quickly. I'm a very fast learner usually, and I'm 
> sure it'll come back to me once I get back into it. I'd really though like to 
> give it another try now that I have an up to date system.
> 
> 
> So yeah, that's where we're at, and I'm very happy to be back on the list, 
> and did miss all o

Re: free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

Hi Katie,

Indeed, accessibility on all fronts has come such a long way. I'm glad to 
finally be able to share it and will continue to contribute as things develop.

Best,
Slau


> On Jun 10, 2022, at 1:14 AM, Kathryn Zodrow  wrote:
> 
> Hi Slau. Thanks for the great news about this ProTools guide for screen 
> reader users. Wow, that is awesome! I didn’t know you and Berklee College of 
> Music had been working on this project for a long time. I’ll have to check it 
> out. :-) I know Berklee has come a long way with accessibility and assisting 
> blind students since I graduated in 2004. I’m very thankful I was one of the 
> blind students that encouraged them to start making things accessible for 
> them like music tech and braille music reading when I was there. I think I 
> had  used ProTools version 5  with Mac OS 9 with outSpoken back then, and 
> accessibility has expanded so much since that time.
> Katie
> 
> 
> Sent from my iPhone
> 
>> On Jun 9, 2022, at 9:21 PM, Slau Halatyn  wrote:
>> 
>> 
>> The long-awaited  "Pro Tools Guide for screen Reader Users" is finally here! 
>> This free online resource, made possible through Berklee College of Music 
>> features a comprehensive series of tutorials aimed specifically at blind 
>> users of Pro Tools. It includes 250 audio demonstrations (totaling 20 hours) 
>> with detailed examples to accompany each topic. All of the session files 
>> used throughout this series are available to download for reference and 
>> practice.
>> 
>> Whether you're completely new to Pro Tools or already use it and want to 
>> fill in the gaps, start your journey by going to:
>> https://ptaccess.github.io <https://ptaccess.github.io/>
>> 
>> As the process of refining Pro Tools accessibility is ongoing, this online 
>> guide will continue to be updated regularly to reflect the most recent 
>> improvements to the Pro Tools user interface from the perspective of a 
>> screen reader user.
>> 
>> Thanks to Chi Kim for facilitating this project and to Berklee for 
>> entrusting me with this massive undertaking. I couldn't have done it without 
>> their support. Thanks also to Avid for making resources available during the 
>> planning, writing and recording of this project.
>> 
>> Slau Halatyn
>> 
>> 
>> 
>> -- 
>> 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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com?utm_medium=email&utm_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/F2C9634D-9DC6-4303-BB0A-419632742149%40att.net
>  
> <https://groups.google.com/d/msgid/ptaccess/F2C9634D-9DC6-4303-BB0A-419632742149%40att.net?utm_medium=email&utm_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/7C4DDB02-798D-47A2-A2C6-CE4FEE215C23%40gmail.com.

free comprehensive Pro Tools Guide for Screen Reader Users now available online

[Slau Halatyn]

The long-awaited  "Pro Tools Guide for screen Reader Users" is finally here! 
This free online resource, made possible through Berklee College of Music 
features a comprehensive series of tutorials aimed specifically at blind users 
of Pro Tools. It includes 250 audio demonstrations (totaling 20 hours) with 
detailed examples to accompany each topic. All of the session files used 
throughout this series are available to download for reference and practice.

Whether you're completely new to Pro Tools or already use it and want to fill 
in the gaps, start your journey by going to:
https://ptaccess.github.io <https://ptaccess.github.io/>

As the process of refining Pro Tools accessibility is ongoing, this online 
guide will continue to be updated regularly to reflect the most recent 
improvements to the Pro Tools user interface from the perspective of a screen 
reader user.

Thanks to Chi Kim for facilitating this project and to Berklee for entrusting 
me with this massive undertaking. I couldn't have done it without their 
support. Thanks also to Avid for making resources available during the 
planning, writing and recording of this project.

Slau Halatyn


-- 
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/AAA10C90-7B37-4B37-BD6B-3EE9E71DC2D1%40gmail.com.

Re: I'd like to get access to the ptaccess dropbox!

[Slau Halatyn]

You already have access. Go to DropBox.com , log in and 
add the folder to your account.

> On Jun 6, 2022, at 5:45 AM, David Ingram  wrote:
> 
> Hi list members, I’d like to be  able to get  to the ptaccess dropbox folder. 
>  In asking this question, do i  also have to have a 16tb available to look 
> through the  ptaccess dropbox folder?  Thank you for any information that you 
> might have  concerning these questions.
> 
> -- 
> 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/D0DA72B5-27CC-4AAA-A5D7-D491F2D35B68%40earthlink.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/DCEC9E61-90FF-4B1E-8810-2C44F7045C7F%40gmail.com.

Re: Unable to click the apply button when setting a linear tempo curve

[Slau Halatyn]

Yes, Conductor needs to be enabled if you're doing tempo changes. It doesn't 
need to be active for static tempos but does need to be active for dynamic 
tempo changes. I see now that Martin had replied to that effect.

> On May 27, 2022, at 3:58 PM, Alex Coleman  
> wrote:
> 
> Thanks for the suggestions. I did try the enter/return keys on the
> main keyboard as well as the numberic keypad, but no luck.
> However I did have the Conductor track unchecked.
> I'll try to select that option and see if I'm able to apply the parameters 
> then.
> Thanks again.
> 
> 
> On 5/27/22, Slau Halatyn  wrote:
>> After entering a value, did you press the enter button?
>> 
>>> On May 26, 2022, at 4:10 PM, Alex Coleman 
>>> wrote:
>>> 
>>> I’ve got a project with seven instrument tracks, and 123 bars of midi
>>> data. I would like to set the overall tempo to 145 BPM, which I have done,
>>> but then I want to insert a  linear tempo change from measure 22 to 24.
>>> However, when I set all of the parameters in the tempo operations window,
>>> the apply button is grayed out. I have tried everything I know to make it
>>> work, but it remains grayed out.
>>> Does anyone have any ideas as to what I am doing wrong, or what I need to
>>> do to get it to work?
>>> Thanks for your assistance.
>>> 
>>> 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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ptaccess/795429AB-DD31-41EB-8193-553E5EB926D3%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/301441A6-842A-47AA-BFD1-EE4C789FC749%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/CAKVN6vNW2mCyD-n2619sUp4-W-1ZTFrEq%2BizME5Qwd%3DG2V5F9g%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/B502B556-CEEF-4F6F-B349-AC198D80282F%40gmail.com.

Re: Unable to click the apply button when setting a linear tempo curve

[Slau Halatyn]

After entering a value, did you press the enter button?

> On May 26, 2022, at 4:10 PM, Alex Coleman  
> wrote:
> 
> I’ve got a project with seven instrument tracks, and 123 bars of midi data. I 
> would like to set the overall tempo to 145 BPM, which I have done, but then I 
> want to insert a  linear tempo change from measure 22 to 24. However, when I 
> set all of the parameters in the tempo operations window, the apply button is 
> grayed out. I have tried everything I know to make it work, but it remains 
> grayed out. 
> Does anyone have any ideas as to what I am doing wrong, or what I need to do 
> to get it to work?
> Thanks for your assistance.
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/795429AB-DD31-41EB-8193-553E5EB926D3%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/301441A6-842A-47AA-BFD1-EE4C789FC749%40gmail.com.

Re: problem with voiceover speaking less

[Slau Halatyn]

There was a bug that creeped in toward the end of the most recent beta cycle that flew under the radar. For the time being, you can import the following macros that will fix the issue:



-- 
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/5D1FDB02-BA2E-4EB0-BBBA-B3673C1D9CD2%40gmail.com.


Speech output fix 2022-05-03.kmmacros
Description: Binary data
From within KM, choose "Import Macros Safely," hold down the Option key and the menu choice will change to just say "Import Macros." While holding down Option, press return and navigate to the above macro file and import.HTH,SlauOn May 22, 2022, at 8:46 AM, Tom Hessels  wrote:Hi All, I just installed latest pro tools and flo tools and every thing works.But there is one thing I don’t understand.Before opdating vo gave me mor inf o.E.g. when I press control z I  get some feedback and when I type in measures I also don’t hear anything.How can I solve this? Tom. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group.To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/ptaccess/000b01d86dd9%24ff92ef20%24feb8cd60%24%40tomhessels.nl.



-- 
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/5D1FDB02-BA2E-4EB0-BBBA-B3673C1D9CD2%40gmail.com.

Re: KK still not compatible with FaderPort 16

[Slau Halatyn]

Not sure what's going on there. There was an issue in 2021.12 where other 
surfaces were limited to 8 channels of control at a time regardless of how many 
faders one had. That was fixed in 2022.4. Komplete Kontrol uses a different 
protocol than the faderport so I'm not sure why there would be an issue. There 
are at least a few others who have this combination of hardware. Hopefully, 
they can chime in with their experiences.
slau


> On May 18, 2022, at 11:50 A M, John André Lium-Netland 
>  wrote:
> 
> Hi,
> 
> Even after the newest update of PT to 2022.4, it’s not possible to run both 
> the Komplete Kontrol implementation at the same time as FaderPort 16. If they 
> are running at the same time, they will both have limited or no functionality 
> at all.
> 
> Does anyone have a solution to this, and have you experienced the same thing 
> with these or other combinations of equipment?
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/13004CF7-C2C8-457D-982B-905B5B4E6DAE%40a-pro-studio.no.

-- 
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/4DCBF5DB-B84A-41D5-955A-F0916FBF1377%40gmail.com.

Re: how do i get to the ptaccess dropbox folder?

[Slau Halatyn]

Alex,
You're already in the Drop Box folder. You'll have to go to the drop box web 
site and add the folder back to your Mac. If you don't see it in your local 
Drop Box folder on your Mac, that means you've deleted the folder from your 
computer. There are tons of videos and tutorials on how to add folders from 
drop Box back to your desktop.
Cheers,
Slau


> On Apr 29, 2022, at 3:08 PM, Alex Coleman  
> wrote:
> 
> I too would like instructions on how to access the PTAccess Dropbox folder. 
> Thanks much.
> Alex
> 
> 
> On Wed, Mar 9, 2022 at 10:12 AM David Ingram  > wrote:
> Hi list members, I don’t know how to get to the ptaccess dropbox folder so 
> that i can copy the fb360 folder to my applications folder.  Can someone 
> please provide the link to this folder?  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 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/BDFB7F20-E87D-4183-B9AD-AC795671ACB7%40earthlink.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/CAKVN6vP8tTN6-zyvwof_XbiqJ-ROYT%2B-2ykQRFJzxfaxYaxjDQ%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/BACBD0CB-8F87-4EEE-8DFC-8BE3950E77D4%40gmail.com.

Re: flotools double tapping no longer working

[Slau Halatyn]

OK, we've figured out what's going on here. Keyboard Maestro version 10 changed 
something in the way stuff is now being handled under the hood which led to a 
hiccup with the update notification.

1. If you update to Flo Tools 2022.4.0 the notification naturally goes away.
2. If you cannot update yet, you have the following 2 options:

A. Go to the first macro in the Flo Tools macro group and edit the macro name 
so that, instead of it saying 2020.5" (or whatever the previous version you 
have) to have 2022.4.0 in the name. This will fool Flo tools into thinking it's 
already on the latest version.
B. If you'd rather not deal with renaming the macro, before launching Pro 
Tools, turn off your WiFi or take your system offline however you prefer, 
launch Pro Tools and then turn WiFi or your Internet back on.

Again, if you're on the latest Pro Tools, you can go ahead and update Flo Tools 
and everything will resolve for future updates.

Best,
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/39F84024-B9EC-4215-BB7A-9AB8C6512488%40gmail.com.

Re: flotools double tapping no longer working

[Slau Halatyn]

Hi Steve,
If you've installed Pro Tools 2022.4, use Flo Tools 22.4. If you're running a 
previous version of Pro Tools, use the previous version of Flo Tools. Hope that 
helps.
Slau


> On Apr 28, 2022, at 2:05 AM, Steve Sparrow  wrote:
> 
> Ok guys. so flotools told me there is an update this morning. Since i’ve got 
> that message, I can no longer double tap keys to enable or disable functions. 
> for example hitting L will read the level metre, but double tapping it will 
> no longer engage watching level metre, I can’t unselect any tracks, and I 
> also can’t engage shuffle mode with f 1. I wonder if there is some 
> notification that is active, it’s telling me no notifications avail. Is there 
> something I need to do here. Maybe i’ll just have to upgrade flotools. I can 
> do this, but my system is a couple of o s behind. So a bit out of date I 
> guess.
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/F26970CE-F712-4326-9DD8-8E7DD8761924%40sparrowsound.com.au.

-- 
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/4D597B15-8306-4DD3-86F9-7D0F0293ED67%40gmail.com.

Re: Pro Tools 2022.04

[Slau Halatyn]

Hi Martin,

Flo Tools 2022.4 will be out by the end of the day today. We tried to have it 
ready for yesterday but a few last minute issues appeared adn we didn't want to 
risk releasing without testing.

There are no limitations on PT studio, per se. You probably meant to say Pro 
Tools Artist which does have the 16 I/O limitation. I think there's a 32 track 
limit or something but I don't recall exactly. Production Expert's web site has 
a bunch of info on it and I see that other blogs are starting to chime in on 
the new licenses and features.

Cheers,
Slau


> On Apr 27, 2022, at 4:26 AM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau and team!
> 
> Where do I find the latest Flo Tools announced in your fantastic m4a
> tutorial? 
> 
> When working only with quite small sessions and a maximum of 16 i/o...
> Are there other important limitations in the "Studio" edition?
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/004501d85a10%24784ba6b0%2468e2f410%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/A88437C8-A462-454D-A76A-D289850C136B%40gmail.com.

Re: ot: aphex plugins

[Slau Halatyn]

While the plug-ins themselves are accessible, whether it's worth it is a 
difficult question to answer. I think you might be able to use them in a trial 
mode, not sure. Personally, I wouldn't go out of my way to acquire them. Two 
cents worth.
Slau


> On Apr 14, 2022, at 7:27 AM, Tom Hessels  wrote:
> 
> Hi,
>  
> When downloading the 2022 versions of the Avid plugins from my account I 
> downloaded Aphex systems.
> When installed I see to plugins:
> Aphex aural exciter enad Aphex bigbottom pro.
> Starting Pro Tools I ran in the message that I must licence Aphex.
> On the website I see that I have to pay for it. (the other plugins I 
> downloade are free).
> The price is 99.
> My questions: is it worth buying and is it accessible.
> Tom Hessels.
>  
>  
> 
> -- 
> 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/001901d84ff2%24a936cb10%24fba46130%24%40tomhessels.nl
>  
> .

-- 
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/D5476FBF-98C7-4CA1-B768-7C7B29AAF3FA%40gmail.com.

Re: after updating to monterey, flowtools complains

[Slau Halatyn]

The OS is notoriously fickle with permissions. Sometimes you need to go through 
the process of checking and unchecking twice, restart and it often resolves the 
issue. If the issue persists, you can launch VoiceOver Utility before starting 
Pro Tools and quit VO Utility after PT is running. There's a command line 
solution that blows out all of your permissions but then you have to re-enable 
all of your permissions one by one in Security & Privacy. Opening the VoiceOVer 
Utility before launching Pro Tools only needs to be done once per reboot so, if 
you don't actually shut down your computer, PT will launch fine and the OS will 
see that checkbox as being checked for VoiceOver to be controlled by 
Applescript.


> On Mar 27, 2022, at 1:46 PM, John Covici  wrote:
> 
> Hi.  I have updated to OS 12.3 and now flowtools says to enable
> applescript, but when I go to vo utilities, its already checked.  Am I
> doing something wrong, or do I have to reinstall flowtools?  I have
> keyboard maistro 10.
> 
> Thanks.
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/m3fsn3s2zb.wl-covici%40ccs.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/B8DDC6C4-B43C-400B-930D-1FEAE429AF49%40gmail.com.

Re: Post for Rocco - The new Flo Tools installer

[Slau Halatyn]

Hi Martin,

The Flo Tools version in the current installer is the regular release version 
of Flo Tools. We're going to test a version with the slight delay to see how it 
responds. If all is fine, it'll be part of the regular release. I'd imagine you 
could just copy the JAVA script from your current macro and paste it into the 
latest installer version and it should run exactly as what you've had thus far.


> On Mar 10, 2022, at 11:46 PM, Martin (Punky) Sopart  
> wrote:
> 
> Hello RoccO!
> 
> Did you get my mail off list?
> Sent on February 16, 2022.
> 
> Best! / Martin
> 
> 
> Begin forwarded message:
> 
> From: "Martin (Punky) Sopart" mailto:m...@cakewalker.de>>
> Subject: The new Flo Tools installer
> Date: February 16, 2022 at 6:17:05 AM GMT+1
> To: Rocco Fiorentino mailto:ro...@musicbyrocco.com>>
> 
> Hello Rocco!
> 
> Regarding the Flo Tools plug-in monitor I got a pre version after the release 
> of Flo Tools 2020.5.
> In that pre version Chi added a delay to prevent the processor to become too 
> hot.
> Do you know if that change is in the new installer or will it come with the 
> next Flo Tools release?
> 
> 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/41055A4D-7E75-4AC9-9E6C-87E651CC24D1%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/F568C689-69E7-4B56-9D5C-C407328AE57E%40gmail.com.

Re: Flo Tools Team in need of a little feedback for upcoming release

[Slau Halatyn]

Nick, just want to make sure we're on the same page so see my reply to Rory. 
Are you using the List commands all the time?

> On Mar 10, 2022, at 9:57 PM, Nick Gawronski  wrote:
> 
> Hi, On the system that I use that has Flo Tools installed I do use that 
> feature for all of those settings so would hope it would stay but if some 
> type of choices or dialog will be required to choose what is to be shown that 
> would be ok but I like the quick methods that are currently working.  Nick 
> Gawronski
> 
> On 3/10/2022 8:31 PM, Rory McDonald wrote:
>> Hey slau,
>> I personally do use the solo, arm, track selection and others quite often. 
>> Option shift s twice quickly to unsolo everything, for example.
>> I would hope for these to stay, if possible.
>> If the feature itself must be modified slightly, as you said bringing up a 
>> list perhaps, with one shortcut, then I could work with that. But I 
>> personally would be against dropping the feature entirely.
>> Thanks,
>> 
>> Rory
>> 
>>> On Mar 10, 2022, at 7:12 PM, Slau Halatyn  wrote:
>>> 
>>> As we prepare the next version of Flo Tools, the Flo Tools Team is 
>>> pondering a particular set of features and wondering whether we should keep 
>>> them, discard them or just change the implementation just a bit.
>>> 
>>> There are 5 keyboard shortcuts with single and double-tap version s that 
>>> list things like Soloed tracks, muted tracks, armed tracks etc. 
>>> Double-tapping lists the unsoloed, unmuted, unarmed tracks, etc. In each 
>>> case, depending on the single or double tap, you get one or the other 
>>> version of the list and can toggle the status of the listed tracks 
>>> individually. The modifier combination includes Control+Shift along with 
>>> letter keys: S for solo, M for mute, R for record arm, K for input 
>>> monitoring and L for track selection.
>>> 
>>> The next release of Pro Tools will use two keyboard shortcuts that'll 
>>> conflict with two of the Flo Tools shortcuts. Since we try to keep modifier 
>>> combinations consistent, we'd be hard pressed to come up with combinations 
>>> for the included letters that don't conflict with other Pro Tools commands.
>>> 
>>> Therefore, we're evaluating whether or not this listing feature is worth 
>>> keeping or not. Personally, I've never used this feature but some people 
>>> might feel it's indispensable for their workflow. we also don't necessarily 
>>> have to ditch the feature itself but rather transform it into a single 
>>> keyboard shortcut that would bring up one extra step where users can choose 
>>> which filter type they'd like, press that button and then be presented with 
>>> the resulting list just as they have in the past. It is an extra step but 
>>> only one shortcut to remember.
>>> 
>>> So, we're asking for feedback from Flo Tools users for the following:
>>> 
>>> Do you feel that the listing feature is something you use often? Is it 
>>> something you'd really like to continue being part of Flo Tools or are you 
>>> indifferent? Again, we could probably implement an intermediate dialog to 
>>> facilitate the feature itself in a similar way but, before we put in the 
>>> time and effort, we'd like to make sure enough people truly want it to 
>>> stay. Otherwise, we're all about streamlining if it makes sense.
>>> 
>>> Please feel free to respond here and we'll make note of general sentiment.
>>> 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/1B0BEBC7-C0EF-4CE0-8A8A-D76EFF2882E9%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/53eb1644-be04-de14-c326-4d09be4921be%40nickgawronski.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/4C2B62AF-7E9C-4AE1-8C9A-8F927E37337F%40gmail.com.

Re: Flo Tools Team in need of a little feedback for upcoming release

[Slau Halatyn]

Just so you understand, I'm not referring to the Option+Shift commands that 
speak what's soloed, muted, selected, armed, etc. where double-tapping unmutes, 
deselects, disarms, etc. I'm talking about Control+Shift plus keys that bring 
up dialogs where tracks are listed and you can toggle the state. In the case of 
Control+Shift+S, a list of soloed tracks appears in a dialog and you can select 
the tracks you wish to unsolo and press the Unsolo Tracks button. It's 
different than the Option+Shift commands which report and a double-tap toggles 
things off.

Now, feel free to weigh in again.

Cheers

> On Mar 10, 2022, at 9:31 PM, Rory McDonald  wrote:
> 
> Hey slau,
> I personally do use the solo, arm, track selection and others quite often. 
> Option shift s twice quickly to unsolo everything, for example.
> I would hope for these to stay, if possible.
> If the feature itself must be modified slightly, as you said bringing up a 
> list perhaps, with one shortcut, then I could work with that. But I 
> personally would be against dropping the feature entirely.
> Thanks,
> 
> Rory
> 
>> On Mar 10, 2022, at 7:12 PM, Slau Halatyn  wrote:
>> 
>> As we prepare the next version of Flo Tools, the Flo Tools Team is 
>> pondering a particular set of features and wondering whether we should keep 
>> them, discard them or just change the implementation just a bit.
>> 
>> There are 5 keyboard shortcuts with single and double-tap version s that 
>> list things like Soloed tracks, muted tracks, armed tracks etc. 
>> Double-tapping lists the unsoloed, unmuted, unarmed tracks, etc. In each 
>> case, depending on the single or double tap, you get one or the other 
>> version of the list and can toggle the status of the listed tracks 
>> individually. The modifier combination includes Control+Shift along with 
>> letter keys: S for solo, M for mute, R for record arm, K for input 
>> monitoring and L for track selection.
>> 
>> The next release of Pro Tools will use two keyboard shortcuts that'll 
>> conflict with two of the Flo Tools shortcuts. Since we try to keep modifier 
>> combinations consistent, we'd be hard pressed to come up with combinations 
>> for the included letters that don't conflict with other Pro Tools commands.
>> 
>> Therefore, we're evaluating whether or not this listing feature is worth 
>> keeping or not. Personally, I've never used this feature but some people 
>> might feel it's indispensable for their workflow. we also don't necessarily 
>> have to ditch the feature itself but rather transform it into a single 
>> keyboard shortcut that would bring up one extra step where users can choose 
>> which filter type they'd like, press that button and then be presented with 
>> the resulting list just as they have in the past. It is an extra step but 
>> only one shortcut to remember.
>> 
>> So, we're asking for feedback from Flo Tools users for the following:
>> 
>> Do you feel that the listing feature is something you use often? Is it 
>> something you'd really like to continue being part of Flo Tools or are you 
>> indifferent? Again, we could probably implement an intermediate dialog to 
>> facilitate the feature itself in a similar way but, before we put in the 
>> time and effort, we'd like to make sure enough people truly want it to stay. 
>> Otherwise, we're all about streamlining if it makes sense.
>> 
>> Please feel free to respond here and we'll make note of general sentiment.
>> 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/1B0BEBC7-C0EF-4CE0-8A8A-D76EFF2882E9%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/B02516A1-E231-46A3-8C12-C4C808747709%40rogers.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/B1C39C8B-443B-4028-A1BE-B94E2DF8C35D%40gmail.com.