ERROR: "One or multiple audio files changed in length"

Question

Level 1

19 points

ERROR: "One or multiple audio files changed in length"

I haven't done any kind of destructive editing. I've been editing live drums for the past 5 days. Simple splitting of regions, and moving them so that they are in sync. That's all. Last night, all I did was save my session, and quit Logic.

Today, when I opened my session, I got that dreaded notification, and all those hours of work gone to waste. I tried to load an older session from the day before, but that didn't work.

I've noticed that this has been an issue for over a decade; how has Apple NOT fixed this as yet? It seems like a MAJOR problem, since it destroys our files, and countless hours of work. Most of the time, it destroys irreplaceable audio.

I'm in a state of shock, because it's making me re-think using Logic as my primary recording software.

Mac mini, macOS 15.5

Posted on Aug 7, 2026 3:22 AM

Reply

Answer 1

defmuse Author

Level 1

19 points

Aug 14, 2026 7:38 AM in response to ehsaas_d

I didn't change any sample rate whatsoever. I've been looking online, and a lot of people have been having this issue. A lot have encountered this issue simple when they hit the "undo" function.

I didn't know what caused mine, but it literally happened again a few hours ago, and now I know what caused it... the "Join Region/Notes" function. I was editing live drums again. Everything was in the same sample rate (session & audio files). After editing, I, one track at a time, merged the edited regions to create 1 full track.

That's it. I saved the session, and closed it. As soon as i opened it again, the error occurred. Luckily, I didn't lose anything this time around. Last time, I lost the original files, AND my back up files: Logic changed the files on my main drive, and my external.

Reply

Answer 2

Pancenter

Level 6

14,820 points

Aug 16, 2026 6:41 AM in response to defmuse

This is an age old problem, we used to think it was a disk format error....nope. Then it was using mismatched sample rates...nope

Next time it happens try copying the original files and project to a new location and open from there. I'm using by today's standards and ancient system but it works perfectly for my needs, recording humans! :-)

Reply

Answer 3

ehsaas_d

Level 1

18 points

Aug 14, 2026 4:11 AM in response to defmuse

It is usually because of change in project sample rate. Changing that will mismatch the sync and hence will mess up the audio

Reply