Jump to content

1-bar Regions "losing" one Tick


AxeAttaxe
 Share

Recommended Posts

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.

Edited by AxeAttaxe
Link to comment
Share on other sites

  • 2 weeks later...

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

Link to comment
Share on other sites

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

Is it because you expect the end of the bar being 0.3.3.240, in your example(which I don’t think is right numbering but I get what you want to get at)? If there’s 240 ticks before going to 0.3.4.000, the last tick is actually at 239 since it started at .000 so .239 is the 240th tick, so the last one before going one number up in the decimal before it.

 

Blink

Link to comment
Share on other sites

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

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...