MOTUnation.com

mikehalloran wrote: ↑Fri Jun 09, 2023 4:23 pm

bayswater wrote: ↑Fri May 05, 2023 8:07 am …
Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

I finally have an answer.
——
I have not tried a System Restore but I now know that it can be done.

Thanks Mike. That’s pretty much the setup I want, but using 12.6 for newer apps (still too much that won’t run on Venture) and keeping 10.14 going for older apps I have to keep using. At this point, only the Mojave startup uses TimeMachine and I manually copy any documents to the backup drive.

The next puzzle is what happens if I tell the 12.6 partition to use my 8T spinner backup drive for TM. My understanding is that 12.6, unlike 10.14 will not give the option to leave the backup drive as HFS and will force it to APS. From what I’ve read, this drive will not perform well if formatted as APS.

bayswater wrote: ↑Sat Jun 10, 2023 8:35 am

mikehalloran wrote: ↑Fri Jun 09, 2023 4:23 pm

bayswater wrote: ↑Fri May 05, 2023 8:07 am …
Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

I finally have an answer.
——
I have not tried a System Restore but I now know that it can be done.

Thanks Mike. That’s pretty much the setup I want, but using 12.6 for newer apps (still too much that won’t run on Venture) and keeping 10.14 going for older apps I have to keep using. At this point, only the Mojave startup uses TimeMachine and I manually copy any documents to the backup drive.

The next puzzle is what happens if I tell the 12.6 partition to use my 8T spinner backup drive for TM. My understanding is that 12.6, unlike 10.14 will not give the option to leave the backup drive as HFS and will force it to APS. From what I’ve read, this drive will not perform well if formatted as APS.

TM drives since Monterey are APFS. Apple recommends HDDs and I'm have no problem with any of mine ranging from 6–14TB.

I'm lousy with 2012 MBPs around here at the moment. Mine is running Catalina and one of the ones I'm working on is over Monterey — both are backed up to one of my drives. The one running Monterey only uses half of the 128GB drive I installed so I did a full System Restore (not APFS Snapshot) just to test this — worked great. This MBP is one of the ones I'm incorporating into the newer one running Ventura.

After I get my new AS Mac, I'll probably reformat the 2T SSD in my MBP to Mojave for the rare occasions I need to use Encore. I am not going to keep my iMac Pro for that one use and have lost confidence that Don Williams's planned upgrade to Encore 6 will ever happen.

I just set a new 4Tb HD for Time Machine and boot drive clone.
This new HD is APFS for both volumes.
The previous was APFS for TM only (the boot drive clone was not).
Now, when DP is running, no more “File not found (-43)“ when TM is backing up.
Back to work!

daniel.sneed wrote: ↑Thu Jun 22, 2023 2:04 pm I just set a new 4Tb HD for Time Machine and boot drive clone.
This new HD is APFS for both volumes.
The previous was APFS for TM only (the boot drive clone was not).
Now, when DP is running, no more “File not found (-43)“ when TM is backing up.
Back to work!

None of that explains why I was getting it since everything has been APFS since Monterey. OTOH, it was a much bigger issue for me in DP 10 and it’s been a few months since I’ve seen it in DP 11.

FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

Rick Cornish wrote: ↑Wed Jul 26, 2023 2:00 pm FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

Did you check the box Copy Audio? If so, it should have cautioned you that it would overwrite when you navigated back to the Project directory. Click Yes and it will overwrite and you will not lose any work.

AutoSave is the culprit—I have been able to demonstrate this to MOTU who told me that it was Time Machine based on your comments. If that was true, it would affect everyone but it doesn't.

Unfortunately, now that I have Activity Monitor on whenever DP is running, I've not experienced this again. I have no doubt it's a conflict. I'd love to find out with what but it has to act up when I'm looking.

mikehalloran wrote: ↑Wed Jul 26, 2023 3:08 pm

Rick Cornish wrote: ↑Wed Jul 26, 2023 2:00 pm FWIW: Since this original post, I have turned off automatic Time Machine backups on my studio Mac and have gotten in the habit of starting a TM backup after I finish for the day.

The other day, I started a TM backup and then re-opened a DP project to check something… same behavior: when I went to save (and NOT "Save As…) it would not save in the original project. The only way to save my work was to create a new DP project.

So, in my experience, this is still an issue.

Did you check the box Copy Audio? If so, it should have cautioned you that it would overwrite when you navigated back to the Project directory. Click Yes and it will overwrite and you will not lose any work.

AutoSave is the culprit—I have been able to demonstrate this to MOTU who told me that it was Time Machine based on your comments. If that was true, it would affect everyone but it doesn't.

Unfortunately, now that I have Activity Monitor on whenever DP is running, I've not experienced this again. I have no doubt it's a conflict. I'd love to find out with what but it has to act up when I'm looking.

Thanks, Mike. Interesting to know that I'm now famous with MOTU tech support!

I'm too nervous about losing a track to overwrite a project that way. For now, I'm OK with limping along the way I've been doing it. Hopefully, it'll get fixed somewhere along the line one way or the other (like when I migrate to an AS machine).

Happened a lot this weekend, multiple times a complete freeze requiring force quit, wouldn't save. Occasionally it went away and I could continue.

Every time I had a look and it was always at the end of an automatic time machine backup. TM is a USB3 Samsung T7 APFS volume. Maybe not related, but.....

ALSO - my working audio project folder is EXCLUDED from TM backups, and is on the internal Studio drive.

Corresponding PITA: autosave has been intermittent for me in dp11. It's semi-random, and sometimes it just stops saving altogether. I've got it set for 1 minute, and if I toggle it on/off it'll do 1 minute again for a short while.

2 months later, still doing manual TM backups, not one (-43) since.

FWIW: I just wanted to post that this issue—which had led me to do manual Time Machine backups on my Intel system—has not appeared since migrating to DP11.3 on Sonoma on my new Mac Studio.

EDIT:
OK—hold on, this may be back.

Sorry to resurrect an old thread.

I had this File Not Found (-43) error pretty much continuously for almost a year on my 2019 Intel Mac Pro. It put a pretty big dent into my workflow constantly having to shut sessions down.

I know there was some debate on here about whether this error is Time Machine related, but after following some of the advice in this thread and going to manual Time Machine backups, I have completely stopped having this error. I do a manual Time Machine backup every night and I also have Backblaze continuously doing cloud backups throughout the day, and everything has been working perfectly for a few weeks. In an ideal world it would be nice to just keep Time Machine running automatically and not have to do it manually but I'd say from my own experience it's worth trying manual backups if you have this error.

It has nothing to do with Time Machine. Period. MOTU was telling people that after reading it here.

It is a DP 10 bug that affects Save (may have first shown up in DP 9). The actual bug was posted last year but not in this thread and I didn't copy it over for reference. When it appears randomly, it's when Autosave is enabled.

The workaround I posted of navigating to your project folder and letting it overwrite works 100% of the time. When I have walked people through it who said it didn't work, it worked.

You may see it in DP 11 if you open a DP 10 file. If you did any work, navigate to the project folder and overwrite. If you haven't done any work yet, Quit, reopen and immediately Save as DP11—you will be prompted to do so on your first Save. I now Save every old project immediately on opening as DP11 and have not seen it since.

If you have not upgraded to DP 11, do so. It fixed a number of unresolved bugs. 11.34 released last week fixed even more including some that go back to DP 7.2x.

There's no debate here - it's Time Machine related. Sorry Mike, it is! If there's a bug that conflicts with time machine, someone please point it out!

I never had DP10, went from 8 to 11. Haven't had the problem since going to manual backups. I can turn on automatic backups and get it within the hour. Been that way for several years now.

Autosaves has been broken for awhile, but I can't say I've turned it off either. Any time I have a crash, I usually find that autosave stopped writing anything new, so it's been kinda worthless since dp11. It'll write a few at the allotted time interval, then the interval gets more random and doesn't follow the dictated timing, then it stops writing new entries.

EMRR wrote: ↑Wed Mar 05, 2025 11:48 am There's no debate here - it's Time Machine related. Sorry Mike, it is! Haven't had the problem since going to manual backups. I can turn on automatic backups and get it within the hour. Been that way for several years now.

Nope. I was getting it without TM on—as I reported to MOTU when they tried to convince me otherwise. Apple Engineering could not find a connection when I sent traces to them, either.

In DP 11, I have only seen it on older projects that I did not Save as DP 11 immediately. The actual bug was reported here but I don't have time to try and find it today.

mikehalloran wrote: ↑Wed Mar 05, 2025 11:56 am

EMRR wrote: ↑Wed Mar 05, 2025 11:48 am There's no debate here - it's Time Machine related. Sorry Mike, it is! Haven't had the problem since going to manual backups. I can turn on automatic backups and get it within the hour. Been that way for several years now.

Nope. I was getting it without TM on—as I reported to MOTU when they tried to convince me otherwise. Apple Engineering could not find a connection when I sent traces to them, either.

In DP 11, I have only seen it on older projects that I did not Save as DP 11 immediately. The actual bug was reported here but I don't have time to try and find it today.

I built all new templates from scratch in DP11 when I got it. Still happens. You say it showed up in 9 or 10, I never had those. When I open anything older it gets saved as a new version under 11 immediately. Still happens. DP11 came in with new computers here - clean installs, no reinstalls from TM or anywhere else.

I have never seen it once with TM set to manual.