JohnnyHands
Member-
Posts
32 -
Joined
-
Last visited
JohnnyHands's Achievements
-
Thanks for the tips. Originally, I tried looking at the event list in the List editor but couldn’t get the events to show for some reason (I think I need to understand List viewing View -> Link better, maybe.) I restarted and the problem went away, but I will keep the CC7 & CC11 culprits in mind if it happens again. This may be some kind of corruption in my Logic setup that’s only affecting me - but maybe not.
-
I start play at the beginning with the Bright Mk II track solo’d by itself, but those first bunch of notes don’t sound. Sound happens around bar 5 with those three held-chord notes play, then it plays fine through the rest of this region. This happens every time. Anyone seen a problem like this before? Note, even though automation is on in screenshot, it happens with it off (Automation Read menu turned gray/off.) There isn’t any automation on this track as far as I know. MY CONFIGURATION: iMac 21.5” (Late 2015), MacOS Monterey 12.7.2, Logic 10.7.9
-
I just noticed this item in the Automation mode menu (for track headers/channel strips.) What is it for? I've never had any problem recording automation with MIDI regions, and I don't think I ever checked this. Am I mistaken? Note: searching for the following in Logic's 'Logic Pro User Guide' does not return any results: Record automation with MIDI regions
-
I wasn't following David's point about Shift until I tried drag selecting only two velocities where there were four velocities at that position - all four were selected anyway. With Shift-Option only the two I drag selected were actually selected. So, yes, more precision with Shift-Option. But Shift is what you want if you combine non-contiguous selections because Shift-Option will deselect your previous selection. Using Shift will preserve your previous selection and let you add to it (just like it does in other places in Logic.) Note, if a Shift drag-selection selects more velocities than you want, you can just use Shift again to deselect the unwanted one(s). Good point, polanoid, the Control in Shift-Control-Option is not necessary here (yes, it does show you the Automation Select cursor - but pointless for this purpose, and just an extra key to hold down.)
- 3 replies
-
- Automation Select tool
- Shift-control-option
- (and 3 more)
-
I was trying to find information, both this site and the web in general, on how to make a partial selection via dragging of MIDI Note Velocities in the automation editor (Automation/MIDI in the Piano Editor, for me, but works in the Main Window automation also) and was having a very hard time. I found this archived post entitled 'Logic Pro Velocity automation [SOLVED]': but that post only dealt with make a selection with a straight line drawing selection where values snap to a selection when you let go of the mouse - which I'm still confounded by. I wanted to know how to just draw a rectangle around a selection, just to select them, then in a following step drag the values up or down. I finally stumbled on the key command to allow you to do it: Shift-Control-Option (turns cursor into the Automation Select tool, temporarily) Then, with Shift-Control-Option still held down, you can draw a rectangle around your desired notes, which only selects them, then you can drag that selection up or down. Note, to select all velocities you can use command-a. My configuration: MacOS Monterey, Logic Pro 10.7.9
- 3 replies
-
- 1
-
- Automation Select tool
- Shift-control-option
- (and 3 more)
-
I'm trying to enter notes with the pencil tool in the key of G (with the project key set to G) - I'm only currently interested in diatonic notes - no sharps or flats. When I click in the staff, Logic seem to want to display a sharp or flat, just above or below the scale note I want, then I have to drag it up or down to fix it. Yes, I can watch the help tag while I carefully drag it to the right chromatic position, but I want to work quicker than that. I've tried, in the Score Editor local inspector, setting Scale Quantize to G and Major, but it doesn't quantize the pencil tool note entry - I guess it will only quantize already-entered/ selected notes - after I click the Scale Quantize section's Q button. Not what I want. Is there a way to force only scale notes to be entered with the pencil tool? (side note: the pencil tool is very unintuitive as a mouse cursor for musical note entry .)
- 1 reply
-
- score editor
- scale quantize
-
(and 1 more)
Tagged with:
-
Oh, OK. I can't do that with these A-88 S1/S2 buttons. But instead of the buttons, I assigned the lowest four keyboard notes as "pads", A-1, A#-1, B-1, and C0. It seems to work - the first time you press/release one of those keys, starts the loop, and the next time it ends it. Then I tried creating a software instrument track to jam along. To not overlap "pad key" assignments, I set the instrument's Inspector key limit to C#0 G8, to skip those four lowest keys. Seems to work. I guess would need to set that same C#0 G8 key limit for any other software instruments I were to create as well in this scenario. Maybe it doesn't work: with the Software instrument in track three and selected, it seems the A-1 and A#-1 keys trigger the two loops the second track instead of the first one. And the B-1 and C0 keys trigger the software instrument on Track. So I guess this keys depend on which track is selected? I'm confused now.
-
I just want to make sure I’ve got the MIDI pad behavior part of Lesson 6 working. My Roland A88 MIDI controller doesn’t have any pads, but it does have a couple of buttons, S1 and S2, that (I think) I’ve got configured to emulate a MIDI controller pad: Roland calls the following “Momentary operation” for button S1 (and S2. ) I’m arbitrarily using using Control Change # 55 on MIDI channel 1. MIDI channel / Control Change # / data value: 1 55 127 (depressing S1 button) 1 55 0 (releasing S1 button) THE ABOVE SEEMS LIKE IT’S “PAD-LIKE” AND WOULD WORK FOR LESSON 6, Live Loop pad triggering. Am I right? If not, Roland calls the following, “Latched Operation.” Again, I’m arbitrarily using using Control Change # 55 on MIDI channel 1. MIDI channel / Control Change # / data value : 1 55 127 (1st press/ release of S1) 1 55 0 (2nd press/ release of S1) 1 55 127 (3rd press/ release of S1) 1 55 0 (4th press/ release of S1) etc… (alternating between 127 and 0)
-
Here's a screenshot from Page 278 of the book, below. You can see in the menu that "B - Comp B" is checked, and is the current comp, but the text at the bottom says the Flatten operation will change the names of all regions to "Splice: Comp A." For me it was, after the Flatten, indeed, "Splice: Comp B:" and I suppose that's what supposed to happen, making "Splice: Comp A" a misprint.
-
Quick Sampler crossfade marker, not seeing it
JohnnyHands replied to JohnnyHands's topic in Logic Pro Book — by David Nahmani
the "less-than-greater-than cursor" could have been written more simply as the <> cursor. That's the cursor directly over the X button in the book's screenshot. -
Quick Sampler crossfade marker, not seeing it
JohnnyHands replied to JohnnyHands's topic in Logic Pro Book — by David Nahmani
Oh, I see. The X button in the book looks different because the mouse cursor (a less-than-greater-than-keys-looking cursor) is right over the X. And the X button goes down a level once you move it left. Got it. Thanks! -
I'm in Lesson 5, 'Looping Sample Playback to Sustain Sound', step 12. I'm in CLASSIC mode, I'm not seeing the crossfade marker (thing the book's red arrow is pointing to. Here's a screenshot of the book at that point): Here's what I'm seeing in Logic. Is there a common mistake I'm making? Thanks! I'm in Logic 10.7.7.
-
Logic Pro book by David Nahmani (Apple Pro Training Series)
JohnnyHands replied to David Nahmani's topic in Logic Pro
Done.