erm87

This was happening to me today when comping bass tracks and was able to narrow down to flex mode. In my situation, I recorded a bass track and quantized it for timing adjustments. Later I went back to punch-in a small section on this same track and boom — every time I flattened the track after creating the take it would nudge the region in back about 1/16 note leaving a spot of silence instead of the intended crossfade. Then I noticed it did the same thing when I turned off Flex mode. However, toggling it off and on made the situation go away — I assume something to do with that triggering Logic to create new flex markers for the newly tracked take. I could then flatten and merge as expected. Hope that helps someone else!

Just wanted to confirm I had this same thing happen to me. I froze ~40 tracks on a current project (Logic Pro X 10.5.1) and noticed that timing seemed off in a few spots. I tried @JCares suggestion and changing to source (blue) freezing did the trick. Unfortunately, I didn't see a way to bulk switch the freezing mode so that was a pain to change... Anyways just wanted to confirm another case so that the Logic team and others had more visibility on the issue.

I have a solution, well for my use case anyways So I have been struggling with this forever too — I have a session where I send midi events out to my Kemper amp to auto-switch presets during lives shows. However, if I accidentally click on the midi track, the auto-arm crashes the Kemper. I think it sends some bogus midi that it can't handle... I found that if you create a Folder Stack (in my case just for a single track) and collapse it, you can then click on folder track without it arming the actual midi track within. This way you can at least interact with the midi regions and do some basic fader adjustments/mute/solo/etc. without accidentally messing your rig up. Hope this helps!