AxeAttaxe

Blink, What you're saying does make sense, but I don't know if that applies here. Because the value that is "0.3.3.239" is the "Length" value when I hover over it - not the position of the final tick. And a "normal" bar should have a length of 1.0 bars, not 0.3.3.239 bars. Also, 90% (if not more) of the 1-bar regions I create doing this remain at 1.0.0.0 on the "length" metric. It's only about 10% (rough estimate) that have this peculiar issue where they start at 1.0.0.0 but after being moved onto a track - and often sandwiched between other 1.0.0.0 regions - later become 0.3.3.239-length regions (I always make sure they are starting at the very "start" of a bar - such as 66.0.0.0).

Ok, not as dumb as I look - I had been using "Selection Start" as search criteria once I located it to see what other key commands were related to it. That, of course, filtered out anything with "End" in it - like "Go to Selection End" which indeed exists as a key command. Nice! In case anybody's curious, it's Control-End, which in my case is Control-Fn-Left Arrow since I don't have an End key.

Is anybody aware of a key command or menu option that moves the playhead to the end of a selected region? I think I've found what moves it to the *beginning* of one - namely, the "Go To Selection Start" key command (I had been looking for "Move Playhead..." and thus wasn't finding it) but don't see any corresponding option to put the playhead at the end of that region.

Hey, thanks for the reply - I have issues getting this site's notifications to my email (perhaps they're going to spam) so just checked in and here was a reply. I have not heard of zero-crossing editing - or edit option - nor have any familiarity/experience with it. In fact, I have no idea what it means. But I'm going to look it up. Sounds as promising as anything I've tried! I'll let you know if I get anywhere...

Howdy all, I've had this ongoing issue with Logic Pro X - nothing to do with the release of 10.5 as this dates back long before that. I often lay down my guitar tracks, then cut the best parts from that track into Regions; many times I "splice in" a Region 1 or 2 bars long (and use crossfades) to clean up a part that wasn't quite right. Every time I do this, I use the Split Regions operation (Command + T) at 1-bar increments on the ruler; example is one split at 75.1.1.1 and another at 76.1.1.1, then pulling the resulting 1-bar Region out and dragging it where it needs to go. Time and time again, when I look back at these Regions I've created (often doing other stuff then returning to the guitar) *some* are no longer "technically" a full bar but instead 0.3.3.239 - exactly one Tick short of a full bar. I'm not putting these regions into areas on the track where there's already a region and thus they are getting shortened; they always have at least a full bar to fit into. I then go through and change the length of them back to 1.0.0.0 by lengthening the right side of the region by 1 tick. After doing this, they all stay at 1.0.0.0 for that project. It's irritating but there are worse things in life. Tonight I noticed something new: When pulling the right side of the region to lengthen it by 1 Tick, it does not say "+0.0.0.1" for "Length Change," but rather "0.0.0.0" as if I'm not actually lengthening it at all. I don't know if that's been the case before as I haven't paid close attention to that field. Either way, it definitely changes the "length" of each of these regions from 0.3.3.239 to 1.0.0.0 when I add the 1-tick length to the region's end. Any idea what's going on here, and any idea if it even matters whether a region is 0.3.3.239 vs 1.0.0.0? The OCD in me says it does which is why I fix it, but seeing the "Length Change" metric read 0.0.0.0 when lengthening these regions has me wondering.

Thank you both! I actually pulled it off last night using the method I guessed at in my post - creating a tiny region comprised only of that final eight note, then Time Stretching it out a way. However, that was a bit tedious and far from elegant. Flex Time always seemed cool/helpful to me, especially after reading/experimenting with it in David's 10.4 book. But I never found a need for it yet (or didn't know I needed it). Now I have, so it's a good time to jump on it. Thanks for the shortcut on how to conduct this particular task, David.

I think I'm dancing around something obvious, but I'm struggling to simply extend an audio (guitar) note an extra half bar without it changing pitch or speed. Let's say I play notes for 1.5 bars, ending on a single 8th note. I later want that eighth note it ended on extended another half bar - to extend from where the region stopped at 1.5 bars out to 2 with (ideally) no noticeable alteration in the note. Volume would remain the same, as would pitch and speed. When I use time stretch to do this (extending it to nearest bar), it cuts the region's play speed in half. If I only played a single note for that region this would be fine, but obviously that's not typical. Maybe I need to split the region so I have a region containing just the note I want extended, then use time stretch? I'll try that in the meantime but was curious if there's a simpler way to extend the end of a region from a given point, maintaining the exact sound(s) at that point. Perhaps I need read up on Flex Time.

This happened to me as well tonight after upgrading to 10.5.1. But after that initial startup taking 5 minutes or so, it's started and acted completely normally every time since. I checked Plug-in Manager (I have many) and they all still look fine, so hopefully just a one-time thing.

Logic 10.5.1 was released to the App Store yesterday and includes a lot of "stability/reliability" fixes. I have't experienced the problem this thread describes in 10.5, but hopefully 10.5.1 irons out the issue completely.

Ok, thanks. Audio file itself will have to do!

I know it's not possible for MIDI - at least I think it isn't - but is it possible to find out when exactly an Audio Region was created and/or modified? I can find the time an Audio *file* was created or modified by looking at its associated file in Finder, but I'm curious if you can go a step further and determine when a particular region was made (cut from the audio file, or whatever you did to create the region from the file).

Is there a way to find the last MIDI note that was edited? If not note, perhaps MIDI region? Undo History doesn't provide specifics on operations. With Audio Tracks, one could theoretically match a region to its corresponding audio file in the Audio File Browser, then find that file's modified date in Finder (I suppose; I haven't actually tested this). Is there a way to determine this with MIDI? Often at/near the end of my Undo History there's a "Move Event" or "Change Note Length" operation, but I can't recall what it was and it becomes lost in the vast sea of MIDI in my project. Even Undo/Redo over and over doesn't "point out" that change - especially since I often need to manually refresh Piano Roll to reflect most recent changes. Any clever ways to figure this out?

Wow, 13" is hard to believe given how what you do. Maybe I've become so used to bigger monitors that I just think I need them... because when I use my Macbook (15") as a laptop it works perfectly well for anything I'm doing. There's probably a lesson there. Your mouse comment hits home: I've had to adjust my Magic Mouse's tracking speed higher several times upon getting a 35" monitor (tracking speed is now 6/7) just to avoid moving my hand wildly over my entire desk to get across the screen. I've dismissed external trackpads only because I've always used external mice, but I like Macbook trackpads above all other navigation techniques so trying one does make sense...

I hear that, I've dialed down more "extras" the past few years and found I now just have more space. Though I do still use external monitors (maybe you do too and just mean you use an external trackpad, not a laptop). Anyhow good info, thanks.

...And saved me from needing a keyboard with a numeric keypad (for now at least). Speaking of - and perhaps this needs its own thread - is that something you (or anybody who wants to chime in) finds useful: the expanded key commands a numeric keypad offers? They sound like nice options but I'm not sure if the extra keyboard width would annoy me. Maybe it's one of those things you could just use at opportune times...