Re: Flotools installation issue in Sonoma

[Juan Pablo Culasso Alonso]

Amazing, thanks!
JP
> On Mar 29, 2024, at 9:24 PM, accessibleproto...@gmail.com wrote:
> 
> https://www.dropbox.com/scl/fi/r1vuro6sybgzo6g7pvxwx/FloTools-Installer-for-mac-OS-Sonoma.zip?rlkey=co4ai4pehdye2yi8j7vg9q1qk&dl=0
> Rocco Fiorentino
> www.musicbyrocco.com
> (609)922-3838
> 
>> On Mar 29, 2024, at 10:15 PM, Juan Pablo Culasso Alonso 
>>  wrote:
>> 
>> Hello Rocco. I have no access to that folder Could you share it in other 
>> way? Thanks,
>> Juan
>> 
>> 
>> 
>> Enviado desde mi iPhone
>> 
>>> El 29 mar 2024, a las 20:47, accessibleproto...@gmail.com escribió:
>>> 
>>> Hi Juan,
>>> 
>>> Please use the Flo tools installer  that's in the PT access dropbox for now.
>>> Thanks so much,
>>> Rocco
>>> Rocco Fiorentino
>>> www.musicbyrocco.com
>>> (609)922-3838
>>> 
>>>> On Mar 29, 2024, at 7:13 PM, Juan Pablo Culasso Alonso 
>>>>  wrote:
>>>> 
>>>> Hello everyone, I have computers that can only have Sonoma installed. I'm 
>>>> on version 14.4.1. When installing Flotools, after pressing the first 
>>>> next, I get this error: "The variable osName is not defined. (-2753)" When 
>>>> I click on edit, it asks me to locate this: "Where is Virtual Extended 
>>>> Keyboard.app?" Any ideas?
>>>> Thanks,
>>>> Juan
>>>> 
>>>> --
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/ptaccess/1F096B65-929F-4B59-B9DB-3D7A49DF9A04%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/8F660951-B02E-4DB4-8BAB-3828DDF8538E%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/AC6293DE-DF74-4FE3-8F4B-95EF2124ACB3%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 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/CD085088-80D4-4854-9C43-39BA4C3888C8%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/CD085088-80D4-4854-9C43-39BA4C3888C8%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/25720C50-56FB-4BB4-A6BE-BB8D92F7D2ED%40gmail.com.

Re: Flotools installation issue in Sonoma

[Juan Pablo Culasso Alonso]

Hello Rocco. I have no access to that folder Could you share it in other way? 
Thanks,
Juan



Enviado desde mi iPhone

> El 29 mar 2024, a las 20:47, accessibleproto...@gmail.com escribió:
> 
> Hi Juan,
> 
> Please use the Flo tools installer  that's in the PT access dropbox for now.
> Thanks so much,
> Rocco
> Rocco Fiorentino
> www.musicbyrocco.com
> (609)922-3838
> 
>> On Mar 29, 2024, at 7:13 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hello everyone, I have computers that can only have Sonoma installed. I'm 
>> on version 14.4.1. When installing Flotools, after pressing the first next, 
>> I get this error: "The variable osName is not defined. (-2753)" When I click 
>> on edit, it asks me to locate this: "Where is Virtual Extended 
>> Keyboard.app?" Any ideas?
>> Thanks,
>> Juan
>> 
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/1F096B65-929F-4B59-B9DB-3D7A49DF9A04%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/8F660951-B02E-4DB4-8BAB-3828DDF8538E%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/AC6293DE-DF74-4FE3-8F4B-95EF2124ACB3%40gmail.com.

Flotools installation issue in Sonoma

[Juan Pablo Culasso Alonso]

Hello everyone, I have computers that can only have Sonoma installed. I'm on 
version 14.4.1. When installing Flotools, after pressing the first next, I get 
this error: "The variable osName is not defined. (-2753)" When I click on edit, 
it asks me to locate this: "Where is Virtual Extended Keyboard.app?" Any ideas?
Thanks,
Juan

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/1F096B65-929F-4B59-B9DB-3D7A49DF9A04%40gmail.com.

Re: on the subject of Sonoma compatibility

[Juan Pablo Culasso Alonso]

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.

Re: looks like another bug

[Juan Pablo Culasso Alonso]

Great, thanks!

> On 8 Apr 2023, at 14:11, Martin (Punky) Sopart  wrote:
> 
> Hello John!
> 
> Here is the macro.
> Just save import it and it should work.
> The key combination is Control+Option+Command+Return.
> 
> 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/E1C8A24D-E047-4F3A-B713-FFE2FB67895A%40cakewalker.de.
> 
> On Apr 8, 2023, at 3:57 PM, Juan Pablo Culasso Alonso  
> wrote:
> 
> Hello, Martin,
> 
> Can you share that macro?
> Thanks,
> Juan
>> On 8 Apr 2023, at 04:23, Martin (Punky) Sopart  wrote:
>> 
>> Hello John!
>> 
>> You have to turn off VoiceOver before opening any session which could cause 
>> a session notes, missing AAX plug-in or any other message/dialog like that.
>> Having turned VO off you could answer the session notes and missing AAX 
>> plug-in dialogs by pressing the letter "n".
>> Further you could force the playback engine dialog to pop up during 
>> launching Pro Tools by pressing and holding the letter "n".
>> After quitting those eventual dialogs successful you can launch VO again.
>> Not perfect but it's working for me here.
>> To make things a bit easier I wrote a Keyboard Maestro macro to speak the 
>> current app and window name via keyboard shortcut and the system speech, 
>> without VoiceOver.
>> 
>> Best! / Martin
>> 
>> 
>> On Apr 8, 2023, at 10:24 AM, John Covici  wrote:
>> 
>> OK, thanks.  Any way to start pt, or do I have to wait till they fix
>> the bug?
>> 
>> On Sat, 08 Apr 2023 02:42:45 -0400,
>> Martin (Punky) Sopart wrote:
>>> 
>>> Hello!
>>> 
>>> It's the same bug PT-298075 I already reported.
>>> Due to the Ventura update from version 13.2.1 to version 13.3 the line 
>>> number changed from 2814to 2812.
>>> Same for latest Ventura 13.3.1.
>>> 
>>> Best! / Martin
>>> 
>>> 
>>> On Mar 25, 2023, at 9:59 AM, Martin (Punky) Sopart  
>>> wrote:
>>> 
>>> Hello!
>>> 
>>> Just for your information...
>>> 
>>> The bug PT-298075 still exists in Pro Tools 2023.3.
>>> 
>>> Best! / Martin
>>> 
>>> 
>>> On Mar 17, 2023, at 6:32 PM, Martin (Punky) Sopart  
>>> wrote:
>>> 
>>> Hello all!
>>> 
>>> The issue has been logged in Avid's system as bug PT-298075 and has to be
>>> tested by the engineering team.
>>> 
>>> Latest Pro Tools (PT) version 2022.12 unter Ventura 13.2.1 (Intel).
>>> 
>>> Start the VoiceOver (VO) screenreader - Command+F5.
>>> 
>>> Open any PT session that will bring up a "session notes, some I/O is
>>> missing" or "missing plug-in" message/dialog and the assertion error will
>>> occur.
>>> 
>>> Best! / Martin
>>> 
>>> 
>>> On Apr 8, 2023, at 2:24 AM, cov...@ccs.covici.com wrote:
>>> 
>>> Hi.  Looks like I have another bug -- I cannot start pt under Venture
>>> with the playback engine set to builtin speakers.
>>> 
>>> Here is the error
>>> 
>>> Could not complete your request because Assertion in 
>>> "/Users/autobld/gitlabci/PT/release/2023/r1/ProTools/DFW/Views/UGridView.cpp",
>>>  line 2812.
>>> 
>>> (Use the Copy button to copy this message to the clipboard.).
>>> 
>>> Any suggestions would be appreciated.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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/AEA2E5CB-7063-4CDA-980C-3770FDEC41B4%40cakewalker.de.
>> 
>> -- 
>> 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 Ac

Re: looks like another bug

[Juan Pablo Culasso Alonso]

Hello, Martin,

Can you share that macro?
Thanks,
Juan
> On 8 Apr 2023, at 04:23, Martin (Punky) Sopart  wrote:
> 
> Hello John!
> 
> You have to turn off VoiceOver before opening any session which could cause a 
> session notes, missing AAX plug-in or any other message/dialog like that.
> Having turned VO off you could answer the session notes and missing AAX 
> plug-in dialogs by pressing the letter "n".
> Further you could force the playback engine dialog to pop up during launching 
> Pro Tools by pressing and holding the letter "n".
> After quitting those eventual dialogs successful you can launch VO again.
> Not perfect but it's working for me here.
> To make things a bit easier I wrote a Keyboard Maestro macro to speak the 
> current app and window name via keyboard shortcut and the system speech, 
> without VoiceOver.
> 
> Best! / Martin
> 
> 
> On Apr 8, 2023, at 10:24 AM, John Covici  wrote:
> 
> OK, thanks.  Any way to start pt, or do I have to wait till they fix
> the bug?
> 
> On Sat, 08 Apr 2023 02:42:45 -0400,
> Martin (Punky) Sopart wrote:
>> 
>> Hello!
>> 
>> It's the same bug PT-298075 I already reported.
>> Due to the Ventura update from version 13.2.1 to version 13.3 the line 
>> number changed from 2814to 2812.
>> Same for latest Ventura 13.3.1.
>> 
>> Best! / Martin
>> 
>> 
>> On Mar 25, 2023, at 9:59 AM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> Just for your information...
>> 
>> The bug PT-298075 still exists in Pro Tools 2023.3.
>> 
>> Best! / Martin
>> 
>> 
>> On Mar 17, 2023, at 6:32 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello all!
>> 
>> The issue has been logged in Avid's system as bug PT-298075 and has to be
>> tested by the engineering team.
>> 
>> Latest Pro Tools (PT) version 2022.12 unter Ventura 13.2.1 (Intel).
>> 
>> Start the VoiceOver (VO) screenreader - Command+F5.
>> 
>> Open any PT session that will bring up a "session notes, some I/O is
>> missing" or "missing plug-in" message/dialog and the assertion error will
>> occur.
>> 
>> Best! / Martin
>> 
>> 
>> On Apr 8, 2023, at 2:24 AM, cov...@ccs.covici.com wrote:
>> 
>> Hi.  Looks like I have another bug -- I cannot start pt under Venture
>> with the playback engine set to builtin speakers.
>> 
>> Here is the error
>> 
>> Could not complete your request because Assertion in 
>> "/Users/autobld/gitlabci/PT/release/2023/r1/ProTools/DFW/Views/UGridView.cpp",
>>  line 2812.
>> 
>> (Use the Copy button to copy this message to the clipboard.).
>> 
>> Any suggestions would be appreciated.
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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/AEA2E5CB-7063-4CDA-980C-3770FDEC41B4%40cakewalker.de.
> 
> -- 
> 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/m3y1n2vl21.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/930151A5-7C0E-4A00-B4A2-A1589BBEBFE1%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/2E210FE7-F53C-402C-BEFA-AB4561C7F0BF%40gmail.com.

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

[Juan Pablo Culasso Alonso]

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

-- 
You received this message because you are subscribed to the Google 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/993FFCB5-D796-404E-810D-A623A8CC1305%40gmail.com.

Re: PS: Adding content in a big session

[Juan Pablo Culasso Alonso]

thank you so much, I will do it and tell you if all is done. Thanks,JP

> On Nov 11, 2021, at 09:58, Martin (Punky) Sopart  wrote:
> 
> Hello Juan Pablo!
> 
> Hope, I got you right...
> 
> In the Edit Window:
> 0. Make shure, that the edit mode "Shuffle" is active (F1).
> 1. Deselect all tracks. Using Flo Tools double press of Shift+Option+L will 
> do it for you.
> 2. Select all desired tracks with one of the common methods.
> 3. Move to the beginning of the session by pressing Entr.
> 4. If the main countr is set to "Minutes/Seconds", make a 5 seconds selection 
> by pressing the NumpadSlash 3 times and type NumpadComma Numpad5 NumpadEnter.
> 5. Chose "Insert Silence" from the Edit Menu and you should be done.
> Don't forget to deselect the tracks.
> 
> Best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com  On Behalf Of Juan 
> Pablo Culasso Alonso
> Sent: Thursday, November 11, 2021 2:07 PM
> To: ptaccess@googlegroups.com
> Subject: Adding content in a big session
> 
> Heelo, i have a sesssion with 75 tracks. I need add a piece of 5 seconds to 
> one of this, is there a way to nudge all the tracks 5 seconds to maitain the 
> aligment of the all sessions? I am reffering if I can do it in all tracks at 
> the same time instead landing in each one and do it one by one.
> thanks,
> juan
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/6E692351-491B-4A3B-B8DC-DFB1DB5C4829%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/00f801d7d70c%24a2773620%24e765a260%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/28FE000E-3DE3-45CE-BE39-E69F77D26E28%40gmail.com.

Adding content in a big session

[Juan Pablo Culasso Alonso]

Heelo, i have a sesssion with 75 tracks. I need add a piece of 5 seconds to one 
of this, is there a way to nudge all the tracks 5 seconds to maitain the 
aligment of the all sessions? I am reffering if I can do it in all tracks at 
the same time instead landing in each one and do it one by one.
thanks,
juan

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/6E692351-491B-4A3B-B8DC-DFB1DB5C4829%40gmail.com.

Loudnes plugin

[Juan Pablo Culasso Alonso]

Hello all, which loudness solution do you use?
Lm correct from Nugen audio, for example?
Thanks,
Juan

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/5650CC39-9A89-46B3-8A34-767D17F87937%40gmail.com.

Re: Go to the first clip in a track?

[Juan Pablo Culasso Alonso]

Thank you!
I did exactly the same thing in other session, however in this one there was a 
different setup. I just could do it. thanks again

JP
> On May 21, 2021, at 12:29, Ignasi Cambra  wrote:
> 
> If you have everything set up correctly you just need to select the track, 
> make sure you have an insertion point, go to the beginning by pressing 
> return, and then press the tab key to go to the first clip, if it’s not at 
> the beginning of the session.
> 
> Sent from my iPhone
> 
>> On 21 May 2021, at 19:05, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hello all, is there a way to go to the first clip of a certain track, if 
>> the track begin at min 30 of the session, how to jump directly there?
>> Thanks,
>> Juan
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/59C0E7D6-2882-41A2-AAF4-C61FC229B3E3%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/A22D3BF5-BF74-4829-ACA1-B4FD71A07BE0%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/00BA1D2C-CD89-4689-8B79-3DECE74B7FE5%40gmail.com.

Go to the first clip in a track?

[Juan Pablo Culasso Alonso]

Hello all, is there a way to go to the first clip of a certain track, if the 
track begin at min 30 of the session, how to jump directly there?
Thanks,
Juan

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/59C0E7D6-2882-41A2-AAF4-C61FC229B3E3%40gmail.com.

About macbook pro with touch bar

[Juan Pablo Culasso Alonso]

Hello all, my macbook pro died and I am thinking replacing the machine with a 
new one. Anyone uses the macbook pro with the touch bar? How you manage this. 
Is usable or for faster tasks you plug an external keyboard?
Thanks,
JP

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/AC833807-ECAB-44A7-B6F4-19469B7061C1%40gmail.com.

Re: Pro Tools 2020.9

[Juan Pablo Culasso Alonso]

Disconsider the last one. I restarted the computer an now works fine.
Tks,
JP.

> On Sep 6, 2020, at 22:29, Slau Halatyn  wrote:
> 
> Yep, it'll work fine.
> 
>> On Sep 6, 2020, at 10:50 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> This week I have to set up a new Pro Tools system for a client.
>> Could I use the new version 2020.9 regarding Flo Tools?
>> 
>> 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/A07B4B6B-225E-4142-BA5A-F79569D55964%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/2918C899-A154-44CA-9827-09913B087347%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/C319A844-FCD2-4D38-96C2-15AF60DB6BBC%40gmail.com.

Re: Pro Tools 2020.9

[Juan Pablo Culasso Alonso]

Slau, in 2020.9 when the inspector is on, even pressing twice a key does not 
make the function. In any case. Twice r for arm, twice i for input, etc
Can you replicate this?


> On Sep 6, 2020, at 22:29, Slau Halatyn  wrote:
> 
> Yep, it'll work fine.
> 
>> On Sep 6, 2020, at 10:50 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> This week I have to set up a new Pro Tools system for a client.
>> Could I use the new version 2020.9 regarding Flo Tools?
>> 
>> 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/A07B4B6B-225E-4142-BA5A-F79569D55964%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/2918C899-A154-44CA-9827-09913B087347%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/65E71C5D-3E52-4FAB-AA14-C7A6E20ED15C%40gmail.com.

Re: Automation question.

[Juan Pablo Culasso Alonso]

Hello all!

Well, there is a VoiceOver confusion. The price of the tutorial download 
lifetime is not 750 dollars, or even 75. The price is 7.50. I just purchased it 
right now.


> On Nov 23, 2019, at 12:56 PM, Slau Halatyn  wrote:
> 
> You can subscribe to Groove 3 on a yearly basis and cancel any time. I think 
> the yearly price is something like $100 or so. Anyone can subscribe for a 
> given amount of time, even a month, and determine whether it's worth it.
> 
> 
>> On Nov 22, 2019, at 7:45 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Same here, i received the same answer and the lifetime download is 750 
>> dollars.
>> 
>> 
>>> On Nov 17, 2019, at 2:46 PM, Martin (Punky) Sopart >> <mailto:m...@cakewalker.de>> wrote:
>>> 
>>> Hello Chuck!
>>> 
>>> I contacted them via e/mail.
>>> 
>>> $75 would be perfect, but the lifetime download is $750.
>>> 
>>> Best! / Martin
>>> 
>>> 
>>> On Nov 17, 2019, at 18:42, CHUCK REICHEL >> <mailto:soundpicturerecord...@gmail.com>> wrote:
>>> 
>>> Hi Martin,
>>> 
>>> Thats very interesting.
>>> I haven't talked to them in a while though.
>>> Did you call them?
>>> I thought I saw on there site that you could still buy the tutorials but 
>>> may be I miss read that.
>>> BTW
>>> That automation secrets is worth more Than #$75.00.
>>> If it saves your "bacon" just once its paid for.
>>> Talk soon
>>> Chuck
>>> 
>>> On Nov 17, 2019, at 11:49 AM, Martin (Punky) Sopart wrote:
>>> 
>>>> Hello Chuch and all!
>>>> 
>>>> I contacted Groove3 and asked for the tutorial.
>>>> They are only selling memberships or lifetime video downloads.
>>>> No mp3.
>>>> The tutorial video "Pro Tools Automation Secrets Pro Tools HD Automation 
>>>> Secrets by Michael Costa” is about 750 $.
>>>> 
>>>> So things have changed I think.
>>>> 
>>>> Best! / Martin
>>>> 
>>>> 
>>>> On Nov 15, 2019, at 19:03, Slau Halatyn >>> <mailto:slauhala...@gmail.com>> wrote:
>>>> 
>>>> Glad to hear you've had some success. Keep in mind that the Write To 
>>>> start, Write to All and Write To End commands are normally meant for when 
>>>> you do not have a selection. There are specific times when you absolutely 
>>>> would use those commands in conjunction with a selection. But, when 
>>>> automating 20 seconds or so, it doesn't necessarily make sense to use 
>>>> those features since it's perfectly reasonable to have the transport play 
>>>> for 20 seconds.
>>>> 
>>>> An instance where you'd use the Write to All is if you're trying to 
>>>> establish the overall level of a track for an entire timeline. You can get 
>>>> into Auto write mode, engage the transport, set the level and, when you're 
>>>> happy with it, press the write to All button. Then you will have the 
>>>> current automation fader level set across your entire timeline. From 
>>>> there, you can make further adjustments.
>>>> 
>>>> Let's say you wanted to then raise the volume at bar 30 and keep it raised 
>>>> until the end of the timeline, you can once again go into Auto write, make 
>>>> the adjustment and use Write to End to keep the fader level a bit higher 
>>>> until the end.
>>>> 
>>>> Let's say you wanted to once again lower the level but only from bar 60 
>>>> until 4 bars before the end of the song. You can make a selection between 
>>>> bar 60 and 4 bars before the end of the song. Now with a longer selection 
>>>> that you don't need to play in its entirety, you can set the new level and 
>>>> then press Write to All. This will write the new level to the selected 
>>>> range.
>>>> 
>>>> Keep in mind that all of the Write to commands are meant to be executed 
>>>> while the transport is engaged.
>>>> 
>>>> Slau
>>>> 
>>>> 
>>>>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso 
>>>>> mailto:jpcula...@gmail.com>> wrote:
>>>>> 
>>>>> Slau, i had success!
>>>>> I selected a portion of 20 seconds of a clip, aut

Re: Automation question.

[Juan Pablo Culasso Alonso]

Same here, i received the same answer and the lifetime download is 750 dollars.


> On Nov 17, 2019, at 2:46 PM, Martin (Punky) Sopart  wrote:
> 
> Hello Chuck!
> 
> I contacted them via e/mail.
> 
> $75 would be perfect, but the lifetime download is $750.
> 
> Best! / Martin
> 
> 
> On Nov 17, 2019, at 18:42, CHUCK REICHEL  <mailto:soundpicturerecord...@gmail.com>> wrote:
> 
> Hi Martin,
> 
> Thats very interesting.
> I haven't talked to them in a while though.
> Did you call them?
> I thought I saw on there site that you could still buy the tutorials but may 
> be I miss read that.
> BTW
> That automation secrets is worth more Than #$75.00.
> If it saves your "bacon" just once its paid for.
> Talk soon
> Chuck
> 
> On Nov 17, 2019, at 11:49 AM, Martin (Punky) Sopart wrote:
> 
>> Hello Chuch and all!
>> 
>> I contacted Groove3 and asked for the tutorial.
>> They are only selling memberships or lifetime video downloads.
>> No mp3.
>> The tutorial video "Pro Tools Automation Secrets Pro Tools HD Automation 
>> Secrets by Michael Costa” is about 750 $.
>> 
>> So things have changed I think.
>> 
>> Best! / Martin
>> 
>> 
>> On Nov 15, 2019, at 19:03, Slau Halatyn > <mailto:slauhala...@gmail.com>> wrote:
>> 
>> Glad to hear you've had some success. Keep in mind that the Write To start, 
>> Write to All and Write To End commands are normally meant for when you do 
>> not have a selection. There are specific times when you absolutely would use 
>> those commands in conjunction with a selection. But, when automating 20 
>> seconds or so, it doesn't necessarily make sense to use those features since 
>> it's perfectly reasonable to have the transport play for 20 seconds.
>> 
>> An instance where you'd use the Write to All is if you're trying to 
>> establish the overall level of a track for an entire timeline. You can get 
>> into Auto write mode, engage the transport, set the level and, when you're 
>> happy with it, press the write to All button. Then you will have the current 
>> automation fader level set across your entire timeline. From there, you can 
>> make further adjustments.
>> 
>> Let's say you wanted to then raise the volume at bar 30 and keep it raised 
>> until the end of the timeline, you can once again go into Auto write, make 
>> the adjustment and use Write to End to keep the fader level a bit higher 
>> until the end.
>> 
>> Let's say you wanted to once again lower the level but only from bar 60 
>> until 4 bars before the end of the song. You can make a selection between 
>> bar 60 and 4 bars before the end of the song. Now with a longer selection 
>> that you don't need to play in its entirety, you can set the new level and 
>> then press Write to All. This will write the new level to the selected range.
>> 
>> Keep in mind that all of the Write to commands are meant to be executed 
>> while the transport is engaged.
>> 
>> Slau
>> 
>> 
>>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso 
>>> mailto:jpcula...@gmail.com>> wrote:
>>> 
>>> Slau, i had success!
>>> I selected a portion of 20 seconds of a clip, automated pan from left to 
>>> center by the first 3 seconds, and in the automation window y pressed the 
>>> button 
>>>  Write Automation to Selection End on Stop
>>> So after the second 20 the sound as I expected, it returns to the left.
>>> So now I need to check if in the Eucon app, there is already an option to 
>>> atach to a key in my  avid transport to this three buttons.
>>> 
>>> Thanks,
>>> JP.
>>>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn >>> <mailto:slauhala...@gmail.com>> wrote:
>>>> 
>>>> Juan,
>>>> There could be any number of reasons your panning isn't sticking to the 
>>>> right side. I'd suggest the following:
>>>> 1. Set your track view to pan.
>>>> 2. Select everything from beginning of the session to the end with Option 
>>>> Shift Return and press Delete.
>>>> 3. Confirm that your audio is still there.
>>>> 4. Put your track into Auto Latch mode and, with your pan at center, 
>>>> engage the transport and pan to the left.
>>>> 
>>>> When you stop the transport, your track should remain panned to the right.
>>>> 
>>>> Another approach you can take is to do this in Auto Write mod

Re: Automation question., • Pro Tools Automation Secrets Pro Tools HD Automation Secrets by Michael Costa

[Juan Pablo Culasso Alonso]

Thanks!!

> On Nov 15, 2019, at 6:27 PM, CHUCK REICHEL  
> wrote:
> 
> Hi John,
> Yeah you could email or;
> Tutorial Videos for Recording, Mixing & Production <https://www.groove3.com/>
> https://www.youtube.com/channel/UCA5DRcDlQAwsXKrLr5vvmhA 
> <https://www.youtube.com/channel/UCA5DRcDlQAwsXKrLr5vvmhA>
> Groove 3 Inc. CALL US:  1-800-460-7509 
> I think I paid $30.00 or so but by now its probably 5 or 10 bucks.
> They have a mp3 version due to my persistence years ago, the PT version is  
> older but still valid! :)
> Oh yeah they know what VoiceOver is! ;)
> Its worth hundreds in the time saved! :)
> YMMV
> Chuck
> 
>>> "God does not play dice with the universe"
>>> "Albert Einstein’
> 
>> 
> 
> On Nov 15, 2019, at 3:18 PM, John Covici wrote:
> 
>> That is an Email address, do I have to write to him to get the
>> tutorial?
>> 
>> On Fri, 15 Nov 2019 13:27:58 -0500,
>> CHUCK REICHEL wrote:
>>> 
>>> [1  ]
>>> [2  ]
>>> Hi Juan,
>>> 
>>> I highly recommend this Pro tools automation tutorial to every one using 
>>> pro tools.
>>> Pro Tools Automation Secrets Pro Tools HD Automation Secrets by Michael 
>>> Costa
>>> You can find out about it here;
>>> supp...@groove3.com <mailto:supp...@groove3.com>
>>> This totally opened up my understanding  years ago for all the automation 
>>> tasks you'll need in pro tools
>>> HTH
>>> Chuck
>>> "God does not play dice with the universe"
>>> "Albert Einstein’
>>> 
>>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso wrote:
>>> 
>>> Slau, i had success!
>>> I selected a portion of 20 seconds of a clip, automated pan from left to 
>>> center by the first 3 seconds, and in the automation window y pressed the 
>>> button 
>>>  Write Automation to Selection End on Stop
>>> So after the second 20 the sound as I expected, it returns to the left.
>>> So now I need to check if in the Eucon app, there is already an option to 
>>> atach to a key in my  avid transport to this three buttons.
>>> 
>>> Thanks,
>>> JP.
>>> 
>>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Juan,
>>> There could be any number of reasons your panning isn't sticking to the 
>>> right side. I'd suggest the following:
>>> 1. Set your track view to pan.
>>> 2. Select everything from beginning of the session to the end with Option 
>>> Shift Return and press Delete.
>>> 3. Confirm that your audio is still there.
>>> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
>>> the transport and pan to the left.
>>> 
>>> When you stop the transport, your track should remain panned to the right.
>>> 
>>> Another approach you can take is to do this in Auto Write mode and, once 
>>> you've panned to the right, press the Write to End button in the Automation 
>>> window. You'll get a dialog informing you that automation has been written 
>>> to
>>> the end of the timeline.
>>> 
>>> Further, it appeared that you had Trim mode checked before engaging the 
>>> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
>>> mode is meant to make relative changes to already recorded automation data.
>>> 
>>> Let me know if this process works for you.
>>> 
>>> Slau
>>> 
>>> On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso 
>>> mailto:jpcula...@gmail.com>> wrote:
>>> 
>>> Slau, here is an example of panning automation I put in latch mode but the 
>>> parameter is not saved.
>>> 
>>> https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
>>>  
>>> <https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1>
>>> Is a 59 seconds recording. can you check that? and tell me what is wrong?
>>> 
>>> Thanks,
>>> Juan.
>>> 
>>> On Nov 13, 2019, at 10:01 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Well, good for you! OK, now when you go to the Automation window, you'll 
>>> see buttons for writing to the start, end or entire length of the session 
>>> from beginning to end. With an Avid control surface, there 

Re: Automation question.

[Juan Pablo Culasso Alonso]

Thanks, Slau. I will practice and tell how I am doing.

Would be nice if you can record something.

thanks,
JP.

> On Nov 15, 2019, at 3:03 PM, Slau Halatyn  wrote:
> 
> Glad to hear you've had some success. Keep in mind that the Write To start, 
> Write to All and Write To End commands are normally meant for when you do not 
> have a selection. There are specific times when you absolutely would use 
> those commands in conjunction with a selection. But, when automating 20 
> seconds or so, it doesn't necessarily make sense to use those features since 
> it's perfectly reasonable to have the transport play for 20 seconds.
> 
> An instance where you'd use the Write to All is if you're trying to establish 
> the overall level of a track for an entire timeline. You can get into Auto 
> write mode, engage the transport, set the level and, when you're happy with 
> it, press the write to All button. Then you will have the current automation 
> fader level set across your entire timeline. From there, you can make further 
> adjustments.
> 
> Let's say you wanted to then raise the volume at bar 30 and keep it raised 
> until the end of the timeline, you can once again go into Auto write, make 
> the adjustment and use Write to End to keep the fader level a bit higher 
> until the end.
> 
> Let's say you wanted to once again lower the level but only from bar 60 until 
> 4 bars before the end of the song. You can make a selection between bar 60 
> and 4 bars before the end of the song. Now with a longer selection that you 
> don't need to play in its entirety, you can set the new level and then press 
> Write to All. This will write the new level to the selected range.
> 
> Keep in mind that all of the Write to commands are meant to be executed while 
> the transport is engaged.
> 
> Slau
> 
> 
>> On Nov 15, 2019, at 12:31 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Slau, i had success!
>> I selected a portion of 20 seconds of a clip, automated pan from left to 
>> center by the first 3 seconds, and in the automation window y pressed the 
>> button 
>>  Write Automation to Selection End on Stop
>> So after the second 20 the sound as I expected, it returns to the left.
>> So now I need to check if in the Eucon app, there is already an option to 
>> atach to a key in my  avid transport to this three buttons.
>> 
>> Thanks,
>> JP.
>>> On Nov 15, 2019, at 1:03 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Juan,
>>> There could be any number of reasons your panning isn't sticking to the 
>>> right side. I'd suggest the following:
>>> 1. Set your track view to pan.
>>> 2. Select everything from beginning of the session to the end with Option 
>>> Shift Return and press Delete.
>>> 3. Confirm that your audio is still there.
>>> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
>>> the transport and pan to the left.
>>> 
>>> When you stop the transport, your track should remain panned to the right.
>>> 
>>> Another approach you can take is to do this in Auto Write mode and, once 
>>> you've panned to the right, press the Write to End button in the Automation 
>>> window. You'll get a dialog informing you that automation has been written 
>>> to the end of the timeline.
>>> 
>>> Further, it appeared that you had Trim mode checked before engaging the 
>>> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
>>> mode is meant to make relative changes to already recorded automation data.
>>> 
>>> Let me know if this process works for you.
>>> 
>>> Slau
>>> 
>>> 
>>>> On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Slau, here is an example of panning automation I put in latch mode but the 
>>>> parameter is not saved.
>>>> 
>>>> https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
>>>>  
>>>> <https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1>
>>>> Is a 59 seconds recording. can you check that? and tell me what is wrong?
>>>> 
>>>> Thanks,
>>>> Juan.
>>>>> On Nov 13, 2019, at 10:01 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>

Re: Automation question.

[Juan Pablo Culasso Alonso]

Slau, i had success!
I selected a portion of 20 seconds of a clip, automated pan from left to center 
by the first 3 seconds, and in the automation window y pressed the button 
 Write Automation to Selection End on Stop
So after the second 20 the sound as I expected, it returns to the left.
So now I need to check if in the Eucon app, there is already an option to atach 
to a key in my  avid transport to this three buttons.

Thanks,
JP.
> On Nov 15, 2019, at 1:03 PM, Slau Halatyn  wrote:
> 
> Juan,
> There could be any number of reasons your panning isn't sticking to the right 
> side. I'd suggest the following:
> 1. Set your track view to pan.
> 2. Select everything from beginning of the session to the end with Option 
> Shift Return and press Delete.
> 3. Confirm that your audio is still there.
> 4. Put your track into Auto Latch mode and, with your pan at center, engage 
> the transport and pan to the left.
> 
> When you stop the transport, your track should remain panned to the right.
> 
> Another approach you can take is to do this in Auto Write mode and, once 
> you've panned to the right, press the Write to End button in the Automation 
> window. You'll get a dialog informing you that automation has been written to 
> the end of the timeline.
> 
> Further, it appeared that you had Trim mode checked before engaging the 
> transport. Don't use Trim mode in this case. Make sure it's unchecked. Trim 
> mode is meant to make relative changes to already recorded automation data.
> 
> Let me know if this process works for you.
> 
> Slau
> 
> 
>> On Nov 13, 2019, at 11:20 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Slau, here is an example of panning automation I put in latch mode but the 
>> parameter is not saved.
>> 
>> https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
>>  
>> <https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1>
>> Is a 59 seconds recording. can you check that? and tell me what is wrong?
>> 
>> Thanks,
>> Juan.
>>> On Nov 13, 2019, at 10:01 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Well, good for you! OK, now when you go to the Automation window, you'll 
>>> see buttons for writing to the start, end or entire length of the session 
>>> from beginning to end. With an Avid control surface, there are dedicated 
>>> buttons for these functions. Anyway, you'll have a much easier time with 
>>> Ultimate.
>>> Slau
>>> 
>>> 
>>> 
>>>> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Thanks, slau, I just installed it.
>>>> 
>>>> 
>>>>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>> For controls like panning, where you want the value to remain the same, 
>>>>> use Latch mode. In other words, if you start from one set of values and 
>>>>> change while in Latch mode, the subsequent automation data will stay at 
>>>>> the last recorded value. This theoretically works with faders as well but 
>>>>> some people have had limited success doing it with faders. Pan automation 
>>>>> should work fine.
>>>>> 
>>>>> Now, you say you've upgraded to Ultimate? If you have, then the 
>>>>> automation process will be infinitely easier. Let me know when you have 
>>>>> it installed.
>>>>> Slau
>>>>> 
>>>>> 
>>>>>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso 
>>>>>> mailto:jpcula...@gmail.com>> wrote:
>>>>>> 
>>>>>> Absolutely amazing, slau.
>>>>>> And for panning? I tried some pan automation and for example, if the 
>>>>>> start point is 70 left 30 right and I go to 30 left and 70 right, after 
>>>>>> press the stop button and play the track, the automation looks fine but 
>>>>>> after the end of the automation the track returns to the begining point. 
>>>>>> How to solve this and the track continues in 30 left 70 right?
>>>>>> I linked the paner
>>>>>> 
>>>>>> Thanks,
>>>>>> Juan.
>>>>>> I upgraded to ultimate
>>>>>>  and I want to use it at 100% in

Re: Automation question.

[Juan Pablo Culasso Alonso]

Thank you so much, slau.

JP.

> On Nov 15, 2019, at 1:21 AM, Slau Halatyn  wrote:
> 
> Of course I understand that you're asking about automation in Pro Tools 
> Ultimate. Your questions are specific in a way but they are quite general at 
> the same time. I'll need to respond in the morning because I'm going to end 
> up typing quite a bit.
> Slau
> 
> 
>> On Nov 14, 2019, at 8:29 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Sure, Slau.
>> 
>> I am reffering specifically to automate in protools ultimate.
>> I am in the automation window, and for example, I select 10 seconds
>> How can i automate this 10 seconds∑
>> When I press the button
>> Write Automation to Selection Start, for example, I get the message: No 
>> automation was written.
>> The same happens in Write Automation to Selection
>> If I press the button
>> Write Automation to Selection on Stop
>> It`s becomes selected, i press the play button, move the fader and when i 
>> return to the button
>> Write Automation to Selection
>> I got the same message
>> 
>> 
>> Other question is?
>> Even putting the mode in latch, in volume or pan automation, when press stop 
>> and go back to read, the last parameter when i left the fader is not 
>> remembered in volume or pan.
>> 
>> I reed the protools reference guide, tried to get som youtube tutorials but 
>> i did not advance too much.
>> 
>> Thanks again for your help and patience.
>> JP.
>> 
>>> On Nov 14, 2019, at 10:12 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Sorry Juan, Automation is complex and you'll need to be very specific with 
>>> your question. I can't write about all aspects of automation. Give me 
>>> details of specific issues.
>>> Slau
>>> 
>>> 
>>>> On Nov 14, 2019, at 6:06 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Hi, Slau, how give me a tips how automation works in ultimate∑ I am very 
>>>> confused in the automation window.
>>>> Thanks,
>>>> JP.
>>>> 
>>>>> On Nov 13, 2019, at 10:01 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>> Well, good for you! OK, now when you go to the Automation window, you'll 
>>>>> see buttons for writing to the start, end or entire length of the session 
>>>>> from beginning to end. With an Avid control surface, there are dedicated 
>>>>> buttons for these functions. Anyway, you'll have a much easier time with 
>>>>> Ultimate.
>>>>> Slau
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso 
>>>>>> mailto:jpcula...@gmail.com>> wrote:
>>>>>> 
>>>>>> Thanks, slau, I just installed it.
>>>>>> 
>>>>>> 
>>>>>>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn >>>>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>>>> 
>>>>>>> For controls like panning, where you want the value to remain the same, 
>>>>>>> use Latch mode. In other words, if you start from one set of values and 
>>>>>>> change while in Latch mode, the subsequent automation data will stay at 
>>>>>>> the last recorded value. This theoretically works with faders as well 
>>>>>>> but some people have had limited success doing it with faders. Pan 
>>>>>>> automation should work fine.
>>>>>>> 
>>>>>>> Now, you say you've upgraded to Ultimate? If you have, then the 
>>>>>>> automation process will be infinitely easier. Let me know when you have 
>>>>>>> it installed.
>>>>>>> Slau
>>>>>>> 
>>>>>>> 
>>>>>>>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso 
>>>>>>>> mailto:jpcula...@gmail.com>> wrote:
>>>>>>>> 
>>>>>>>> Absolutely amazing, slau.
>>>>>>>> And for panning? I tried some pan automation and for example, if the 
>>>>>>>> start point is 70 left 30 right and I go to 30 left and 70 right, 
>>>>>>>> after p

Re: Automation question.

[Juan Pablo Culasso Alonso]

Slau, here is an example of panning automation I put in latch mode but the 
parameter is not saved.

https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1
 
<https://www.dropbox.com/s/jrq345rs4tohn36/System%20Audio%2020191114%200114.mp3?dl=1>
Is a 59 seconds recording. can you check that? and tell me what is wrong?

Thanks,
Juan.
> On Nov 13, 2019, at 10:01 PM, Slau Halatyn  wrote:
> 
> Well, good for you! OK, now when you go to the Automation window, you'll see 
> buttons for writing to the start, end or entire length of the session from 
> beginning to end. With an Avid control surface, there are dedicated buttons 
> for these functions. Anyway, you'll have a much easier time with Ultimate.
> Slau
> 
> 
> 
>> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Thanks, slau, I just installed it.
>> 
>> 
>>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> For controls like panning, where you want the value to remain the same, use 
>>> Latch mode. In other words, if you start from one set of values and change 
>>> while in Latch mode, the subsequent automation data will stay at the last 
>>> recorded value. This theoretically works with faders as well but some 
>>> people have had limited success doing it with faders. Pan automation should 
>>> work fine.
>>> 
>>> Now, you say you've upgraded to Ultimate? If you have, then the automation 
>>> process will be infinitely easier. Let me know when you have it installed.
>>> Slau
>>> 
>>> 
>>>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Absolutely amazing, slau.
>>>> And for panning? I tried some pan automation and for example, if the start 
>>>> point is 70 left 30 right and I go to 30 left and 70 right, after press 
>>>> the stop button and play the track, the automation looks fine but after 
>>>> the end of the automation the track returns to the begining point. How to 
>>>> solve this and the track continues in 30 left 70 right?
>>>> I linked the paner
>>>> 
>>>> Thanks,
>>>> Juan.
>>>> I upgraded to ultimate
>>>>  and I want to use it at 100% in post production capabilities
>>>>> On Nov 13, 2019, at 12:40 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>> Replying here on the PTAccess list because that's where public questions 
>>>>> belong. My reply follows below the question.
>>>>> Begin forwarded message:
>>>>>> 
>>>>>> From: Juan Pablo Culasso Alonso >>>>> <mailto:jpcula...@gmail.com>>
>>>>>> Subject: Re: Automation question.
>>>>>> Date: November 12, 2019 at 11:34:55 PM EST
>>>>>> To: Slau Halatyn >>>>> <mailto:s...@besharpstudios.com>>
>>>>>> 
>>>>>> Hi, slau, but if I want to make some different. A track that is already 
>>>>>> playing and there is an other track that I want that begin at minus inf 
>>>>>> and ends at -3 db  and continues at -3db after automation ends?
>>>>>> 
>>>>>> Thanks again,
>>>>>> JP.
>>>>>> 
>>>>> Hi Juan,
>>>>> The thing to remember is that Pro Tools Ultimate can do this simply but 
>>>>> Pro Tools Vanilla has no way of doing this simply. What you need to 
>>>>> remember is, once you've written automation, that's the level that the 
>>>>> parameter will return to whenever you stop recording. So, if you wish to 
>>>>> end up at minus 3 dB, that's where you start right at the top with minus 
>>>>> 3 dB in write mode. Then start again from the top at minus infinity and 
>>>>> raise your level to minus 3 dB  and the track should then remain at minus 
>>>>> 3 dB for the rest of the timeline.
>>>>> 
>>>>> A guaranteed way of getting this result is to let the track play for its 
>>>>> entire duration while in write mode while you make your level adjustments.
>>>>> 
>>>>> Again, this is very straight-forward with PT Ultimate. If you do a lot of 
>>>>> automation all the time and you're using P

Fwd: Automation question.

[Juan Pablo Culasso Alonso]

> 
> Hello all,
> 
> Just for know.
> When I make an automation after put the mode in write, I need quickly turn 
> down completely the volume after press the play button and after make the 
> necessary curve.
> If I did not do it, and for example put the volume in 0 db, before press 
> play.. after end the automation, the track continues in volume minus infinite.
> Why? Is there a way that after automation the track continues in the same 
> level after end the automation?
> Slau talk about trim automation that is availabe in ultimate. How it works∑

-- 
You received this message because you are subscribed to the Google 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/C2C91CCB-18F4-488D-8208-24B9C4A2566A%40gmail.com.

Re: Automation question.

[Juan Pablo Culasso Alonso]

Sure, Slau.

I am reffering specifically to automate in protools ultimate.
I am in the automation window, and for example, I select 10 seconds
How can i automate this 10 seconds∑
When I press the button
Write Automation to Selection Start, for example, I get the message: No 
automation was written.
The same happens in Write Automation to Selection
If I press the button
Write Automation to Selection on Stop
It`s becomes selected, i press the play button, move the fader and when i 
return to the button
Write Automation to Selection
I got the same message


Other question is?
Even putting the mode in latch, in volume or pan automation, when press stop 
and go back to read, the last parameter when i left the fader is not remembered 
in volume or pan.

I reed the protools reference guide, tried to get som youtube tutorials but i 
did not advance too much.

Thanks again for your help and patience.
JP.

> On Nov 14, 2019, at 10:12 PM, Slau Halatyn  wrote:
> 
> Sorry Juan, Automation is complex and you'll need to be very specific with 
> your question. I can't write about all aspects of automation. Give me details 
> of specific issues.
> Slau
> 
> 
>> On Nov 14, 2019, at 6:06 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Hi, Slau, how give me a tips how automation works in ultimate∑ I am very 
>> confused in the automation window.
>> Thanks,
>> JP.
>> 
>>> On Nov 13, 2019, at 10:01 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Well, good for you! OK, now when you go to the Automation window, you'll 
>>> see buttons for writing to the start, end or entire length of the session 
>>> from beginning to end. With an Avid control surface, there are dedicated 
>>> buttons for these functions. Anyway, you'll have a much easier time with 
>>> Ultimate.
>>> Slau
>>> 
>>> 
>>> 
>>>> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Thanks, slau, I just installed it.
>>>> 
>>>> 
>>>>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>> For controls like panning, where you want the value to remain the same, 
>>>>> use Latch mode. In other words, if you start from one set of values and 
>>>>> change while in Latch mode, the subsequent automation data will stay at 
>>>>> the last recorded value. This theoretically works with faders as well but 
>>>>> some people have had limited success doing it with faders. Pan automation 
>>>>> should work fine.
>>>>> 
>>>>> Now, you say you've upgraded to Ultimate? If you have, then the 
>>>>> automation process will be infinitely easier. Let me know when you have 
>>>>> it installed.
>>>>> Slau
>>>>> 
>>>>> 
>>>>>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso 
>>>>>> mailto:jpcula...@gmail.com>> wrote:
>>>>>> 
>>>>>> Absolutely amazing, slau.
>>>>>> And for panning? I tried some pan automation and for example, if the 
>>>>>> start point is 70 left 30 right and I go to 30 left and 70 right, after 
>>>>>> press the stop button and play the track, the automation looks fine but 
>>>>>> after the end of the automation the track returns to the begining point. 
>>>>>> How to solve this and the track continues in 30 left 70 right?
>>>>>> I linked the paner
>>>>>> 
>>>>>> Thanks,
>>>>>> Juan.
>>>>>> I upgraded to ultimate
>>>>>>  and I want to use it at 100% in post production capabilities
>>>>>>> On Nov 13, 2019, at 12:40 PM, Slau Halatyn >>>>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>>>> 
>>>>>>> Replying here on the PTAccess list because that's where public 
>>>>>>> questions belong. My reply follows below the question.
>>>>>>> Begin forwarded message:
>>>>>>>> 
>>>>>>>> From: Juan Pablo Culasso Alonso >>>>>>> <mailto:jpcula...@gmail.com>>
>>>>>>>> Subject: Re: Automation question.
>>>>>>>> Date: November 12, 2019 at 11:34:55 PM EST
>>>>>>>>

Re: Automation question.

[Juan Pablo Culasso Alonso]

Hi, Slau, how give me a tips how automation works in ultimate∑ I am very 
confused in the automation window.
Thanks,
JP.

> On Nov 13, 2019, at 10:01 PM, Slau Halatyn  wrote:
> 
> Well, good for you! OK, now when you go to the Automation window, you'll see 
> buttons for writing to the start, end or entire length of the session from 
> beginning to end. With an Avid control surface, there are dedicated buttons 
> for these functions. Anyway, you'll have a much easier time with Ultimate.
> Slau
> 
> 
> 
>> On Nov 13, 2019, at 4:11 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Thanks, slau, I just installed it.
>> 
>> 
>>> On Nov 13, 2019, at 6:10 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> For controls like panning, where you want the value to remain the same, use 
>>> Latch mode. In other words, if you start from one set of values and change 
>>> while in Latch mode, the subsequent automation data will stay at the last 
>>> recorded value. This theoretically works with faders as well but some 
>>> people have had limited success doing it with faders. Pan automation should 
>>> work fine.
>>> 
>>> Now, you say you've upgraded to Ultimate? If you have, then the automation 
>>> process will be infinitely easier. Let me know when you have it installed.
>>> Slau
>>> 
>>> 
>>>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>> Absolutely amazing, slau.
>>>> And for panning? I tried some pan automation and for example, if the start 
>>>> point is 70 left 30 right and I go to 30 left and 70 right, after press 
>>>> the stop button and play the track, the automation looks fine but after 
>>>> the end of the automation the track returns to the begining point. How to 
>>>> solve this and the track continues in 30 left 70 right?
>>>> I linked the paner
>>>> 
>>>> Thanks,
>>>> Juan.
>>>> I upgraded to ultimate
>>>>  and I want to use it at 100% in post production capabilities
>>>>> On Nov 13, 2019, at 12:40 PM, Slau Halatyn >>>> <mailto:slauhala...@gmail.com>> wrote:
>>>>> 
>>>>> Replying here on the PTAccess list because that's where public questions 
>>>>> belong. My reply follows below the question.
>>>>> Begin forwarded message:
>>>>>> 
>>>>>> From: Juan Pablo Culasso Alonso >>>>> <mailto:jpcula...@gmail.com>>
>>>>>> Subject: Re: Automation question.
>>>>>> Date: November 12, 2019 at 11:34:55 PM EST
>>>>>> To: Slau Halatyn >>>>> <mailto:s...@besharpstudios.com>>
>>>>>> 
>>>>>> Hi, slau, but if I want to make some different. A track that is already 
>>>>>> playing and there is an other track that I want that begin at minus inf 
>>>>>> and ends at -3 db  and continues at -3db after automation ends?
>>>>>> 
>>>>>> Thanks again,
>>>>>> JP.
>>>>>> 
>>>>> Hi Juan,
>>>>> The thing to remember is that Pro Tools Ultimate can do this simply but 
>>>>> Pro Tools Vanilla has no way of doing this simply. What you need to 
>>>>> remember is, once you've written automation, that's the level that the 
>>>>> parameter will return to whenever you stop recording. So, if you wish to 
>>>>> end up at minus 3 dB, that's where you start right at the top with minus 
>>>>> 3 dB in write mode. Then start again from the top at minus infinity and 
>>>>> raise your level to minus 3 dB  and the track should then remain at minus 
>>>>> 3 dB for the rest of the timeline.
>>>>> 
>>>>> A guaranteed way of getting this result is to let the track play for its 
>>>>> entire duration while in write mode while you make your level adjustments.
>>>>> 
>>>>> Again, this is very straight-forward with PT Ultimate. If you do a lot of 
>>>>> automation all the time and you're using Pro Tools on a daily basis, 
>>>>> consider upgrading to Ultimate. It's expensive at first but it pays off 
>>>>> over the long run the more you use it.
>>>>> Slau
>>>>> 
>>>&g

Re: Automation question.

[Juan Pablo Culasso Alonso]

Thanks, slau, I just installed it.


> On Nov 13, 2019, at 6:10 PM, Slau Halatyn  wrote:
> 
> For controls like panning, where you want the value to remain the same, use 
> Latch mode. In other words, if you start from one set of values and change 
> while in Latch mode, the subsequent automation data will stay at the last 
> recorded value. This theoretically works with faders as well but some people 
> have had limited success doing it with faders. Pan automation should work 
> fine.
> 
> Now, you say you've upgraded to Ultimate? If you have, then the automation 
> process will be infinitely easier. Let me know when you have it installed.
> Slau
> 
> 
>> On Nov 13, 2019, at 2:44 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> Absolutely amazing, slau.
>> And for panning? I tried some pan automation and for example, if the start 
>> point is 70 left 30 right and I go to 30 left and 70 right, after press the 
>> stop button and play the track, the automation looks fine but after the end 
>> of the automation the track returns to the begining point. How to solve this 
>> and the track continues in 30 left 70 right?
>> I linked the paner
>> 
>> Thanks,
>> Juan.
>> I upgraded to ultimate
>>  and I want to use it at 100% in post production capabilities
>>> On Nov 13, 2019, at 12:40 PM, Slau Halatyn >> <mailto:slauhala...@gmail.com>> wrote:
>>> 
>>> Replying here on the PTAccess list because that's where public questions 
>>> belong. My reply follows below the question.
>>> Begin forwarded message:
>>>> 
>>>> From: Juan Pablo Culasso Alonso >>> <mailto:jpcula...@gmail.com>>
>>>> Subject: Re: Automation question.
>>>> Date: November 12, 2019 at 11:34:55 PM EST
>>>> To: Slau Halatyn mailto:s...@besharpstudios.com>>
>>>> 
>>>> Hi, slau, but if I want to make some different. A track that is already 
>>>> playing and there is an other track that I want that begin at minus inf 
>>>> and ends at -3 db  and continues at -3db after automation ends?
>>>> 
>>>> Thanks again,
>>>> JP.
>>>> 
>>> Hi Juan,
>>> The thing to remember is that Pro Tools Ultimate can do this simply but Pro 
>>> Tools Vanilla has no way of doing this simply. What you need to remember 
>>> is, once you've written automation, that's the level that the parameter 
>>> will return to whenever you stop recording. So, if you wish to end up at 
>>> minus 3 dB, that's where you start right at the top with minus 3 dB in 
>>> write mode. Then start again from the top at minus infinity and raise your 
>>> level to minus 3 dB  and the track should then remain at minus 3 dB for the 
>>> rest of the timeline.
>>> 
>>> A guaranteed way of getting this result is to let the track play for its 
>>> entire duration while in write mode while you make your level adjustments.
>>> 
>>> Again, this is very straight-forward with PT Ultimate. If you do a lot of 
>>> automation all the time and you're using Pro Tools on a daily basis, 
>>> consider upgrading to Ultimate. It's expensive at first but it pays off 
>>> over the long run the more you use it.
>>> Slau
>>> 
>>> 
>>>>> On Nov 12, 2019, at 3:23 PM, Slau Halatyn >>>> <mailto:s...@besharpstudios.com>> wrote:
>>>>> 
>>>>> Hi Juan,
>>>>> Pro Tools Ultimate allows for simple execution of what you're trying to 
>>>>> do. Without Ultimate, you have to follow these steps:
>>>>> 1. If you want the remaining part of the track to be at minus infinity, 
>>>>> you need to start there while in write mode. Set your fader all the way 
>>>>> down.
>>>>> 2. In write mode, press play for a little bit and press stop.
>>>>> 3. Go to the exact place where you want the track to be at 0 dB and set 
>>>>> your fader to 0 dB and make sure you're in Write mode again.
>>>>> 4. Start playback and lower the fader until it's all the way down then 
>>>>> press stop.
>>>>> 
>>>>> Your track will now stay down at infinite resistance.
>>>>> Hope that helps,
>>>>> Slau
>>>>> 
>>>>> 
>>>>>> On Nov 12, 2019, at 12:29 PM, Juan Pablo Culasso Alonso 
>>>>>> mailto:jpcula...@gmail.com>> wro

Re: Automation question.

[Juan Pablo Culasso Alonso]

Absolutely amazing, slau.
And for panning? I tried some pan automation and for example, if the start 
point is 70 left 30 right and I go to 30 left and 70 right, after press the 
stop button and play the track, the automation looks fine but after the end of 
the automation the track returns to the begining point. How to solve this and 
the track continues in 30 left 70 right?
I linked the paner

Thanks,
Juan.
I upgraded to ultimate
 and I want to use it at 100% in post production capabilities
> On Nov 13, 2019, at 12:40 PM, Slau Halatyn  wrote:
> 
> Replying here on the PTAccess list because that's where public questions 
> belong. My reply follows below the question.
> Begin forwarded message:
>> 
>> From: Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>>
>> Subject: Re: Automation question.
>> Date: November 12, 2019 at 11:34:55 PM EST
>> To: Slau Halatyn mailto:s...@besharpstudios.com>>
>> 
>> Hi, slau, but if I want to make some different. A track that is already 
>> playing and there is an other track that I want that begin at minus inf and 
>> ends at -3 db  and continues at -3db after automation ends?
>> 
>> Thanks again,
>> JP.
>> 
> Hi Juan,
> The thing to remember is that Pro Tools Ultimate can do this simply but Pro 
> Tools Vanilla has no way of doing this simply. What you need to remember is, 
> once you've written automation, that's the level that the parameter will 
> return to whenever you stop recording. So, if you wish to end up at minus 3 
> dB, that's where you start right at the top with minus 3 dB in write mode. 
> Then start again from the top at minus infinity and raise your level to minus 
> 3 dB  and the track should then remain at minus 3 dB for the rest of the 
> timeline.
> 
> A guaranteed way of getting this result is to let the track play for its 
> entire duration while in write mode while you make your level adjustments.
> 
> Again, this is very straight-forward with PT Ultimate. If you do a lot of 
> automation all the time and you're using Pro Tools on a daily basis, consider 
> upgrading to Ultimate. It's expensive at first but it pays off over the long 
> run the more you use it.
> Slau
> 
> 
>>> On Nov 12, 2019, at 3:23 PM, Slau Halatyn >> <mailto:s...@besharpstudios.com>> wrote:
>>> 
>>> Hi Juan,
>>> Pro Tools Ultimate allows for simple execution of what you're trying to do. 
>>> Without Ultimate, you have to follow these steps:
>>> 1. If you want the remaining part of the track to be at minus infinity, you 
>>> need to start there while in write mode. Set your fader all the way down.
>>> 2. In write mode, press play for a little bit and press stop.
>>> 3. Go to the exact place where you want the track to be at 0 dB and set 
>>> your fader to 0 dB and make sure you're in Write mode again.
>>> 4. Start playback and lower the fader until it's all the way down then 
>>> press stop.
>>> 
>>> Your track will now stay down at infinite resistance.
>>> Hope that helps,
>>> Slau
>>> 
>>> 
>>>> On Nov 12, 2019, at 12:29 PM, Juan Pablo Culasso Alonso 
>>>> mailto:jpcula...@gmail.com>> wrote:
>>>> 
>>>>> 
>>>>> Hello all,
>>>>> 
>>>>> Just for know.
>>>>> When I make an automation after put the mode in write, I need quickly 
>>>>> turn down completely the volume after press the play button and after 
>>>>> make the necessary curve.
>>>>> If I did not do it, and for example put the volume in 0 db, before press 
>>>>> play.. after end the automation, the track continues in volume minus 
>>>>> infinite.
>>>>> Why? Is there a way that after automation the track continues in the same 
>>>>> level after end the automation?
>>>>> Slau talk about trim automation that is availabe in ultimate. How it 
>>>>> works∑
>>>> 
>>>> 
>> 
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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/24689E05-9117-436C-A6A0-60F53EEEF0B9%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/24689E05-9117-436C-A6A0-60F53EEEF0B9%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/595E0879-ABF9-48B0-B9A6-D4D718D6F662%40gmail.com.

Automation question.

[Juan Pablo Culasso Alonso]

Hello all,

Just for know.
When I make an automation after put the mode in write, I need quickly turn down 
completely the volume after press the play button and after make the necessary 
curve.
If I did not do it, and for example put the volume in 0 db, before press play.. 
after end the automation, the track continues in volume minus infinite.
Why? Is there a way that after automation the track continues in the same level 
after end the automation?
Slau talk about trim automation that is availabe in ultimate. How it works∑

-- 
You received this message because you are subscribed to the Google 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/C6FB5A2D-104D-4E08-9CE9-66FCE8DB2610%40gmail.com.

New aves central

[Juan Pablo Culasso Alonso]

As you provably know, waves announced Its version 11 with a new waves central 
app. As you can imagine, this new waves central is totally inaccessible for 
VoiceOVer users.

JP

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/190DADA4-1376-4D20-83C1-D39DD2A004E3%40gmail.com.

flotools issue?

[Juan Pablo Culasso Alonso]

Hello,

latest protools and km9. The double press commands in all circunstances are not 
working, two times r to arm a track, two times command plus f1 to enter a 
value. Can you replicate this?

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/24F98F4E-6CE0-4C9F-83A6-ACFAA7D1781F%40gmail.com.

Re: To all S3-Users

[Juan Pablo Culasso Alonso]

Slau, how can I remap the encoders in a control sufrace? i am using artist mix

thanks,
jp

Enviado desde mi iPhone

> El 29 ago 2019, a las 15:05, Slau Halatyn  escribió:
> 
> Right, each surface can have its own specific mapping. Clearly, the S3 has 
> its own map because the threshold is the fourth knob on a C24. You do have 
> the option to create your own custom map if you'd like. Of course, there's 
> also the Flo Tools Plug-in Monitor feature that'll tell you exactly which 
> parameter is assigned to any knob or fader by simply touching it and, 
> further, reporting the current value and value changes. Of course, since the 
> threshold isn't seen by VoiceOver, that parameter won't be spoken but the 
> others are. HTH,
> Slau
> 
> 
>> On Aug 29, 2019, at 10:19 AM, 'Stefan Albertshauser' via Pro Tools 
>> Accessibility  wrote:
>> 
>> Hi,
>> 
>> Thanks Slau. I had my wife look at the display. The Threshold is the 8th 
>> knop.
>> 
>> Best
>> Stefan
>>> Am 28.08.2019 um 21:12 schrieb Slau Halatyn :
>>> 
>>> On some other surfaces, it's the fourth encoder or fader in flip mode. It 
>>> doesn't come up as a parameter. HTH
>>> 
>>> 
 On Aug 28, 2019, at 2:43 PM, 'Stefan Albertshauser' via Pro Tools 
 Accessibility  wrote:
 
 Hi,
 
 I’m trying to find the Threshold in Pro Limiter with my S3. Does anyone 
 know which knop this parameter is assigned to?
 
 Thanks in advance
 
 Stefan
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "Pro Tools Accessibility" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email toptaccess+unsubscr...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/ptaccess/0D6FFCCE-3A2C-418E-9A9C-1031E98BE062%40icloud.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/738F8A3A-99FF-4C37-97FE-273E81793578%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/666DA47F-2FD5-4DAA-B1BC-1F2DFF0E7772%40icloud.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/B515B63F-A489-4BC9-AB77-1F4A8D44F186%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/DCCF54B0-BBAC-441C-AD92-A17C1F64F02A%40gmail.com.

VOCR issue - Image magic not found

[Juan Pablo Culasso Alonso]

Hello,
Just trying install VOCR but when I open the import macros after run the 
install, a message says that: Image magic not found.
Using OsX 10.14.

Ideas?

Thanks
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Joy Bausch is here?

[Juan Pablo Culasso Alonso]

Thanks so much.

I just have one initial question. How insert a plugin and after it, the 
flotools plugin watch reads the information when I change the faders∑ sometimes 
it works, sometimes not. I do not be aware how thing am I wrong.

When inserted the 7 band eq and VoiceOver said the parameter info,, only the 
first fader changes the freq band. The others do not work. I need to press the 
page button to change other value, like mid freq gain, etc. How turn on the 
band, change Shelf, eTC∑

and lastly, how insert annother plugin that is not default in the protools 
preferences, or if I need to use, for example, waves ultra maximizer, I need to 
set it in the protools default eucon plugin?

Thanks in advance.
JP.
> On Mar 23, 2018, at 2:43 AM, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Hey Jp,
> i am in this list, but there are many people that work with the Artist Mix 
> controller, so just feel free to ask your question.
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 23.03.2018 um 00:38 schrieb Juan Pablo Culasso Alonso 
>> :
>> 
>> Hello all,
>> Just for know if Joy Bausch is yet in this list.
>> I have some questions about using an artist mix.
>> 
>> Thanks,
>> JP.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Joy Bausch is here?

[Juan Pablo Culasso Alonso]

Hello all,
Just for know if Joy Bausch is yet in this list.
I have some questions about using an artist mix.

Thanks,
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Artist mix

[Juan Pablo Culasso Alonso]

Hello list.
Finally an artist mix is in fornt of me. It has more keys than I expected. 
Sometime ago I wrote speciffically how it works inside plugins, automation, 
ETc. So the first question is:
How can I jump to fade flip mode to control the parameters using the faders and 
flotools watching plugin function?

Thanks,
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: More automation question.

[Juan Pablo Culasso Alonso]

Amazing, Slau.
It worked greatly.
Just for know, how works the trim automation in HD?

JP
> On 3 Sep 2017, at 10:55, Slau Halatyn  wrote:
> 
> I would say the best thing to do is to simply redo the automation in the 
> section you want. Make a selection of the range, turn on pre and post roll 
> and set the automation mode to Write. Make a pass and see if you're happy 
> with it. If not, set it to write mode again and repeat until you're satisfied.
> Hope that helps.
> 
>> On Sep 2, 2017, at 11:59 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hi, Slau.
>> Thanks for your explanation.
>> 
>> Do you know other approach to achieve that? Really jump to a Hd version are 
>> not in the horizon. I tried with some fades but the ressult is too far that 
>> I need.
>> 
>> JP.
>>> On 2 Sep 2017, at 21:08, Slau Halatyn  wrote:
>>> 
>>> JP,
>>> This mode is called Trim mode and I think it's only available in HD. All 
>>> values are proportionally raised or lowered by whatever amount the fader is 
>>> moved in Trim Mode. There might be a way to visually select several volume 
>>> break points but I know of no way to do that without visually editing 
>>> within the timeline.
>>> Slau
>>> 
>>>> On Sep 2, 2017, at 10:36 AM, Juan Pablo Culasso Alonso 
>>>>  wrote:
>>>> 
>>>> Hello all.
>>>> 
>>>> I've been wondering this for quite some time now...I'm not even sure if 
>>>> it's possible. Let's say in the middle of mixing a track, I want to fade 
>>>> some selection down at a certain point, and then fade them back up. I'd 
>>>> normally do this with volume automation. However, let's say a week later I 
>>>> want to change the overall volume of that track, but keep the automation. 
>>>> Is this possible? Whenever I try to change the volume on a track where 
>>>> automation is written, it slides the fader back to its original position. 
>>>> I guess I'm wondering if there's a way to proportionaly keep the 
>>>> automation in relation to the volume changes. Any help would be greatly 
>>>> appreciated. Thanks
>>>> JP
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: More automation question.

[Juan Pablo Culasso Alonso]

Hi, Slau.
Thanks for your explanation.

Do you know other approach to achieve that? Really jump to a Hd version are not 
in the horizon. I tried with some fades but the ressult is too far that I need.

JP.
> On 2 Sep 2017, at 21:08, Slau Halatyn  wrote:
> 
> JP,
> This mode is called Trim mode and I think it's only available in HD. All 
> values are proportionally raised or lowered by whatever amount the fader is 
> moved in Trim Mode. There might be a way to visually select several volume 
> break points but I know of no way to do that without visually editing within 
> the timeline.
> Slau
> 
>> On Sep 2, 2017, at 10:36 AM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hello all.
>> 
>> I've been wondering this for quite some time now...I'm not even sure if it's 
>> possible. Let's say in the middle of mixing a track, I want to fade some 
>> selection down at a certain point, and then fade them back up. I'd normally 
>> do this with volume automation. However, let's say a week later I want to 
>> change the overall volume of that track, but keep the automation. Is this 
>> possible? Whenever I try to change the volume on a track where automation is 
>> written, it slides the fader back to its original position. I guess I'm 
>> wondering if there's a way to proportionaly keep the automation in relation 
>> to the volume changes. Any help would be greatly appreciated. Thanks
>> JP
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Flotools - upgrading issues.

[Juan Pablo Culasso Alonso]

Just nothing, because the message when I resize the clips list

Clips table is 96 points wide. Click and drag to resize.


Does not come up when I press the sorcut to resize the tracklist.
Just for clarification, the track list is vissible.

Thanks,
JP.
> On 2 Sep 2017, at 15:14, Slau Halatyn  wrote:
> 
> HI JP,
> After you issue the Command+Control+Shift+t macro, exactly what are you doing 
> after that?
> 
> Slau
> 
>> On Sep 2, 2017, at 1:41 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hello Chi.
>> After uninstall flotools, delete all in keyboard maestro and reinstall 
>> flotools again,
>> The only macro that is not working for me now is resizing the track list.
>> Control+shift+command+t
>> 
>> JP
>>> On 2 Sep 2017, at 14:31, Chi Kim  wrote:
>>> 
>>> Juan, how does it not work. Need more information.
>>> 
>>> As far as shortcut conflicts, it seems like you manually changed 
>>> something before.
>>> 
>>> Flo Tools Mouse uses modifiers command+option+shift.
>>> 
>>> All other shortcuts you mentioned use command+control_+shift, it uses 
>>> control instead of option.
>>> 
>>> If it gives you list of commands when you execute a macro, that means 
>>> there's shortcut conflict. Keyboard Maestro doesn't know which one you 
>>> meant to execute because there are more than one commands with the same 
>>> shortcut.
>>> 
>>> However, there shouldn't be shortcut conflict in Flo Tools unless you 
>>> changed something. I just confirmed it.
>>> 
>>> However, if you use VOCR there is some conflicts.
>>> 
>>> 
>>> Chi
>>> 
>>> On 9/1/2017 6:51 PM, Juan Pablo Culasso Alonso wrote:
>>>> Hello,
>>>> I unistalled (again) Flotools, opened keyboard maestro, deleted the 
>>>> residual marcos, reinstalled flotools. Now almost looks fine exceptin the 
>>>> track resizing macro.
>>>> 
>>>> Best,
>>>> Juan.
>>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Flotools - upgrading issues.

[Juan Pablo Culasso Alonso]

Hello Chi.
After uninstall flotools, delete all in keyboard maestro and reinstall flotools 
again,
The only macro that is not working for me now is resizing the track list.
Control+shift+command+t

JP
> On 2 Sep 2017, at 14:31, Chi Kim  wrote:
> 
> Juan, how does it not work. Need more information.
> 
> As far as shortcut conflicts, it seems like you manually changed 
> something before.
> 
> Flo Tools Mouse uses modifiers command+option+shift.
> 
> All other shortcuts you mentioned use command+control_+shift, it uses 
> control instead of option.
> 
> If it gives you list of commands when you execute a macro, that means 
> there's shortcut conflict. Keyboard Maestro doesn't know which one you 
> meant to execute because there are more than one commands with the same 
> shortcut.
> 
> However, there shouldn't be shortcut conflict in Flo Tools unless you 
> changed something. I just confirmed it.
> 
> However, if you use VOCR there is some conflicts.
> 
> 
> Chi
> 
> On 9/1/2017 6:51 PM, Juan Pablo Culasso Alonso wrote:
>> Hello,
>> I unistalled (again) Flotools, opened keyboard maestro, deleted the residual 
>> marcos, reinstalled flotools. Now almost looks fine exceptin the track 
>> resizing macro.
>> 
>> Best,
>> Juan.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

More automation question.

[Juan Pablo Culasso Alonso]

Hello all.

 I've been wondering this for quite some time now...I'm not even sure if it's 
possible. Let's say in the middle of mixing a track, I want to fade some 
selection down at a certain point, and then fade them back up. I'd normally do 
this with volume automation. However, let's say a week later I want to change 
the overall volume of that track, but keep the automation. Is this possible? 
Whenever I try to change the volume on a track where automation is written, it 
slides the fader back to its original position. I guess I'm wondering if 
there's a way to proportionaly keep the automation in relation to the volume 
changes. Any help would be greatly appreciated. Thanks
JP

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Flotools - upgrading issues.

[Juan Pablo Culasso Alonso]

Hello,
I unistalled (again) Flotools, opened keyboard maestro, deleted the residual 
marcos, reinstalled flotools. Now almost looks fine exceptin the track resizing 
macro.

Best,
Juan.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Flotools - possible bugs.

[Juan Pablo Culasso Alonso]

Hello all,


I will put on the table different situations, tell me  if are bugs or the bug 
is me ?P

Before starting,
I am running the latest protools 12.8.1

The window is completely maximized.

1.
The sortcut to resize the track list is not working.

2
The sorcut to resize the clip list, when pressed, a keyboard maestro dialog 
apeare asking me to decide which macro I want to call, move mouse to the center 
of window or resize clip list.

3
Dragging clips to a track.
When I do the last sorcut command+option+list+, this message apeare:
Keyboard Maestro Engine Macro Cancelled Move or Click Mouse calculation 
point2.x+point2.width failed. Macro ‘Beta: Drag Clip’ cancelled (while 
executing Move and Click and Drag 

I tried it several times without success.

Finally, there is a conflit with sorcuts when panning change is necessary, 
again, keyboard maestro ask for chosing panning or move the mouse to the left 
or right.

Anyone can duplicate these?

Best,
Juan.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Volume - Step climb

[Juan Pablo Culasso Alonso]

Hello all.

I imagine that this question is vasic but…
what is the method to make a track volume step climb? Begin the clip with -30 
dB. After x seconds, up to -25 but smoothly, like a fade in, after x seconds 
again, continuing raising to -20, -15, etc, to make very softs transisions?

Thanks,
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessible loudness meter plug-ins for mastering

[Juan Pablo Culasso Alonso]

Hello.
When I say without difficulties is that the loudness applied is that presset  I 
selected.
If you  can install iZotope RX and test it as a demo.

> On 25 Aug 2017, at 11:16, Nickus de Vos  wrote:
> 
> Hi Juan
> Please elaborate on using them without difficulties. How much info and 
> details can you see, what ports are accessible and what parts not? I'll  go 
> check if they offer a demo Version.
> 
> Nickus
> Sent from my iPhone, please excuse any typos...
> 
> On 25 Aug 2017, at 15:53, Juan Pablo Culasso Alonso  <mailto:jpcula...@gmail.com>> wrote:
> 
>> Hello. In izotope rX, there is the izotope loudness control. There you have 
>> the pressets that matches all the differents type of loudness. I used them 
>> without dificulties.
>>> On 25 Aug 2017, at 10:34, Phil Muir >> <mailto:i...@accessibilitytraining.co.uk>> wrote:
>>> 
>>> Tools Alt T followed by the letter S for statistics.  You can then tab over
>>> and copy the data to notepad and it will most likely look something like
>>> this:
>>> 
>>>Left Channel
>>> Right Channel   
>>> Cursor position (Time)   00:00:00.000
>>> 00:00:00.000
>>> Sample value at cursor (dB)  -92.029
>>> -90.585 
>>> Minimum sample position (Time)   00:00:55.606
>>> 00:01:08.721
>>> Minimum sample value (dB)-1.021
>>> -1.021  
>>> Maximum sample position (Time)   00:00:56.092
>>> 00:00:12.405
>>> Maximum sample value (dB)-1.022
>>> -1.022  
>>> RMS level (dB)   -15.548
>>> -15.556 
>>> Average value (dB)   -Inf.
>>> -Inf.   
>>> Zero crossings (Hz)  1,703.44
>>> 1,585.26
>>> Maximum true peak sample position (Time) 00:02:21.047
>>> 00:02:18.652
>>> Maximum true peak sample value (dB)  -0.989
>>> -0.993  
>>> Maximum filtered true peak sample position (Time)00:00:16.736
>>> 00:00:20.089
>>> Maximum filtered true peak sample value (dB) -0.000
>>> -0.186  
>>> 
>>> Integrated Loudness (LUFS)-12.24
>>> Loudness Range (LU) 3.80
>>> Maximum True Peak Loudness (dBTP)-0.99
>>> Maximum Short-Term Loudness (LUFS)-10.13
>>> Maximum Momentary Loudness (LUFS)-8.48
>>> 
>>> -Original Message-
>>> From: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com> 
>>> [mailto:ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com>] On 
>>> Behalf
>>> Of Peter Bosher
>>> Sent: 25 August 2017 14:22
>>> To: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com>
>>> Subject: Re: Accessible loudness meter plug-ins for mastering
>>> 
>>> Hi Phil,
>>> 
>>> 
>>> You wrote:
>>> 
>>> 
>>> Can also easily check LUFS in Sound Forge 11
>>> 
>>> How do you do that please?
>>> 
>>> Best,
>>> 
>>> Peter
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this grou

Re: Accessible loudness meter plug-ins for mastering

[Juan Pablo Culasso Alonso]

Hello. In izotope rX, there is the izotope loudness control. There you have the 
pressets that matches all the differents type of loudness. I used them without 
dificulties.
> On 25 Aug 2017, at 10:34, Phil Muir  wrote:
> 
> Tools Alt T followed by the letter S for statistics.  You can then tab over
> and copy the data to notepad and it will most likely look something like
> this:
> 
>   Left Channel
> Right Channel   
> Cursor position (Time)00:00:00.000
> 00:00:00.000
> Sample value at cursor (dB)   -92.029
> -90.585 
> Minimum sample position (Time)00:00:55.606
> 00:01:08.721
> Minimum sample value (dB) -1.021
> -1.021  
> Maximum sample position (Time)00:00:56.092
> 00:00:12.405
> Maximum sample value (dB) -1.022
> -1.022  
> RMS level (dB)-15.548
> -15.556 
> Average value (dB)-Inf.
> -Inf.   
> Zero crossings (Hz)   1,703.44
> 1,585.26
> Maximum true peak sample position (Time)  00:02:21.047
> 00:02:18.652
> Maximum true peak sample value (dB)   -0.989
> -0.993  
> Maximum filtered true peak sample position (Time) 00:00:16.736
> 00:00:20.089
> Maximum filtered true peak sample value (dB)  -0.000
> -0.186  
> 
> Integrated Loudness (LUFS)-12.24
> Loudness Range (LU)3.80
> Maximum True Peak Loudness (dBTP) -0.99
> Maximum Short-Term Loudness (LUFS)-10.13
> Maximum Momentary Loudness (LUFS) -8.48
> 
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf
> Of Peter Bosher
> Sent: 25 August 2017 14:22
> To: ptaccess@googlegroups.com
> Subject: Re: Accessible loudness meter plug-ins for mastering
> 
> Hi Phil,
> 
> 
> You wrote:
> 
> 
>  Can also easily check LUFS in Sound Forge 11
> 
> How do you do that please?
> 
> Best,
> 
> Peter
> 
> -- 
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: update and simplification of procedure for resizing Track and Clips List tables with VoiceOver and Flo Tools

[Juan Pablo Culasso Alonso]

jpcula...@gmail.com
> On 2 May 2017, at 10:29, Slau Halatyn  wrote:
> 
> Sure. Which email address do you use for Drop Box?
> 
>> On May 1, 2017, at 10:56 PM, Juan Pablo Culasso  wrote:
>> 
>> Hi, Slau.As I reed in a previous e-mail, is there a dropbox folder were you 
>> put these tutorials?
>> If yes, how can I join this?
>> Thanks
>> Jp
>> 
>> 
>> 
>> 
>> Visita mi web
>> www.jpculasso.net
>> 
>>> El 1 may 2017, a las 12:41, Slau Halatyn  escribió:
>>> 
>>> I've updated the info on resizing the Track List and Clip List tables with 
>>> VoiceOver and Flo Tools. It's a bit simpler although the concept is still 
>>> the same.
>>> Slau
>>> 
>>> How to Resize the Track List and Clip List Tables with VoiceOver and Flo 
>>> Tools
>>> 
>>> Occasionally, it might be necessary to resize either the Track List or Clip 
>>> List. One might receive a session whose lists are either too narrow or too 
>>> wide. For example, when trying to click and drag a clip from the Clip List 
>>> table to the timeline, if the Clip List table is too narrow, as VoiceOver 
>>> navigates the table, the mouse pointer can end up outside of the actual 
>>> table, making it impossible to click and drag. The Track List and Clip List 
>>> tables can be resized (that is, widened or narrowed) by clicking and 
>>> dragging their borders, the right edge for the Track List and the left edge 
>>> for the Clip List. When the cursor is in the correct position laterally, 
>>> the mouse pointer changes shape to visually indicate that the table edge 
>>> will resize if dragged. For VoiceOver users, there’s no way to know when 
>>> the mouse pointer has changed shape. So here are instructions for how to 
>>> resize each table. The procedure is similar for each table but slightly 
>>> different. Before starting:
>>> 1. Make sure VoiceOver is set to report measurements in points rather than 
>>> inches. A point is a relative measurement and will be a different 
>>> measurement depending on your screen size and resolution but, regardless of 
>>> those variables, the relative size and location of UI elements will always 
>>> be the same point value on any Mac.  Go to VoiceOver Utility/Verbosity 
>>> category/Announcements tab and navigate to the "Announce Size and Position 
>>> In" pop-up menu and select "points."
>>> 2. Make sure there are no system dialogs or notifications blocking the Pro 
>>> Tools interface and close all floating Pro Tools windows.
>>> 3. Make sure the Flo Tools Mouse macro group is enabled. Press Command+/ 
>>> (slash) to toggle the group on or off.
>>> 4. Turn off the Flo Tools Inspector.
>>> 
>>> The objective is to route the mouse pointer to either the right edge of the 
>>> Track List table or the left edge of the Clip List table to drag the edge 
>>> to resize the respective tables. To determine the width of either table, 
>>> navigate to a table and press VO+Command+f3. VoiceOver will announce the 
>>> window name along with the session name and then report the width and 
>>> height in points. Pressing VO+Command+f3 again will report a table's 
>>> location across and down from the window's top left corner. Once the width 
>>> or height of the table is determined, the edge will always be a fixed 
>>> amount of horizontal points away.
>>> 
>>> Track List Table instructions:
>>> 1. Navigate to the Track List without interacting.
>>> Press VO+Command+f3. VoiceOver will report the width and height of the 
>>> table in points.
>>> 3. Add 23 points to the horizontal coordinate (the first value). For 
>>> example, if the Track List table is 86 points wide, add 23. The target 
>>> coordinates where we’d need to move the mouse pointer would be 109 points 
>>> right and either 28 points down if we’re in the Mix window or 112 points 
>>> down if we’re in the Edit window.
>>> 4. Use the "Move Mouse to Coordinates Relative to Current Window" macro to 
>>> move the mouse pointer. Press Command+Option+Shift+w and enter the 
>>> coordinates. Type the horizontal value (the value VoiceOver reported for 
>>> the Track List width plus 23), a comma then the vertical value (28 for the 
>>> Mix window or 112 for the Edit window) with no spaces and press Return. You 
>>> can verify the mouse pointer position with the flo Tools "Copy and Speak 
>>> Mouse Coordinates Relative to Front Window" macro by pressing 
>>> Command+Option+Shift+c.
>>> 5. Press VO+Command+Shift+Space Bar to mouse down on the Track List table 
>>> edge.
>>> 6. Drag the Mouse pointer either to the left to narrow or to the right to 
>>> widen the table using the Flo Tools Move Mouse shortcuts, 
>>> Command+Option+Shift+left or right arrow. Each press of the shortcut will 
>>> move the mouse pointer by 10 points.
>>> 7. Press Command+Option+Shift+Space Bar again to mouse up. You can verify 
>>> the results by navigating back to the table and pressing VO+Command+f3 once 
>>> and VoiceOver will report the new width and height of the table.
>>> 
>>> Clip List Table instructions:
>>> 1. N

Re: Flotools plugin views.

[Juan Pablo Culasso Alonso]

And just for clarification, the Control+left and right arrow are used in mision 
control.

Thanks.

> On 4 Jan 2017, at 20:11, Slau Halatyn  wrote:
> 
> Yep, thanks and nice catch, Brian ;) Kevin just had this exact issue and 
> posted on the Roger group about it. I'm thinking we might have to point out 
> the exact conflicts in the Flo Tools Read Me file. Cheers,
> Slau
> 
>> On Jan 4, 2017, at 4:42 PM, Brian Casey  
>> wrote:
>> 
>> Go to system preferences keyboard shortcuts and make sure control left/right 
>> arrows aren't being used for spotlight. 
>> 
>> Hope that helps
>> 
>> Sent from my smart-ish phone!
>> 
>>> On 4/01/2017, at 9:13 pm, Juan Pablo Culasso Alonso  
>>> wrote:
>>> 
>>> I again Slau.
>>> When I arrowing up or down with CTRL, I can navigate the column. However, 
>>> when arrowing to the right VO don`t say anything. This happen in default 
>>> and view 1 in the EQ7
>>> I didn`t try the other template.
>>> 
>>> Thanks,
>>> JP.
>>>> On 4 Jan 2017, at 18:03, Slau Halatyn  wrote:
>>>> 
>>>> OK, cool.
>>>> Slau
>>>> 
>>>>> On Jan 4, 2017, at 3:58 PM, Juan Pablo Culasso Alonso 
>>>>>  wrote:
>>>>> 
>>>>> Solved. I was checking the sistem library, I unhidden the user library 
>>>>> and found it.
>>>>> Thanks.
>>>>> 
>>>>>> On 4 Jan 2017, at 17:54, Slau Halatyn  wrote:
>>>>>> 
>>>>>> Which library are you checking, the user library or the system library?
>>>>>> 
>>>>>>> On Jan 4, 2017, at 3:42 PM, Juan Pablo Culasso Alonso 
>>>>>>>  wrote:
>>>>>>> 
>>>>>>> Hello all,
>>>>>>> 
>>>>>>> I just updated to version 2.01. But the folder with the plugin views is 
>>>>>>> not at the app-suport subfolder.
>>>>>>> 
>>>>>>> Ideas?
>>>>>>> 
>>>>>>> Best,
>>>>>>> 
>>>>>>> 
>>>>>>> Juan.
>>>>>>> 
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "Pro Tools Accessibility" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>>> an email to ptaccess+unsubscr...@googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Pro Tools Accessibility" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>> an email to ptaccess+unsubscr...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Pro Tools Accessibility" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Flotools plugin views.

[Juan Pablo Culasso Alonso]

Thanks. Worked..

> On 4 Jan 2017, at 18:42, Brian Casey  wrote:
> 
> Go to system preferences keyboard shortcuts and make sure control left/right 
> arrows aren't being used for spotlight. 
> 
> Hope that helps
> 
> Sent from my smart-ish phone!
> 
>> On 4/01/2017, at 9:13 pm, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> I again Slau.
>> When I arrowing up or down with CTRL, I can navigate the column. However, 
>> when arrowing to the right VO don`t say anything. This happen in default and 
>> view 1 in the EQ7
>> I didn`t try the other template.
>> 
>> Thanks,
>> JP.
>>> On 4 Jan 2017, at 18:03, Slau Halatyn  wrote:
>>> 
>>> OK, cool.
>>> Slau
>>> 
>>>> On Jan 4, 2017, at 3:58 PM, Juan Pablo Culasso Alonso 
>>>>  wrote:
>>>> 
>>>> Solved. I was checking the sistem library, I unhidden the user library and 
>>>> found it.
>>>> Thanks.
>>>> 
>>>>> On 4 Jan 2017, at 17:54, Slau Halatyn  wrote:
>>>>> 
>>>>> Which library are you checking, the user library or the system library?
>>>>> 
>>>>>> On Jan 4, 2017, at 3:42 PM, Juan Pablo Culasso Alonso 
>>>>>>  wrote:
>>>>>> 
>>>>>> Hello all,
>>>>>> 
>>>>>> I just updated to version 2.01. But the folder with the plugin views is 
>>>>>> not at the app-suport subfolder.
>>>>>> 
>>>>>> Ideas?
>>>>>> 
>>>>>> Best,
>>>>>> 
>>>>>> 
>>>>>> Juan.
>>>>>> 
>>>>>> -- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "Pro Tools Accessibility" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>> an email to ptaccess+unsubscr...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Pro Tools Accessibility" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Flotools plugin views.

[Juan Pablo Culasso Alonso]

I again Slau.
When I arrowing up or down with CTRL, I can navigate the column. However, when 
arrowing to the right VO don`t say anything. This happen in default and view 1 
in the EQ7
I didn`t try the other template.

Thanks,
JP.
> On 4 Jan 2017, at 18:03, Slau Halatyn  wrote:
> 
> OK, cool.
> Slau
> 
>> On Jan 4, 2017, at 3:58 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Solved. I was checking the sistem library, I unhidden the user library and 
>> found it.
>> Thanks.
>> 
>>> On 4 Jan 2017, at 17:54, Slau Halatyn  wrote:
>>> 
>>> Which library are you checking, the user library or the system library?
>>> 
>>>> On Jan 4, 2017, at 3:42 PM, Juan Pablo Culasso Alonso 
>>>>  wrote:
>>>> 
>>>> Hello all,
>>>> 
>>>> I just updated to version 2.01. But the folder with the plugin views is 
>>>> not at the app-suport subfolder.
>>>> 
>>>> Ideas?
>>>> 
>>>> Best,
>>>> 
>>>> 
>>>> Juan.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Flotools plugin views.

[Juan Pablo Culasso Alonso]

Solved. I was checking the sistem library, I unhidden the user library and 
found it.
Thanks.

> On 4 Jan 2017, at 17:54, Slau Halatyn  wrote:
> 
> Which library are you checking, the user library or the system library?
> 
>> On Jan 4, 2017, at 3:42 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> Hello all,
>> 
>> I just updated to version 2.01. But the folder with the plugin views is not 
>> at the app-suport subfolder.
>> 
>> Ideas?
>> 
>> Best,
>> 
>> 
>> Juan.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Flotools plugin views.

[Juan Pablo Culasso Alonso]

Hello all,

I just updated to version 2.01. But the folder with the plugin views is not at 
the app-suport subfolder.

Ideas?

Best,


Juan.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Waves plugins usability

[Juan Pablo Culasso Alonso]

This kind of answer will make me order this artist mix. A S3 is too much for 
the complexity of project that I do.

Thank you again,
JP.
> On Oct 21, 2016, at 13:20, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Hi Juan,
> the nice thing about this approach is that you'll learn the lay-out of 
> parameters rather quickly. Yes, you only have 8 encoders, or faders, if you 
> switch to Flip Mode, but usually the lay-out is so nicely organized, that you 
> easily keep track.
> For instance, the Waves Q10 Equalizer, has two frequency bands per page, so 5 
> pages for 10 bands.
> Each band always has gain, Frequency, and Q. The buttons on Artist Mix also 
> have functions, in this case band on/off, and Filter Type.
> If you spend time with a plugin, as you should anyways, you'll learn what 
> fader and button is mapped to in no time, and the more often you use the 
> plugin, the faster you'll be at going straight to a certain parameter.
> 
> Joy
> 
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 21.10.2016 um 17:15 schrieb Juan Pablo Culasso Alonso 
>> :
>> 
>> Hello, joy, as an artist mix user, can you tell me if the encoders are 
>> enough to use plugins with lots of parameters oor how many times do you need 
>> to use the button to change the page?
>> I really am planning to take antist mix so all the info that you can provide 
>> will be very much apreciated.
>> Best,
>> Juan. 
>>> On Oct 21, 2016, at 12:12, 'Joy Bausch' via Pro Tools Accessibility 
>>>  wrote:
>>> 
>>> Hi,
>>> I use them in both Logic and ProTools, mostly with an Avid Artist Mix DAW 
>>> Controller. In PT that's the best solution, imho, while in Logic it is 
>>> quite possible to change values with VO.
>>> In PT it works as well, but too slowly and not in a real-time, musical, way.
>>> 
>>> hth
>>> Joy
>>> 
>>> 
>>> 
>>> Von meinem iPhone gesendet
>>> 
>>>> Am 21.10.2016 um 15:59 schrieb HYP :
>>>> 
>>>> Hello does any one use the waves plugin and can change  the value fields   
>>>> When I   Load a WaVe plug-in I am not able to change the value field using 
>>>> regular VoiceOver keystrokes   but my gf was able to  manipulate it Using 
>>>> mouse, Does anyone have the same problem  and if so what are your 
>>>> workaround for this 
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Waves plugins usability

[Juan Pablo Culasso Alonso]

Hello, joy, as an artist mix user, can you tell me if the encoders are enough 
to use plugins with lots of parameters oor how many times do you need to use 
the button to change the page?
I really am planning to take antist mix so all the info that you can provide 
will be very much apreciated.
Best,
Juan. 
> On Oct 21, 2016, at 12:12, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Hi,
> I use them in both Logic and ProTools, mostly with an Avid Artist Mix DAW 
> Controller. In PT that's the best solution, imho, while in Logic it is quite 
> possible to change values with VO.
> In PT it works as well, but too slowly and not in a real-time, musical, way.
> 
> hth
> Joy
> 
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 21.10.2016 um 15:59 schrieb HYP :
>> 
>> Hello does any one use the waves plugin and can change  the value fields   
>> When I   Load a WaVe plug-in I am not able to change the value field using 
>> regular VoiceOver keystrokes   but my gf was able to  manipulate it Using 
>> mouse, Does anyone have the same problem  and if so what are your workaround 
>> for this 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Waves central

[Juan Pablo Culasso Alonso]

All,

someone wrote to waves about the complete unusability of their platform to 
download and activate the plugins?
I did that but they never answered me.

Best,
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IMPORTANT: announcing Flo Tools

[Juan Pablo Culasso Alonso]

Really amazing, it`s a new bunch of possibilities opening with this sets of 
scripts.

Best,
JP.
> On Oct 15, 2016, at 09:53, Rui Vilarinho  wrote:
> 
> Wow... for sure ... really  appreciated!!!
> Thank you very much to the group,
>> Rui Vilarinho 
>> - Original Message - 
>> From: Slau Halatyn 
>> To: ptaccess@googlegroups.com 
>> Sent: Friday, October 14, 2016 11:32 PM
>> Subject: IMPORTANT: announcing Flo Tools
>> 
>> Here’s an important new development for our community. A new free product 
>> specifically designed for blind users of Pro Tools has been released today 
>> and it’s called Flo Tools. Point your browsers at
>> http://flotools.github.io 
>> and get these free scripts for Pro Tools and, yes, we said, “scripts for Pro 
>> Tools.” You’ll need Keyboard Maestro to trigger them. These are scripts that 
>> perform and automate certain tasks and provide feedback through VoiceOver. 
>> Everything you need to know can be found at the web site. There’s a detailed 
>> Read Me file plus an “Intro to Flo Tools” mp3. This open source project will 
>> transform the way blind users use Pro Tools. Since it’s open source, other 
>> programmers can get involved and who knows what this might eventually lead 
>> to but, right now, it’s the most exciting development in Pro Tools 
>> accessibility this community has seen in years. Flo Tools is brought to you 
>> by Chi Kim, Rocco Fiorentino and Slau Halatyn.
>> 
>> The Flo Tools Team
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Which Mac model makes ProTools happy?

[Juan Pablo Culasso Alonso]

Hi have an iMac 27 inch late 2013 with 32 gb of ram and the fusion drive on it.
And a macbook pro early 2015 with 16 gb of ram and a SSD
Both of them with the processor maxed.

> On Aug 8, 2016, at 15:33, Phil Muir  wrote:
> 
> Very happy with my mid 2012 15 inch macbook pro. It runs pro tools great but 
> I put in an ssd drive and 16 gv of ram.
> 
> On 8 August 2016 17:18:15 CEST, Rocco Fiorentino 
>  wrote:
> Hi all,
> 
> I’m thinking about selling/replacing laptops, and had a few thoughts. I have 
> both a 2012 and 2014 MacBook Pro. The 2012 machine seems to run ProTools 
> better then the 2014 computer, but they both still have significant issues 
> with playback, recording, lag, etc. So, do I sell both laptops and get a 
> desktop? Then I can’t travel anywhere if I need to record. Or, do I get a 
> desktop and MacBook Air for traveling? I already store my sessions on an 
> external drive, but is this not enough cpu/processor power? Or maybe a Mac 
> mini? Or just an iMac desktop and another MacBook Pro?
> I’m curious what has worked for you, and what you find produces the best 
> environment for ProTools to operate successfully. For anyone running the 
> public or developer betas of Sierra, you’ll notice that PT runs amazingly 
> well on it, even though it’s not supported officially yet. However, Karabiner 
> is broken in 10.12 Sierra, making protools unusable for me on a laptop
> without an external keyboard for a numbpad. The developer is aware, but 
> apparently he has to rewrite the entire UI…
> 
> Thanks in advance for all of your help and suggestions.
> 
> Rocco
> 
> -- 
> Regards,
> Accessibility Training
> Telephone: UK +44-1747-228-459
> Mobile: UK +44-7968-136-246
> E-mail:
> i...@accessibilitytraining.co.uk
> URL:
> http://www.accessibilitytraining.co.uk 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Q: does PT V12.5.2 work with Roland Quad-capture audio interface?

[Juan Pablo Culasso Alonso]

I Use Quad-capture with pt 12.5.2 without issues.
Best,
JP.
> On Aug 3, 2016, at 17:47, TheOreoMonster  wrote:
> 
> So long as you have the core audio drivers for it installed i see no
> reason why it wouldn't work with PT.
> 
> On 8/3/16, 'Patrick Schuppe' via Pro Tools Accessibility
>  wrote:
>> Hello everyone,
>> Does PT 12.5.2 work with my Roland quad-capture that I have used with
>> Windows?
>> I am asking because I setup my test-system tomorrow. My control s49 and
>> ultimate is allready here. Hope it will work. I will just use it to hear
>> the synth sounds over it. Thats all I will use it for and may be connecting
>> 
>> a Micro for singing.
>> Thanks in atvance:-)
>> Patrick
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: audio tutorial on dragging clips to the timeline in Pro Tools with VoiceOver

[Juan Pablo Culasso Alonso]

Thank you so much, Slau!.
I really apreciated the demonstration, looks completely well now I did my own 
tests with the expected results.
Best,
JP.
> On Jul 27, 2016, at 15:03, Slau Halatyn  wrote:
> 
> Folks,
> 
> This subject has come up so many times over the years and, while it was 
> easier many years ago and then it wasn’t so easy, it’s now easier than ever. 
> I’ve put together an audio tutorial on how to do it. Keep in mind that each 
> example I give takes moments but, having to explain it and go through it step 
> by step makes the process seem fifty times longer than the process actually 
> is. Dragging clips to the timeline in Pro Tools, especially if you use 
> Keyboard Maestro, is super easy and, in fact, you don’t even need Keyboard 
> Maestro necessarily. Most important, however, in this tutorial, I show how to 
> drop multiple clips into the timeline into one single track with clips 
> dropping into sequential order onto the one track. For those who are 
> interested, please file this mp3 away (because I tend to lose track of these 
> things) and, next time somebody asks, please throw this their way. Here’s a 
> link to it:
> https://dl.dropboxusercontent.com/u/3016244/Dragging%20Clips%20to%20the%20Timeline%20with%20VoiceOver.m4a
> 
> 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.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jog/sutle between tracks.

[Juan Pablo Culasso Alonso]

That’s correct Slau.
each  clip are in separate tracks.
I selected one of this, Cuted and pasted it after the other one in the timeline.
I use an artist transport so There is a nice sorcut to select one track at a 
time.
How can import multiple audio clips to one track?
Thank you,
JP.
> On Jul 21, 2016, at 12:38, Slau Halatyn  wrote:
> 
> Hi JP,
> 
> When you say you’ve imported audio files to tracks, do you mean that, after 
> importing to new tracks, you then cut and pasted them into one audio track? 
> If you’re shuttling through a track that has a clip in it, you’ll be able to 
> hear it but, if the second clip resides in another track, you won’t hear it 
> in shuttle mode or scrub mode. Rewind and Fast Forward works differently and 
> all tracks are heard in bits and pieces while moving in rewind or fast 
> forward. I would double-check to make sure that the second clip is actually 
> on the very same audio track as the first clip. If you need them to be on 
> separate tracks, you’ll need to select the second track to be able to monitor 
> the clip in shuttle mode. You can use Control-semicolon and Control-p to 
> select the next lower track or upper track respectively. Hope that helps,
> Slau
> 
>> On Jul 20, 2016, at 8:51 PM, Juan Pablo Culasso Alonso  
>> wrote:
>> 
>> All;
>> 
>> I imported files to tracks. When I cut one of this and paste it after the 
>> other, putting a second of silence and return to the begin of the session. I 
>> navigate with the jog or sutle and when the first track ends, I can continue 
>> navigating but without playback. I know that I am moving because the main 
>> counter changes. If I press play, the sound come up. if I use the num pad to 
>> FF or RW, I have sound. but when I tried use the jog or sutle, nothing. If I 
>> return to the begin of the session, I have again sound response until the 
>> end of the first track.
>> ideas?
>> Thanks,
>> JP.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jog/sutle between tracks.

[Juan Pablo Culasso Alonso]

All;

I imported files to tracks. When I cut one of this and paste it after the 
other, putting a second of silence and return to the begin of the session. I 
navigate with the jog or sutle and when the first track ends, I can continue 
navigating but without playback. I know that I am moving because the main 
counter changes. If I press play, the sound come up. if I use the num pad to FF 
or RW, I have sound. but when I tried use the jog or sutle, nothing. If I 
return to the begin of the session, I have again sound response until the end 
of the first track.
ideas?
Thanks,
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Editing problem, please please help!

[Juan Pablo Culasso Alonso]

I believe that you need change the edition mode to Spot. Use F3 to do it.
Best,
JP.
> On Jul 18, 2016, at 17:07, Jesse Kragiel  wrote:
> 
> When I edit a track, say a vocal, instead of just keeping everything in time, 
> time is deleted from the vocal. For instance, if I'm trimming the noise from 
> the beginning of the vocal, and select from the start of the song to the 
> start of the vocal and press delete, instead of just deleting all the data I 
> don't want, it actually is moving the vocal back to the beginning of the 
> song, making it out of sync with the music. It only does this in certain 
> files, and others work just fine. What could be the problem, and how do I fix 
> it? Thanks in advance for any help you can give.
> Jesse
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sound mixer question.

[Juan Pablo Culasso Alonso]

Hi all.
May be someone of you can give me an idea what is the best choice.
I need a device that hasa 3.5mm input and output, with at least four RCA input 
and output with at least 2 xlr input and ouput.
There are hundreds of diferents sound mixers and I am really lost.
All your help be very much apreciated.
thanks.
Juan.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: iZotope Ozone 7

[Juan Pablo Culasso Alonso]

Hi, Slau.
Yes, I’m use rx for the last three years and the installer is 100% accessible.
I just wanted install ozone 7 advanced because now it offers a standalone 
version and I found that problem at the very first step.

Best,
JP.
> On May 15, 2016, at 10:58, Slau Halatyn  wrote:
> 
> That's interesting to hear. Is the Ozone installer any different from the RX 
> installer? The RX installer is completely accessible. It would be a curious 
> thing if the installer were different but I guess more than one person has 
> experienced this.
> Slau
> 
> On May 15, 2016, at 3:02 AM, Phil Muir  <mailto:i...@accessibilitytraining.co.uk>> wrote:
> 
>> The installer is inaccessible on the Mac and also inaccessible unless you 
>> are using a screen reader on Windows such as Jaws.
>> 
>> On 14 May 2016 23:20:02 BST, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> All,
>> 
>> someone tried install izotope ozone 7? 
>> the installer seems not accessible. 
>> Thanks.
>> JP.
>> 
>> -- 
>> Regards,
>> Accessibility Training
>> Telephone: UK +44-1747-228-459
>> Mobile: UK +44-7968-136-246
>> E-mail:
>> i...@accessibilitytraining.co.uk <mailto:i...@accessibilitytraining.co.uk>
>> URL:
>> http://www.accessibilitytraining.co.uk 
>> <http://www.accessibilitytraining.co.uk/>
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

iZotope Ozone 7

[Juan Pablo Culasso Alonso]

All,

someone tried install izotope ozone 7? 
the installer seems not accessible. 
Thanks.
JP.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Juan Pablo Culasso Alonso]

Well, you can manage the time Freq edition.

> On Aug 27, 2015, at 23:54, Steve Martin  wrote:
> 
> 100% accessible? Are you able to work with the spectrogram and etc?
>> On Aug 27, 2015, at 5:34 PM, Juan Pablo Culasso Alonso > <mailto:jpcula...@gmail.com>> wrote:
>> 
>> RX4 has his stand alone app 100% accessible. I use the advanced version but 
>> for demonising purposes the standard will make the job.
>> 
>> 
>>> On Aug 27, 2015, at 18:29, Christopher-Mark Gilland >> <mailto:clgillan...@gmail.com>> wrote:
>>> 
>>> Guys,
>>>  
>>> I have a cassette tape that I'm trying to remove a major! and I do mean 
>>> major! hiss from.  It's me as a child, and it has some of the worst quality 
>>> tape recording audio I've ever heard.  No doubt, my parents must a recorded 
>>> this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't gonna 
>>> get rid a this.
>>>  
>>> Anyway, has anyone used either the Isotope RX4 Standard or Advanced, 
>>> preferably Standard plugins with PT?  If so, are they even somewhat 
>>> accessible?  I'm thinking I'll probably use the D-Noise module.
>>>  
>>> If not that accessible, if I just wanna see, though probably not advisable, 
>>> if it just naturally with no tweaking would make it a little better, do you 
>>> think just popping it on an insert and being done with it would possibly 
>>> even get rid of the slightest bit, even if not enough to be desirable?
>>>  
>>> If it's not accessible, does anyone have custom made presets that'll help 
>>> me?  If not, what other plugs would be accessible that may help with this.  
>>> It's not really a hum type of hiss.  It's more the type background air 
>>> noise kind a hiss you heard when recording on real cheap consumer grade 
>>> little portable pocket tape recorders with the built in mikes.  Like 
>>> something you'd buy at Radio Shaq or Circuit Shitty.
>>>  
>>> Chris.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com 
>>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com 
>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Isotope RX4?

[Juan Pablo Culasso Alonso]

RX4 has his stand alone app 100% accessible. I use the advanced version but for 
demonising purposes the standard will make the job.


> On Aug 27, 2015, at 18:29, Christopher-Mark Gilland  
> wrote:
> 
> Guys,
>  
> I have a cassette tape that I'm trying to remove a major! and I do mean 
> major! hiss from.  It's me as a child, and it has some of the worst quality 
> tape recording audio I've ever heard.  No doubt, my parents must a recorded 
> this on a real el cheapo tape recorder.  It's horriffic!  E Q isn't gonna get 
> rid a this.
>  
> Anyway, has anyone used either the Isotope RX4 Standard or Advanced, 
> preferably Standard plugins with PT?  If so, are they even somewhat 
> accessible?  I'm thinking I'll probably use the D-Noise module.
>  
> If not that accessible, if I just wanna see, though probably not advisable, 
> if it just naturally with no tweaking would make it a little better, do you 
> think just popping it on an insert and being done with it would possibly even 
> get rid of the slightest bit, even if not enough to be desirable?
>  
> If it's not accessible, does anyone have custom made presets that'll help me? 
>  If not, what other plugs would be accessible that may help with this.  It's 
> not really a hum type of hiss.  It's more the type background air noise kind 
> a hiss you heard when recording on real cheap consumer grade little portable 
> pocket tape recorders with the built in mikes.  Like something you'd buy at 
> Radio Shaq or Circuit Shitty.
>  
> Chris.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.