des99

Ok, so it was an audio latency issue after all. Thanks for letting us know what solved it. 👍

If you search for the error message, you'll bring up previous discussions on this, eg: https://www.logicprohelp.com/search/?&q="One or multiple audio files changed in length"&quick=1&search_and_or=and&sortby=relevancy

Try trashing your control surface prefs and re-setting up any of your controllers, it sounds like they've gone flaky...

Strange - does it even make sense there should be a sample rate selection, the program is working with MIDI & timing data, not audio... (!) Edit: Ok, it does say (can't copy/paste from AppStore, grr...) "Select Project Sample Rate to match the current project setting", for some reason. In any case, whatever the sample rate you are working at in your project, that's the option you should choose in that plugin, presumably for some timing reasons or something. If the timing is out at a particular sample rate, maybe contact the developer and give them a bug report...

It's fine. Your notes actually start 1 tick before the bar (check in the event list), and when you zoom out on the arrange, the zoom resolution makes it look like the region starts on the beat - and this is exactly what happens in the piano roll - it simply can't zoom in far enough to make 1 tick span 200 pixels or whatever, so it just looks like it's on the beat. So the problem here is a 1 tick difference that isn't really meaningful in the piano roll - it simply can't display that high a resolution, regardless of how far you're zoomed in. Again, the event and region positions are all fine here.

Perhaps you are seeing previous auto-backedup versions? Logic saves previous copies of the project (up to an amount you specify in the preferences, I think it defaults to 10 maybe), as a safety feature. But the recent save will always be the project you are saving to. Just ignore those backups, or you can turn it off in the preferences (I forget the exact place offhand, it's been a decade since I opened Logic 9...)

Those two windows are at different horizontal zoom levels, that's all. They are independent, and can be zoomed independently - there is no expectation they should be displaying the same zoom level all the time.

I don't know what "Audio Chops" is, but you can determine what assets/audio files/samples etc you want Logic to copy into the project with the project save options.

You'll need to compress the logicx file, not attach it directly. This will bring the file size down too.

Logic's file size does not increase every time you open/close it. However, there is stuff stored in there like your undo history, and different versions and alternates. Why don't you have a look inside the package and see which data is taking up the space? Right-click on it in Finder, and select "Show Package Contents" and have a look...

"Save as" creates a new project, yes, that's what it does. Save just saves your current project. You should just "save" your work, not keep "save as"-ing to a new project.

It's just Command S to save the project you are working on to disk. It just saves the current project to the existing project file.

I don't know what is happening in your specific case. I'm saying though that just because the progress bar says "Channel EQ" and doesn't progress further, doesn't mean Logic is hanging on it's own code - that really doesn't happen in my experience. Leaving aside corrupt projects, it's 95% of the time third-party plugin problems. There was an iLok issue a couple of years back that could be fixed in the way you describe for specific reasons (I won't go into this in detail here), but unless you're running old iLok code, that's probably not the case here. In the case of Fabfilter, these have a reputation of being pretty solid, but the environment software is running in is a wild card - I see in your case, you're running a patched macOS on presumably an otherwise unsupported hardware machine (which is the point of patching it), so it's difficult to say what's going on. It could even be something hardware related like RAM issues. But if you feel that the FF plugin (or other ones) is unreliable on your system, you might want to connect with support, they might have some ideas.

Softube VCA Compressor Presets from the dbx-style compressor plugin. Softube VCA Compressor.zip Instructions: Once unpacked, Copy the "Factory" folder to ~/Library/Audio/Presets/Softube/VCA Compressor/ (that's the Library folder in your home directory) Index to this thread by Type / Manufacturer / Plugin: Third-party Patches Index

Softube Tape Echoes Presets from the analog saturation processor plugin. Softube Tape Echoes.zip Instructions: Once unpacked, Copy the "Factory" folder to ~/Library/Audio/Presets/Softube/Tape Echoes/ (that's the Library folder in your home directory) Index to this thread by Type / Manufacturer / Plugin: Third-party Patches Index