Re: Flo Tools

[Ricky Prevatte]

Could you add me to the dropbox as well please?

Sent from my iPhone

> On Mar 12, 2019, at 1:11 PM, jimmie smith  
> wrote:
> 
> W

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

Re: Flo Tools

[Slau Halatyn]

Not sure which Read Me you're referring to. Hot Spots are a VoiceOver feature 
rather than a Pro Tools thing and they're somewhat unreliable. There are a lot 
of PDF manuals so it'll take a lot of reading. Start with Intro to Pro Tools 
and then start hitting the Reference Guide. HTML version is in the Drop Box.
HTH,
Slau


> On Mar 12, 2019, at 1:11 PM, jimmie smith  
> wrote:
> 
> Will the read me explain how to make hot spots, make a selection, and edit 
> audio?  If not, where should I go to find this info?  Switching from sonar to 
> pro tools and a iMac 21.
> 
> 
> 
> Jimmie Smith
> A+ and MCSA Certified
> 
> -- 
> You received this message because you are subscribed to the Google 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.

Flo Tools

[jimmie smith]

Will the read me explain how to make hot spots, make a selection, and edit 
audio?  If not, where should I go to find this info?  Switching from sonar to 
pro tools and a iMac 21.



Jimmie Smith
A+ and MCSA Certified

-- 
You received this message because you are subscribed to the Google 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: Understanding question - plug-in views

[Slau Halatyn]

Hi Martin,
I've updated the version number to reflect your change. The default view is 
loaded automatically. there's no need to specifically press Command 0. The 
reason for the multiple view files is for plug-ins that have tabs. Not all 
plug-ins have tabs. When they do, it makes sense for the order of the tabs to 
follow a 1 2 3 order.
HTH,
Slau


> On Mar 12, 2019, at 6:29 AM, Martin (Punky) Sopart  wrote:
> 
> Hello!
> 
> I found a version number in the Superior Drummer MultiOut.txt
> This view is loaded by pressing Command+0
> For my it looks the same like the Superior Drummer MultiOut-1.txt
> Only the version number is missing here.
> 
> My idea was updating the version number because of the changes fort he
> Electric EZX. 
> But I'm a little comfused about the two similar text files.
> 
> Can someone help me out here?
> 
> Thanks and best! / Martin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> 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.

Understanding question - plug-in views

[Martin (Punky) Sopart]

Hello!

I found a version number in the Superior Drummer MultiOut.txt
This view is loaded by pressing Command+0
For my it looks the same like the Superior Drummer MultiOut-1.txt
Only the version number is missing here.

My idea was updating the version number because of the changes fort he
Electric EZX. 
But I'm a little comfused about the two similar text files.

Can someone help me out here?

Thanks and best! / Martin

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

RE: midi event list problem

[Martin (Punky) Sopart]

Hi Tom and others!

I have no problems when using a German Mac OS for years now.
Very important is to set the Pro Tools language to English in Pro Tools setup 
menu and to add a English US keyboard in the system preferences.

For other reasons I already set my Mac from German to English OS some time ago.
This also can be done in the system preferences under language very easily.
It takes some time and restarts, but more and more the Mac becomes English.

Best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Tom Hessels
> Sent: Tuesday, March 12, 2019 10:55 AM
> To: ptaccess@googlegroups.com
> Subject: RE: midi event list problem
> 
> Hi Slau,
> 
> 
> 
> Thank you! Indeed, this helps.
> 
> I found that the standard punctuation setting in vo is Some.
> 
> About the language: as I allready wrote I encountered more problems when
> using the dutch version of macos. The problem is that when you buy a mac
> it’s most of the time configured in the language of your country.
> 
> 
> 
> Tom.
> 
> 
> 
> 
> 
> 
> 
> Van: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> Namens Slau Halatyn
> Verzonden: vrijdag 8 maart 2019 23:27
> Aan: PTAccess List 
> Onderwerp: Re: midi event list problem
> 
> 
> 
> Hi Tom,
> 
> 
> 
> There are several things that I need to point out.
> 
> 1. The Flo Tools Read Me clearly states early on that only English operating
> systems are currently supported by Flo Tools. We can't do anything about
> that limitation at this time.
> 
> 
> 
> 2. You're listening to an older demo that is not applicable right now. The 
> MIDI
> Event List doesn't need to be opened anymore for Flo Tools to access MIDI
> information for editing.
> 
> 
> 
> 3. You shouldn't necessarily change the keyboard shortcuts in Flo Tools
> unless you have a very good reason. The shortcuts you were reading as
> "Option Shift" were actually displaying "Option Shift ]" which, if your
> punctuation is not reading out every character, would miss the "]" or Right
> Bracket, Left Bracket, etc.
> 
> 
> 
> 4. Your MIDI and/or instrument tracks need to be in Notes view in order to
> edit MIDI from the Mix or Edit windows. It's no longer necessary to use
> Control as a modifier.
> 
> 
> 
> Hope that helps,
> 
> 
> 
> Slau
> 
> 
> 
> 
> 
> 
> 
>   On Mar 7, 2019, at 7:02 AM, Tom Hessels   > wrote:
> 
> 
> 
>   Hi Slau and others,
> 
> 
> 
>   It’s allready a few months ago that  i wrote about my flo tools/midi
> event list problem.
> 
>   One of the things that can cause the problem was my dutch macos.
> 
>   I decided to reset my mac and install englesh macos.
> 
>   To work with flo tools you have to check a few things in the edit
> toolbar options menu such as transport.
> 
>   With the dutch version voiceover did not say if something is checked
> or not.
> 
>   With the english version of macos vo tells me the state of the
> checkboxes.
> 
>   With the dutch version i had a problem with Velvet, When i load teh
> plugin i get the message content not found.
> 
>   Searching on the internet shows that there are more people with this
> problem but no aducate solution.
> 
>   With the english os this error did not occur.
> 
>   I figured out that the probem was the mapname.
> 
>   Velvet is installed in the application map. In dutch this map is called
> Programma’s.
> 
>   Allthough velvet and its content was installed in the right map in the
> dutch version of macos it doesn’t work. Perhaps mapnames are hardwired.
> 
>   So if people on the list that are not native english speakers as i and
> use a non englesh macos perhaps installing the englesh macos may help.
> 
>   That brings me to the event list problem.
> 
>   Control arrow left and right stil didn’t work.
> 
>   And as you showed in your demo of flotools 2 (you can find it in the
> dropbox) It would be very helpful if it works.
> 
>   So i took a look in the flo tools scripts.
> 
>   First of all i don’t know much about keyboard maestro scripting so
> perhaps i did things that i can better not do .
> 
>   In the macro group scroll area i choose flo tools midi events list macro
> groups.
> 
>   In the macros scroll area i navigate to Next column Option Shift
> macro.
> 
>   What i didn’t understand was this Option Shift. I thougt that i should
> see control arror right.
> 
>   But perhaps ist due to may missing knoledge
> 
>   But i edit the macro a changed the trigger from Option Shift in control
> arrow right.
> 
>   And now it works.
> 
>   Also the previous column macro shows that Option Shift trigger.
> 
>   I change this too and now it works as aspected.
> 
>   Of caurse it is nice for me that it is working now but i want
> understand how this works and why the trigger original is Option Shift. I like
> to lern from the things i do.
> 
>   

RE: midi event list problem

[Tom Hessels]

Hi Slau,

 

Thank you! Indeed, this helps.

I found that the standard punctuation setting in vo is Some.

About the language: as I allready wrote I encountered more problems when using 
the dutch version of macos. The problem is that when you buy a mac it’s most of 
the time configured in the language of your country.

 

Tom.

 

 

 

Van: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] Namens Slau 
Halatyn
Verzonden: vrijdag 8 maart 2019 23:27
Aan: PTAccess List 
Onderwerp: Re: midi event list problem

 

Hi Tom,

 

There are several things that I need to point out.

1. The Flo Tools Read Me clearly states early on that only English operating 
systems are currently supported by Flo Tools. We can't do anything about that 
limitation at this time.

 

2. You're listening to an older demo that is not applicable right now. The MIDI 
Event List doesn't need to be opened anymore for Flo Tools to access MIDI 
information for editing.

 

3. You shouldn't necessarily change the keyboard shortcuts in Flo Tools unless 
you have a very good reason. The shortcuts you were reading as "Option Shift" 
were actually displaying "Option Shift ]" which, if your punctuation is not 
reading out every character, would miss the "]" or Right Bracket, Left Bracket, 
etc.

 

4. Your MIDI and/or instrument tracks need to be in Notes view in order to edit 
MIDI from the Mix or Edit windows. It's no longer necessary to use Control as a 
modifier.

 

Hope that helps,

 

Slau

 





On Mar 7, 2019, at 7:02 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

 

Hi Slau and others,

 

It’s allready a few months ago that  i wrote about my flo tools/midi event list 
problem.

One of the things that can cause the problem was my dutch macos.

I decided to reset my mac and install englesh macos.

To work with flo tools you have to check a few things in the edit toolbar 
options menu such as transport.

With the dutch version voiceover did not say if something is checked or not.

With the english version of macos vo tells me the state of the checkboxes.

With the dutch version i had a problem with Velvet, When i load teh plugin i 
get the message content not found.

Searching on the internet shows that there are more people with this problem 
but no aducate solution.

With the english os this error did not occur.

I figured out that the probem was the mapname.

Velvet is installed in the application map. In dutch this map is called 
Programma’s.

Allthough velvet and its content was installed in the right map in the dutch 
version of macos it doesn’t work. Perhaps mapnames are hardwired.

So if people on the list that are not native english speakers as i and use a 
non englesh macos perhaps installing the englesh macos may help.

That brings me to the event list problem.

Control arrow left and right stil didn’t work.

And as you showed in your demo of flotools 2 (you can find it in the dropbox) 
It would be very helpful if it works.

So i took a look in the flo tools scripts.

First of all i don’t know much about keyboard maestro scripting so perhaps i 
did things that i can better not do .

In the macro group scroll area i choose flo tools midi events list macro groups.

In the macros scroll area i navigate to Next column Option Shift macro.

What i didn’t understand was this Option Shift. I thougt that i should see 
control arror right.

But perhaps ist due to may missing knoledge

But i edit the macro a changed the trigger from Option Shift in control arrow 
right.

And now it works.

Also the previous column macro shows that Option Shift trigger.

I change this too and now it works as aspected.

Of caurse it is nice for me that it is working now but i want understand how 
this works and why the trigger original is Option Shift. I like to lern from 
the things i do. 

Second part of your’demo where you close the event list and use the tab key an 
control arrow keys to navigate still don’t work for me.

Sorry for This was a long post but I’m veru corious.

Tom.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Van: ptaccess@googlegroups.com   
[mailto:ptaccess@googlegroups.com] Namens Slau Halatyn
Verzonden: donderdag 20 december 2018 14:24
Aan: PTAccess List mailto:ptaccess@googlegroups.com> >
Onderwerp: Re: midi event list problem

 

Well, one thing I can say is that Flo Tools currently only supports English. 
That's probably not what's going on here but, I'll look into it shortly.

Slau

 

On Dec 20, 2018, at 8:19 AM, Tom Hessels <  
tomhessel...@gmail.com> wrote:

 

Hi Slau,

It is your flotools 2.2 demo and your demo about midi starts about 18 minutes.

In the second part whre you stopped working with the midi event list en 
starting using tabkay and control-arrow keys to navigate the tabkey don’t 
trigger anny note (no sound).

I’m using pro tools 2018-7, the latest flotools version, keyboard maestro 8.2.4

And macos 10.12.6 Sierra dutch