Re: midi editing question

[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 

Re: Autolaunch Avid app manager

[Slau Halatyn]

Had a little trouble finding this as it was under a different thread name but 
here's what I said back then. Of course, since then, the Applications Manager 
has become accessible:
Slau wrote:
To prevent the Application Manager from loading, go to your Library folder and, 
within the Launch select the two plist files with Avid.ApplicationManager in 
the name. There should only be two such files in there. Move them to another 
folder outside the Library folder and reboot. Having done this, you'll have to 
manually launch the Application Manager to have it check for updates.

On Apr 21, 2016, at 11:55 AM, Martin (Punky) Sopart  wrote:

> Hi Slau!
> 
> Some time ago you sent a mail with instructions to stop the autolaunch of
> the app manager from Avid.
> Could you forward it again, please?
> 
> Thanks in advance and best regards! / 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

[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 

Re: Template

[Ricky Prevatte]

Now that is strange. I hope that part shows up in the archive. I think I better 
check.

Ricky Prevatte LMBT1154

> On Apr 20, 2016, at 3:18 PM, Slau Halatyn  wrote:
> 
> Hi Ricky,
> Glad it worked out although I'm a little puzzled why my quoted message below 
> yours simply says, "recorded." I did write quite a bit more than that :) 
> Maybe there's an editor troll on the site. :) At any rate, sounds like you're 
> all set.
> Best,
> Slau
> 
>> On Apr 20, 2016, at 2:01 PM, Ricky Prevatte  wrote:
>> 
>> Slau this is why a list like this is worth waiting through any other less 
>> than desirable conversation. I knew Protools user like myself that is just 
>> catching on to voiceover would not have time to find this type of thing out. 
>> Thanks guys this settled my difficulty but I feel like we got a bit more 
>> discussion for the archive for folks who might have this problem in the 
>> future.
>> 
>> Ricky Prevatte LMBT1154
>> 
>>> On Apr 20, 2016, at 9:15 AM, Slau Halatyn  wrote:
>>> 
>>> recorded
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Pro Tools Accessibility" group.
>> To unsubscribe from this group 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: pro tools and video question

[Vaughn Brown]

Hi folks,

This is helpful as I am trying to find ways of adding music to video
recorded of nature etc.
Thank you very much!
Vaughn

On 4/21/16, Slau Halatyn  wrote:
> Turns out, the video implementation has actually improved in Pro Tools since
> I last checked. My needs were simple at the time but it appears that it's
> come along and there appear to be more options. Here's a PTE video on the
> subject:
> http://www.pro-tools-expert.com/home-page/pro-tools-has-a-useful-feature-even-some-professionals-dont-know-about
>
> To get a true projection situation going, it still requires external
> hardware but, the point is, it's possible.
> HTH,
> Slau
>
> --
> You received this message because you are subscribed to the Google Groups
> "Pro Tools Accessibility" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ptaccess+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Vaughn Brown
Berklee College of Music Graduate, Bachelor in Music, Drummer, educator
504-202-8492
http://www.vaughnbrown.net

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

Autolaunch Avid app manager

[Martin (Punky) Sopart]

Hi Slau!

Some time ago you sent a mail with instructions to stop the autolaunch of
the app manager from Avid.
Could you forward it again, please?

Thanks in advance and best regards! / Martin


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

Re: midi editing question

[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 

Re: pro tools and video question

[Slau Halatyn]

Turns out, the video implementation has actually improved in Pro Tools since I 
last checked. My needs were simple at the time but it appears that it's come 
along and there appear to be more options. Here's a PTE video on the subject:
http://www.pro-tools-expert.com/home-page/pro-tools-has-a-useful-feature-even-some-professionals-dont-know-about

To get a true projection situation going, it still requires external hardware 
but, the point is, it's possible.
HTH,
Slau

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

Re: Adjusting gain of selected clip

[John André Lium-Netland]

Hi Peter,

While the clip is selected, press control-shift-up arrow or down arrow to 
adjust the gain. The amount of each adjustment is set in the preferences.

Remember, you don’t have to separate the clip first, just make a selection in 
the edit window and make your adjustments.

Best,
John André

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

Adjusting gain of selected clip

[Peter Bosher]

Hi All,

How do you adjust the gain of a selected clip, other than with a control 
surface?

Best,

Peter

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