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 <ptaccess@googlegroups.com>
> 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 <tomhessel...@gmail.com
> <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 <smile>.
> 
>       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>
> [mailto:ptaccess@googlegroups.com] Namens Slau Halatyn
>       Verzonden: donderdag 20 december 2018 14:24
>       Aan: PTAccess List <ptaccess@googlegroups.com
> <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 <mailto: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 version.
> 
>               What I can try is to change macos to English version.
> 
>               But I can’t imagine that that is the problem but you never
> know.
> 
>               If there are other dutch pro tools users on this list please let
> me know if you have this kind of problems.
> 
>               Tom.
> 
> 
> 
> 
> 
> 
> 
>               From: ptaccess@googlegroups.com
> <mailto:ptaccess@googlegroups.com>  [mailto:ptaccess@googlegroups.com
> <mailto:ptaccess@googlegroups.com> ] On Behalf Of Slau Halatyn
>               Sent: woensdag 19 december 2018 18:06
>               To: PTAccess List
>               Subject: Re: midi event list problem
> 
> 
> 
>               Hi Tom,
> 
>               I'm not sure precisely which demo you're referring to and
> varius demos were made at various times where certain features either
> were or weren't available within Pro Tools so I'm not sure exactly how to
> answer your question. Since you mentioned Control Command Enter, I take
> it you're already using Flo Tools and possibly referring to the Flo Tools demo
> on MIDI editing. If you can confirm that, I'll look into it and see what 
> issue you
> might be running into.
> 
>               Slau
> 
> 
> 
>                       On Dec 19, 2018, at 6:24 AM, Tom Hessels
> <tomhessel...@gmail.com <mailto:tomhessel...@gmail.com> > wrote:
> 
> 
> 
>                       Hi All,
> 
> 
> 
>                       I just listen to the demo from Slau about using the
> midi event list.
> 
>                       The option-p, option-a etc works fine. But when I use
> the control plus arrow keys I hear the notes but voiceover says nothing at all
> and when I type control-command-return
> 
>                       I realize that I’m still in the first column.
> 
>                       What can be the problem?
> 
>                       Tom.
> 
> 
> 
> 
> 
>                       --
>                       You received this message because you are
> subscribed to the Google Groups "Pro Tools Accessibility" group.
>                       To unsubscribe from this group and stop receiving
> emails from it, send an email to ptaccess+unsubscr...@googlegroups.com
> <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
> <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.
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com
> <mailto:ptaccess+unsubscr...@googlegroups.com> .
> For more options, visit https://groups.google.com/d/optout.


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

Reply via email to