Hello,
I am running a 2012 Mac Mini with Mavericks and I recently encountered a weird issue, and I honestly can't quite tell if this is more of an an issue with MacOS or MuLab. Figured I would post it here just in case. I can remove this post if necessary.
MacOS is my preferred environment for MuLab, though I have not tested this problem on Windows yet.
So here's my situation: I have noticed that M7 suddenly stopped saving a project file even though I've had this set up and was working just fine for quite some time. I just thought it might have been a weird glitch, but not only is the file itself, though IS openable, MuLab cannot save after making changes. Most of the time, it does not capture waveforms when recording, and it doesn't even save changes to instrument presets. I know because I am also fighting MuLab for failing to open most of my drum sounds despite the fact that I have never moved the files since that was set up in this system, plus it seems to be randomly choosing to NOT load specific sounds.
I double checked, and not only are all of my project files locally stored on this machine, but they're also on the desktop with the MuLab folder. There should be no write permission issue as far as I am aware, and yes, I am the owner of this Mac and there are no other users. Also, the drive is in good health and is an SSD I bought new about 7 months ago, with 70 GB free.
Initially, I thought it also may have just been an issue with M7, but I recently got M9 and I am still seeing the same behavior despite the fact that I just upgraded MuLab. Same Mac, same OS, same everything except I'm using M9. Yes, the project files were upgraded with M8 first.
Has anyone heard of things like this to systems that shouldn't have writing issues? Was there possibly something that I did that broke something? Is this file recoverable in any way? This is a song that I am currently working on and am quite proud of so far and I really don't want to lose all of that work
Multiple MuLab Versions Struggling to Save on Mac
-
- KVRer
- 22 posts since 13 May, 2018
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Have you checked all disks? Checked them all for disk health as well as space? I'm not a macOS user but it really does sound like it's having problems finding "good" disk space.CobaltHeart wrote: Thu Nov 03, 2022 12:28 amAlso, the drive is in good health and is an SSD I bought new about 7 months ago, with 70 GB free.
-
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- Beware the Quoth
- 35439 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Well, it might be time to create one, as a test account, to see if this is specific to your account or home directory...CobaltHeart wrote: Thu Nov 03, 2022 12:28 am There should be no write permission issue as far as I am aware, and yes, I am the owner of this Mac and there are no other users.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
- KVRer
- Topic Starter
- 22 posts since 13 May, 2018
Yeah, I think you're right. I tested this out with a new account and MuLab did not struggle with saving anything. The SMART data on the SSD looks alright, so I think there's just something weird with my main account despite the fact that MuLab is the only program affected by this. I am fairly knowledgable with computers but I am still fairly new with MacOS. I'm sure I'll be able to figure it outwhyterabbyt wrote: Thu Nov 03, 2022 9:53 amWell, it might be time to create one, as a test account, to see if this is specific to your account or home directory...CobaltHeart wrote: Thu Nov 03, 2022 12:28 am There should be no write permission issue as far as I am aware, and yes, I am the owner of this Mac and there are no other users.