dven

Probably local time machine backups. From the command line, run You’ll probably see a long list of backups. You can purge old snapshots: The 1st number is the amount you want to purge and the second is a priority setting - high in this case.

Anything with a T2 is already doing the encrypt/decrypt by default - its actually permanently on. The Filevault setting just turns on the password requirement. Its different from the pre-T2 machines where the encrypt/decrypt was actually on or off depending on the Filevault setting. So basically, there's no difference speed-wise - its just a matter of whether you want the extra security of requiring a password.

In 10.4.4, if you have tracks using Kontakt 5, you can deactivate the plugin and (assuming Kontakt 6 is installed) Logic will replace the K5 instances with K6. This appears to be broken with 10.4.5. Anyone else confirm? Cheers, Dorian

Is there any sort of log of the crash? Sometimes there's a thread trace that points to the culprit - be it a bad plugin or something else.

Hi Dven, When you say "that particular method" - is there another way of doing the same thing that I could use as a workaround? thanks Malcolm Sorry - really meant I never use that particular way of creating arrange tracks (method not the best terminology in this case!) I didn't try the key command. But, it does work from the mixer window..... just not the arrange window......

Didn't they assign something like this to showing associated aux tracks? I just tried it and can replicate the 'no track created' behavior. And, bonus!, if I try it again, Logic crashes instantly. Fortunately I never use that particular method, but....seems like a bug.

https://itunes.apple.com/us/app/macos-high-sierra/id1246284741?ls=1&mt=12 for the HS installer

Cheers for the CCC info. That's very interesting!

From what I've read (eg https://derflounder.wordpress.com/2019/02/23/mounting-time-machine-local-snapshots-as-read-only-volumes/) the local snapshots in HS are apfs (assuming the drive is apfs). The snapshots do register as used space on the drive. What I don't know, since I've never gotten that far, is whether the snapshots will actually be automatically deleted when a critical threshold is reached. From the docs I've read its something along the lines of 20% or 5GB free space. I do know that contrary to the docs, the local snapshots are stored for longer than the advertised 24 hour period.

They're definitely using user accessible disk space - or at least are now being reported as used disk space to the finder, since the available free space is directly tied to the snapshot usage. IE - I can delete a bunch of them and watch the free space on the disk rise. I've never gotten to the point of little enough free space to find out if they get overwritten as needed, but I have seen people reporting free space dropping into the single GB range.

I just upgraded to Mojave this weekend, so please fill me in. I was under the impression that Time Machine is not using APFS yet. TM has always been making local "snapshots" behind the scenes for quite a while and it also automatically removes them and never reports that space as used up on the drive either. Did they change to something that is APFS based and not automatically cleaned up? I was not aware if so. I will need to look into that. I am also using a free tool called TimeMachineEditor which gives me the ability to change when TM will run and to disable the local snapshots entirely..... timemachineeditor.jpg This may be an afps thing or High Sierra only, but on my 2018 MBP, the local snapshots eat a ton of space and do not get deleted in a timely fashion - even when I connect my time machine backup drive. The snapshots can eat a *lot* - many 10s of GB. If you google 'tmutil' you'll find a bunch of stuff about it. As an example....I had 1.5 GB of local snaps just from today - and that's *with* a backup drive connected. As a bonus, the free space reported by the finder is a wildly inaccurate measurement due to the way that the local snapshots are kept. I can delete a couple of GB and the free space won't budge. I'm still on High Sierra, since I've also got the USB audio bug that the MBPs suffer from and have some workarounds in place for my current O/S. Hoping that Mojave has sorted that issue in 10.4.6, but waiting to jump until I know for sure.

@skijumptoes - On the free space issue... And you probably know this already.... If the O/S is High Sierra or Mojave, the local snapshots that time machine creates will quickly fill up the drive. And, as a bonus, time machine doesn't actually manage the deletion of those snapshots very well. I periodically go in and remove the extraneous snapshots to free up more drive space. tmutil has a bunch of options that let you manage that process manually. In general I agree on the Windows vs. Mac thing. Both are useful and both have flaws. Though Apple as a company does seem to be winning the evil empire contest at the moment......

Bog standard 24/44.1. I haven't experimented with other sample rates. Since changing the SR resets the audio engine, some people initially trumpeted that as a solution (on the macrumors forums at least), but obviously not!

Nothing to do on my end, since the audio engine restarts on its own. The interface (tested with Focusrite 2i2, Focusrite solo, NI Komplete) remains attached and Logic doesn't seem to notice or care. The only evidence is an audible glitch/dropout and the audio engine errors in the logs. If you were recording, you'd also get a glitch in the recording as well....which is where the real headache lies. When I had the fan control installed, the issue manifested as everything from micro dropouts, to full scale stuttering and ring mod sounding jitter. Without the fan control, its basically just microdropouts/glitches as the audio engine gets reset. The frequency depends on a bunch of factors. For me its about every couple of hours if I turn off time syncing. With it on, its about every 15-30 minutes. With wifi and other networks turned off, the problem goes away (at least it appears to). I have iCloud, bluetooth, time syncing and wifi turned off if I'm doing serious audio work. However!, the frequency and extent of the dropouts seems to vary from machine to machine (as you can see on the various threads all over the place - macrumors, etc). I'm also lucky in that I have only had one kernel panic where others have multiple KPs per day.

I think I'm probably the user that was running the fan control. That made the dropouts a *lot* worse, but removing it didn't fix things. Like many others it seems like my issues (which still occur) are down to the way that the T2 chip handles time syncing via timed and other processes that... for whatever reason... interrupt the USB audio stream. Disabling time syncing and other services that rely on it (like iCloud stuff) ameliorates the issue, but is not a real, permanent solution. The jury is still out on whether this is a hardware flaw or a software flaw or some combination of both. PS. For those of you with the option, it seems like the last two security updates for 10.13.6 made the audio issue more likely to occur, so I've not installed those. For those with minis....I think those are Mojave only so the above doesn't apply.