subject:"Re\: Midi"

Re: MIDI Event List finally fixed in latest Pro Tools release

2021-03-25 Thread Rory McDonald

Interesting, so one can now input midi without having a keyboard around?
Was wondering when, or if they would ever add that. Lol not that I'd ever use 
that over a keyboard, but its nice to have that available in a pinch. 

Rory

> On Mar 25, 2021, at 1:40 PM, Slau Halatyn  wrote:
> 
> I wanted to make sure I didn't bury the lead so, as the subject says, the 
> MIDI Event List bug has finally been fixed. For those following along at 
> home, this has been an issue for a few years. I noticed it but, at first, 
> thought it was just an anomaly and worked around it. When others brought it 
> up, I confirmed that it was indeed a bug and filed it. Technically, it wasn't 
> even an accessibility issue and affected all users. Finally it's fixed and 
> deleting or editing events in the MIDI Event List now works as expected.
> 
> The other notable thing in this new version is the virtual keyboard which 
> allows for QWERTY note input much like Sibelius.
> 
> enjoy,
> 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/7AC4BBCA-8C4D-42AF-99B7-268128B7DF26%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/25265145-B5FE-4A55-9342-D806F610C2EB%40rogers.com.

Re: Midi Editing

2020-09-11 Thread Rory McDonald

Sorry, my mistake. Got the number right anyway though, lol.

Rory

> On Sep 11, 2020, at 7:09 AM, CHUCK REICHEL  
> wrote:
> 
> Hi Rory,
> 
> The memory locates window command is "Command num pad 5"
> Just hit the same command again to close it also.
> HTH
> Chuck
> "God does not play dice with the universe"
> "Albert Einstein’
> 
> 
>> On Sep 11, 2020, at 1:08 AM, Rory McDonald wrote:
>> 
>> I believe the memory window shortcut is option 5 on the numpad. In there 
>> theres a clear memory locations button.
>> 
>> Rory
>> 
 On Sep 10, 2020, at 1:26 PM, Janne Svensson  
 wrote:
>>> 
>>> 2020-09-09 16:34 GMT+02:00, Rory McDonald :
 If your using Flow Tools, hit F1 twice to go into shuffle mode, go to the
 spot in the session you would like to paste and drop it there. If all goes
 well it should have no problems.
 Alternatively, I believe you could get in shuffle mode, then, assuming the
 section you'd like to paste is selected, hit command D and have it
 duplicated.
 I'm not sure if you plan to record more drums there on that same track
 afterwards, but if not and you can do this, I often find for whatever 
 reason
 that committing instrument tracks to audio before doing any editing like
 that makes it go smoother than not, sometimes notes move around weirdly
 where they shouldn't, might just be on my end for some reason though. 
 Anyway
 though hope this helps at least somewhat.
 
 Rory
 
> On Sep 9, 2020, at 5:44 AM, Janne Svensson 
> wrote:
> 
> Hello list.
> 
> I have a problem and I will try to explain it easy.
> 
> I have selected 2 bars of a drumtrack and would like to paste it in
> the middle of this track to make a part 2 bars longer. Can anyone
> explain how to do this?
> 
> I want to keep Everything at the right of the insetion Point and just
> move it 2 bars forward. Hope you understand my question.
> 
> Thanks in advance.
> --
> 
> 
> Med vänlig hälsning
> Janne Svensson
> Tel: +46-(0)702-60 52 04
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXATGHE-mitioVx%2BEDyYPVap2_crx9-yu-1SnfHGV-p2EA%40mail.gmail.com.
 
 --
 You received this message because you are subscribed to the Google Groups
 "Pro Tools Accessibility" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to ptaccess+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/ptaccess/55C0F4F0-5439-4205-A5A5-C06B6E2149BA%40rogers.com.
 
>>> 
>>> Hello Rory!
>>> 
>>> Thank you for this tip. It worked after a while. Now I underständ what
>>> these different edit modes are. I have one more question and this is
>>> not only in midi editing. If I want to clear all memory locations, is
>>> there a shortcut or somewhere in menus i can clear all locations?
>>> -- 
>>> 
>>> 
>>> Med vänlig hälsning
>>> Janne Svensson
>>> Tel: +46-(0)702-60 52 04
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXBcXWDj7_BmSEdM5GFCDmxfj90ub%3D8nDrScEbmguwGt1w%40mail.gmail.com.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/DEA0669E-8A00-4FF6-B31B-3FD912EDF57A%40rogers.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/D06BE29D-F2CD-4F29-A1A4-7087F5CDD343%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/0C8864EE-5458-4D03-AD85-56073FAACD76%40rogers.com.

Re: Midi Editing

2020-09-11 Thread CHUCK REICHEL

Hi Rory,

The memory locates window command is "Command num pad 5"
Just hit the same command again to close it also.
HTH
Chuck
"God does not play dice with the universe"
"Albert Einstein’


On Sep 11, 2020, at 1:08 AM, Rory McDonald wrote:

> I believe the memory window shortcut is option 5 on the numpad. In there 
> theres a clear memory locations button.
> 
> Rory
> 
>> On Sep 10, 2020, at 1:26 PM, Janne Svensson  wrote:
>> 
>> 2020-09-09 16:34 GMT+02:00, Rory McDonald :
>>> If your using Flow Tools, hit F1 twice to go into shuffle mode, go to the
>>> spot in the session you would like to paste and drop it there. If all goes
>>> well it should have no problems.
>>> Alternatively, I believe you could get in shuffle mode, then, assuming the
>>> section you'd like to paste is selected, hit command D and have it
>>> duplicated.
>>> I'm not sure if you plan to record more drums there on that same track
>>> afterwards, but if not and you can do this, I often find for whatever reason
>>> that committing instrument tracks to audio before doing any editing like
>>> that makes it go smoother than not, sometimes notes move around weirdly
>>> where they shouldn't, might just be on my end for some reason though. Anyway
>>> though hope this helps at least somewhat.
>>> 
>>> Rory
>>> 
 On Sep 9, 2020, at 5:44 AM, Janne Svensson 
 wrote:
 
 Hello list.
 
 I have a problem and I will try to explain it easy.
 
 I have selected 2 bars of a drumtrack and would like to paste it in
 the middle of this track to make a part 2 bars longer. Can anyone
 explain how to do this?
 
 I want to keep Everything at the right of the insetion Point and just
 move it 2 bars forward. Hope you understand my question.
 
 Thanks in advance.
 --
 
 
 Med vänlig hälsning
 Janne Svensson
 Tel: +46-(0)702-60 52 04
 
 --
 You received this message because you are subscribed to the Google Groups
 "Pro Tools Accessibility" group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to ptaccess+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXATGHE-mitioVx%2BEDyYPVap2_crx9-yu-1SnfHGV-p2EA%40mail.gmail.com.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ptaccess/55C0F4F0-5439-4205-A5A5-C06B6E2149BA%40rogers.com.
>>> 
>> 
>> Hello Rory!
>> 
>> Thank you for this tip. It worked after a while. Now I underständ what
>> these different edit modes are. I have one more question and this is
>> not only in midi editing. If I want to clear all memory locations, is
>> there a shortcut or somewhere in menus i can clear all locations?
>> -- 
>> 
>> 
>> Med vänlig hälsning
>> Janne Svensson
>> Tel: +46-(0)702-60 52 04
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXBcXWDj7_BmSEdM5GFCDmxfj90ub%3D8nDrScEbmguwGt1w%40mail.gmail.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/DEA0669E-8A00-4FF6-B31B-3FD912EDF57A%40rogers.com.

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

Re: Midi Editing

2020-09-10 Thread Rory McDonald

I believe the memory window shortcut is option 5 on the numpad. In there theres 
a clear memory locations button.

Rory

> On Sep 10, 2020, at 1:26 PM, Janne Svensson  wrote:
> 
> 2020-09-09 16:34 GMT+02:00, Rory McDonald :
>> If your using Flow Tools, hit F1 twice to go into shuffle mode, go to the
>> spot in the session you would like to paste and drop it there. If all goes
>> well it should have no problems.
>> Alternatively, I believe you could get in shuffle mode, then, assuming the
>> section you'd like to paste is selected, hit command D and have it
>> duplicated.
>> I'm not sure if you plan to record more drums there on that same track
>> afterwards, but if not and you can do this, I often find for whatever reason
>> that committing instrument tracks to audio before doing any editing like
>> that makes it go smoother than not, sometimes notes move around weirdly
>> where they shouldn't, might just be on my end for some reason though. Anyway
>> though hope this helps at least somewhat.
>> 
>> Rory
>> 
>>> On Sep 9, 2020, at 5:44 AM, Janne Svensson 
>>> wrote:
>>> 
>>> Hello list.
>>> 
>>> I have a problem and I will try to explain it easy.
>>> 
>>> I have selected 2 bars of a drumtrack and would like to paste it in
>>> the middle of this track to make a part 2 bars longer. Can anyone
>>> explain how to do this?
>>> 
>>> I want to keep Everything at the right of the insetion Point and just
>>> move it 2 bars forward. Hope you understand my question.
>>> 
>>> Thanks in advance.
>>> --
>>> 
>>> 
>>> Med vänlig hälsning
>>> Janne Svensson
>>> Tel: +46-(0)702-60 52 04
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXATGHE-mitioVx%2BEDyYPVap2_crx9-yu-1SnfHGV-p2EA%40mail.gmail.com.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/55C0F4F0-5439-4205-A5A5-C06B6E2149BA%40rogers.com.
>> 
> 
> Hello Rory!
> 
> Thank you for this tip. It worked after a while. Now I underständ what
> these different edit modes are. I have one more question and this is
> not only in midi editing. If I want to clear all memory locations, is
> there a shortcut or somewhere in menus i can clear all locations?
> -- 
> 
> 
> Med vänlig hälsning
> Janne Svensson
> Tel: +46-(0)702-60 52 04
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXBcXWDj7_BmSEdM5GFCDmxfj90ub%3D8nDrScEbmguwGt1w%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DEA0669E-8A00-4FF6-B31B-3FD912EDF57A%40rogers.com.

Re: Midi Editing

2020-09-10 Thread Janne Svensson

2020-09-09 16:34 GMT+02:00, Rory McDonald :
> If your using Flow Tools, hit F1 twice to go into shuffle mode, go to the
> spot in the session you would like to paste and drop it there. If all goes
> well it should have no problems.
> Alternatively, I believe you could get in shuffle mode, then, assuming the
> section you'd like to paste is selected, hit command D and have it
> duplicated.
> I'm not sure if you plan to record more drums there on that same track
> afterwards, but if not and you can do this, I often find for whatever reason
> that committing instrument tracks to audio before doing any editing like
> that makes it go smoother than not, sometimes notes move around weirdly
> where they shouldn't, might just be on my end for some reason though. Anyway
> though hope this helps at least somewhat.
>
> Rory
>
>> On Sep 9, 2020, at 5:44 AM, Janne Svensson 
>> wrote:
>>
>> Hello list.
>>
>> I have a problem and I will try to explain it easy.
>>
>> I have selected 2 bars of a drumtrack and would like to paste it in
>> the middle of this track to make a part 2 bars longer. Can anyone
>> explain how to do this?
>>
>> I want to keep Everything at the right of the insetion Point and just
>> move it 2 bars forward. Hope you understand my question.
>>
>> Thanks in advance.
>> --
>>
>>
>> Med vänlig hälsning
>> Janne Svensson
>> Tel: +46-(0)702-60 52 04
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXATGHE-mitioVx%2BEDyYPVap2_crx9-yu-1SnfHGV-p2EA%40mail.gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ptaccess/55C0F4F0-5439-4205-A5A5-C06B6E2149BA%40rogers.com.
>

Hello Rory!

Thank you for this tip. It worked after a while. Now I underständ what
these different edit modes are. I have one more question and this is
not only in midi editing. If I want to clear all memory locations, is
there a shortcut or somewhere in menus i can clear all locations?
-- 


Med vänlig hälsning
Janne Svensson
Tel: +46-(0)702-60 52 04

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

Re: Midi Editing

2020-09-09 Thread Rory McDonald

If your using Flow Tools, hit F1 twice to go into shuffle mode, go to the spot 
in the session you would like to paste and drop it there. If all goes well it 
should have no problems.
Alternatively, I believe you could get in shuffle mode, then, assuming the 
section you'd like to paste is selected, hit command D and have it duplicated.
I'm not sure if you plan to record more drums there on that same track 
afterwards, but if not and you can do this, I often find for whatever reason 
that committing instrument tracks to audio before doing any editing like that 
makes it go smoother than not, sometimes notes move around weirdly where they 
shouldn't, might just be on my end for some reason though. Anyway though hope 
this helps at least somewhat.

Rory

> On Sep 9, 2020, at 5:44 AM, Janne Svensson  wrote:
> 
> Hello list.
> 
> I have a problem and I will try to explain it easy.
> 
> I have selected 2 bars of a drumtrack and would like to paste it in
> the middle of this track to make a part 2 bars longer. Can anyone
> explain how to do this?
> 
> I want to keep Everything at the right of the insetion Point and just
> move it 2 bars forward. Hope you understand my question.
> 
> Thanks in advance.
> -- 
> 
> 
> Med vänlig hälsning
> Janne Svensson
> Tel: +46-(0)702-60 52 04
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/CAMn%3DFXATGHE-mitioVx%2BEDyYPVap2_crx9-yu-1SnfHGV-p2EA%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/55C0F4F0-5439-4205-A5A5-C06B6E2149BA%40rogers.com.

Re: midi event list scipts not workin in pro tools 2019-10

2019-12-06 Thread Slau Halatyn

No worries, I totally get it. Let me know if any other issues come up. Cheers,
Slau


> On Dec 6, 2019, at 4:57 AM, Tom Hessels  wrote:
> 
> Ok Slau,
>  
> I’ll change my workflow in 2019.10.
> I think the raison why the marcros still worked in 2019.6 was that the macros 
> for the event list are still there in flotools 2019.5.1.
> Sorry for bothering you but i’m a computer programmer and worked with them 
> since 1972 . I’m retired now but still wanna know why things work or (often) 
> don’t work. 
> Tom.
>  
>  
> Van: ptaccess@googlegroups.com  Namens Slau Halatyn
> Verzonden: donderdag 5 december 2019 16:23
> Aan: PTAccess List 
> Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10
>  
> Again, don't use the MIDI Event List. All the things you're talking about you 
> can do right in the Mix or Edit window. There are no macros for the MIDI 
> Event List. There used to be at one time but, because of changes in Pro Tools 
> itself, the Flo Tools commands have changed. 
> HTH,
> Slau
> 
> 
>> On Dec 5, 2019, at 6:59 AM, Tom Hessels > <mailto:tomhessel...@gmail.com>> wrote:
>>  
>> Hi Slau,
>>  
>> Here again from a cold and foggy the netherlands.
>> I updated again to 2019.10 with the same result:
>> The scripts don’t work for me.
>> I selected the track in the track list table. Set the track vies to notes 
>> and started the event list.
>> Selected the first row and with the arrow keys searched the note i wanna 
>> change.
>> With shift+option+} went to the length collumn.
>> And with control+command+enter try to change the length.
>> Typed in the new length.
>> In 2019.6 every thing worked: the lengtyh was changed and i could use the 
>> arrow keys to find the nect note.
>> In 2019.19 the length didn’t changed and when pressing the arrow keys i not 
>> hear any notes anny more.
>> I have to select a column to hear another note but length or another param 
>> didn’t change when using the key combination to change it.
>> In both versions of pro tools i use the same procedure.
>> Do you Have any idea?
>>  
>> Tom.
>>  
>>  
>>  
>>  
>>  
>>  
>> Van: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com> 
>> mailto:ptaccess@googlegroups.com>> Namens Slau 
>> Halatyn
>> Verzonden: woensdag 4 december 2019 17:51
>> Aan: PTAccess List > <mailto:ptaccess@googlegroups.com>>
>> Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10
>>  
>> Hi Tom, everything works in 2019.10 as well. You might not have had the 
>> track view set to Notes rather than Clips. Actually, unless you're editing 
>> controller data or other non-MIDI note events, you don't have to open the 
>> MIDI Event List. You can just arrow to the notes and edit them. Some of that 
>> is just baked into Pro Tools itself. Of course, Flo Tools turbo charges it 
>> but everything does work in 2019.10.
>> HTH,
>> Slau
>>  
>> 
>> 
>> 
>>> On Dec 4, 2019, at 11:39 AM, Tom Hessels >> <mailto:tomhessel...@gmail.com>> wrote:
>>>  
>>> Hi,
>>>  
>>> To day i tried to usee the midi event list within pro tools 2019.10 using 
>>> the flo tools hotkeys.
>>> They didn’t work properly. I coudn’t edit events using the flo tools hot 
>>> keys etc.
>>> I took a look at the flo tools website and saw that 2019-10 was not 
>>> menioned. So i got back to pro tools 2019.6 and all worked fine.
>>> So if you use the midi event list you can better stay on 2019.6.
>>> Hope this helps.
>>>  
>>> 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>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com?utm_medium=email&utm_source=footer>.
>> 
>>  
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receivi

RE: midi event list scipts not workin in pro tools 2019-10

2019-12-06 Thread Tom Hessels

Ok Slau,

I’ll change my workflow in 2019.10.

I think the raison why the marcros still worked in 2019.6 was that the macros
for the event list are still there in flotools 2019.5.1.

Sorry for bothering you but i’m a computer programmer and worked with them
since 1972 . I’m retired now but still wanna know why things work or (often)
don’t work.

Tom.

Van: ptaccess@googlegroups.com Namens Slau Halatyn
Verzonden: donderdag 5 december 2019 16:23
Aan: PTAccess List
Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10

Again, don't use the MIDI Event List. All the things you're talking about you
can do right in the Mix or Edit window. There are no macros for the MIDI Event
List. There used to be at one time but, because of changes in Pro Tools itself,
the Flo Tools commands have changed.

HTH,

Slau

On Dec 5, 2019, at 6:59 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi Slau,

Here again from a cold and foggy the netherlands.

I updated again to 2019.10 with the same result:

The scripts don’t work for me.

I selected the track in the track list table. Set the track vies to notes and
started the event list.

Selected the first row and with the arrow keys searched the note i wanna change.

With shift+option+} went to the length collumn.

And with control+command+enter try to change the length.

Typed in the new length.

In 2019.6 every thing worked: the lengtyh was changed and i could use the arrow
keys to find the nect note.

In 2019.19 the length didn’t changed and when pressing the arrow keys i not
hear any notes anny more.

I have to select a column to hear another note but length or another param
didn’t change when using the key combination to change it.

In both versions of pro tools i use the same procedure.

Do you Have any idea?

Tom.

Van: <mailto:ptaccess@googlegroups.com> ptaccess@googlegroups.com <
<mailto:ptaccess@googlegroups.com> ptaccess@googlegroups.com> Namens Slau
Halatyn
Verzonden: woensdag 4 december 2019 17:51
Aan: PTAccess List < <mailto:ptaccess@googlegroups.com>
ptaccess@googlegroups.com>
Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10

Hi Tom, everything works in 2019.10 as well. You might not have had the track
view set to Notes rather than Clips. Actually, unless you're editing controller
data or other non-MIDI note events, you don't have to open the MIDI Event List.
You can just arrow to the notes and edit them. Some of that is just baked into
Pro Tools itself. Of course, Flo Tools turbo charges it but everything does
work in 2019.10.

HTH,

Slau

On Dec 4, 2019, at 11:39 AM, Tom Hessels < <mailto:tomhessel...@gmail.com>
tomhessel...@gmail.com> wrote:

Hi,

To day i tried to usee the midi event list within pro tools 2019.10 using the
flo tools hotkeys.

They didn’t work properly. I coudn’t edit events using the flo tools hot keys
etc.

I took a look at the flo tools website and saw that 2019-10 was not menioned.
So i got back to pro tools 2019.6 and all worked fine.

So if you use the midi event list you can better stay on 2019.6.

Hope this helps.

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 <mailto:ptaccess+unsubscr...@googlegroups.com>
ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit
<https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com?utm_medium=email&utm_source=footer>

https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Pro
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to <mailto:ptaccess+unsubscr...@googlegroups.com>
ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit
<https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com?utm_medium=email&utm_source=footer>

https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%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 <mailto:ptaccess+unsubscr...@googlegroups.com>
ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit
<https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com?utm_medium=email&utm_source=footer>

https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail

Re: midi event list scipts not workin in pro tools 2019-10

2019-12-05 Thread Slau Halatyn

BTW, when you've selected a note with left/right arrow, double tap Command F3 
and type in the new value. If you want to change where the note starts, select 
the note, double-tap Command F1 and enter the new start time.
Slau


> On Dec 5, 2019, at 6:59 AM, Tom Hessels  wrote:
> 
> Hi Slau,
>  
> Here again from a cold and foggy the netherlands.
> I updated again to 2019.10 with the same result:
> The scripts don’t work for me.
> I selected the track in the track list table. Set the track vies to notes and 
> started the event list.
> Selected the first row and with the arrow keys searched the note i wanna 
> change.
> With shift+option+} went to the length collumn.
> And with control+command+enter try to change the length.
> Typed in the new length.
> In 2019.6 every thing worked: the lengtyh was changed and i could use the 
> arrow keys to find the nect note.
> In 2019.19 the length didn’t changed and when pressing the arrow keys i not 
> hear any notes anny more.
> I have to select a column to hear another note but length or another param 
> didn’t change when using the key combination to change it.
> In both versions of pro tools i use the same procedure.
> Do you Have any idea?
>  
> Tom.
>  
>  
>  
>  
>  
>  
> Van: ptaccess@googlegroups.com  Namens Slau Halatyn
> Verzonden: woensdag 4 december 2019 17:51
> Aan: PTAccess List 
> Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10
>  
> Hi Tom, everything works in 2019.10 as well. You might not have had the track 
> view set to Notes rather than Clips. Actually, unless you're editing 
> controller data or other non-MIDI note events, you don't have to open the 
> MIDI Event List. You can just arrow to the notes and edit them. Some of that 
> is just baked into Pro Tools itself. Of course, Flo Tools turbo charges it 
> but everything does work in 2019.10.
> HTH,
> Slau
>  
> 
> 
>> On Dec 4, 2019, at 11:39 AM, Tom Hessels > <mailto:tomhessel...@gmail.com>> wrote:
>>  
>> Hi,
>>  
>> To day i tried to usee the midi event list within pro tools 2019.10 using 
>> the flo tools hotkeys.
>> They didn’t work properly. I coudn’t edit events using the flo tools hot 
>> keys etc.
>> I took a look at the flo tools website and saw that 2019-10 was not 
>> menioned. So i got back to pro tools 2019.6 and all worked fine.
>> So if you use the midi event list you can better stay on 2019.6.
>> Hope this helps.
>>  
>> 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>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com?utm_medium=email&utm_source=footer>.
> 
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com?utm_medium=email&utm_source=footer>.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/8F9DEA7F-1732-4692-B1A6-0E80D1208975%40gmail.com.

Re: midi event list scipts not workin in pro tools 2019-10

2019-12-05 Thread Slau Halatyn

Again, don't use the MIDI Event List. All the things you're talking about you 
can do right in the Mix or Edit window. There are no macros for the MIDI Event 
List. There used to be at one time but, because of changes in Pro Tools itself, 
the Flo Tools commands have changed. 
HTH,
Slau

> On Dec 5, 2019, at 6:59 AM, Tom Hessels  wrote:
> 
> Hi Slau,
>  
> Here again from a cold and foggy the netherlands.
> I updated again to 2019.10 with the same result:
> The scripts don’t work for me.
> I selected the track in the track list table. Set the track vies to notes and 
> started the event list.
> Selected the first row and with the arrow keys searched the note i wanna 
> change.
> With shift+option+} went to the length collumn.
> And with control+command+enter try to change the length.
> Typed in the new length.
> In 2019.6 every thing worked: the lengtyh was changed and i could use the 
> arrow keys to find the nect note.
> In 2019.19 the length didn’t changed and when pressing the arrow keys i not 
> hear any notes anny more.
> I have to select a column to hear another note but length or another param 
> didn’t change when using the key combination to change it.
> In both versions of pro tools i use the same procedure.
> Do you Have any idea?
>  
> Tom.
>  
>  
>  
>  
>  
>  
> Van: ptaccess@googlegroups.com <mailto:ptaccess@googlegroups.com> 
> mailto:ptaccess@googlegroups.com>> Namens Slau 
> Halatyn
> Verzonden: woensdag 4 december 2019 17:51
> Aan: PTAccess List  <mailto:ptaccess@googlegroups.com>>
> Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10
>  
> Hi Tom, everything works in 2019.10 as well. You might not have had the track 
> view set to Notes rather than Clips. Actually, unless you're editing 
> controller data or other non-MIDI note events, you don't have to open the 
> MIDI Event List. You can just arrow to the notes and edit them. Some of that 
> is just baked into Pro Tools itself. Of course, Flo Tools turbo charges it 
> but everything does work in 2019.10.
> HTH,
> Slau
>  
> 
> 
>> On Dec 4, 2019, at 11:39 AM, Tom Hessels > <mailto:tomhessel...@gmail.com>> wrote:
>>  
>> Hi,
>>  
>> To day i tried to usee the midi event list within pro tools 2019.10 using 
>> the flo tools hotkeys.
>> They didn’t work properly. I coudn’t edit events using the flo tools hot 
>> keys etc.
>> I took a look at the flo tools website and saw that 2019-10 was not 
>> menioned. So i got back to pro tools 2019.6 and all worked fine.
>> So if you use the midi event list you can better stay on 2019.6.
>> Hope this helps.
>>  
>> 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>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com?utm_medium=email&utm_source=footer>.
> 
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com?utm_medium=email&utm_source=footer>.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> <mailto:ptaccess+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com
>  
> <https://groups.google.com/d/msgid/ptaccess/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com?utm_medium=email&utm_source=footer>.

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

RE: midi event list scipts not workin in pro tools 2019-10

2019-12-05 Thread Tom Hessels

Hi Slau,

Here again from a cold and foggy the netherlands.

I updated again to 2019.10 with the same result:

The scripts don’t work for me.

I selected the track in the track list table. Set the track vies to notes and
started the event list.

Selected the first row and with the arrow keys searched the note i wanna change.

With shift+option+} went to the length collumn.

And with control+command+enter try to change the length.

Typed in the new length.

In 2019.6 every thing worked: the lengtyh was changed and i could use the arrow
keys to find the nect note.

In 2019.19 the length didn’t changed and when pressing the arrow keys i not
hear any notes anny more.

I have to select a column to hear another note but length or another param
didn’t change when using the key combination to change it.

In both versions of pro tools i use the same procedure.

Do you Have any idea?

Tom.

Van: ptaccess@googlegroups.com Namens Slau Halatyn
Verzonden: woensdag 4 december 2019 17:51
Aan: PTAccess List
Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10

HTH,

Slau

On Dec 4, 2019, at 11:39 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi,

To day i tried to usee the midi event list within pro tools 2019.10 using the
flo tools hotkeys.

They didn’t work properly. I coudn’t edit events using the flo tools hot keys
etc.

I took a look at the flo tools website and saw that 2019-10 was not menioned.
So i got back to pro tools 2019.6 and all worked fine.

So if you use the midi event list you can better stay on 2019.6.

Hope this helps.

Tom.

https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Pro
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com
<mailto:ptaccess+unsubscr...@googlegroups.com> .
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com

<https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%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/000a01d5ab63%2479f0e4c0%246dd2ae40%24%40gmail.com.

RE: midi event list scipts not workin in pro tools 2019-10

2019-12-05 Thread Tom Hessels

Hi Slau,

I did set the view to notes.

Strange.

I will do an update to 2019.10 again.

I’ll come back, Tom.

Van: ptaccess@googlegroups.com Namens Slau Halatyn
Verzonden: woensdag 4 december 2019 17:51
Aan: PTAccess List
Onderwerp: Re: midi event list scipts not workin in pro tools 2019-10

HTH,

Slau

On Dec 4, 2019, at 11:39 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi,

To day i tried to usee the midi event list within pro tools 2019.10 using the
flo tools hotkeys.

They didn’t work properly. I coudn’t edit events using the flo tools hot keys
etc.

I took a look at the flo tools website and saw that 2019-10 was not menioned.
So i got back to pro tools 2019.6 and all worked fine.

So if you use the midi event list you can better stay on 2019.6.

Hope this helps.

Tom.

https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Pro
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ptaccess+unsubscr...@googlegroups.com
<mailto:ptaccess+unsubscr...@googlegroups.com> .
To view this discussion on the web visit
https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com

<https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%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/003f01d5ab56%24a21a7e00%24e64f7a00%24%40gmail.com.

Re: midi event list scipts not workin in pro tools 2019-10

2019-12-04 Thread Slau Halatyn

Hi Tom, everything works in 2019.10 as well. You might not have had the track 
view set to Notes rather than Clips. Actually, unless you're editing controller 
data or other non-MIDI note events, you don't have to open the MIDI Event List. 
You can just arrow to the notes and edit them. Some of that is just baked into 
Pro Tools itself. Of course, Flo Tools turbo charges it but everything does 
work in 2019.10.
HTH,
Slau


> On Dec 4, 2019, at 11:39 AM, Tom Hessels  wrote:
> 
> Hi,
>  
> To day i tried to usee the midi event list within pro tools 2019.10 using the 
> flo tools hotkeys.
> They didn’t work properly. I coudn’t edit events using the flo tools hot keys 
> etc.
> I took a look at the flo tools website and saw that 2019-10 was not menioned. 
> So i got back to pro tools 2019.6 and all worked fine.
> So if you use the midi event list you can better stay on 2019.6.
> Hope this helps.
>  
> Tom.
>  
>  
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/001e01d5aac1%246668ec60%24333ac520%24%40gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/5CDC1139-1907-46EE-94A9-3DD5E33E21E5%40gmail.com.

RE: Midi problem

2019-11-21 Thread Tom Hessels

Hi Slau,

I think that it might be a system problem. The problem occurs the most when i
load a project from the recent list within pro tools.

When i load a project using a finder a takes a more time

And mostly every thing works fine. There is no difference with the age of the
project. When loading a project from the recent list it seems to load at once
and allso when i wati to play it there are no instruments or other plugins such
as reverb.

I pro tools using a kind of caching when loading from the recent list?

I thin that the only way to solve this problem is to install every thing from
scratch.

Tom.

Van: ptaccess@googlegroups.com Namens Slau Halatyn
Verzonden: maandag 18 november 2019 16:57
Aan: PTAccess List
Onderwerp: Re: Midi problem

Hi Tom,

I don't know what's going on with your instrument tracks not playing. Depending
on what type of instruments they are, it sometimes can take a minute to load
the instruments themselves. There are also tons of variables of which I'm not
aware. Are these older sessions? Were the instrument tracks created within the
session itself and the tracks played back correctly the last time? Further,
there could be any number of issues with the session file itself. Of course,
nobody here is in a position to offer technical support to troubleshoot such
issues. Can you create a new session, create an instrument track, record
something and hear it back with your pedal working properly? Eliminating
variables is, of course, the key to figuring out what the root of the problem
might be. Did you remove your FB 360 plug-ins?

slau

On Nov 18, 2019, at 2:45 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi Slau,

I posted this message in the KK list but because of the fact that it perhaps
has something to do with a pt problem I weill also post it here:

Hi Slau,

The pedals are always connected.

So that’s not the problem.

There is also another strange problem that might be connected with my midi
problem.

How can i explain it (I read a lot of english but i write it not very often)

And perhaps is what i write now is more in place in the ptaccess list.

Ok, when i start pro tools and choose a project from the recent table the
project loads innediate and the faders of the fadeport 8 reacts.

But when i start to play the project I only hear ;my audio tracks. No
instruments tracks are playing and also no effects are heard: no reverbs on
audio tracks etc.

What i do then is loading the project using the .ptx file.

Often then I have that pedal issue.

I’Ll post this message also in ptaccess.

Tom.

Tom Herssels (the Netherlands.)

Van: <mailto:komplete-kontrol-acc...@googlegroups.com>
komplete-kontrol-acc...@googlegroups.com <
<mailto:komplete-kontrol-acc...@googlegroups.com>
komplete-kontrol-acc...@googlegroups.com> Namens Slau Halatyn
Verzonden: maandag 18 november 2019 00:00
Aan: <mailto:komplete-kontrol-acc...@googlegroups.com>
komplete-kontrol-acc...@googlegroups.com
Onderwerp: Re: [komplete-kontrol-access] Midi problem

The first thing that occurs to me is that you need to make sure that your pedal
is connected before powering up the NI keyboard. Once that is the case, only
then you should boot-up your system. At least as a starting point, I'd make
sure to follow those steps to eliminate variables.

slau

On Nov 17, 2019, at 1:28 PM, Tom Hessels < <mailto:tomhessel...@gmail.com>
tomhessel...@gmail.com> wrote:

Hi,

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I’m using teh Faderport) I have problems with the
pedals connected to the s61.

Suddenly the sustain does’nt work annymore or the expression pedal acts strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie setup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the same
port?

I tried to change ports but the app seems not very accessible or am i doing
things wrong?

Tom.

Tom Hessels (the Netherlands)

--
You received this message because you are subscribed to the Google Groups
"Komplete Kontrol Access" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com>
komplete-kontrol-access+unsubscr...@googlegroups.com.
To view this discussion on the web, visit
<https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com?utm_medium=email&utm_source=footer>

https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups
"Komplete Kontrol Access" group.
To

RE: Midi problem

2019-11-21 Thread Tom Hessels

Hi Alex,

This article discribes how to connect en configure the pedals.
You have to do that the first time you want to use your pedals. Sighted help is 
needed.
Tom.



-Oorspronkelijk bericht-
Van: ptaccess@googlegroups.com  Namens Alex Coleman
Verzonden: maandag 18 november 2019 19:51
Aan: ptaccess@googlegroups.com
Onderwerp: Re: Midi problem

Tom, also regarding your pedal issue, I found the following article that is 
supposed to correct the issue on the MKII devices. Perhaps it will work for you 
as well. I have not had a chance to try it out for my self yet, but am just 
passing it along for your reference. See following link:

https://support.native-instruments.com/hc/en-us/articles/115005166305-How-to-Configure-Sustain-Expression-Pedals-on-a-KOMPLETE-KONTROL-MK2-Keyboard?_ga=2.74440599.423050809.1574102050-346329362.1571253812

I haven't had a chance to try this for myself on my S61 MKII yet,

On 11/18/19, Slau Halatyn  wrote:
> Hi Tom,
> I don't know what's going on with your instrument tracks not playing.
> Depending on what type of instruments they are, it sometimes can take 
> a minute to load the instruments themselves. There are also tons of 
> variables of which I'm not aware. Are these older sessions? Were the 
> instrument tracks created within the session itself and the tracks 
> played back correctly the last time? Further, there could be any 
> number of issues with the session file itself. Of course, nobody here 
> is in a position to offer technical support to troubleshoot such 
> issues. Can you create a new session, create an instrument track, 
> record something and hear it back with your pedal working properly? 
> Eliminating variables is, of course, the key to figuring out what the root of 
> the problem might be. Did you remove your FB 360 plug-ins?
> slau
>
>
>> On Nov 18, 2019, at 2:45 AM, Tom Hessels  wrote:
>>
>> Hi Slau,
>> I posted this message in the KK list but because of the fact that it 
>> perhaps has something to do with a pt problem I weill also post it here:
>> Hi Slau,
>>
>> The pedals are always connected.
>> So that’s not the problem.
>> There is also another strange problem that might be connected with my 
>> midi problem.
>> How can i explain it (I read a lot of english but i write it not very
>> often)
>> And perhaps is what i write now is more in place in the ptaccess list.
>> Ok, when i start pro tools and choose a project from the recent table 
>> the project loads innediate and the faders of the fadeport 8 reacts.
>> But when i start to play the project I only hear ;my audio tracks. No 
>> instruments tracks are playing and also no effects are heard: no 
>> reverbs on audio tracks etc.
>> What i do then is loading the project using the .ptx file.
>> Often then I have that pedal issue.
>> I’Ll post this message also in ptaccess.
>>
>> Tom.
>> Tom Herssels (the Netherlands.)
>>
>>
>> Van: komplete-kontrol-acc...@googlegroups.com
>> <mailto:komplete-kontrol-acc...@googlegroups.com>
>> > <mailto:komplete-kontrol-acc...@googlegroups.com>> Namens Slau 
>> Halatyn
>> Verzonden: maandag 18 november 2019 00:00
>> Aan: komplete-kontrol-acc...@googlegroups.com
>> <mailto:komplete-kontrol-acc...@googlegroups.com>
>> Onderwerp: Re: [komplete-kontrol-access] Midi problem
>>
>> The first thing that occurs to me is that you need to make sure that 
>> your pedal is connected before powering up the NI keyboard. Once that 
>> is the case, only then you should boot-up your system. At least as a 
>> starting point, I'd make sure to follow those steps to eliminate variables.
>> slau
>>
>>
>>
>> On Nov 17, 2019, at 1:28 PM, Tom Hessels > <mailto:tomhessel...@gmail.com>> wrote:
>>
>> Hi,
>>
>> I have to midi devices connected to my mac:
>> Native instruments s61 keyboard;
>> Faderport 8.
>> The last time (I think since I’m using teh Faderport) I have problems 
>> with the pedals connected to the s61.
>> Suddenly the sustain does’nt work annymore or the expression pedal 
>> acts strange.
>> I have to reset things or even restore a time machine backup.
>> I had alook at audio midie setup app and saw that both devices use 
>> port 1.
>> Could that be the problem or is is it possible to use mor devices on 
>> the same port?
>> I tried to change ports but the app seems not very accessible or am i 
>> doing things wrong?
>>
>> Tom.
>> Tom Hessels (the Netherlands)
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to t

Re: Midi problem

2019-11-18 Thread Alex Coleman

trol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com
>> <https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com?utm_medium=email&utm_source=footer>.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Komplete Kontrol Access" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to komplete-kontrol-access+unsubscr...@googlegroups.com
>> <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com>.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com
>> <https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com?utm_medium=email&utm_source=footer>.
>>
>>
>> Van: ptaccess@googlegroups.com  Namens Slau
>> Halatyn
>> Verzonden: zondag 17 november 2019 16:08
>> Aan: PTAccess List 
>> Onderwerp: Re: Midi problem
>>
>> Not sure as this is not Pro Tools specific but there is a Komplete Kontrol
>> email list where somebody might have a better idea. I think you can find
>> subscription info on www.kk-access.com <http://www.kk-access.com/>
>> HTH,
>> Slau
>>
>>
>>
>>> On Nov 17, 2019, at 9:59 AM, Tom Hessels >> <mailto:tomhessel...@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> I have to midi devices connected to my mac:
>>> Native instruments s61 keyboard;
>>> Faderport 8.
>>> The last time (I think since I’m using teh Faderport) I have problems
>>> with the pedals connected to the s61.
>>> Suddenly the sustain does’nt work annymore or the expression pedal acts
>>> strange.
>>> I have to reset things or even restore a time machine backup.
>>> I had alook at audio midie srtup app and saw that both devices use port
>>> 1.
>>> Could that be the problem or is is it possible to use mor devices on the
>>> same port?
>>> I tried to change ports but the app seems not very accessible or am i
>>> doing things wrong?
>>>
>>> Tom.
>>> Tom Hessels (the Netherlands)
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google 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/000801d59d57%24942647f0%24bc72d7d0%24%40gmail.com
>>> <https://groups.google.com/d/msgid/ptaccess/000801d59d57%24942647f0%24bc72d7d0%24%40gmail.com?utm_medium=email&utm_source=footer>.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com
>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/2E29C104-395A-45EE-9CDF-41DFF409932B%40gmail.com
>> <https://groups.google.com/d/msgid/ptaccess/2E29C104-395A-45EE-9CDF-41DFF409932B%40gmail.com?utm_medium=email&utm_source=footer>.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com
>> <mailto:ptaccess+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ptaccess/004601d59de4%242c211e90%2484635bb0%24%40gmail.com
>> <https://groups.google.com/d/msgid/ptaccess/004601d59de4%242c211e90%2484635bb0%24%40gmail.com?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ptaccess/F73832A4-5B5F-4411-9B1C-A6FCC2E1A216%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/CAKVN6vM-ngpX4RobCVUVjR%3DM3cbK1Ow_s9u-0ExF%3DfaPaR2n8g%40mail.gmail.com.

Re: Midi problem

2019-11-18 Thread Slau Halatyn

Hi Tom,
I don't know what's going on with your instrument tracks not playing. Depending 
on what type of instruments they are, it sometimes can take a minute to load 
the instruments themselves. There are also tons of variables of which I'm not 
aware. Are these older sessions? Were the instrument tracks created within the 
session itself and the tracks played back correctly the last time? Further, 
there could be any number of issues with the session file itself. Of course, 
nobody here is in a position to offer technical support to troubleshoot such 
issues. Can you create a new session, create an instrument track, record 
something and hear it back with your pedal working properly? Eliminating 
variables is, of course, the key to figuring out what the root of the problem 
might be. Did you remove your FB 360 plug-ins?
slau


> On Nov 18, 2019, at 2:45 AM, Tom Hessels  wrote:
> 
> Hi Slau,
> I posted this message in the KK list but because of the fact that it perhaps 
> has something to do with a pt problem I weill also post it here:
> Hi Slau,
>  
> The pedals are always connected.
> So that’s not the problem.
> There is also another strange problem that might be connected with my midi 
> problem.
> How can i explain it (I read a lot of english but i write it not very often)
> And perhaps is what i write now is more in place in the ptaccess list.
> Ok, when i start pro tools and choose a project from the recent table the 
> project loads innediate and the faders of the fadeport 8 reacts.
> But when i start to play the project I only hear ;my audio tracks. No 
> instruments tracks are playing and also no effects are heard: no reverbs on 
> audio tracks etc.
> What i do then is loading the project using the .ptx file.
> Often then I have that pedal issue.
> I’Ll post this message also in ptaccess.
>  
> Tom.
> Tom Herssels (the Netherlands.)
>  
>  
> Van: komplete-kontrol-acc...@googlegroups.com 
> <mailto:komplete-kontrol-acc...@googlegroups.com> 
>  <mailto:komplete-kontrol-acc...@googlegroups.com>> Namens Slau Halatyn
> Verzonden: maandag 18 november 2019 00:00
> Aan: komplete-kontrol-acc...@googlegroups.com 
> <mailto:komplete-kontrol-acc...@googlegroups.com>
> Onderwerp: Re: [komplete-kontrol-access] Midi problem
>  
> The first thing that occurs to me is that you need to make sure that your 
> pedal is connected before powering up the NI keyboard. Once that is the case, 
> only then you should boot-up your system. At least as a starting point, I'd 
> make sure to follow those steps to eliminate variables.
> slau
>  
> 
> 
> On Nov 17, 2019, at 1:28 PM, Tom Hessels  <mailto:tomhessel...@gmail.com>> wrote:
>  
> Hi,
>  
> I have to midi devices connected to my mac:
> Native instruments s61 keyboard;
> Faderport 8.
> The last time (I think since I’m using teh Faderport) I have problems with 
> the pedals connected to the s61.
> Suddenly the sustain does’nt work annymore or the expression pedal acts 
> strange.
> I have to reset things or even restore a time machine backup.
> I had alook at audio midie setup app and saw that both devices use port 1.
> Could that be the problem or is is it possible to use mor devices on the same 
> port?
> I tried to change ports but the app seems not very accessible or am i doing 
> things wrong?
>  
> Tom.
> Tom Hessels (the Netherlands)
>  
>  
>  
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Komplete Kontrol Access" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to komplete-kontrol-access+unsubscr...@googlegroups.com 
> <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com>.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com
>  
> <https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com?utm_medium=email&utm_source=footer>.
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Komplete Kontrol Access" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to komplete-kontrol-access+unsubscr...@googlegroups.com 
> <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com>.
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com
>  
> <https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com?utm_medium=email&utm_source=footer>.
>

Re: Midi problem

2019-11-18 Thread Alex Coleman

I too am having an issue with my sustain pedal not working on my S61
MKII. It was working fine, until I came in the other day to work on
some tracks and had no functionality of my sus pedal.
I too am dead in the water until I find a resolution.
Very frustrating.
Thanks for any guidance that anyone can share toward a swift resolution.


On 11/18/19, Tom Hessels  wrote:
> Hi Slau,
>
> I posted this message in the KK list but because of the fact that it perhaps
> has something to do with a pt problem I weill also post it here:
>
> Hi Slau,
>
>
>
> The pedals are always connected.
>
> So that’s not the problem.
>
> There is also another strange problem that might be connected with my midi
> problem.
>
> How can i explain it (I read a lot of english but i write it not very
> often)
>
> And perhaps is what i write now is more in place in the ptaccess list.
>
> Ok, when i start pro tools and choose a project from the recent table the
> project loads innediate and the faders of the fadeport 8 reacts.
>
> But when i start to play the project I only hear ;my audio tracks. No
> instruments tracks are playing and also no effects are heard: no reverbs on
> audio tracks etc.
>
> What i do then is loading the project using the .ptx file.
>
> Often then I have that pedal issue.
>
> I’Ll post this message also in ptaccess.
>
>
>
> Tom.
>
> Tom Herssels (the Netherlands.)
>
>
>
>
>
> Van: komplete-kontrol-acc...@googlegroups.com
>  Namens Slau Halatyn
> Verzonden: maandag 18 november 2019 00:00
> Aan: komplete-kontrol-acc...@googlegroups.com
> Onderwerp: Re: [komplete-kontrol-access] Midi problem
>
>
>
> The first thing that occurs to me is that you need to make sure that your
> pedal is connected before powering up the NI keyboard. Once that is the
> case, only then you should boot-up your system. At least as a starting
> point, I'd make sure to follow those steps to eliminate variables.
>
> slau
>
>
>
>
>
>
>
> On Nov 17, 2019, at 1:28 PM, Tom Hessels  <mailto:tomhessel...@gmail.com> > wrote:
>
>
>
> Hi,
>
>
>
> I have to midi devices connected to my mac:
>
> Native instruments s61 keyboard;
>
> Faderport 8.
>
> The last time (I think since I’m using teh Faderport) I have problems with
> the pedals connected to the s61.
>
> Suddenly the sustain does’nt work annymore or the expression pedal acts
> strange.
>
> I have to reset things or even restore a time machine backup.
>
> I had alook at audio midie setup app and saw that both devices use port 1.
>
> Could that be the problem or is is it possible to use mor devices on the
> same port?
>
> I tried to change ports but the app seems not very accessible or am i doing
> things wrong?
>
>
>
> Tom.
>
> Tom Hessels (the Netherlands)
>
>
>
>
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Komplete Kontrol Access" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to  <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com>
> komplete-kontrol-access+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> <https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com?utm_medium=email&utm_source=footer>
> https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Komplete Kontrol Access" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to komplete-kontrol-access+unsubscr...@googlegroups.com
> <mailto:komplete-kontrol-access+unsubscr...@googlegroups.com> .
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com
> <https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
>
>
>
> Van: ptaccess@googlegroups.com  Namens Slau
> Halatyn
> Verzonden: zondag 17 november 2019 16:08
> Aan: PTAccess List 
> Onderwerp: Re: Midi problem
>
>
>
> Not sure as this is not Pro Tools specific but there is a Komplete Kontrol
> email list where somebody might have a better idea. I think you can find
> subscription info on www.kk-access.com <http://www.kk-access.com>
>
> HTH,
>
> Slau
>
>
>
>
>
>
>
> On Nov 17, 2019, at 9:59 AM, Tom Hessel

RE: Midi problem

2019-11-17 Thread Tom Hessels

Hi Slau,

I posted this message in the KK list but because of the fact that it perhaps
has something to do with a pt problem I weill also post it here:

Hi Slau,

The pedals are always connected.

So that’s not the problem.

There is also another strange problem that might be connected with my midi
problem.

How can i explain it (I read a lot of english but i write it not very often)

And perhaps is what i write now is more in place in the ptaccess list.

Ok, when i start pro tools and choose a project from the recent table the
project loads innediate and the faders of the fadeport 8 reacts.

But when i start to play the project I only hear ;my audio tracks. No
instruments tracks are playing and also no effects are heard: no reverbs on
audio tracks etc.

What i do then is loading the project using the .ptx file.

Often then I have that pedal issue.

I’Ll post this message also in ptaccess.

Tom.

Tom Herssels (the Netherlands.)

Van: komplete-kontrol-acc...@googlegroups.com
Namens Slau Halatyn
Verzonden: maandag 18 november 2019 00:00
Aan: komplete-kontrol-acc...@googlegroups.com
Onderwerp: Re: [komplete-kontrol-access] Midi problem

slau

On Nov 17, 2019, at 1:28 PM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi,

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I’m using teh Faderport) I have problems with the
pedals connected to the s61.

Suddenly the sustain does’nt work annymore or the expression pedal acts strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie setup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the same
port?

I tried to change ports but the app seems not very accessible or am i doing
things wrong?

Tom.

Tom Hessels (the Netherlands)

https://groups.google.com/d/msgid/komplete-kontrol-access/001a01d59d74%24d1375810%2473a60830%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups
"Komplete Kontrol Access" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to komplete-kontrol-access+unsubscr...@googlegroups.com
<mailto:komplete-kontrol-access+unsubscr...@googlegroups.com> .
To view this discussion on the web, visit
https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com

<https://groups.google.com/d/msgid/komplete-kontrol-access/CF8D1570-5B7C-4639-B1E4-54B303B37B63%40gmail.com?utm_medium=email&utm_source=footer>
.

Van: ptaccess@googlegroups.com Namens Slau Halatyn
Verzonden: zondag 17 november 2019 16:08
Aan: PTAccess List
Onderwerp: Re: Midi problem

Not sure as this is not Pro Tools specific but there is a Komplete Kontrol
email list where somebody might have a better idea. I think you can find
subscription info on www.kk-access.com <http://www.kk-access.com>

HTH,

Slau

On Nov 17, 2019, at 9:59 AM, Tom Hessels mailto:tomhessel...@gmail.com> > wrote:

Hi,

I have to midi devices connected to my mac:

Native instruments s61 keyboard;

Faderport 8.

The last time (I think since I’m using teh Faderport) I have problems with the
pedals connected to the s61.

Suddenly the sustain does’nt work annymore or the expression pedal acts strange.

I have to reset things or even restore a time machine backup.

I had alook at audio midie srtup app and saw that both devices use port 1.

Could that be the problem or is is it possible to use mor devices on the same
port?

I tried to change ports but the app seems not very accessible or am i doing
things wrong?

Tom.

Tom Hessels (the Netherlands)

Re: Midi problem

2019-11-17 Thread Slau Halatyn

Not sure as this is not Pro Tools specific but there is a Komplete Kontrol 
email list where somebody might have a better idea. I think you can find 
subscription info on www.kk-access.com 
HTH,
Slau


> On Nov 17, 2019, at 9:59 AM, Tom Hessels  wrote:
> 
> Hi,
>  
> I have to midi devices connected to my mac:
> Native instruments s61 keyboard;
> Faderport 8.
> The last time (I think since I’m using teh Faderport) I have problems with 
> the pedals connected to the s61.
> Suddenly the sustain does’nt work annymore or the expression pedal acts 
> strange.
> I have to reset things or even restore a time machine backup.
> I had alook at audio midie srtup app and saw that both devices use port 1.
> Could that be the problem or is is it possible to use mor devices on the same 
> port?
> I tried to change ports but the app seems not very accessible or am i doing 
> things wrong?
>  
> Tom.
> Tom Hessels (the Netherlands)
>  
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ptaccess/000801d59d57%24942647f0%24bc72d7d0%24%40gmail.com
>  
> .

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/2E29C104-395A-45EE-9CDF-41DFF409932B%40gmail.com.

Re: Midi packages accessible out of the box

2019-09-13 Thread jimmie smith

You would be covered out of the box with all that you listed.  Avid does well 
with its plugins.

Jimmie Smith
A+ and MCSA Certified

From: ptaccess@googlegroups.com on behalf of Kenneth Son 
Sent: Friday, September 13, 2019 11:18 AM
To: PTAccess List
Subject: Midi packages accessible out of the box

Greetings.

If I get the Protools program, what midi packs or plugins can I get and
install that will work with Voice over out of the box?

I would want a piano package with the different piano sounds, grands and
upright piano sounds as well as the old time Saloon sounding out of tune
piano sound.

I would also be looking for a good midi set of organ sounds and some
band and orchestra sounds.

Drums to round out the list.

Just what is out there in the way of midi that is truly accessible?

I just want something that is easy to start off with, then later I may
look at this Contact midi plugin or what ever it is.

Thank you much.

Kenneth Son.

--
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ptaccess+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/7a5d10b9-1d74-aa7d-7684-816dafdcfcda%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/SN6PR01MB430432F40C0CC8A5DC78EA5EF6B30%40SN6PR01MB4304.prod.exchangelabs.com.

Re: Midi

2019-05-21 Thread jimmie smith

Thanks for that!



From: ptaccess@googlegroups.com on behalf of CHUCK REICHEL 

Sent: Tuesday, May 21, 2019 2:16 PM
To: ptaccess@googlegroups.com
Subject: Re: Midi

Hi jimmie,
Just use the "commit track" after your done recording the Kick on the 
instrument track.

HTH
Chuck


On May 21, 2019, at 2:20 PM, jimmie smith wrote:

 If I use the drum VST that came with Pro tools, and I want to record a kick 
drum, what is the best way to get that kick drum back down to audio. Do I 
bounce? Or is there an easier way?   Should I buy a dedicated drum VST such as 
superior drummer?


--
You received this message because you are subscribed to the Google 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 
visithttps://groups.google.com/d/msgid/ptaccess/DM6PR01MB562662B5CCFF11234EE1776CF6070%40DM6PR01MB5626.prod.exchangelabs.com<https://groups.google.com/d/msgid/ptaccess/DM6PR01MB562662B5CCFF11234EE1776CF6070%40DM6PR01MB5626.prod.exchangelabs.com?utm_medium=email&utm_source=footer>.
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>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/8A6D35C1-3842-47CA-BEE4-DE795532842F%40gmail.com<https://groups.google.com/d/msgid/ptaccess/8A6D35C1-3842-47CA-BEE4-DE795532842F%40gmail.com?utm_medium=email&utm_source=footer>.
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/DM6PR01MB56264A77FFFA08F86F0A6815F6070%40DM6PR01MB5626.prod.exchangelabs.com.
For more options, visit https://groups.google.com/d/optout.

Re: Midi

2019-05-21 Thread CHUCK REICHEL

Hi jimmie,
Just use the "commit track" after your done recording the Kick on the 
instrument track.

HTH
Chuck


On May 21, 2019, at 2:20 PM, jimmie smith wrote:

>  If I use the drum VST that came with Pro tools, and I want to record a kick 
> drum, what is the best way to get that kick drum back down to audio. Do I 
> bounce? Or is there an easier way?   Should I buy a dedicated drum VST such 
> as superior drummer?  
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> To view this discussion on the web 
> visithttps://groups.google.com/d/msgid/ptaccess/DM6PR01MB562662B5CCFF11234EE1776CF6070%40DM6PR01MB5626.prod.exchangelabs.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ptaccess/8A6D35C1-3842-47CA-BEE4-DE795532842F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: midi event list problem

2019-03-12 Thread 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  <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.
&

RE: midi event list problem

2019-03-12 Thread 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>  
[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 < <mailto:tomhessel...@gmail.com> 
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 p

Re: midi event list problem

2019-03-08 Thread Slau Halatyn

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

RE: midi event list problem

2019-03-08 Thread Tom Hessels

Hi Slau,

 

Thank you for your answer. As you probably know now I’m not a native English 
speaker so i have to search the dutch translation for swamped. 

Take your time.

I can wait and take your rest, man.

 

Tom.

 

 

 

Van: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] Namens Slau 
Halatyn
Verzonden: donderdag 7 maart 2019 19:30
Aan: PTAccess List 
Onderwerp: Re: midi event list problem

 

Hi Tom,

I'm swamped right now but will reply more fully later.

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>  
[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 < <mailto:tomhessel...@gmail.com> 
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:  <mailto:ptaccess@googlegroups.com> 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

Re: midi event list problem

2019-03-07 Thread Slau Halatyn

Hi Tom,
I'm swamped right now but will reply more fully later.
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. 
> 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 
> 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 > <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 
>&

RE: midi event list problem

2019-03-07 Thread Tom Hessels

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 
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 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] 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 < <mailto:tomhessel...@gmail.com> 
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

RE: midi event list problem

2018-12-20 Thread Tom Hessels

Just changed default language settings to English with no result.

 

Tom.

 

 

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

 

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 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: midi event list problem

2018-12-20 Thread Slau Halatyn

Ah, but it just occurred to me that you don't need to use Control, just use the 
arrow keys while making sure the track is in Note View. That's one of the 
things where Flo Tools was one step ahead of Avid in implementing such a simple 
method. Avid's workflow directly supports the arrow key navigation so no need 
to rely on the Flo Tools command, although you can have Flo Tools report a 
bunch of different info while navigating each note.
HTH,
Slau

> On Dec 20, 2018, at 8:19 AM, Tom Hessels  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] 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 > <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.
For more options, visit https://groups.google.com/d/optout.

Re: midi event list problem

2018-12-20 Thread Slau Halatyn

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  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] 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 > <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.
For more options, visit https://groups.google.com/d/optout.

RE: midi event list problem

2018-12-20 Thread Tom Hessels

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

 

-- 
You received this message because you are subscribed to the Google Groups "Pro 
Tools Accessibility" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 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: midi event list problem

2018-12-19 Thread Slau Halatyn

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  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 
> .
> 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: MIDI with Pro Tools12.8.2

2017-11-03 Thread Slau Halatyn

Hi Martin,

That shortcuts document was based on version 12.6 and the shortcut was 
certainly there before 12.8.2. I'm not sure precisely which version saw its 
introduction. I'll be creating a new shortcuts document in the near future.
Best,
Slau

> On Nov 3, 2017, at 9:18 AM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau!
> 
> I tryed to find the Control+NumpadMinus key combination in the Pro Tools 
> shortcut document you wrote some time ago and also in the "What's new in 
> version 12.8.2"
> No success..
> 
> Where did you find it and are there additional ones to change selected MIDI?
> 
> Thanks and best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Slau Halatyn
>> Sent: Thursday, November 2, 2017 5:57 PM
>> To: PTAccess List 
>> Subject: Re: MIDI with Pro Tools12.8.2
>> 
>> Hi Martin,
>> 
>> It's not exactly clear what you're trying to accomplish. I mean, it's 
>> probably
>> clear in your mind but, upon reading, one could interpret your message a
>> couple of ways. so, I'm going to assume you mean that you wish to transpose
>> each instance of a particular MIDI note like, say, B flat 3 to a different 
>> MIDI
>> note like C4. Is that what you mean?
>> 
>> If so, I'm also going to assume that you've chosen the second radio button in
>> the Select/Split Notes dialog and that you're not using other criteria and,
>> finally, that you've enabled the radio button to select notes rather than 
>> split
>> them. Assuming you've entered in the correct note range in the edit fields,
>> pressing Apply should correctly select the notes within the range. Rather
>> than transposing, you can use Control num pad plus or minus to transpose
>> the selected notes up or down a semitone without using the Transpose
>> dialog. It works fine for me. Let me know what you find.
>> 
>> Slau
>> 
>> 
>>> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart 
>> wrote:
>>> 
>>> Hello!
>>> 
>>> I have a midi track, trackview is notes.
>>> Now I select the whole track.
>>> Then I press option+y to select one of the midi notes for later transposing.
>>> After the selection I press option+t and chose the transpose step.
>>> And after that all notes became transposed. Not only the before selected
>> one.
>>> With older versions of Pro Tools the way described worked fine.
>>> 
>>> Did I miss any ting or is there a change in Pro Tools?
>>> 
>>> Best! / Martin
>>> 
>>> --
>>> You received this message because you are subscribed to the Google
>> Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 with Pro Tools12.8.2

2017-11-03 Thread Martin (Punky) Sopart

Hello Slau!

I tryed to find the Control+NumpadMinus key combination in the Pro Tools 
shortcut document you wrote some time ago and also in the "What's new in 
version 12.8.2"
No success..

Where did you find it and are there additional ones to change selected MIDI?

Thanks and best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Slau Halatyn
> Sent: Thursday, November 2, 2017 5:57 PM
> To: PTAccess List 
> Subject: Re: MIDI with Pro Tools12.8.2
> 
> Hi Martin,
> 
> It's not exactly clear what you're trying to accomplish. I mean, it's probably
> clear in your mind but, upon reading, one could interpret your message a
> couple of ways. so, I'm going to assume you mean that you wish to transpose
> each instance of a particular MIDI note like, say, B flat 3 to a different 
> MIDI
> note like C4. Is that what you mean?
> 
> If so, I'm also going to assume that you've chosen the second radio button in
> the Select/Split Notes dialog and that you're not using other criteria and,
> finally, that you've enabled the radio button to select notes rather than 
> split
> them. Assuming you've entered in the correct note range in the edit fields,
> pressing Apply should correctly select the notes within the range. Rather
> than transposing, you can use Control num pad plus or minus to transpose
> the selected notes up or down a semitone without using the Transpose
> dialog. It works fine for me. Let me know what you find.
> 
> Slau
> 
> 
> > On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart 
> wrote:
> >
> > Hello!
> >
> > I have a midi track, trackview is notes.
> > Now I select the whole track.
> > Then I press option+y to select one of the midi notes for later transposing.
> > After the selection I press option+t and chose the transpose step.
> > And after that all notes became transposed. Not only the before selected
> one.
> > With older versions of Pro Tools the way described worked fine.
> >
> > Did I miss any ting or is there a change in Pro Tools?
> >
> > Best! / Martin
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

RE: MIDI with Pro Tools12.8.2

2017-11-03 Thread Martin (Punky) Sopart

Hello Slau!

So far no FaceBook and What's App for me.
A very lot of traffic to get through.
Hoping that mails still be there for some time.

Best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Slau Halatyn
> Sent: Thursday, November 2, 2017 6:35 PM
> To: ptaccess@googlegroups.com
> Subject: Re: MIDI with Pro Tools12.8.2
> 
> Also curious why you're not on the What's App group?
> > On Nov 2, 2017, at 1:23 PM, Martin (Punky) Sopart 
> wrote:
> >
> > Funny…
> >
> > When entering the note values with the Apple keyboard and not with the
> midi keyboard, the selection works.
> > Both are blue tooth devices.
> > And the entries in the edit fields look the same…
> >
> > Best! / Martin
> >
> >
> > Am 02.11.2017 um 17:57 schrieb Slau Halatyn :
> >
> > Hi Martin,
> >
> > It's not exactly clear what you're trying to accomplish. I mean, it's 
> > probably
> clear in your mind but, upon reading, one could interpret your message a
> couple of ways. so, I'm going to assume you mean that you wish to transpose
> each instance of a particular MIDI note like, say, B flat 3 to a different 
> MIDI
> note like C4. Is that what you mean?
> >
> > If so, I'm also going to assume that you've chosen the second radio button
> in the Select/Split Notes dialog and that you're not using other criteria and,
> finally, that you've enabled the radio button to select notes rather than 
> split
> them. Assuming you've entered in the correct note range in the edit fields,
> pressing Apply should correctly select the notes within the range. Rather
> than transposing, you can use Control num pad plus or minus to transpose
> the selected notes up or down a semitone without using the Transpose
> dialog. It works fine for me. Let me know what you find.
> >
> > Slau
> >
> >
> >> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart
>  wrote:
> >>
> >> Hello!
> >>
> >> I have a midi track, trackview is notes.
> >> Now I select the whole track.
> >> Then I press option+y to select one of the midi notes for later 
> >> transposing.
> >> After the selection I press option+t and chose the transpose step.
> >> And after that all notes became transposed. Not only the before selected
> one.
> >> With older versions of Pro Tools the way described worked fine.
> >>
> >> Did I miss any ting or is there a change in Pro Tools?
> >>
> >> Best! / Martin
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google 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: MIDI with Pro Tools12.8.2

2017-11-02 Thread Slau Halatyn

Awesome :)

> On Nov 2, 2017, at 1:59 PM, Martin (Punky) Sopart  wrote:
> 
> Hello Slau!
> 
> It is working now for me.
> And using the midi keyboard you are so right. I missed the enter key after 
> pressing the note on the midi keyboard.
> I have to add that to my Pro Tools documentation.
> 
> Yes, I am running 12.8.2 and the arrow keys to select a midi note are working 
> and also the transposing afterwards using Control+NumpadMinus and 
> Control+NumpadPlus.
> 
> Best! / Martin
> 
> Am 02.11.2017 um 18:33 schrieb Slau Halatyn :
> 
> Hi Martin,
> But does that mean that it's working for you now? It's a bit quirky but, 
> after entering a value, I think you need to hit Return for it to take effect 
> and then hit Apply. Keep me posted. If you're on 12.8.2, in Notes View, press 
> the right arrow to select one note and try to transpose it. Does that work? 
> Curious.
> 
>> On Nov 2, 2017, at 1:23 PM, Martin (Punky) Sopart  wrote:
>> 
>> Funny…
>> 
>> When entering the note values with the Apple keyboard and not with the midi 
>> keyboard, the selection works.
>> Both are blue tooth devices.
>> And the entries in the edit fields look the same…
>> 
>> Best! / Martin
>> 
>> 
>> Am 02.11.2017 um 17:57 schrieb Slau Halatyn :
>> 
>> Hi Martin,
>> 
>> It's not exactly clear what you're trying to accomplish. I mean, it's 
>> probably clear in your mind but, upon reading, one could interpret your 
>> message a couple of ways. so, I'm going to assume you mean that you wish to 
>> transpose each instance of a particular MIDI note like, say, B flat 3 to a 
>> different MIDI note like C4. Is that what you mean?
>> 
>> If so, I'm also going to assume that you've chosen the second radio button 
>> in the Select/Split Notes dialog and that you're not using other criteria 
>> and, finally, that you've enabled the radio button to select notes rather 
>> than split them. Assuming you've entered in the correct note range in the 
>> edit fields, pressing Apply should correctly select the notes within the 
>> range. Rather than transposing, you can use Control num pad plus or minus to 
>> transpose the selected notes up or down a semitone without using the 
>> Transpose dialog. It works fine for me. Let me know what you find.
>> 
>> Slau
>> 
>> 
>>> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  
>>> wrote:
>>> 
>>> Hello!
>>> 
>>> I have a midi track, trackview is notes.
>>> Now I select the whole track.
>>> Then I press option+y to select one of the midi notes for later transposing.
>>> After the selection I press option+t and chose the transpose step.
>>> And after that all notes became transposed. Not only the before selected 
>>> one.
>>> With older versions of Pro Tools the way described worked fine.
>>> 
>>> Did I miss any ting or is there a change in Pro Tools?
>>> 
>>> Best! / Martin
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google 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: MIDI with Pro Tools12.8.2

2017-11-02 Thread Martin (Punky) Sopart

Hello Slau!

It is working now for me.
And using the midi keyboard you are so right. I missed the enter key after 
pressing the note on the midi keyboard.
I have to add that to my Pro Tools documentation.

Yes, I am running 12.8.2 and the arrow keys to select a midi note are working 
and also the transposing afterwards using Control+NumpadMinus and 
Control+NumpadPlus.

Best! / Martin

Am 02.11.2017 um 18:33 schrieb Slau Halatyn :

Hi Martin,
But does that mean that it's working for you now? It's a bit quirky but, after 
entering a value, I think you need to hit Return for it to take effect and then 
hit Apply. Keep me posted. If you're on 12.8.2, in Notes View, press the right 
arrow to select one note and try to transpose it. Does that work? Curious.

> On Nov 2, 2017, at 1:23 PM, Martin (Punky) Sopart  wrote:
> 
> Funny…
> 
> When entering the note values with the Apple keyboard and not with the midi 
> keyboard, the selection works.
> Both are blue tooth devices.
> And the entries in the edit fields look the same…
> 
> Best! / Martin
> 
> 
> Am 02.11.2017 um 17:57 schrieb Slau Halatyn :
> 
> Hi Martin,
> 
> It's not exactly clear what you're trying to accomplish. I mean, it's 
> probably clear in your mind but, upon reading, one could interpret your 
> message a couple of ways. so, I'm going to assume you mean that you wish to 
> transpose each instance of a particular MIDI note like, say, B flat 3 to a 
> different MIDI note like C4. Is that what you mean?
> 
> If so, I'm also going to assume that you've chosen the second radio button in 
> the Select/Split Notes dialog and that you're not using other criteria and, 
> finally, that you've enabled the radio button to select notes rather than 
> split them. Assuming you've entered in the correct note range in the edit 
> fields, pressing Apply should correctly select the notes within the range. 
> Rather than transposing, you can use Control num pad plus or minus to 
> transpose the selected notes up or down a semitone without using the 
> Transpose dialog. It works fine for me. Let me know what you find.
> 
> Slau
> 
> 
>> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> I have a midi track, trackview is notes.
>> Now I select the whole track.
>> Then I press option+y to select one of the midi notes for later transposing.
>> After the selection I press option+t and chose the transpose step.
>> And after that all notes became transposed. Not only the before selected one.
>> With older versions of Pro Tools the way described worked fine.
>> 
>> Did I miss any ting or is there a change in Pro Tools?
>> 
>> Best! / Martin
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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: MIDI with Pro Tools12.8.2

2017-11-02 Thread Slau Halatyn

Also curious why you're not on the What's App group?
> On Nov 2, 2017, at 1:23 PM, Martin (Punky) Sopart  wrote:
> 
> Funny…
> 
> When entering the note values with the Apple keyboard and not with the midi 
> keyboard, the selection works.
> Both are blue tooth devices.
> And the entries in the edit fields look the same…
> 
> Best! / Martin
> 
> 
> Am 02.11.2017 um 17:57 schrieb Slau Halatyn :
> 
> Hi Martin,
> 
> It's not exactly clear what you're trying to accomplish. I mean, it's 
> probably clear in your mind but, upon reading, one could interpret your 
> message a couple of ways. so, I'm going to assume you mean that you wish to 
> transpose each instance of a particular MIDI note like, say, B flat 3 to a 
> different MIDI note like C4. Is that what you mean?
> 
> If so, I'm also going to assume that you've chosen the second radio button in 
> the Select/Split Notes dialog and that you're not using other criteria and, 
> finally, that you've enabled the radio button to select notes rather than 
> split them. Assuming you've entered in the correct note range in the edit 
> fields, pressing Apply should correctly select the notes within the range. 
> Rather than transposing, you can use Control num pad plus or minus to 
> transpose the selected notes up or down a semitone without using the 
> Transpose dialog. It works fine for me. Let me know what you find.
> 
> Slau
> 
> 
>> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> I have a midi track, trackview is notes.
>> Now I select the whole track.
>> Then I press option+y to select one of the midi notes for later transposing.
>> After the selection I press option+t and chose the transpose step.
>> And after that all notes became transposed. Not only the before selected one.
>> With older versions of Pro Tools the way described worked fine.
>> 
>> Did I miss any ting or is there a change in Pro Tools?
>> 
>> Best! / Martin
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 with Pro Tools12.8.2

2017-11-02 Thread Slau Halatyn

Hi Martin,
But does that mean that it's working for you now? It's a bit quirky but, after 
entering a value, I think you need to hit Return for it to take effect and then 
hit Apply. Keep me posted. If you're on 12.8.2, in Notes View, press the right 
arrow to select one note and try to transpose it. Does that work? Curious.

> On Nov 2, 2017, at 1:23 PM, Martin (Punky) Sopart  wrote:
> 
> Funny…
> 
> When entering the note values with the Apple keyboard and not with the midi 
> keyboard, the selection works.
> Both are blue tooth devices.
> And the entries in the edit fields look the same…
> 
> Best! / Martin
> 
> 
> Am 02.11.2017 um 17:57 schrieb Slau Halatyn :
> 
> Hi Martin,
> 
> It's not exactly clear what you're trying to accomplish. I mean, it's 
> probably clear in your mind but, upon reading, one could interpret your 
> message a couple of ways. so, I'm going to assume you mean that you wish to 
> transpose each instance of a particular MIDI note like, say, B flat 3 to a 
> different MIDI note like C4. Is that what you mean?
> 
> If so, I'm also going to assume that you've chosen the second radio button in 
> the Select/Split Notes dialog and that you're not using other criteria and, 
> finally, that you've enabled the radio button to select notes rather than 
> split them. Assuming you've entered in the correct note range in the edit 
> fields, pressing Apply should correctly select the notes within the range. 
> Rather than transposing, you can use Control num pad plus or minus to 
> transpose the selected notes up or down a semitone without using the 
> Transpose dialog. It works fine for me. Let me know what you find.
> 
> Slau
> 
> 
>> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  
>> wrote:
>> 
>> Hello!
>> 
>> I have a midi track, trackview is notes.
>> Now I select the whole track.
>> Then I press option+y to select one of the midi notes for later transposing.
>> After the selection I press option+t and chose the transpose step.
>> And after that all notes became transposed. Not only the before selected one.
>> With older versions of Pro Tools the way described worked fine.
>> 
>> Did I miss any ting or is there a change in Pro Tools?
>> 
>> Best! / Martin
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 with Pro Tools12.8.2

2017-11-02 Thread Martin (Punky) Sopart

Funny…

When entering the note values with the Apple keyboard and not with the midi 
keyboard, the selection works.
Both are blue tooth devices.
And the entries in the edit fields look the same…

Best! / Martin

Am 02.11.2017 um 17:57 schrieb Slau Halatyn :

Hi Martin,

It's not exactly clear what you're trying to accomplish. I mean, it's probably 
clear in your mind but, upon reading, one could interpret your message a couple 
of ways. so, I'm going to assume you mean that you wish to transpose each 
instance of a particular MIDI note like, say, B flat 3 to a different MIDI note 
like C4. Is that what you mean?

If so, I'm also going to assume that you've chosen the second radio button in 
the Select/Split Notes dialog and that you're not using other criteria and, 
finally, that you've enabled the radio button to select notes rather than split 
them. Assuming you've entered in the correct note range in the edit fields, 
pressing Apply should correctly select the notes within the range. Rather than 
transposing, you can use Control num pad plus or minus to transpose the 
selected notes up or down a semitone without using the Transpose dialog. It 
works fine for me. Let me know what you find.

Slau

> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  wrote:
> 
> Hello!
> 
> I have a midi track, trackview is notes.
> Now I select the whole track.
> Then I press option+y to select one of the midi notes for later transposing.
> After the selection I press option+t and chose the transpose step.
> And after that all notes became transposed. Not only the before selected one.
> With older versions of Pro Tools the way described worked fine.
> 
> Did I miss any ting or is there a change in Pro Tools?
> 
> Best! / Martin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

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

Re: MIDI with Pro Tools12.8.2

2017-11-02 Thread Martin (Punky) Sopart

Hi Slau and thanks for your fast response.

Yes, yes and yes :-)

I want to select  all  D1 notes of the whole instrument track to transpose them 
to A1.
It is a drum track.

When using control+numpadMinus or -Plus, all the C1 notes are transposed, too.

So my selection must be wrong.

Strange, best! / Martin

Am 02.11.2017 um 17:57 schrieb Slau Halatyn :

Hi Martin,

It's not exactly clear what you're trying to accomplish. I mean, it's probably 
clear in your mind but, upon reading, one could interpret your message a couple 
of ways. so, I'm going to assume you mean that you wish to transpose each 
instance of a particular MIDI note like, say, B flat 3 to a different MIDI note 
like C4. Is that what you mean?

If so, I'm also going to assume that you've chosen the second radio button in 
the Select/Split Notes dialog and that you're not using other criteria and, 
finally, that you've enabled the radio button to select notes rather than split 
them. Assuming you've entered in the correct note range in the edit fields, 
pressing Apply should correctly select the notes within the range. Rather than 
transposing, you can use Control num pad plus or minus to transpose the 
selected notes up or down a semitone without using the Transpose dialog. It 
works fine for me. Let me know what you find.

Slau

> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  wrote:
> 
> Hello!
> 
> I have a midi track, trackview is notes.
> Now I select the whole track.
> Then I press option+y to select one of the midi notes for later transposing.
> After the selection I press option+t and chose the transpose step.
> And after that all notes became transposed. Not only the before selected one.
> With older versions of Pro Tools the way described worked fine.
> 
> Did I miss any ting or is there a change in Pro Tools?
> 
> Best! / Martin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

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

Re: MIDI with Pro Tools12.8.2

2017-11-02 Thread Slau Halatyn

Hi Martin,

It's not exactly clear what you're trying to accomplish. I mean, it's probably 
clear in your mind but, upon reading, one could interpret your message a couple 
of ways. so, I'm going to assume you mean that you wish to transpose each 
instance of a particular MIDI note like, say, B flat 3 to a different MIDI note 
like C4. Is that what you mean?

If so, I'm also going to assume that you've chosen the second radio button in 
the Select/Split Notes dialog and that you're not using other criteria and, 
finally, that you've enabled the radio button to select notes rather than split 
them. Assuming you've entered in the correct note range in the edit fields, 
pressing Apply should correctly select the notes within the range. Rather than 
transposing, you can use Control num pad plus or minus to transpose the 
selected notes up or down a semitone without using the Transpose dialog. It 
works fine for me. Let me know what you find.

Slau

> On Nov 2, 2017, at 12:34 PM, Martin (Punky) Sopart  wrote:
> 
> Hello!
> 
> I have a midi track, trackview is notes.
> Now I select the whole track.
> Then I press option+y to select one of the midi notes for later transposing.
> After the selection I press option+t and chose the transpose step.
> And after that all notes became transposed. Not only the before selected one.
> With older versions of Pro Tools the way described worked fine.
> 
> Did I miss any ting or is there a change in Pro Tools?
> 
> Best! / Martin
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: Midi event list

2017-06-09 Thread Slau Halatyn

Great point, Martin, and thanks for pointing that out. Indeed, when navigating 
while tabbing, if things have been edited, it gets a bit crazy with clip 
layering. Awesome.
Slau

> On Jun 9, 2017, at 4:25 AM, Martin (Punky) Sopart  wrote:
> 
> Hi Andre!
> 
> In addition to Slau's helpful explanations.
> 
> When working with midi in the counter display cluster, everything is fine 
> until you start editing the midi track like copying / pasting etc.
> After that edits you have to consolidate the track again to make Shure that 
> the tab key will bring you to the next midi event the whole track through.
> Same for ottion+tab for the prior midi event.
> 
> After every edit of the midi track a new clip is created and the midi event 
> navigation in the counter display cluster only works for the current clip.
> Consolidating the whole track again will make one large clip out of all clips.
> 
> To consolidate:
> Set the track view to notes.
> Select the desired track from start to end.
> Consolidate by pressing shift+option+3.
> Set the track view back to clips.
> 
> Good success! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Slau Halatyn
>> Sent: Thursday, June 8, 2017 5:27 PM
>> To: PTAccess List 
>> Subject: Re: Midi event list
>> 
>> Hi Andre,
>> Although it's technically accessible in the sense that VoiceOver sees the
>> elements within each column, it's just a little tricky to work with and I'll
>> explain a few things you can do to get around it. Before I do, I must say, 
>> the
>> upcoming Flo Tools will make all of this a moot point but it doesn't hurt to
>> have a backup plan when you're working on a system that doesn't have Flo
>> Tools.
>> 
>> First, VoiceOver can read down an area beyond what is displayed visually on
>> screen. This is both good and bad. If you navigate the event list with
>> VoiceOver only, you can certainly select notes (even discontiguously) and do
>> things like delete or edit using event operations. However, if you want to do
>> things like double-click to type a new value directly, you have to make sure
>> the selected event is visible in the window. Pressing Command+h will bring
>> the selection into view. For VoiceOver to see it correctly, though, you'll 
>> need
>> to stop interacting with the table and then re-interact. Then performing a
>> double-click will work as expected.
>> 
>> Rather than doing that, however, it's possible to edit without clicking, per 
>> se.
>> When an event is selected, pressing Command+Enter (on the numeric key
>> pad) will put the event into an edit field which will always start with the 
>> first
>> column. Pressing right arrow will advance the edit field to the next column.
>> Be aware that the second column will either be beats or seconds, depending
>> on the main counter format. Having pressed the right arrow 3 times, you'd be
>> on the note field. Type a value and press either enter or return. With this
>> method, you don't have to worry about what's in focus in the Event List
>> window.
>> 
>> Alternatively, you can also focus on the counter display cluster in the Edit
>> window and, as you use the Tab key to advance to each note, the note name
>> along with a few other controls will be displayed and you can double-click to
>> edit those values. There's a caveat in that you have to make sure you're
>> tabbing through a contiguous clip but in Notes view in the track view 
>> options.
>> 
>> Again, this will all be a lot simpler when Flo Tools 2.2 is out. It'll be 
>> just a few
>> more days.
>> 
>> HTH,
>> Slau
>> 
>>> On Jun 8, 2017, at 7:39 AM, Andre Woods 
>> wrote:
>>> 
>>> 
>>> 
>>> Sent from my iPhonehello to all,
>>> 
>>> Is the midi event list accessible with voice over on protools? If so, how do
>> you change the note value on it?
>>> Best regards,
>>> Andre Woods
>>> 
>>> --
>>> You received this message because you are subscribed to the Google
>> 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.
>>

RE: Midi event list

2017-06-09 Thread Martin (Punky) Sopart

Hi Andre!

In addition to Slau's helpful explanations.

When working with midi in the counter display cluster, everything is fine until 
you start editing the midi track like copying / pasting etc.
After that edits you have to consolidate the track again to make Shure that the 
tab key will bring you to the next midi event the whole track through.
Same for ottion+tab for the prior midi event.

After every edit of the midi track a new clip is created and the midi event 
navigation in the counter display cluster only works for the current clip.
Consolidating the whole track again will make one large clip out of all clips.

To consolidate:
Set the track view to notes.
Select the desired track from start to end.
Consolidate by pressing shift+option+3.
Set the track view back to clips.

Good success! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Slau Halatyn
> Sent: Thursday, June 8, 2017 5:27 PM
> To: PTAccess List 
> Subject: Re: Midi event list
> 
> Hi Andre,
> Although it's technically accessible in the sense that VoiceOver sees the
> elements within each column, it's just a little tricky to work with and I'll
> explain a few things you can do to get around it. Before I do, I must say, the
> upcoming Flo Tools will make all of this a moot point but it doesn't hurt to
> have a backup plan when you're working on a system that doesn't have Flo
> Tools.
> 
> First, VoiceOver can read down an area beyond what is displayed visually on
> screen. This is both good and bad. If you navigate the event list with
> VoiceOver only, you can certainly select notes (even discontiguously) and do
> things like delete or edit using event operations. However, if you want to do
> things like double-click to type a new value directly, you have to make sure
> the selected event is visible in the window. Pressing Command+h will bring
> the selection into view. For VoiceOver to see it correctly, though, you'll 
> need
> to stop interacting with the table and then re-interact. Then performing a
> double-click will work as expected.
> 
> Rather than doing that, however, it's possible to edit without clicking, per 
> se.
> When an event is selected, pressing Command+Enter (on the numeric key
> pad) will put the event into an edit field which will always start with the 
> first
> column. Pressing right arrow will advance the edit field to the next column.
> Be aware that the second column will either be beats or seconds, depending
> on the main counter format. Having pressed the right arrow 3 times, you'd be
> on the note field. Type a value and press either enter or return. With this
> method, you don't have to worry about what's in focus in the Event List
> window.
> 
> Alternatively, you can also focus on the counter display cluster in the Edit
> window and, as you use the Tab key to advance to each note, the note name
> along with a few other controls will be displayed and you can double-click to
> edit those values. There's a caveat in that you have to make sure you're
> tabbing through a contiguous clip but in Notes view in the track view options.
> 
> Again, this will all be a lot simpler when Flo Tools 2.2 is out. It'll be 
> just a few
> more days.
> 
> HTH,
> Slau
> 
> > On Jun 8, 2017, at 7:39 AM, Andre Woods 
> wrote:
> >
> >
> >
> > Sent from my iPhonehello to all,
> >
> > Is the midi event list accessible with voice over on protools? If so, how do
> you change the note value on it?
> > Best regards,
> > Andre Woods
> >
> > --
> > You received this message because you are subscribed to the Google
> 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: Midi event list

2017-06-08 Thread Brian Howerton

Sweet, can’t wait for flo tools 2.2!  Waiting with much anticipation!
> On Jun 8, 2017, at 11:27 AM, Slau Halatyn  wrote:
> 
> Hi Andre,
> Although it's technically accessible in the sense that VoiceOver sees the 
> elements within each column, it's just a little tricky to work with and I'll 
> explain a few things you can do to get around it. Before I do, I must say, 
> the upcoming Flo Tools will make all of this a moot point but it doesn't hurt 
> to have a backup plan when you're working on a system that doesn't have Flo 
> Tools.
> 
> First, VoiceOver can read down an area beyond what is displayed visually on 
> screen. This is both good and bad. If you navigate the event list with 
> VoiceOver only, you can certainly select notes (even discontiguously) and do 
> things like delete or edit using event operations. However, if you want to do 
> things like double-click to type a new value directly, you have to make sure 
> the selected event is visible in the window. Pressing Command+h will bring 
> the selection into view. For VoiceOver to see it correctly, though, you'll 
> need to stop interacting with the table and then re-interact. Then performing 
> a double-click will work as expected.
> 
> Rather than doing that, however, it's possible to edit without clicking, per 
> se. When an event is selected, pressing Command+Enter (on the numeric key 
> pad) will put the event into an edit field which will always start with the 
> first column. Pressing right arrow will advance the edit field to the next 
> column. Be aware that the second column will either be beats or seconds, 
> depending on the main counter format. Having pressed the right arrow 3 times, 
> you'd be on the note field. Type a value and press either enter or return. 
> With this method, you don't have to worry about what's in focus in the Event 
> List window.
> 
> Alternatively, you can also focus on the counter display cluster in the Edit 
> window and, as you use the Tab key to advance to each note, the note name 
> along with a few other controls will be displayed and you can double-click to 
> edit those values. There's a caveat in that you have to make sure you're 
> tabbing through a contiguous clip but in Notes view in the track view options.
> 
> Again, this will all be a lot simpler when Flo Tools 2.2 is out. It'll be 
> just a few more days.
> 
> HTH,
> Slau
> 
>> On Jun 8, 2017, at 7:39 AM, Andre Woods  wrote:
>> 
>> 
>> 
>> Sent from my iPhonehello to all, 
>> 
>> Is the midi event list accessible with voice over on protools? If so, how do 
>> you change the note value on it?
>> Best regards, 
>> Andre Woods
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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: Midi event list

2017-06-08 Thread Slau Halatyn

Hi Andre,
Although it's technically accessible in the sense that VoiceOver sees the 
elements within each column, it's just a little tricky to work with and I'll 
explain a few things you can do to get around it. Before I do, I must say, the 
upcoming Flo Tools will make all of this a moot point but it doesn't hurt to 
have a backup plan when you're working on a system that doesn't have Flo Tools.

First, VoiceOver can read down an area beyond what is displayed visually on 
screen. This is both good and bad. If you navigate the event list with 
VoiceOver only, you can certainly select notes (even discontiguously) and do 
things like delete or edit using event operations. However, if you want to do 
things like double-click to type a new value directly, you have to make sure 
the selected event is visible in the window. Pressing Command+h will bring the 
selection into view. For VoiceOver to see it correctly, though, you'll need to 
stop interacting with the table and then re-interact. Then performing a 
double-click will work as expected.

Rather than doing that, however, it's possible to edit without clicking, per 
se. When an event is selected, pressing Command+Enter (on the numeric key pad) 
will put the event into an edit field which will always start with the first 
column. Pressing right arrow will advance the edit field to the next column. Be 
aware that the second column will either be beats or seconds, depending on the 
main counter format. Having pressed the right arrow 3 times, you'd be on the 
note field. Type a value and press either enter or return. With this method, 
you don't have to worry about what's in focus in the Event List window.

Alternatively, you can also focus on the counter display cluster in the Edit 
window and, as you use the Tab key to advance to each note, the note name along 
with a few other controls will be displayed and you can double-click to edit 
those values. There's a caveat in that you have to make sure you're tabbing 
through a contiguous clip but in Notes view in the track view options.

Again, this will all be a lot simpler when Flo Tools 2.2 is out. It'll be just 
a few more days.

HTH,
Slau

> On Jun 8, 2017, at 7:39 AM, Andre Woods  wrote:
> 
> 
> 
> Sent from my iPhonehello to all, 
> 
> Is the midi event list accessible with voice over on protools? If so, how do 
> you change the note value on it?
> Best regards, 
> Andre Woods
> 
> -- 
> You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-11 Thread Slau Halatyn

Hi Joy,
Well, to an extent, you can transpose within the Edit window as long as the 
selected note pitch within the Counter Display cluster is double-clicked. You 
can then press any key on your MIDI keyboard to change the pitch. The Transpose 
window does retain your previous settings so you can pretty quickly bring up 
the Transpose window as well. But regarding notes vs. clips, when using tab 
commands along with modifiers, it is necessary to switch between notes and 
clips when you want to edit one over the other. Hope that makes sense.
Best,
Slau

> On Jan 11, 2017, at 10:49 AM, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Slau, 
> thanks for the tipp. Will do that and see how things work.
> I hope you don't mind me asking another, related, question...or two. *smile*
> When in notes.view, is it still possible to select clips?
> I found out that you can move, or nudge, individual midi notes while in the 
> note-view, but can you also transpose from the edit window?
> 
> best,
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
> Am 11.01.2017 um 15:03 schrieb CHUCK REICHEL  >:
> 
>> Hi Kevin,
>> You can't "ASSUME" flowtools is being used! :)
>> HTH
>> Chuck
>> 
>> 
>> On Jan 10, 2017, at 6:19 PM, Kevin Reeves wrote:
>> 
>>> Why mark the track with a hotspot when we now have FloTools?
>>> 
>>> On 1/10/2017 5:32 PM, CHUCK REICHEL wrote:
 Hi Joy,
 First of all you half to have made a selection in the track your going to 
 quantize.
 Second of all you half to make sure the track is still selected in the 
 tracks list.
 I mark the track with a hotspot in the tracks list and query the hotspot 
 to make sure its still selected before trying to edit it! :)
 I've noticed that tracks drop out of being selected for a while now, and 
 still need to track down what causes it to get un selected.
 But most of all I "ALWAYS" hide all tracks not being edited to avoid 
 issues that might come up.
 HTH
 Chuck
 
 CHUCK REICHEL
 soundpicturerecord...@gmail.com 
 www.SoundPictureRecording.com 
 954-742-0019
 Isaiah 26 : 3
  Thou wilt keep him in perfect peace, whose mind is stayed on thee: 
 because he trusteth in thee.
 
 In GOD I Trust
 
 On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
 wrote:
 
> Hey list,
> i've encountered the following situation when tracking MIDI in PT12.7. 
> Maybe someone can either reproduce this, or point out what i'm doing 
> wrong.
> Scenario: I have, let's say, 6 Instrument tracks going, and record on 
> them in sequence. So, 16 bars, then add another 8, and so on.
> I've noticed that for some reason the quantize-function stops working 
> after a while. I call it up, option 0, and the apply button is greyed out.
> Why is that?
> 
> thanks for any suggestions,
> 
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
> -- 
> You received this message because you are subscribed to the Google 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 ptacc

Re: Midi help needed

2017-01-11 Thread 'Joy Bausch' via Pro Tools Accessibility

Slau, 
thanks for the tipp. Will do that and see how things work.
I hope you don't mind me asking another, related, question...or two. *smile*
When in notes.view, is it still possible to select clips?
I found out that you can move, or nudge, individual midi notes while in the 
note-view, but can you also transpose from the edit window?

best,
Joy


Von meinem iPhone gesendet

> Am 11.01.2017 um 15:03 schrieb CHUCK REICHEL 
> :
> 
> Hi Kevin,
> You can't "ASSUME" flowtools is being used! :)
> HTH
> Chuck
> 
> 
>> On Jan 10, 2017, at 6:19 PM, Kevin Reeves wrote:
>> 
>> Why mark the track with a hotspot when we now have FloTools?
>> 
>>> On 1/10/2017 5:32 PM, CHUCK REICHEL wrote:
>>> Hi Joy,
>>> First of all you half to have made a selection in the track your going to 
>>> quantize.
>>> Second of all you half to make sure the track is still selected in the 
>>> tracks list.
>>> I mark the track with a hotspot in the tracks list and query the hotspot to 
>>> make sure its still selected before trying to edit it! :)
>>> I've noticed that tracks drop out of being selected for a while now, and 
>>> still need to track down what causes it to get un selected.
>>> But most of all I "ALWAYS" hide all tracks not being edited to avoid issues 
>>> that might come up.
>>> HTH
>>> Chuck
>>> 
>>> CHUCK REICHEL
>>> soundpicturerecord...@gmail.com
>>> www.SoundPictureRecording.com
>>> 954-742-0019
>>> Isaiah 26 : 3
>>>  Thou wilt keep him in perfect peace, whose mind is stayed on thee: because 
>>> he trusteth in thee.
>>> 
>>> In GOD I Trust
>>> 
 On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
 wrote:
 
 Hey list,
 i've encountered the following situation when tracking MIDI in PT12.7. 
 Maybe someone can either reproduce this, or point out what i'm doing wrong.
 Scenario: I have, let's say, 6 Instrument tracks going, and record on them 
 in sequence. So, 16 bars, then add another 8, and so on.
 I've noticed that for some reason the quantize-function stops working 
 after a while. I call it up, option 0, and the apply button is greyed out.
 Why is that?
 
 thanks for any suggestions,
 
 Joy
 
 
 Von meinem iPhone gesendet
 
 -- 
 You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-11 Thread CHUCK REICHEL

Hi Kevin,
You can't "ASSUME" flowtools is being used! :)
HTH
Chuck


On Jan 10, 2017, at 6:19 PM, Kevin Reeves wrote:

> Why mark the track with a hotspot when we now have FloTools?
> 
> On 1/10/2017 5:32 PM, CHUCK REICHEL wrote:
>> Hi Joy,
>> First of all you half to have made a selection in the track your going to 
>> quantize.
>> Second of all you half to make sure the track is still selected in the 
>> tracks list.
>> I mark the track with a hotspot in the tracks list and query the hotspot to 
>> make sure its still selected before trying to edit it! :)
>> I've noticed that tracks drop out of being selected for a while now, and 
>> still need to track down what causes it to get un selected.
>> But most of all I "ALWAYS" hide all tracks not being edited to avoid issues 
>> that might come up.
>> HTH
>> Chuck
>> 
>> CHUCK REICHEL
>> soundpicturerecord...@gmail.com
>> www.SoundPictureRecording.com
>> 954-742-0019
>> Isaiah 26 : 3
>>  Thou wilt keep him in perfect peace, whose mind is stayed on thee: because 
>> he trusteth in thee.
>> 
>> In GOD I Trust
>> 
>> On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility wrote:
>> 
>>> Hey list,
>>> i've encountered the following situation when tracking MIDI in PT12.7. 
>>> Maybe someone can either reproduce this, or point out what i'm doing wrong.
>>> Scenario: I have, let's say, 6 Instrument tracks going, and record on them 
>>> in sequence. So, 16 bars, then add another 8, and so on.
>>> I've noticed that for some reason the quantize-function stops working after 
>>> a while. I call it up, option 0, and the apply button is greyed out.
>>> Why is that?
>>> 
>>> thanks for any suggestions,
>>> 
>>> Joy
>>> 
>>> 
>>> Von meinem iPhone gesendet
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-11 Thread Slau Halatyn

Hi Joy,
One thing I forgot to mention was that you should make sure your track view is 
set to Notes rather than clips. If your tracks are set to at least medium 
height, since you're using Flo Tools, you can simply focus on the track in the 
Mix window and double-tap w to bring up the track view selector and make sure 
Notes is checked in the list.
HTH,
Slau

> On Jan 11, 2017, at 12:47 AM, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Hey guys,
> thanks for your answers. What I should've added in my question was that i 
> double and triple checked that both track and region was selected, and the 
> greyed-out "apply"-button still kept on showing up.
> I'll try what Slau suggested, and see what happens.
> Since FloTools has been mentioned, man, it's so awesome. *grin* 
> 
> Thanks again, guys,
> 
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
>> Am 11.01.2017 um 00:35 schrieb Slau Halatyn > >:
>> 
>> Hi Joy,
>> 
>> On occasion, when working with MIDI or Instrument tracks, the focus gets 
>> lost a bit and it might be necessary to close and reopen the session or, if 
>> that doesn't do it, quit and relaunch Pro Tools. Most of the time, however, 
>> as long as the track and an edit range are selected, things work smoothly. 
>> Sometimes I also find it helpful to have an audio track showing for the 
>> purpose of moving the insertion point to it and then back to the instrument 
>> track and that sometimes is all it takes to restore the focus.
>> I school HTH,
>> Slau
>> 
>>> On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
>>>  wrote:
>>> 
>>> Hey list,
>>> i've encountered the following situation when tracking MIDI in PT12.7. 
>>> Maybe someone can either reproduce this, or point out what i'm doing wrong.
>>> Scenario: I have, let's say, 6 Instrument tracks going, and record on them 
>>> in sequence. So, 16 bars, then add another 8, and so on.
>>> I've noticed that for some reason the quantize-function stops working after 
>>> a while. I call it up, option 0, and the apply button is greyed out.
>>> Why is that?
>>> 
>>> thanks for any suggestions,
>>> 
>>> Joy
>>> 
>>> 
>>> Von meinem iPhone gesendet
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-10 Thread 'Joy Bausch' via Pro Tools Accessibility

Hey guys,
thanks for your answers. What I should've added in my question was that i 
double and triple checked that both track and region was selected, and the 
greyed-out "apply"-button still kept on showing up.
I'll try what Slau suggested, and see what happens.
Since FloTools has been mentioned, man, it's so awesome. *grin* 

Thanks again, guys,

Joy


Von meinem iPhone gesendet

> Am 11.01.2017 um 00:35 schrieb Slau Halatyn :
> 
> Hi Joy,
> 
> On occasion, when working with MIDI or Instrument tracks, the focus gets lost 
> a bit and it might be necessary to close and reopen the session or, if that 
> doesn't do it, quit and relaunch Pro Tools. Most of the time, however, as 
> long as the track and an edit range are selected, things work smoothly. 
> Sometimes I also find it helpful to have an audio track showing for the 
> purpose of moving the insertion point to it and then back to the instrument 
> track and that sometimes is all it takes to restore the focus.
> I school HTH,
> Slau
> 
>> On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
>>  wrote:
>> 
>> Hey list,
>> i've encountered the following situation when tracking MIDI in PT12.7. Maybe 
>> someone can either reproduce this, or point out what i'm doing wrong.
>> Scenario: I have, let's say, 6 Instrument tracks going, and record on them 
>> in sequence. So, 16 bars, then add another 8, and so on.
>> I've noticed that for some reason the quantize-function stops working after 
>> a while. I call it up, option 0, and the apply button is greyed out.
>> Why is that?
>> 
>> thanks for any suggestions,
>> 
>> Joy
>> 
>> 
>> Von meinem iPhone gesendet
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-10 Thread Slau Halatyn

Hi Joy,

On occasion, when working with MIDI or Instrument tracks, the focus gets lost a 
bit and it might be necessary to close and reopen the session or, if that 
doesn't do it, quit and relaunch Pro Tools. Most of the time, however, as long 
as the track and an edit range are selected, things work smoothly. Sometimes I 
also find it helpful to have an audio track showing for the purpose of moving 
the insertion point to it and then back to the instrument track and that 
sometimes is all it takes to restore the focus.
HTH,
Slau

> On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
>  wrote:
> 
> Hey list,
> i've encountered the following situation when tracking MIDI in PT12.7. Maybe 
> someone can either reproduce this, or point out what i'm doing wrong.
> Scenario: I have, let's say, 6 Instrument tracks going, and record on them in 
> sequence. So, 16 bars, then add another 8, and so on.
> I've noticed that for some reason the quantize-function stops working after a 
> while. I call it up, option 0, and the apply button is greyed out.
> Why is that?
> 
> thanks for any suggestions,
> 
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
> -- 
> You received this message because you are subscribed to the Google 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: Midi help needed

2017-01-10 Thread Kevin Reeves


Why mark the track with a hotspot when we now have FloTools?


On 1/10/2017 5:32 PM, CHUCK REICHEL wrote:

Hi Joy,
First of all you half to have made a selection in the track your going 
to quantize.
Second of all you half to make sure the track is still selected in the 
tracks list.
I mark the track with a hotspot in the tracks list and query the 
hotspot to make sure its still selected before trying to edit it! :)
I've noticed that tracks drop out of being selected for a while now, 
and still need to track down what causes it to get un selected.
But most of all I "ALWAYS" hide all tracks not being edited to avoid 
issues that might come up.

HTH
Chuck

CHUCK REICHEL
soundpicturerecord...@gmail.com 
www.SoundPictureRecording.com 
954-742-0019
Isaiah 26 : 3
 Thou wilt keep him in perfect peace, whose mind is stayed on thee: 
because he trusteth in thee.


In GOD I Trust

On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility 
wrote:



Hey list,
i've encountered the following situation when tracking MIDI in 
PT12.7. Maybe someone can either reproduce this, or point out what 
i'm doing wrong.
Scenario: I have, let's say, 6 Instrument tracks going, and record on 
them in sequence. So, 16 bars, then add another 8, and so on.
I've noticed that for some reason the quantize-function stops working 
after a while. I call it up, option 0, and the apply button is greyed 
out.

Why is that?

thanks for any suggestions,

Joy


Von meinem iPhone gesendet

--
You received this message because you are subscribed to the Google 
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: Midi help needed

2017-01-10 Thread CHUCK REICHEL

Hi Joy,
First of all you half to have made a selection in the track your going to 
quantize.
Second of all you half to make sure the track is still selected in the tracks 
list.
I mark the track with a hotspot in the tracks list and query the hotspot to 
make sure its still selected before trying to edit it! :)
I've noticed that tracks drop out of being selected for a while now, and still 
need to track down what causes it to get un selected.
But most of all I "ALWAYS" hide all tracks not being edited to avoid issues 
that might come up.
HTH
Chuck

CHUCK REICHEL
soundpicturerecord...@gmail.com
www.SoundPictureRecording.com
954-742-0019
Isaiah 26 : 3
 Thou wilt keep him in perfect peace, whose mind is stayed on thee: because he 
trusteth in thee.

In GOD I Trust

On Jan 10, 2017, at 1:20 PM, 'Joy Bausch' via Pro Tools Accessibility wrote:

> Hey list,
> i've encountered the following situation when tracking MIDI in PT12.7. Maybe 
> someone can either reproduce this, or point out what i'm doing wrong.
> Scenario: I have, let's say, 6 Instrument tracks going, and record on them in 
> sequence. So, 16 bars, then add another 8, and so on.
> I've noticed that for some reason the quantize-function stops working after a 
> while. I call it up, option 0, and the apply button is greyed out.
> Why is that?
> 
> thanks for any suggestions,
> 
> Joy
> 
> 
> Von meinem iPhone gesendet
> 
> -- 
> You received this message because you are subscribed to the Google 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: MIDI settings

2016-12-06 Thread Slau Halatyn

Hi Martin,
Glad it's working now. Cheers!
Slau

> On Dec 6, 2016, at 9:09 AM, Martin (Punky) Sopart  wrote:
> 
> Hi Slau!
> 
> Thanks for answering.
> 
> I fixed this issue yesterday.
> It was again that insertion point thing.
> Moving the selection via control+p or control+; made it work. :-)
> 
> Starting and ending scrub mode maybe would have done the same job.
> 
> Best! / Martin
>> -Original Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
>> On Behalf Of Slau Halatyn
>> Sent: Monday, December 5, 2016 11:06 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: MIDI settings
>> 
>> Hi Martin,
>> I'm not sure why that's not working for you. It seems you're following the
>> right steps. I just double-checked and it works for me.
>> slau
>> 
>>> On Nov 28, 2016, at 6:58 PM, Martin (Punky) Sopart 
>> wrote:
>>> 
>>> Hi all!
>>> 
>>> I went through Slau's "MIDI how to" and the following action does not wok
>> on my Yousemity-PT12.4 system:
>>> 
>>> I select a MIDI or instrument track and check "Notes" in the tracks track
>> view popup.
>>> Track hide is "Medium".
>>> 
>>> Pressing Tab does not play note after note.
>>> 
>>> Checking and unchecking Tab to transient does not change anyting.
>>> 
>>> What else do I have to check to get the desired functionallity?
>>> Or did it come aftr PT12.4?
>>> 
>>> Thanks in advance and best! / Martin
>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to the Google
>> Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> --
>> You received this message because you are subscribed to the Google 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: MIDI settings

2016-12-06 Thread Martin (Punky) Sopart

Hi Slau!

Thanks for answering.

I fixed this issue yesterday.
It was again that insertion point thing.
Moving the selection via control+p or control+; made it work. :-)

Starting and ending scrub mode maybe would have done the same job.

Best! / Martin
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com]
> On Behalf Of Slau Halatyn
> Sent: Monday, December 5, 2016 11:06 PM
> To: ptaccess@googlegroups.com
> Subject: Re: MIDI settings
> 
> Hi Martin,
> I'm not sure why that's not working for you. It seems you're following the
> right steps. I just double-checked and it works for me.
> slau
> 
> > On Nov 28, 2016, at 6:58 PM, Martin (Punky) Sopart 
> wrote:
> >
> > Hi all!
> >
> > I went through Slau's "MIDI how to" and the following action does not wok
> on my Yousemity-PT12.4 system:
> >
> > I select a MIDI or instrument track and check "Notes" in the tracks track
> view popup.
> > Track hide is "Medium".
> >
> > Pressing Tab does not play note after note.
> >
> > Checking and unchecking Tab to transient does not change anyting.
> >
> > What else do I have to check to get the desired functionallity?
> > Or did it come aftr PT12.4?
> >
> > Thanks in advance and best! / Martin
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Pro Tools Accessibility" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> --
> You received this message because you are subscribed to the Google 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: MIDI settings

2016-12-05 Thread Slau Halatyn

Hi Martin,
I'm not sure why that's not working for you. It seems you're following the 
right steps. I just double-checked and it works for me.
slau

> On Nov 28, 2016, at 6:58 PM, Martin (Punky) Sopart  wrote:
> 
> Hi all!
> 
> I went through Slau's "MIDI how to" and the following action does not wok on 
> my Yousemity-PT12.4 system:
> 
> I select a MIDI or instrument track and check "Notes" in the tracks track 
> view popup.
> Track hide is "Medium".
> 
> Pressing Tab does not play note after note.
> 
> Checking and unchecking Tab to transient does not change anyting.
> 
> What else do I have to check to get the desired functionallity?
> Or did it come aftr PT12.4?
> 
> Thanks in advance and best! / Martin
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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-Loop-Player

2016-11-24 Thread TheOreoMonster

 The problem with midi files is its just Data saying which notes to
trigger and velocities and etc. There is no actual sound to them so
there is no way to preview them outside of an app with samplers or
synths that have sounds that the note data mapp to for triggering. You
will probably end up having to use something like the workspace in Pro
Tools or one of the browser in logic with an appropriate instrument
selected.

On 11/24/16, Martin (Punky) Sopart  wrote:
> Hi all!
>
> I have some MIDI-loops. When opening them with the Finder PT reports, that
> it is not a valid PT format.
> Is there an accessible App to play MIDI on the Mac? Just to check it before
> inporting  into PT?
>
> 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.

Re: midi editing question

2016-05-02 Thread Slau Halatyn

Hi Tim,

Hopefully, you'll understand how difficult it is to give step-by-step 
instructions because there's no way I can know what your starting point is. 
However, I'll try to explain exactly what I would do myself if I were 
experiencing problems.

1. I'd make sure no other applications are running except Pro Tools.
2. I would close all windows except for the Mix and Edit windows and I would 
keep the Edit window as the foremost window.
3. I'd press Control-Option-f2 twice in a row to open the window chooser menu 
and make sure that there are no other windows like system dialogs open.
4. I'd enter the approximate bar/beat location where I want to edit by using 
the numeric keypad.
5. I'd press Option-= (equals) to open the MIDI Event List.
6. I'd use voiceOver to navigate to the value I want to change.
7. I'd click once on that event to select it.
8. I'd press Command-h to make sure the event is focused visibly in the MIDI 
Event List window.
9. I'd navigate to the field I want to change.
10. I'd simply use Control-Option-Shift along with the Space Bar twice to 
double-click the field.
11. I'd type in the value I want and I'd press Return on the qwerty keyboard.

If I've ever had any issue whatsoever, following the steps above would always 
result in success. Once you follow the initial steps, you don't have to repeat 
them. Just navigate, select and, if you've moved through a significant number 
of events (like 30 or 40), it's a good idea to use the Command-h shortcut to 
scroll that event into view once you've selected that event.
Hopefully that helps,
Slau

On May 2, 2016, at 7:33 AM, Tim Liu  wrote:

> Hi Slau:
> 
> I use MacBook Pro now, so already have apple track pad,
> What should I do now?
> can you step by step to teach me?
> excuse, forgive my stupid please.
> 
> Thanks
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 editing question

2016-05-02 Thread Tim Liu

Hi Slau:

I use MacBook Pro now, so already have apple track pad,
What should I do now?
can you step by step to teach me?
excuse, forgive my stupid please.

Thanks

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

Re: midi editing question

2016-04-30 Thread Slau Halatyn

Hi Tim,

I would recommend the Apple Magic Track Pad. While a mouse is OK, sometimes in 
the process of physically locating it on a table or desktop can cause the mouse 
pointer to move. With a track pad, it doesn't matter exactly where you tap the 
pad. I find it far better than a mouse—just something to consider.
Slau

On Apr 30, 2016, at 7:31 PM, TheOreoMonster  wrote:

> You do need to have a mouse attached to your computer if you aren’t using a 
> laptop. This can be one of the apple mic but most any USB or BlueTooth mice 
> should work as well. If you have  laptop then the trackpad is your mouse. 
> 
>> On Apr 29, 2016, at 8:23 PM, Tim Liu  wrote:
>> 
>> Hi Slau:
>> 
>> I already try this method but is not take effect.
>> Now, I'm more interested to know I should buy the apple mouse or not?
>> because I'm a totally blind, but I mean you say press the physical
>> mouse can fix the problem, so I want to learn about how do you do?
>> 
>> Thanks
>> 
>> On 4/29/16, Slau Halatyn  wrote:
>>> Hi Tim,
>>> 
>>> There's nothing else that I can offer except one important bit of advice
>>> that you should always remember when using VoiceOver and physical mouse
>>> clicks: Make sure there are no other windows blocking the window within
>>> which you're trying to click. Use Control-Option-f2 f2 (that is, function 2
>>> twice in a row) to bring up the Window Chooser menu. This list should have
>>> nothing other than the Mix and Edit windows along with the MIDI Event list
>>> (which should be the foremost window and there should be no other windows in
>>> that list. If so, focus on that window and close it.
>>> Hope that helps,
>>> Slau
>>> 
>>> On Apr 29, 2016, at 9:30 AM, Tim Liu  wrote:
>>> 
 Hi Slau:
 
 I already following your step to control the midi event list in my old
 project, but is not exactly focus the event to edit the time/verlosity.
 I create the new project is OK, but I want to edit back my old project,
 can you help me?
 
 On Tuesday, April 12, 2016 at 8:23:05 PM UTC+8, Peter Durieux wrote:
 Hi Listers,
 
 this is a question for those who have Pro Tools and Logic Pro X.
 the midi editor in pro tools isn't accessible in some way. If I understand
 it well
 Logic Pro X should be better for this job.
 
 The last update of lp addresses a lot of bugfixes for voiceover users and
 it stands that the piano roll is accessible.
 Does this means that midi editing is a doable job.
 If someone could tell me what can we do or not?
 
 Thanks in advance
 
 With kind regards,
 
 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 a topic in the
>>> Google Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/ptaccess/obzjKljejq4/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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: midi editing question

2016-04-30 Thread TheOreoMonster

You do need to have a mouse attached to your computer if you aren’t using a 
laptop. This can be one of the apple mic but most any USB or BlueTooth mice 
should work as well. If you have  laptop then the trackpad is your mouse. 

> On Apr 29, 2016, at 8:23 PM, Tim Liu  wrote:
> 
> Hi Slau:
> 
> I already try this method but is not take effect.
> Now, I'm more interested to know I should buy the apple mouse or not?
> because I'm a totally blind, but I mean you say press the physical
> mouse can fix the problem, so I want to learn about how do you do?
> 
> Thanks
> 
> On 4/29/16, Slau Halatyn  wrote:
>> Hi Tim,
>> 
>> There's nothing else that I can offer except one important bit of advice
>> that you should always remember when using VoiceOver and physical mouse
>> clicks: Make sure there are no other windows blocking the window within
>> which you're trying to click. Use Control-Option-f2 f2 (that is, function 2
>> twice in a row) to bring up the Window Chooser menu. This list should have
>> nothing other than the Mix and Edit windows along with the MIDI Event list
>> (which should be the foremost window and there should be no other windows in
>> that list. If so, focus on that window and close it.
>> Hope that helps,
>> Slau
>> 
>> On Apr 29, 2016, at 9:30 AM, Tim Liu  wrote:
>> 
>>> Hi Slau:
>>> 
>>> I already following your step to control the midi event list in my old
>>> project, but is not exactly focus the event to edit the time/verlosity.
>>> I create the new project is OK, but I want to edit back my old project,
>>> can you help me?
>>> 
>>> On Tuesday, April 12, 2016 at 8:23:05 PM UTC+8, Peter Durieux wrote:
>>> Hi Listers,
>>> 
>>> this is a question for those who have Pro Tools and Logic Pro X.
>>> the midi editor in pro tools isn't accessible in some way. If I understand
>>> it well
>>> Logic Pro X should be better for this job.
>>> 
>>> The last update of lp addresses a lot of bugfixes for voiceover users and
>>> it stands that the piano roll is accessible.
>>> Does this means that midi editing is a doable job.
>>> If someone could tell me what can we do or not?
>>> 
>>> Thanks in advance
>>> 
>>> With kind regards,
>>> 
>>> 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 a topic in the
>> Google Groups "Pro Tools Accessibility" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/ptaccess/obzjKljejq4/unsubscribe.
>> To unsubscribe from this group and all its topics, 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: midi editing question

2016-04-29 Thread Tim Liu

Hi Slau:

I already try this method but is not take effect.
Now, I'm more interested to know I should buy the apple mouse or not?
because I'm a totally blind, but I mean you say press the physical
mouse can fix the problem, so I want to learn about how do you do?

Thanks

On 4/29/16, Slau Halatyn  wrote:
> Hi Tim,
>
> There's nothing else that I can offer except one important bit of advice
> that you should always remember when using VoiceOver and physical mouse
> clicks: Make sure there are no other windows blocking the window within
> which you're trying to click. Use Control-Option-f2 f2 (that is, function 2
> twice in a row) to bring up the Window Chooser menu. This list should have
> nothing other than the Mix and Edit windows along with the MIDI Event list
> (which should be the foremost window and there should be no other windows in
> that list. If so, focus on that window and close it.
> Hope that helps,
> Slau
>
> On Apr 29, 2016, at 9:30 AM, Tim Liu  wrote:
>
>> Hi Slau:
>>
>> I already following your step to control the midi event list in my old
>> project, but is not exactly focus the event to edit the time/verlosity.
>> I create the new project is OK, but I want to edit back my old project,
>> can you help me?
>>
>> On Tuesday, April 12, 2016 at 8:23:05 PM UTC+8, Peter Durieux wrote:
>> Hi Listers,
>>
>> this is a question for those who have Pro Tools and Logic Pro X.
>> the midi editor in pro tools isn't accessible in some way. If I understand
>> it well
>> Logic Pro X should be better for this job.
>>
>> The last update of lp addresses a lot of bugfixes for voiceover users and
>> it stands that the piano roll is accessible.
>> Does this means that midi editing is a doable job.
>> If someone could tell me what can we do or not?
>>
>> Thanks in advance
>>
>> With kind regards,
>>
>> 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 a topic in the
> Google Groups "Pro Tools Accessibility" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ptaccess/obzjKljejq4/unsubscribe.
> To unsubscribe from this group and all its topics, 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: midi editing question

2016-04-29 Thread Slau Halatyn

Hi Tim,

There's nothing else that I can offer except one important bit of advice that 
you should always remember when using VoiceOver and physical mouse clicks: Make 
sure there are no other windows blocking the window within which you're trying 
to click. Use Control-Option-f2 f2 (that is, function 2 twice in a row) to 
bring up the Window Chooser menu. This list should have nothing other than the 
Mix and Edit windows along with the MIDI Event list (which should be the 
foremost window and there should be no other windows in that list. If so, focus 
on that window and close it.
Hope that helps,
Slau

On Apr 29, 2016, at 9:30 AM, Tim Liu  wrote:

> Hi Slau:
> 
> I already following your step to control the midi event list in my old 
> project, but is not exactly focus the event to edit the time/verlosity.
> I create the new project is OK, but I want to edit back my old project, can 
> you help me?
> 
> On Tuesday, April 12, 2016 at 8:23:05 PM UTC+8, Peter Durieux wrote:
> Hi Listers, 
> 
> this is a question for those who have Pro Tools and Logic Pro X. 
> the midi editor in pro tools isn't accessible in some way. If I understand it 
> well 
> Logic Pro X should be better for this job. 
> 
> The last update of lp addresses a lot of bugfixes for voiceover users and it 
> stands that the piano roll is accessible. 
> Does this means that midi editing is a doable job. 
> If someone could tell me what can we do or not? 
> 
> Thanks in advance 
> 
> With kind regards, 
> 
> 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.

Re: midi editing question

2016-04-29 Thread Tim Liu

Hi Slau:

I already following your step to control the midi event list in my old 
project, but is not exactly focus the event to edit the time/verlosity.
I create the new project is OK, but I want to edit back my old project, can 
you help me?

On Tuesday, April 12, 2016 at 8:23:05 PM UTC+8, Peter Durieux wrote:
>
> Hi Listers, 
>
> this is a question for those who have Pro Tools and Logic Pro X. 
> the midi editor in pro tools isn't accessible in some way. If I understand 
> it well 
> Logic Pro X should be better for this job. 
>
> The last update of lp addresses a lot of bugfixes for voiceover users and 
> it stands that the piano roll is accessible. 
> Does this means that midi editing is a doable job. 
> If someone could tell me what can we do or not? 
>
> Thanks in advance 
>
> With kind regards, 
>
> 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.

Re: midi editing question

2016-04-21 Thread Slau Halatyn

Glad to hear it, Steve. Hopefully, it'll help some folks.
Cheers,
Slau

On Apr 21, 2016, at 4:10 PM, Steve Matzura  wrote:

> This message is one of the most helpful I've had in this topic area.
> Thanks so much, brother New Yorker.
> 
> On Wed, 20 Apr 2016 18:01:24 -0400, you wrote:
> 
>> Hi Peter,
>> 
>> I'm finally starting to work on an upcoming project that involves MIDI and 
>> I've refreshed my memory on a few tips. Hopefully, this will help.
>> 
>> The MIDI Event List is what you'll use primarily. that said, you'll need to 
>> have the Edit window at least opened in the background. The MIDI Event List 
>> is essentially just a table. As you'd expect, double-clicking a field will 
>> create an edit box around the field and you can type in a value and press 
>> Return to enter that value. Be aware that sometimes VoiceOver will read the 
>> new value but, unless you press Return to enter that value, the change won't 
>> take effect because the edit field hasn't truly been changed until that 
>> Return key has been pressed. Also, I should point out that it's best to 
>> either use a mouse or track pad but double pressing 
>> Control-Option-Shift-Space Bar will also work if the mouse pointer is routed 
>> to the VoiceOver cursor.
>> 
>> When you click on an event in the list, it becomes highlighted and, if you 
>> have a module or virtual instrument active, you'll hear the note as well. 
>> When the event is highlighted, the entire row gets highlighted including the 
>> start time, pitch, velocity, etc. When you double-click a specific field, 
>> only that field gets the edit box until you press Return.
>> 
>> You can move the edit box to the left or right by using the left or right 
>> arrow keys. So, let's say you wanted to change the start time of a note and 
>> let's assume we're in bars and beats. If you read down the event list to the 
>> note you wish to change and you've focused on the start time, 
>> double-clicking the start time in the event list row for that note will both 
>> highlight the event and create an edit box around the bar number. Pressing 
>> the right arrow will move the edit box to the beat field and pressing it 
>> again will move it to the tick field. You can enter a value and hit Return 
>> and the selected note will move to the newly edited start time.
>> 
>> Let's say you wanted to edit the pitch. If you double-click on the pitch, 
>> you can either type a value or press a note on your controller. Let's say 
>> you wanted to change the velocity as well. Instead of pressing Return after 
>> having changed the pitch, you could press the right arrow to move the edit 
>> box to the velocity field, enter a new velocity and then press Return.
>> 
>> Here's one more thing to be aware of regarding moving between fields in a 
>> row in the Event List: If you're in a start or length field where there are 
>> a few subdivisions associated with that main column, pressing the decimal 
>> key will cycle through the subdivisions much like it cycles through them to 
>> enter a start value or main counter value. It'll just keep cycling and not 
>> proceed to the other columns like pitch and velocity. This is neither a good 
>> nor a bad thing but it's just something to be aware of.
>> 
>> Here's something else to keep in mind that might trip people up: Just as 
>> VoiceOver can see things that are not necessarily visible in the Mix window 
>> and technically off-screen, the same applies to the MIDI Event List. If you 
>> get into the table and start reading down the list with VoiceOver, you can 
>> move through an entire song but the window won't necessarily visually 
>> scroll. If you then go to double-click on a value, the mouse will actually 
>> be clicking on something entirely different like the desktop or something. 
>> What you need to do in a case like this is first select the event by 
>> clicking on it with VoiceOver. This selects the event in Pro tools but then 
>> you have to use Command-h to bring that event into focus in the MIDI Event 
>> List window. The window will scroll the selected event into view. Now if you 
>> double-click it with the mouse, the edit box will appear as expected.
>> 
>> So that's the main overall picture. Here's an alternative and, for some 
>> folks, perhaps it'll work better under certain circumstances. I wouldn't 
>> recommend it as default procedure but, again, it's an alternative and, in a 
>> way, perhaps easier or more verifiable.
>> 
>> When you click on an event in the MIDI Event List, the Edit window reflects 
>> the selection. Just as selecting a range displays various values in the edit 
>> window's counter display, selecting an event in the MIDI Event List defines 
>> a start point of the event, an end point, a length and even pitch, velocity 
>> etc. If you've selected an event in the Event List, press Command-accent to 
>> cycle to the Edit window. You'll notice that in the counter display cluster, 
>> the note pitch and velocity, among

Re: midi editing question

2016-04-21 Thread Steve Matzura

This message is one of the most helpful I've had in this topic area.
Thanks so much, brother New Yorker.

On Wed, 20 Apr 2016 18:01:24 -0400, you wrote:

>Hi Peter,
>
>I'm finally starting to work on an upcoming project that involves MIDI and 
>I've refreshed my memory on a few tips. Hopefully, this will help.
>
>The MIDI Event List is what you'll use primarily. that said, you'll need to 
>have the Edit window at least opened in the background. The MIDI Event List is 
>essentially just a table. As you'd expect, double-clicking a field will create 
>an edit box around the field and you can type in a value and press Return to 
>enter that value. Be aware that sometimes VoiceOver will read the new value 
>but, unless you press Return to enter that value, the change won't take effect 
>because the edit field hasn't truly been changed until that Return key has 
>been pressed. Also, I should point out that it's best to either use a mouse or 
>track pad but double pressing Control-Option-Shift-Space Bar will also work if 
>the mouse pointer is routed to the VoiceOver cursor.
>
>When you click on an event in the list, it becomes highlighted and, if you 
>have a module or virtual instrument active, you'll hear the note as well. When 
>the event is highlighted, the entire row gets highlighted including the start 
>time, pitch, velocity, etc. When you double-click a specific field, only that 
>field gets the edit box until you press Return.
>
>You can move the edit box to the left or right by using the left or right 
>arrow keys. So, let's say you wanted to change the start time of a note and 
>let's assume we're in bars and beats. If you read down the event list to the 
>note you wish to change and you've focused on the start time, double-clicking 
>the start time in the event list row for that note will both highlight the 
>event and create an edit box around the bar number. Pressing the right arrow 
>will move the edit box to the beat field and pressing it again will move it to 
>the tick field. You can enter a value and hit Return and the selected note 
>will move to the newly edited start time.
>
>Let's say you wanted to edit the pitch. If you double-click on the pitch, you 
>can either type a value or press a note on your controller. Let's say you 
>wanted to change the velocity as well. Instead of pressing Return after having 
>changed the pitch, you could press the right arrow to move the edit box to the 
>velocity field, enter a new velocity and then press Return.
>
>Here's one more thing to be aware of regarding moving between fields in a row 
>in the Event List: If you're in a start or length field where there are a few 
>subdivisions associated with that main column, pressing the decimal key will 
>cycle through the subdivisions much like it cycles through them to enter a 
>start value or main counter value. It'll just keep cycling and not proceed to 
>the other columns like pitch and velocity. This is neither a good nor a bad 
>thing but it's just something to be aware of.
>
>Here's something else to keep in mind that might trip people up: Just as 
>VoiceOver can see things that are not necessarily visible in the Mix window 
>and technically off-screen, the same applies to the MIDI Event List. If you 
>get into the table and start reading down the list with VoiceOver, you can 
>move through an entire song but the window won't necessarily visually scroll. 
>If you then go to double-click on a value, the mouse will actually be clicking 
>on something entirely different like the desktop or something. What you need 
>to do in a case like this is first select the event by clicking on it with 
>VoiceOver. This selects the event in Pro tools but then you have to use 
>Command-h to bring that event into focus in the MIDI Event List window. The 
>window will scroll the selected event into view. Now if you double-click it 
>with the mouse, the edit box will appear as expected.
>
>So that's the main overall picture. Here's an alternative and, for some folks, 
>perhaps it'll work better under certain circumstances. I wouldn't recommend it 
>as default procedure but, again, it's an alternative and, in a way, perhaps 
>easier or more verifiable.
>
>When you click on an event in the MIDI Event List, the Edit window reflects 
>the selection. Just as selecting a range displays various values in the edit 
>window's counter display, selecting an event in the MIDI Event List defines a 
>start point of the event, an end point, a length and even pitch, velocity etc. 
>If you've selected an event in the Event List, press Command-accent to cycle 
>to the Edit window. You'll notice that in the counter display cluster, the 
>note pitch and velocity, among other things, are displayed.
>
>Let's say you selected middle c and it landed on bar 1, beat 1 and 56 ticks. 
>With the note selected, you can press the slash key on the numeric keypad 3 
>times to get to the ticks field, enter 0 and hit Enter to change the start 
>time of the n

Re: midi editing question

2016-04-21 Thread peter

Hi Slau,

Thanks for the update, I'll take a look when I'm find some time. :)
Keep you posted.

kr

Peter


On Wed, Apr 20, 2016 at 06:01:24PM -0400, Slau Halatyn wrote:
> Hi Peter,
> 
> I'm finally starting to work on an upcoming project that involves MIDI and 
> I've refreshed my memory on a few tips. Hopefully, this will help.
> 
> The MIDI Event List is what you'll use primarily. that said, you'll need to 
> have the Edit window at least opened in the background. The MIDI Event List 
> is essentially just a table. As you'd expect, double-clicking a field will 
> create an edit box around the field and you can type in a value and press 
> Return to enter that value. Be aware that sometimes VoiceOver will read the 
> new value but, unless you press Return to enter that value, the change won't 
> take effect because the edit field hasn't truly been changed until that 
> Return key has been pressed. Also, I should point out that it's best to 
> either use a mouse or track pad but double pressing 
> Control-Option-Shift-Space Bar will also work if the mouse pointer is routed 
> to the VoiceOver cursor.
> 
> When you click on an event in the list, it becomes highlighted and, if you 
> have a module or virtual instrument active, you'll hear the note as well. 
> When the event is highlighted, the entire row gets highlighted including the 
> start time, pitch, velocity, etc. When you double-click a specific field, 
> only that field gets the edit box until you press Return.
> 
> You can move the edit box to the left or right by using the left or right 
> arrow keys. So, let's say you wanted to change the start time of a note and 
> let's assume we're in bars and beats. If you read down the event list to the 
> note you wish to change and you've focused on the start time, double-clicking 
> the start time in the event list row for that note will both highlight the 
> event and create an edit box around the bar number. Pressing the right arrow 
> will move the edit box to the beat field and pressing it again will move it 
> to the tick field. You can enter a value and hit Return and the selected note 
> will move to the newly edited start time.
> 
> Let's say you wanted to edit the pitch. If you double-click on the pitch, you 
> can either type a value or press a note on your controller. Let's say you 
> wanted to change the velocity as well. Instead of pressing Return after 
> having changed the pitch, you could press the right arrow to move the edit 
> box to the velocity field, enter a new velocity and then press Return.
> 
> Here's one more thing to be aware of regarding moving between fields in a row 
> in the Event List: If you're in a start or length field where there are a few 
> subdivisions associated with that main column, pressing the decimal key will 
> cycle through the subdivisions much like it cycles through them to enter a 
> start value or main counter value. It'll just keep cycling and not proceed to 
> the other columns like pitch and velocity. This is neither a good nor a bad 
> thing but it's just something to be aware of.
> 
> Here's something else to keep in mind that might trip people up: Just as 
> VoiceOver can see things that are not necessarily visible in the Mix window 
> and technically off-screen, the same applies to the MIDI Event List. If you 
> get into the table and start reading down the list with VoiceOver, you can 
> move through an entire song but the window won't necessarily visually scroll. 
> If you then go to double-click on a value, the mouse will actually be 
> clicking on something entirely different like the desktop or something. What 
> you need to do in a case like this is first select the event by clicking on 
> it with VoiceOver. This selects the event in Pro tools but then you have to 
> use Command-h to bring that event into focus in the MIDI Event List window. 
> The window will scroll the selected event into view. Now if you double-click 
> it with the mouse, the edit box will appear as expected.
> 
> So that's the main overall picture. Here's an alternative and, for some 
> folks, perhaps it'll work better under certain circumstances. I wouldn't 
> recommend it as default procedure but, again, it's an alternative and, in a 
> way, perhaps easier or more verifiable.
> 
> When you click on an event in the MIDI Event List, the Edit window reflects 
> the selection. Just as selecting a range displays various values in the edit 
> window's counter display, selecting an event in the MIDI Event List defines a 
> start point of the event, an end point, a length and even pitch, velocity 
> etc. If you've selected an event in the Event List, press Command-accent to 
> cycle to the Edit window. You'll notice that in the counter display cluster, 
> the note pitch and velocity, among other things, are displayed.
> 
> Let's say you selected middle c and it landed on bar 1, beat 1 and 56 ticks. 
> With the note selected, you can press the slash key on the numeric keypad 3

Re: midi editing question

2016-04-20 Thread Slau Halatyn

Hi Peter,

I'm finally starting to work on an upcoming project that involves MIDI and I've 
refreshed my memory on a few tips. Hopefully, this will help.

The MIDI Event List is what you'll use primarily. that said, you'll need to 
have the Edit window at least opened in the background. The MIDI Event List is 
essentially just a table. As you'd expect, double-clicking a field will create 
an edit box around the field and you can type in a value and press Return to 
enter that value. Be aware that sometimes VoiceOver will read the new value 
but, unless you press Return to enter that value, the change won't take effect 
because the edit field hasn't truly been changed until that Return key has been 
pressed. Also, I should point out that it's best to either use a mouse or track 
pad but double pressing Control-Option-Shift-Space Bar will also work if the 
mouse pointer is routed to the VoiceOver cursor.

When you click on an event in the list, it becomes highlighted and, if you have 
a module or virtual instrument active, you'll hear the note as well. When the 
event is highlighted, the entire row gets highlighted including the start time, 
pitch, velocity, etc. When you double-click a specific field, only that field 
gets the edit box until you press Return.

You can move the edit box to the left or right by using the left or right arrow 
keys. So, let's say you wanted to change the start time of a note and let's 
assume we're in bars and beats. If you read down the event list to the note you 
wish to change and you've focused on the start time, double-clicking the start 
time in the event list row for that note will both highlight the event and 
create an edit box around the bar number. Pressing the right arrow will move 
the edit box to the beat field and pressing it again will move it to the tick 
field. You can enter a value and hit Return and the selected note will move to 
the newly edited start time.

Let's say you wanted to edit the pitch. If you double-click on the pitch, you 
can either type a value or press a note on your controller. Let's say you 
wanted to change the velocity as well. Instead of pressing Return after having 
changed the pitch, you could press the right arrow to move the edit box to the 
velocity field, enter a new velocity and then press Return.

Here's one more thing to be aware of regarding moving between fields in a row 
in the Event List: If you're in a start or length field where there are a few 
subdivisions associated with that main column, pressing the decimal key will 
cycle through the subdivisions much like it cycles through them to enter a 
start value or main counter value. It'll just keep cycling and not proceed to 
the other columns like pitch and velocity. This is neither a good nor a bad 
thing but it's just something to be aware of.

Here's something else to keep in mind that might trip people up: Just as 
VoiceOver can see things that are not necessarily visible in the Mix window and 
technically off-screen, the same applies to the MIDI Event List. If you get 
into the table and start reading down the list with VoiceOver, you can move 
through an entire song but the window won't necessarily visually scroll. If you 
then go to double-click on a value, the mouse will actually be clicking on 
something entirely different like the desktop or something. What you need to do 
in a case like this is first select the event by clicking on it with VoiceOver. 
This selects the event in Pro tools but then you have to use Command-h to bring 
that event into focus in the MIDI Event List window. The window will scroll the 
selected event into view. Now if you double-click it with the mouse, the edit 
box will appear as expected.

So that's the main overall picture. Here's an alternative and, for some folks, 
perhaps it'll work better under certain circumstances. I wouldn't recommend it 
as default procedure but, again, it's an alternative and, in a way, perhaps 
easier or more verifiable.

When you click on an event in the MIDI Event List, the Edit window reflects the 
selection. Just as selecting a range displays various values in the edit 
window's counter display, selecting an event in the MIDI Event List defines a 
start point of the event, an end point, a length and even pitch, velocity etc. 
If you've selected an event in the Event List, press Command-accent to cycle to 
the Edit window. You'll notice that in the counter display cluster, the note 
pitch and velocity, among other things, are displayed.

Let's say you selected middle c and it landed on bar 1, beat 1 and 56 ticks. 
With the note selected, you can press the slash key on the numeric keypad 3 
times to get to the ticks field, enter 0 and hit Enter to change the start time 
of the note to be at bar 1, beat 1 and zero ticks. Note that, since we're using 
the num pad to modify the value, we need to use the Enter key rather than the 
Return key like we did in the MIDI Event List window. The same editing options

Re: midi editing question

2016-04-12 Thread peter

Hi Slau,

That would be great. :)

grtz

Peter

On Tue, Apr 12, 2016 at 08:41:26AM -0400, Slau Halatyn wrote:
> Yep,
> 
> Don't use the MIDI Editor in Pro Tools, use the MIDI Event List which lays 
> everything out in a table. There are a few quirks but it works. I'll be doing 
> a bunch of MIDI work next week so I'll try to gather a few pointers and put 
> something together as an outline of what one should be aware of when using 
> the MIDI Event List.
> Slau
> 
> On Apr 12, 2016, at 8:22 AM, peter  wrote:
> 
> > Hi Listers,
> > 
> > this is a question for those who have Pro Tools and Logic Pro X.
> > the midi editor in pro tools isn't accessible in some way. If I understand 
> > it well
> > Logic Pro X should be better for this job.
> > 
> > The last update of lp addresses a lot of bugfixes for voiceover users and 
> > it stands that the piano roll is accessible.
> > Does this means that midi editing is a doable job.
> > If someone could tell me what can we do or not?
> > 
> > Thanks in advance 
> > 
> > With kind regards,
> > 
> > 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: midi editing question

2016-04-12 Thread Slau Halatyn

Yep,

Don't use the MIDI Editor in Pro Tools, use the MIDI Event List which lays 
everything out in a table. There are a few quirks but it works. I'll be doing a 
bunch of MIDI work next week so I'll try to gather a few pointers and put 
something together as an outline of what one should be aware of when using the 
MIDI Event List.
Slau

On Apr 12, 2016, at 8:22 AM, peter  wrote:

> Hi Listers,
> 
> this is a question for those who have Pro Tools and Logic Pro X.
> the midi editor in pro tools isn't accessible in some way. If I understand it 
> well
> Logic Pro X should be better for this job.
> 
> The last update of lp addresses a lot of bugfixes for voiceover users and it 
> stands that the piano roll is accessible.
> Does this means that midi editing is a doable job.
> If someone could tell me what can we do or not?
> 
> Thanks in advance 
> 
> With kind regards,
> 
> 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.

Re: [midi-mag] Accessible Multi Track Editing Software

2015-04-21 Thread Chris Smart

Sound Forge is accessible under Windows. ProTools is accessible on 
the Mac and I urge you to join the PTAccess Google group. You should 
be able to send a message to ptaccess+subscr...@googlegroups.com


Also, Reaper is accessible under Windows.

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.

RE: midi

2015-03-16 Thread Poppa Bear

Glad I could help a little Steve. It's good to see you hanging in there and 
moving forward. 

-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Monday, March 16, 2015 2:57 AM
To: ptaccess@googlegroups.com
Subject: Re: midi

thanks poppa
Steve

> On 16 Mar 2015, at 6:01 pm, Poppa Bear  wrote:
> 
> Steve, when you are under Expand and you have the instrument up that you want 
> then you can VO arrow right and start messing with the couple dozen 
> parameters and dig into the settings more meticulously to dial stuff in. As a 
> rule, I create different drum tracks for different parts of the kit a lot of 
> the time. Others may have some tips on working in expand. Boom is another 
> instrument set that is drums and may have different settings. 
> 
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
> Of Steve Sparrow
> Sent: Sunday, March 15, 2015 9:03 PM
> To: ptaccess@googlegroups.com
> Subject: Re: midi
> 
> is there a way of changing the velocity of these drums. the dynamic range is 
> quite large.
> Steve
> 
>> On 16 Mar 2015, at 2:39 pm, Steve Sparrow  wrote:
>> 
>> Hey Poppa. it’s all working fine. Sounding good.
>> 
>> i do have one question. If i record a drum track with a couple of drums in 
>> it, say kick and snare, and maybe hats, is there a way of splitting it out 
>> in to individual tracks afterwards. or do i have to record each drum sound 
>> separately on a separate track.
>> Steve
>> 
>>> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
>>> 
>>> Hey Steve, once you have the drivers installed then just create an 
>>> instrument track, arm it, put expand on the insert track and your good to 
>>> go. You can change the instrument banks under the presets for expand just 
>>> like you would for any other plug in.
>>> HTH 
>>> Message-----
>>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On 
>>> Behalf Of Steve Sparrow
>>> Sent: Sunday, March 15, 2015 12:35 PM
>>> To: ptaccess@googlegroups.com
>>> Subject: Re: midi
>>> 
>>> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
>>> driver disk, as far as windows goes, it was just a plug and play thing. 
>>> would it not work the same on mac,or is it possible i may need to look for 
>>> drivers on line.
>>> Steve
>>> 
>>>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>>> 
>>>> Steve,
>>>> 
>>>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way 
>>>> to explaining what needs to be done. I'll just say that, if you haven't 
>>>> already done so, you'll need to install the USB driver for your keyboard.
>>>> 
>>>> Slau
>>>> 
>>>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  
>>>> wrote:
>>>> 
>>>>> Hi. can anyone give me some instructions as to how to get me up and 
>>>>> running with midi in p t. 
>>>>> Hiere is what i’ve done so far.
>>>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>>>> my u s b hub. In my session i’ve inserted an stereo instrument track. 
>>>>> I’ve then incerted the x band 2 plug over this track. But where do i find 
>>>>> the library of categories to choos from, , also do i need to do anything 
>>>>> else to get the keyboard set up for midi in p t.I really need to program 
>>>>> drum tracks, so i guess somewhere i’ll need to select a midi channel and 
>>>>> tell it to use channel 10. But not really sure how it all works in here.
>>>>> 
>>>>> Steve
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Pro Tools Accessibility" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> F

Re: midi

2015-03-16 Thread Slau Halatyn

Steve,

You can select/split notes within the Event Operations window. Remember that 
the dialog box will help you define the range of notes but what you'll need to 
do beside that is define the range within the timeline. First, make sure your 
MIDI track is selected. Select a range in the timeline. Press Option-y to bring 
up the Event Operations dialog. If you choose to select the note range, cut it 
and paste the information into a new track. I haven't tried splitting in years 
so I can't remember what the default behavior is but you might want to 
experiment.

Slau

On Mar 16, 2015, at 12:39 AM, Steve Sparrow  wrote:

> Hey Poppa. it’s all working fine. Sounding good.
> 
> i do have one question. If i record a drum track with a couple of drums in 
> it, say kick and snare, and maybe hats, is there a way of splitting it out in 
> to individual tracks afterwards. or do i have to record each drum sound 
> separately on a separate track.
> Steve
> 
>> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
>> 
>> Hey Steve, once you have the drivers installed then just create an 
>> instrument track, arm it, put expand on the insert track and your good to 
>> go. You can change the instrument banks under the presets for expand just 
>> like you would for any other plug in.
>> HTH 
>> Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
>> Of Steve Sparrow
>> Sent: Sunday, March 15, 2015 12:35 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: midi
>> 
>> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
>> driver disk, as far as windows goes, it was just a plug and play thing. 
>> would it not work the same on mac,or is it possible i may need to look for 
>> drivers on line.
>> Steve
>> 
>>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>> 
>>> Steve,
>>> 
>>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>>> explaining what needs to be done. I'll just say that, if you haven't 
>>> already done so, you'll need to install the USB driver for your keyboard.
>>> 
>>> Slau
>>> 
>>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>>> 
>>>> Hi. can anyone give me some instructions as to how to get me up and 
>>>> running with midi in p t. 
>>>> Hiere is what i’ve done so far.
>>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>>> then incerted the x band 2 plug over this track. But where do i find the 
>>>> library of categories to choos from, , also do i need to do anything else 
>>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell 
>>>> it to use channel 10. But not really sure how it all works in here.
>>>> 
>>>> Steve
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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: midi

2015-03-16 Thread Steve Sparrow

thanks poppa
Steve

> On 16 Mar 2015, at 6:01 pm, Poppa Bear  wrote:
> 
> Steve, when you are under Expand and you have the instrument up that you want 
> then you can VO arrow right and start messing with the couple dozen 
> parameters and dig into the settings more meticulously to dial stuff in. As a 
> rule, I create different drum tracks for different parts of the kit a lot of 
> the time. Others may have some tips on working in expand. Boom is another 
> instrument set that is drums and may have different settings. 
> 
> -Original Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
> Of Steve Sparrow
> Sent: Sunday, March 15, 2015 9:03 PM
> To: ptaccess@googlegroups.com
> Subject: Re: midi
> 
> is there a way of changing the velocity of these drums. the dynamic range is 
> quite large.
> Steve
> 
>> On 16 Mar 2015, at 2:39 pm, Steve Sparrow  wrote:
>> 
>> Hey Poppa. it’s all working fine. Sounding good.
>> 
>> i do have one question. If i record a drum track with a couple of drums in 
>> it, say kick and snare, and maybe hats, is there a way of splitting it out 
>> in to individual tracks afterwards. or do i have to record each drum sound 
>> separately on a separate track.
>> Steve
>> 
>>> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
>>> 
>>> Hey Steve, once you have the drivers installed then just create an 
>>> instrument track, arm it, put expand on the insert track and your good to 
>>> go. You can change the instrument banks under the presets for expand just 
>>> like you would for any other plug in.
>>> HTH 
>>> Message-
>>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On 
>>> Behalf Of Steve Sparrow
>>> Sent: Sunday, March 15, 2015 12:35 PM
>>> To: ptaccess@googlegroups.com
>>> Subject: Re: midi
>>> 
>>> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
>>> driver disk, as far as windows goes, it was just a plug and play thing. 
>>> would it not work the same on mac,or is it possible i may need to look for 
>>> drivers on line.
>>> Steve
>>> 
>>>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>>> 
>>>> Steve,
>>>> 
>>>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way 
>>>> to explaining what needs to be done. I'll just say that, if you haven't 
>>>> already done so, you'll need to install the USB driver for your keyboard.
>>>> 
>>>> Slau
>>>> 
>>>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  
>>>> wrote:
>>>> 
>>>>> Hi. can anyone give me some instructions as to how to get me up and 
>>>>> running with midi in p t. 
>>>>> Hiere is what i’ve done so far.
>>>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>>>> my u s b hub. In my session i’ve inserted an stereo instrument track. 
>>>>> I’ve then incerted the x band 2 plug over this track. But where do i find 
>>>>> the library of categories to choos from, , also do i need to do anything 
>>>>> else to get the keyboard set up for midi in p t.I really need to program 
>>>>> drum tracks, so i guess somewhere i’ll need to select a midi channel and 
>>>>> tell it to use channel 10. But not really sure how it all works in here.
>>>>> 
>>>>> Steve
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Pro Tools Accessibility" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google 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

RE: midi

2015-03-16 Thread Poppa Bear

Steve, when you are under Expand and you have the instrument up that you want 
then you can VO arrow right and start messing with the couple dozen parameters 
and dig into the settings more meticulously to dial stuff in. As a rule, I 
create different drum tracks for different parts of the kit a lot of the time. 
Others may have some tips on working in expand. Boom is another instrument set 
that is drums and may have different settings. 

-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Sunday, March 15, 2015 9:03 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

is there a way of changing the velocity of these drums. the dynamic range is 
quite large.
Steve

> On 16 Mar 2015, at 2:39 pm, Steve Sparrow  wrote:
> 
> Hey Poppa. it’s all working fine. Sounding good.
> 
> i do have one question. If i record a drum track with a couple of drums in 
> it, say kick and snare, and maybe hats, is there a way of splitting it out in 
> to individual tracks afterwards. or do i have to record each drum sound 
> separately on a separate track.
> Steve
> 
>> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
>> 
>> Hey Steve, once you have the drivers installed then just create an 
>> instrument track, arm it, put expand on the insert track and your good to 
>> go. You can change the instrument banks under the presets for expand just 
>> like you would for any other plug in.
>> HTH 
>> Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
>> Of Steve Sparrow
>> Sent: Sunday, March 15, 2015 12:35 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: midi
>> 
>> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
>> driver disk, as far as windows goes, it was just a plug and play thing. 
>> would it not work the same on mac,or is it possible i may need to look for 
>> drivers on line.
>> Steve
>> 
>>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>> 
>>> Steve,
>>> 
>>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>>> explaining what needs to be done. I'll just say that, if you haven't 
>>> already done so, you'll need to install the USB driver for your keyboard.
>>> 
>>> Slau
>>> 
>>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>>> 
>>>> Hi. can anyone give me some instructions as to how to get me up and 
>>>> running with midi in p t. 
>>>> Hiere is what i’ve done so far.
>>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>>> then incerted the x band 2 plug over this track. But where do i find the 
>>>> library of categories to choos from, , also do i need to do anything else 
>>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell 
>>>> it to use channel 10. But not really sure how it all works in here.
>>>> 
>>>> Steve
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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

Re: midi

2015-03-15 Thread Steve Sparrow

is there a way of changing the velocity of these drums. the dynamic range is 
quite large.
Steve

> On 16 Mar 2015, at 2:39 pm, Steve Sparrow  wrote:
> 
> Hey Poppa. it’s all working fine. Sounding good.
> 
> i do have one question. If i record a drum track with a couple of drums in 
> it, say kick and snare, and maybe hats, is there a way of splitting it out in 
> to individual tracks afterwards. or do i have to record each drum sound 
> separately on a separate track.
> Steve
> 
>> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
>> 
>> Hey Steve, once you have the drivers installed then just create an 
>> instrument track, arm it, put expand on the insert track and your good to 
>> go. You can change the instrument banks under the presets for expand just 
>> like you would for any other plug in.
>> HTH 
>> Message-
>> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
>> Of Steve Sparrow
>> Sent: Sunday, March 15, 2015 12:35 PM
>> To: ptaccess@googlegroups.com
>> Subject: Re: midi
>> 
>> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
>> driver disk, as far as windows goes, it was just a plug and play thing. 
>> would it not work the same on mac,or is it possible i may need to look for 
>> drivers on line.
>> Steve
>> 
>>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>> 
>>> Steve,
>>> 
>>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>>> explaining what needs to be done. I'll just say that, if you haven't 
>>> already done so, you'll need to install the USB driver for your keyboard.
>>> 
>>> Slau
>>> 
>>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>>> 
>>>> Hi. can anyone give me some instructions as to how to get me up and 
>>>> running with midi in p t. 
>>>> Hiere is what i’ve done so far.
>>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>>> then incerted the x band 2 plug over this track. But where do i find the 
>>>> library of categories to choos from, , also do i need to do anything else 
>>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell 
>>>> it to use channel 10. But not really sure how it all works in here.
>>>> 
>>>> Steve
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Pro Tools Accessibility" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to ptaccess+unsubscr...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Steve Sparrow

Hey Poppa. it’s all working fine. Sounding good.

i do have one question. If i record a drum track with a couple of drums in it, 
say kick and snare, and maybe hats, is there a way of splitting it out in to 
individual tracks afterwards. or do i have to record each drum sound separately 
on a separate track.
Steve

> On 16 Mar 2015, at 7:24 am, Poppa Bear  wrote:
> 
> Hey Steve, once you have the drivers installed then just create an instrument 
> track, arm it, put expand on the insert track and your good to go. You can 
> change the instrument banks under the presets for expand just like you would 
> for any other plug in.
> HTH 
> Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
> Of Steve Sparrow
> Sent: Sunday, March 15, 2015 12:35 PM
> To: ptaccess@googlegroups.com
> Subject: Re: midi
> 
> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
> driver disk, as far as windows goes, it was just a plug and play thing. would 
> it not work the same on mac,or is it possible i may need to look for drivers 
> on line.
> Steve
> 
>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>> 
>> Steve,
>> 
>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>> explaining what needs to be done. I'll just say that, if you haven't already 
>> done so, you'll need to install the USB driver for your keyboard.
>> 
>> Slau
>> 
>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>> 
>>> Hi. can anyone give me some instructions as to how to get me up and running 
>>> with midi in p t. 
>>> Hiere is what i’ve done so far.
>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>> then incerted the x band 2 plug over this track. But where do i find the 
>>> library of categories to choos from, , also do i need to do anything else 
>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell it 
>>> to use channel 10. But not really sure how it all works in here.
>>> 
>>> Steve
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Nick Gawronski

Hi, I was using the export to midi option I believe it was called but 
like I said the midi files when they played back sounded completely 
different then they did in pro tools so not sure what is going on 
there.  Nick Gawronski


On 3/15/2015 6:00 PM, Christopher-Mark Gilland wrote:

I'd love to know how you're saving a session as a .mid file.  I've always 
wanted to know how to do that!

Chris.


-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Nick Gawronski
Sent: Sunday, March 15, 2015 6:04 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

Hi, If I create a midi session or get someone elses session and save the
file as a normal midi file when I try to play it back the tempo and
everything else about the midi session is totally wrong.  What am I
missing as if I open up the sessions in pro tools they sound like they
should but if I save them as midi they are all messed up and I have
tried importing a midi file into pro tools to hear how the included pro
tools midi maps sound but when I hit play even when I see the different
tracks no sound plays?  Nick Gawronski

On 3/15/2015 4:24 PM, Poppa Bear wrote:

Hey Steve, once you have the drivers installed then just create an instrument 
track, arm it, put expand on the insert track and your good to go. You can 
change the instrument banks under the presets for expand just like you would 
for any other plug in.
HTH
Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Sunday, March 15, 2015 12:35 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

cool. thanks for this. regarding the keyboard, i don’t think it came with a 
driver disk, as far as windows goes, it was just a plug and play thing. would 
it not work the same on mac,or is it possible i may need to look for drivers on 
line.
Steve


On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:

Steve,

The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
explaining what needs to be done. I'll just say that, if you haven't already 
done so, you'll need to install the USB driver for your keyboard.

Slau

On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:


Hi. can anyone give me some instructions as to how to get me up and running 
with midi in p t.
Hiere is what i’ve done so far.
I have an 88 note usb midi controller keyboard. i have this plugged in to my u 
s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
incerted the x band 2 plug over this track. But where do i find the library of 
categories to choos from, , also do i need to do anything else to get the 
keyboard set up for midi in p t.I really need to program drum tracks, so i 
guess somewhere i’ll need to select a midi channel and tell it to use channel 
10. But not really sure how it all works in here.

Steve

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

--
You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Christopher-Mark Gilland

I'd love to know how you're saving a session as a .mid file.  I've always 
wanted to know how to do that!

Chris.


-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Nick Gawronski
Sent: Sunday, March 15, 2015 6:04 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

Hi, If I create a midi session or get someone elses session and save the 
file as a normal midi file when I try to play it back the tempo and 
everything else about the midi session is totally wrong.  What am I 
missing as if I open up the sessions in pro tools they sound like they 
should but if I save them as midi they are all messed up and I have 
tried importing a midi file into pro tools to hear how the included pro 
tools midi maps sound but when I hit play even when I see the different 
tracks no sound plays?  Nick Gawronski

On 3/15/2015 4:24 PM, Poppa Bear wrote:
> Hey Steve, once you have the drivers installed then just create an instrument 
> track, arm it, put expand on the insert track and your good to go. You can 
> change the instrument banks under the presets for expand just like you would 
> for any other plug in.
> HTH
> Message-
> From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf 
> Of Steve Sparrow
> Sent: Sunday, March 15, 2015 12:35 PM
> To: ptaccess@googlegroups.com
> Subject: Re: midi
>
> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
> driver disk, as far as windows goes, it was just a plug and play thing. would 
> it not work the same on mac,or is it possible i may need to look for drivers 
> on line.
> Steve
>
>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>>
>> Steve,
>>
>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>> explaining what needs to be done. I'll just say that, if you haven't already 
>> done so, you'll need to install the USB driver for your keyboard.
>>
>> Slau
>>
>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>>
>>> Hi. can anyone give me some instructions as to how to get me up and running 
>>> with midi in p t.
>>> Hiere is what i’ve done so far.
>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>> then incerted the x band 2 plug over this track. But where do i find the 
>>> library of categories to choos from, , also do i need to do anything else 
>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell it 
>>> to use channel 10. But not really sure how it all works in here.
>>>
>>> Steve
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> -- 
>> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Nick Gawronski

Hi, If I create a midi session or get someone elses session and save the 
file as a normal midi file when I try to play it back the tempo and 
everything else about the midi session is totally wrong.  What am I 
missing as if I open up the sessions in pro tools they sound like they 
should but if I save them as midi they are all messed up and I have 
tried importing a midi file into pro tools to hear how the included pro 
tools midi maps sound but when I hit play even when I see the different 
tracks no sound plays?  Nick Gawronski


On 3/15/2015 4:24 PM, Poppa Bear wrote:

Hey Steve, once you have the drivers installed then just create an instrument 
track, arm it, put expand on the insert track and your good to go. You can 
change the instrument banks under the presets for expand just like you would 
for any other plug in.
HTH
Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Sunday, March 15, 2015 12:35 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

cool. thanks for this. regarding the keyboard, i don’t think it came with a 
driver disk, as far as windows goes, it was just a plug and play thing. would 
it not work the same on mac,or is it possible i may need to look for drivers on 
line.
Steve


On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:

Steve,

The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
explaining what needs to be done. I'll just say that, if you haven't already 
done so, you'll need to install the USB driver for your keyboard.

Slau

On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:


Hi. can anyone give me some instructions as to how to get me up and running 
with midi in p t.
Hiere is what i’ve done so far.
I have an 88 note usb midi controller keyboard. i have this plugged in to my u 
s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
incerted the x band 2 plug over this track. But where do i find the library of 
categories to choos from, , also do i need to do anything else to get the 
keyboard set up for midi in p t.I really need to program drum tracks, so i 
guess somewhere i’ll need to select a midi channel and tell it to use channel 
10. But not really sure how it all works in here.

Steve

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

--
You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Christopher-Mark Gilland

Has anyone found with Pianotech that when you start recording, if the first 
note/chord requires you to have your sustain peddle down, it doesn't take, 
therefore making it be legado regardless what you do?

Let me be very very clear to say, no.  I am not pressing the peddle before 
hitting record.  I don't put the pedal down until I've started the recording 
process.  Xpand 2 doesn't give me this problem, but I hate! The piano samples 
included in it!

Chris.


-Original Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Poppa Bear
Sent: Sunday, March 15, 2015 5:24 PM
To: ptaccess@googlegroups.com
Subject: RE: midi

Hey Steve, once you have the drivers installed then just create an instrument 
track, arm it, put expand on the insert track and your good to go. You can 
change the instrument banks under the presets for expand just like you would 
for any other plug in.
HTH 
Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Sunday, March 15, 2015 12:35 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

cool. thanks for this. regarding the keyboard, i don’t think it came with a 
driver disk, as far as windows goes, it was just a plug and play thing. would 
it not work the same on mac,or is it possible i may need to look for drivers on 
line.
Steve

> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
> 
> Steve,
> 
> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
> explaining what needs to be done. I'll just say that, if you haven't already 
> done so, you'll need to install the USB driver for your keyboard.
> 
> Slau
> 
> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
> 
>> Hi. can anyone give me some instructions as to how to get me up and running 
>> with midi in p t. 
>> Hiere is what i’ve done so far.
>> I have an 88 note usb midi controller keyboard. i have this plugged in to my 
>> u s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
>> incerted the x band 2 plug over this track. But where do i find the library 
>> of categories to choos from, , also do i need to do anything else to get the 
>> keyboard set up for midi in p t.I really need to program drum tracks, so i 
>> guess somewhere i’ll need to select a midi channel and tell it to use 
>> channel 10. But not really sure how it all works in here.
>> 
>> Steve
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Poppa Bear

Hey Steve, once you have the drivers installed then just create an instrument 
track, arm it, put expand on the insert track and your good to go. You can 
change the instrument banks under the presets for expand just like you would 
for any other plug in.
HTH 
Message-
From: ptaccess@googlegroups.com [mailto:ptaccess@googlegroups.com] On Behalf Of 
Steve Sparrow
Sent: Sunday, March 15, 2015 12:35 PM
To: ptaccess@googlegroups.com
Subject: Re: midi

cool. thanks for this. regarding the keyboard, i don’t think it came with a 
driver disk, as far as windows goes, it was just a plug and play thing. would 
it not work the same on mac,or is it possible i may need to look for drivers on 
line.
Steve

> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
> 
> Steve,
> 
> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
> explaining what needs to be done. I'll just say that, if you haven't already 
> done so, you'll need to install the USB driver for your keyboard.
> 
> Slau
> 
> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
> 
>> Hi. can anyone give me some instructions as to how to get me up and running 
>> with midi in p t. 
>> Hiere is what i’ve done so far.
>> I have an 88 note usb midi controller keyboard. i have this plugged in to my 
>> u s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
>> incerted the x band 2 plug over this track. But where do i find the library 
>> of categories to choos from, , also do i need to do anything else to get the 
>> keyboard set up for midi in p t.I really need to program drum tracks, so i 
>> guess somewhere i’ll need to select a midi channel and tell it to use 
>> channel 10. But not really sure how it all works in here.
>> 
>> Steve
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Slau Halatyn

Here's what I did: I looked at the manufacturer's web site to see if there was 
a Mac OS X driver for the keyboard and, boom, there it was. What clued me in 
was mention in the keyboard user manual that there was a driver so maybe that 
would be the way to go.

Slau

On Mar 15, 2015, at 4:34 PM, Steve Sparrow  wrote:

> cool. thanks for this. regarding the keyboard, i don’t think it came with a 
> driver disk, as far as windows goes, it was just a plug and play thing. would 
> it not work the same on mac,or is it possible i may need to look for drivers 
> on line.
> Steve
> 
>> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
>> 
>> Steve,
>> 
>> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
>> explaining what needs to be done. I'll just say that, if you haven't already 
>> done so, you'll need to install the USB driver for your keyboard.
>> 
>> Slau
>> 
>> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
>> 
>>> Hi. can anyone give me some instructions as to how to get me up and running 
>>> with midi in p t. 
>>> Hiere is what i’ve done so far.
>>> I have an 88 note usb midi controller keyboard. i have this plugged in to 
>>> my u s b hub. In my session i’ve inserted an stereo instrument track. I’ve 
>>> then incerted the x band 2 plug over this track. But where do i find the 
>>> library of categories to choos from, , also do i need to do anything else 
>>> to get the keyboard set up for midi in p t.I really need to program drum 
>>> tracks, so i guess somewhere i’ll need to select a midi channel and tell it 
>>> to use channel 10. But not really sure how it all works in here.
>>> 
>>> Steve
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Steve Sparrow

cool. thanks for this. regarding the keyboard, i don’t think it came with a 
driver disk, as far as windows goes, it was just a plug and play thing. would 
it not work the same on mac,or is it possible i may need to look for drivers on 
line.
Steve

> On 16 Mar 2015, at 1:26 am, Slau Halatyn  wrote:
> 
> Steve,
> 
> The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
> explaining what needs to be done. I'll just say that, if you haven't already 
> done so, you'll need to install the USB driver for your keyboard.
> 
> Slau
> 
> On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:
> 
>> Hi. can anyone give me some instructions as to how to get me up and running 
>> with midi in p t. 
>> Hiere is what i’ve done so far.
>> I have an 88 note usb midi controller keyboard. i have this plugged in to my 
>> u s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
>> incerted the x band 2 plug over this track. But where do i find the library 
>> of categories to choos from, , also do i need to do anything else to get the 
>> keyboard set up for midi in p t.I really need to program drum tracks, so i 
>> guess somewhere i’ll need to select a midi channel and tell it to use 
>> channel 10. But not really sure how it all works in here.
>> 
>> Steve
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google 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: midi

2015-03-15 Thread Slau Halatyn

Steve,

The chapters on MIDI in the Pro Tools Reference Guide will go a long way to 
explaining what needs to be done. I'll just say that, if you haven't already 
done so, you'll need to install the USB driver for your keyboard.

Slau

On Mar 15, 2015, at 8:46 AM, Steve Sparrow  wrote:

> Hi. can anyone give me some instructions as to how to get me up and running 
> with midi in p t. 
> Hiere is what i’ve done so far.
> I have an 88 note usb midi controller keyboard. i have this plugged in to my 
> u s b hub. In my session i’ve inserted an stereo instrument track. I’ve then 
> incerted the x band 2 plug over this track. But where do i find the library 
> of categories to choos from, , also do i need to do anything else to get the 
> keyboard set up for midi in p t.I really need to program drum tracks, so i 
> guess somewhere i’ll need to select a midi channel and tell it to use channel 
> 10. But not really sure how it all works in here.
> 
> Steve
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 Editor in current PT release

2014-07-02 Thread Gordon Kent


   Hi:
The midi event list is accessible, and it is also possible to activate midi 
controllers to make parameter changes on compatible hardware and virtual 
synths.

Gord

-Original Message- 
From: Slau Halatyn

Sent: Wednesday, July 2, 2014 2:03 PM
To: ptaccess@googlegroups.com
Subject: Re: Midi Editor in current PT release

MIDI Event List is accessible.

Cheers,

Slau

On Jul 2, 2014, at 11:26 AM, J. R. Westmoreland  wrote:


Good morning everyone

I'm asking this question because a friend and I were having a discussion 
and I thought I'd recalled that Avid had fixed the issue in the current 
release.
Is the Midi Editor accessible now? Or, have I mis-remembered? The later 
item wouldn't be the first time. lOL


Thanks,
J. R.



--
You received this message because you are subscribed to the Google 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: Midi Editor in current PT release

2014-07-02 Thread Slau Halatyn

MIDI Event List is accessible.

Cheers,

Slau

On Jul 2, 2014, at 11:26 AM, J. R. Westmoreland  wrote:

> Good morning everyone
> 
> I'm asking this question because a friend and I were having a discussion and 
> I thought I'd recalled that Avid had fixed the issue in the current release.
> Is the Midi Editor accessible now? Or, have I mis-remembered? The later item 
> wouldn't be the first time. lOL
> 
> Thanks,
> J. R.
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google 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: midi question

2014-06-26 Thread TheOreoMonster

if its standard midid, then drivers wouldn't be needed.  PT reference manual 
should be able to get up and going with configuring midi devices and what 
exactly you can do with standard midi in PT. 
On Jun 17, 2014, at 1:44 PM, Brian Howerton  wrote:

> Hello all,
>  
> I have a small protools setup, running PT on my macbook pro just to learn it 
> and begin to use for myself.  I have a PSR-e433 small midi keyboard that I am 
> using as a controller via usb.  I don't see any drivers for it on the Yamaha 
> site for the mac, and it is not showing up in PT.  Is there something I am 
> missing.  I'm pretty new to PT, just have started playing with it again, 
> after not having it on my mac for a while.  I put it back just recently.  
> Thanks for the help.
>  
> Brian
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google 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 controller issues in protools 11

2014-01-04 Thread Slau Halatyn

Hmm… I'm not sure what the problem might be. I had a similar experience, albeit 
with audio, going from an older MacBook Pro to a new MacBook Pro. Everything 
played back on the old system and, even though I had migrated my settings to 
the new computer, I wasn't getting playback. I thought the migration would be 
seamless but therein lay the problem: not all settings for audio are 
translatable between computers. The solution had to do with creating a new 
aggregate device. With MIDI, however, I suspect it might be similar but perhaps 
a bit different. I haven't worked with MIDI in PT 11 and even barely in version 
10 so I'm not the person to troubleshoot it. However, if you purchased version 
11, you're certainly entitled to technical support for at least 90 days. 
Hopefully, you've learned VoiceOver enough so that, when tech support asks you 
to navigate Pro Tools or the operating system, you'll be able to get around. 
Maybe somebody else on the list has some ideas.

slau

On Jan 4, 2014, at 12:27 PM, chad baker  wrote:

> hi yes i got a error saying original device hui cannot be found
> i ran it through pt10 and all is well and logic pro x controller works both 
> in pt10 and logic pro x just not pt11
> 
> On Jan 4, 2014, at 12:22 PM, Slau Halatyn  wrote:
> 
>> Hi Chad,
>> 
>> Did you go through the "Intro to Pro Tools" pdf to follow instructions on 
>> how to set up MIDI tracks for recording and playback? Also, did you have a 
>> look at the Audio MIDI Utility to see if your device is recognized and 
>> enabled? Just two things off the top of my head that I would try.
>> 
>> Slau
>> 
>> On Jan 4, 2014, at 5:35 AM, chad baker  wrote:
>> 
>>> hi i wrote yesterday i have sound i imported and playback is fine
>>> but my novation impulse 61 key midi controller there’s no sound when i play 
>>> the keys
>>> i followed the novation instructions for auto map
>>> i get the following error
>>> the original device hui could not be found
>>> i’m not a advanced protools user i’m in the middle
>>> thanks
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Pro Tools Accessibility" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google 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/groups/opt_out.

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: midi controller issues in protools 11

2014-01-04 Thread chad baker

hi yes i got a error saying original device hui cannot be found
i ran it through pt10 and all is well and logic pro x controller works both in 
pt10 and logic pro x just not pt11

On Jan 4, 2014, at 12:22 PM, Slau Halatyn  wrote:

> Hi Chad,
> 
> Did you go through the "Intro to Pro Tools" pdf to follow instructions on how 
> to set up MIDI tracks for recording and playback? Also, did you have a look 
> at the Audio MIDI Utility to see if your device is recognized and enabled? 
> Just two things off the top of my head that I would try.
> 
> Slau
> 
> On Jan 4, 2014, at 5:35 AM, chad baker  wrote:
> 
>> hi i wrote yesterday i have sound i imported and playback is fine
>> but my novation impulse 61 key midi controller there’s no sound when i play 
>> the keys
>> i followed the novation instructions for auto map
>> i get the following error
>> the original device hui could not be found
>> i’m not a advanced protools user i’m in the middle
>> thanks
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google 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/groups/opt_out.

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: midi controller issues in protools 11

2014-01-04 Thread Slau Halatyn

Hi Chad,

Did you go through the "Intro to Pro Tools" pdf to follow instructions on how 
to set up MIDI tracks for recording and playback? Also, did you have a look at 
the Audio MIDI Utility to see if your device is recognized and enabled? Just 
two things off the top of my head that I would try.

Slau

On Jan 4, 2014, at 5:35 AM, chad baker  wrote:

> hi i wrote yesterday i have sound i imported and playback is fine
> but my novation impulse 61 key midi controller there’s no sound when i play 
> the keys
> i followed the novation instructions for auto map
> i get the following error
> the original device hui could not be found
> i’m not a advanced protools user i’m in the middle
> thanks
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: MIDI merge

2013-06-24 Thread Eric Lambier

Thanks Kevin!

Mark, midi merge is for adding more the one part to a midi track IE. You record 
a kick art then want to add high hat or snare etc on the same track. You can 
record over the first track without erasing it.

Cheers

Eric

On 2013-06-16, at 3:01 PM, Chris Gilland wrote:

> Can someone tell me in the firrst place, what exactly even is! midi merge?
> 
> Chris.
> 
> - Original Message - From: "Kevin Reeves" 
> To: 
> Sent: Sunday, June 16, 2013 1:55 PM
> Subject: Re: MIDI merge
> 
> 
>> Press 9 on the numpad. That will toggle midi murge on and off.
>> 
>> Kevin
>> 
>> 
>> On Jun 12, 2013, at 4:12 PM, Eric Lambier wrote:
>> 
>>> Hello All!
>>> 
>>> I'm having a wee prob with unselecting MIDI merge. As far as I know it used 
>>> to unselect when I went into the transport window and MIDI control cluster. 
>>> Anyone know why it might have stopped letting me unselect it?
>>> Cheers
>>> 
>>> Eric
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google 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/groups/opt_out.
>>> 
>>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google 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/groups/opt_out.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google 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/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: MIDI merge

2013-06-18 Thread Kevin Reeves

With merge on, anytime you record over a midi track, you add to it. With it 
off, it erases what's there and records your new data.

Merge is good for building rhythm tracks one piece at a time onto a track.

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: MIDI merge

2013-06-16 Thread Chris Gilland

Can someone tell me in the firrst place, what exactly even is! midi merge?

Chris.

- Original Message - 
From: "Kevin Reeves" 

To: 
Sent: Sunday, June 16, 2013 1:55 PM
Subject: Re: MIDI merge

Press 9 on the numpad. That will toggle midi murge on and off.

Kevin

On Jun 12, 2013, at 4:12 PM, Eric Lambier wrote:

Hello All!

I'm having a wee prob with unselecting MIDI merge. As far as I know it 
used to unselect when I went into the transport window and MIDI control 
cluster. Anyone know why it might have stopped letting me unselect it?

Cheers

Eric

--
You received this message because you are subscribed to the Google 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/groups/opt_out.

--
You received this message because you are subscribed to the Google 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/groups/opt_out.

--
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: MIDI merge

2013-06-16 Thread Kevin Reeves

Press 9 on the numpad. That will toggle midi murge on and off.

Kevin


On Jun 12, 2013, at 4:12 PM, Eric Lambier wrote:

> Hello All!
> 
> I'm having a wee prob with unselecting MIDI merge. As far as I know it used 
> to unselect when I went into the transport window and MIDI control cluster. 
> Anyone know why it might have stopped letting me unselect it? 
> Cheers
> 
> Eric 
> 
> -- 
> You received this message because you are subscribed to the Google 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/groups/opt_out.
> 
> 

-- 
You received this message because you are subscribed to the Google 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/groups/opt_out.

Re: MIDI from GarageBand to Pro Tools

2013-05-18 Thread Chris Norman

Ah, sorry, I forgot about all that Pro Tools LE stuff, sorry, I only
came into Pro Tools at version 9...

You could record the track in Logic, and probably export MIDI from
that easier... Other than that, I'm afraid I don't really know... Good
old QWS? That would definitely do it dead easy.

HTH, and sorry I can't be more use.

On 17/05/2013, Jon Solitro  wrote:
> Because PT 8 doesn't open without an interface. I figured since I don't need
> any extra hardware to record in GB, I could record my MIDI track in GB and
> then export it into PT upstairs
> On May 17, 2013, at 11:52 AM, Chris Norman 
> wrote:
>
>> So, I'm confused. How would exporting MIDI from Garage Band help you
>> in this instance? You could just unhook everything, and USB in
>> downstairs, carrying just the MacBook?
>>
>> Sorry for the confusion,
>>
>> On 17/05/2013, Jon Solitro  wrote:
>>> I am not recording MIDI intro GB currently. I have never recorded MIDI
>>> with
>>> GB. I bought a drum set, and I am going to get some drum triggers for
>>> the
>>> heads, and run those into an Alesis Trigger IO. From there I would go
>>> USB
>>> into a computer, ideally running PT. But since I only have PT 8, I need
>>> an
>>> interface with it. So with my current setup, I would have to unhook my
>>> 003
>>> from the studio and take it down two flights to record into my Macbook.
>>> There's no way. I suppose I could get a 50 or 100 ft usb cable, but then
>>> there's the issue of monitoring. The virtual drums would be upstairs on
>>> the
>>> Mac Pro with Strike.
>>>
>>>
>>> On May 17, 2013, at 11:23 AM, Chris Norman
>>> 
>>> wrote:
>>>
 From what you've said, seems like you could just record into Pro Tools,
 the same way you record into Garage Band? A massively long MIDI cable
 or
 something?

 Sorry I can't be more helpful. How is it you're getting MIDI into GB
 currently?

 Cheers,

 Take care,

 Chris Norman.
 




 On 17 May 2013, at 16:03, Jon Solitro  wrote:

> My issue is, I have drum triggers down stairs. My studio is upstairs.
> I
> can record onto my Macbook, but I'm still on PT 8.04  so I would need
> to
> haul my 003 down as well. I'd like some software on my Macbook with
> which
> I can record MIDI without having to haul my interface down as well.
>
> Any ideas on the best way to do this?
>
> Jon
> On May 17, 2013, at 10:26 AM, Chris Norman
> 
> wrote:
>
>> I don't think so.
>> But you could record MIDI into Pro Tools, then export that and edit
>> it.
>>
>> HTH,
>>
>> On 17/05/2013, Jon Solitro  wrote:
>>> Can I record MIDI into Garageband, and then export the MIDI file to
>>> PT?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>
>> --
>> Take care,
>>
>> Chris Norman.
>>
>> 
>>
>> --
>> You received this message because you are subscribed to a topic in
>> the
>> Google Groups "Pro Tools Accessibility" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/ptaccess/WEuF0RtuuzM/unsubscribe?hl=en.
>> To unsubscribe from this group and all its topics, send an email to
>> ptaccess+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
> --
> You received this message because you are subscribed to the Google
> 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/groups/opt_out.
>
>


 --
 You received this message because you are subscribed to a topic in the
 Google Groups "Pro Tools Accessibility" group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/ptaccess/WEuF0RtuuzM/unsubscribe?hl=en.
 To unsubscribe from this group and all its topics, send an email to
 ptaccess+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>
>> --
>> Take care,
>>
>> Chris Norman.
>>
>> 
>>
>> --
>> You received

Re: MIDI from GarageBand to Pro Tools

2013-05-17 Thread Jon Solitro

Because PT 8 doesn't open without an interface. I figured since I don't need 
any extra hardware to record in GB, I could record my MIDI track in GB and then 
export it into PT upstairs 
On May 17, 2013, at 11:52 AM, Chris Norman  wrote:

> So, I'm confused. How would exporting MIDI from Garage Band help you
> in this instance? You could just unhook everything, and USB in
> downstairs, carrying just the MacBook?
> 
> Sorry for the confusion,
> 
> On 17/05/2013, Jon Solitro  wrote:
>> I am not recording MIDI intro GB currently. I have never recorded MIDI with
>> GB. I bought a drum set, and I am going to get some drum triggers for the
>> heads, and run those into an Alesis Trigger IO. From there I would go USB
>> into a computer, ideally running PT. But since I only have PT 8, I need an
>> interface with it. So with my current setup, I would have to unhook my 003
>> from the studio and take it down two flights to record into my Macbook.
>> There's no way. I suppose I could get a 50 or 100 ft usb cable, but then
>> there's the issue of monitoring. The virtual drums would be upstairs on the
>> Mac Pro with Strike.
>> 
>> 
>> On May 17, 2013, at 11:23 AM, Chris Norman 
>> wrote:
>> 
>>> From what you've said, seems like you could just record into Pro Tools,
>>> the same way you record into Garage Band? A massively long MIDI cable or
>>> something?
>>> 
>>> Sorry I can't be more helpful. How is it you're getting MIDI into GB
>>> currently?
>>> 
>>> Cheers,
>>> 
>>> Take care,
>>> 
>>> Chris Norman.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 17 May 2013, at 16:03, Jon Solitro  wrote:
>>> 
 My issue is, I have drum triggers down stairs. My studio is upstairs. I
 can record onto my Macbook, but I'm still on PT 8.04  so I would need to
 haul my 003 down as well. I'd like some software on my Macbook with which
 I can record MIDI without having to haul my interface down as well.
 
 Any ideas on the best way to do this?
 
 Jon
 On May 17, 2013, at 10:26 AM, Chris Norman 
 wrote:
 
> I don't think so.
> But you could record MIDI into Pro Tools, then export that and edit it.
> 
> HTH,
> 
> On 17/05/2013, Jon Solitro  wrote:
>> Can I record MIDI into Garageband, and then export the MIDI file to
>> PT?
>> 
>> --
>> You received this message because you are subscribed to the Google
>> 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/groups/opt_out.
>> 
>> 
>> 
> 
> 
> --
> Take care,
> 
> Chris Norman.
> 
> 
> 
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Pro Tools Accessibility" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/ptaccess/WEuF0RtuuzM/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to
> ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
 
 --
 You received this message because you are subscribed to the Google 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/groups/opt_out.
 
 
>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Pro Tools Accessibility" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/ptaccess/WEuF0RtuuzM/unsubscribe?hl=en.
>>> To unsubscribe from this group and all its topics, send an email to
>>> ptaccess+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>> 
>>> 
>> 
>> --
>> You received this message because you are subscribed to the Google 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/groups/opt_out.
>> 
>> 
>> 
> 
> 
> -- 
> Take care,
> 
> Chris Norman.
> 
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Pro Tools Accessibility" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/ptaccess/WEuF0RtuuzM/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to 
> ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

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

1 2 >

1 - 100 of 133 matches

Mail list logo