jdpro

Thanks. Old habit of replace recording and only keeping good takes to reduce clutter and dick space. I'l keep the resizing advise in mind, although I have ruled that out on at least a few instance when it happened after no resizing was done and all regions were at the originally recorded length. Also, always just that tiny bit short as in my example (7/3/3/239 instead of 8). It's almost always that regardless of tempo. I did see 7/3/3/241 a time or 2. For a while I thought might have been caused turning FLEX functions on/off, but it has now occurred when no flex was ever activated. I'll stay on it. Thanks.

apple menu / recent items / Logic Pro x file menu / new. Create track window opens. click "cancel" to open "choose project" window Tap in tempo, select key sig, and leave all other settings. Select "choose" Create track window opens. Leave all settings and click "create" and 1 audio track is created. Rename track Click "Replace" record and "autopunch" buttons at top of window. Drag red autopunch area to bar 3. Length is 4 bars (start 3 / end 7) I usually set playhead to bar 2 to provide 2 bars of pre-roll. Click/activate click track/metronome Record enable track Click record (red circle). Now I have recorded 4 regions, then changed auto punch length to 2 bars and recorded 4 more regions, and, as expected, all are perfect full bar length. Unfortunately, I have no doubt that the problem will occur again. As I stated earlier, I am quite certain that somehow the regions are changing in length after the fact, I can only assume as the result of some other looping or repeating manipulation. Sort of why I never sat and documented step by step before, but t least now I have my setup process here on the forum. The regions I recorded yesterday are scratch tracks for a new tune. I will re-record them soon and will try to watch for the problem. Obviously it's nice to be focusing on creating and performing and not technical forensics at every step. Oh well. Hopefully at some point I'll catch the exact function that is causing the problem. Thanks for your time.

So again. New song. No flex or editing at all. 2 gtr regions and 2 bass regions recorded and as I go to move a region I notice a region recorded with the punch set for 16 bars is somehow 15/3/3/239 while another is 16/0/0/0. Likewise an 8 bar region is still 8/0/0/0 and another is somehow 7/3/3/239. 4/4 sig and the tempo is 124bpm. I really don't believe the tempo is the issue because this has happened at many different tempos. Everything previously mentioned above is still the case. I should also mention I just got the latest upgrade last week and obviously that didn't help. So freaking annoying. Please help.

I'll try. I hate the idea of having to constantly check region lengths, but I think tthat'sthe only way I'm going to solve this if Apple doesn't. Thanks.

Thanks. Happens when there has been no cutting. But after reading the split region bug, it seems very similar. It dawned on me it could be the result of "repeat multiple" which I use regularly and that not only are the repeated regions of unintended length, but the original source region length is also being altered by the process. I know my original regions are good because I listen a repeating loop playback with click to make sure it's good, then I either repeat multiple or drag out looping repetitions of the region, and that's around the time the problem starts.

Auto punch is set for 8 bars and records 8 bars. I'm certain it's not the recording process. The region is recording at the intended length. I know this because I have referred back to previously save versions. Also, I ask again. Have you heard others mention regions changing length?

Yes. Records correctly.

No cycle. Punch snaps and records exactly. Obviously I don't get to see it change but I noticed in the past when zooming in and editing other regions. Now I am forced to keep checking when I am about to loop or repeat a region. Has anyone else had this problem?

This happens with many projects of various tempos. Not surprisingly, most are 4/4 signature.

I'll just start with the exact problem I keep having. 8 bar audio regions that I have recorded are automatically switched to a length of 7/3/3/239. I have check to see if the region can be expanded to real more audio and it never has. What is strange is that not all 8 bar regions are effected. Often I get lucky. This happens quite often and is a problem as I often use looping. Recorded with auto punch set to exactly 8 bars. Tempo set to KEEP. Snap set to SMART with ABSOLUTE values. No tempo changes have been made in the project. Please help.

Mr L, you made my day. It worked. What's crazy though is I had ZERO CROSSING checked and it did not split exactly at the bar. UNchecking it allowed me to split exactly at the bar. To me that's not exactly logical. Anyway, another tool for the toolbox. Thanks again.

ANYONE?? PLEASE??

Yes. You are correct. 1 not 0.

OMFG !!! PLEEEEEASE HELP !!! Read for about an hour and found several people with this unresolved problem. Occurs with certain regions but not others in same project. I have an audio region that starts at bar 2/0/0/0 and ends at 19/0/0/0. I can easily as usual pop the playhead to 3/0/0/0 or any other bar. Choose the SPLIT AT PLAYHEAD feature and it splits not at bar 3 but at 2/4/4/240. I've tried TRIM, marquee tool, copy/paste, and locators and all the same results. I also tried every possible combo of SNAP settings. I tried creating a new track, even a new empty project and importing the raw file and get the same results. What's strange is I recorded some takes, then created "another track with duplicate settings" and did some more takes. When I try to split a region on the new adjacent/duplicate track, it splits perfectly at 3/0/0/0. So I drag my previously mentioned region to that adjacent track at 20/0/0/0 to 39/0/0/0, pop the playhead to 21/0/0/0 and try split at playhead and, you guessed it, it splits at 20/4/4/240. So I have two regions that were born in the same project and seem to have the same exact attributes, and sit next to each other on the same track, and one splits on the bar (#/0/0/0) and one doesn't (#/4/4/240). I considered that the recurring 240 might suggest some type of quantization or region delay, but that would be eliminated in a new default project with the imported file. As I I said I got the same 240 in a brand new default project after a full computer restart. It seems it has to be something with the region itself because the function works elsewhere in the project. What's killing me is I decided to go back to this one final song and redo this one final verse guitar and my album is DONE and off to be mastered. After about 15 takes, I have the performance I want via two 2 regions and should be able to comp them together in about 1 minute, but instead the performance is held hostage by (IL)LOGIC. I'd rather spend a few hours learning to overcome this in the future, rather than try to rebuild the project which I don't believe will work anyway.

Thanks guys, I do always save as folder not package, so that's not an issue. And I did discover the problem thanks to you. It was the "Alternatives / Undo Data.nosync" folder. Still not sure why this is the only project of many that had this problem. Anyway, after getting rid of unnecessary files, I'm back to normal 5-10MB project files for 2 of 3 project files in question. After attempting the same fix on the 3rd, I still show 13GB. When I show package contents and get info on all the contents, nothing in there adds up to even a MB. Even tried empty trash and restart and it still shows 13GB. Very strange.