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 > 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 can be used to change the end time or duration. Again, > pressing Enter after typing the new values. > > You can also change the pitch or velocity in the counter display cluster of > the Edit window. Here, however, you don't need to double-click. You can > simply click one once on the value with Control-Option-Space Bar, type the > value or press a note on a controller and hit Return. > > I should reiterate that this alternative method which I just described > involves cycling between the Event List and the Edit window. While each > window has focus, the down and up arrow keys will behave differently. In the > Event List, if there's an event selected, the arrow keys will selecte notes > as the keys are pressed. This doesn't select a range but rather individual > notes at a time whether you're moving up or down. The same arrow keys have a > very different function in the Edit window, of course. If you press the down > arrow in the Edit window, you will move the insertion point to reflect the > Start time and it will deselect any duration or note value. In other words, > with this alternate method, one has to be conscious of which window is active > and when to use the arrow keys for which purpose. > > So, there are advantages to either method, I suppose. Hopefully, that'll help > some folks with their MIDI editing. There are still some peculiarities > regarding how Pro Tools displays bank and program change values in the Event > List. It's an active bug which I hope will be resolved in the future. As > always, things sound so much more complicated when they're written out. All > of this is actually quite easy when you've done it a bit. > > Best, > Slau > parameters > On Apr 12, 2016, at 8:22 AM, peter <peter.durieux1...@gmail.com> 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.
