Welp, spoke too soon. The issue is persisting even though have a completely new copy! Fak!!!
I did some recording with analog audio and the cannot save/open file bug started again. This time, I noticed that MuLab was unable to see any volumes that it could save to, making it so the entire volume structure of the Mac straight up not show up. It showed the top "Volumes" option, and when I clicked on that, nothing popped up below it, as if "Volumes" was an empty folder (which is obviously wrong). It's worth noting that I haven't noticed any read/write issues with the rest of the system, though MuLab is practically the only program that I use on this Mac that heavily writes data.
I tend to record in small chunks, so I don't believe this is a file size error.
I have not tested with a fully new song yet, as it can take me a long time to get to the point that this song is at and has started failing. I also don't want to sink that much time into a project if I know that those files are going to be unusable anyway.
This does not look like a permissions issue, as for a while the program can save normally, and everything was contained in a folder on the desktop. Everything therefore was saved on the internal SSD of the system.
The really funny thing is that like 95% of the time when this save glitch happens, its right when I pull of a good recording session with my bass. I don't believe the bass itself is the problem, as I record my guitar with the same Scarlett Solo that I also have been recording my guitar into since I got this Mac. I have only noticed this issue with a couple of my recent projects made with MuLab 9. I have produced several albums with MuLab, most of my semi-early stuff and two official albums with M7, and an EP with M9 starting in late 2022. I have only ever seen these specific issues after that EP released in 2023, and so far only with a couple of unfinished projects.
I do have GTune, which doesn't seem to have perfect compatibility with MuLab for some reason, but it is not being used in the projects with this issue.
At some point in the future, I could see if M7 does this as well, but again, I don't want to sink that much time into a project if I know that those files are going to be unusable anyway.
At this point, there could be a handful of possibilities, in order from decreasing likelihood
- Those projects, for whatever reason, are just ruined
- There's something wrong with my saved Racks and/or modified MuLab instruments (some of which were from M7)
- MuLab doesn't like being limited to 4 GB of RAM (which I didn't initially think could be a problem but I guess it's possible)
- There's something wrong with my MacOS install in general that MuLab doesn't like
- MuLab 9, for some reason, doesn't like MacOS 10.14
I did some recording with analog audio and the cannot save/open file bug started again. This time, I noticed that MuLab was unable to see any volumes that it could save to, making it so the entire volume structure of the Mac straight up not show up. It showed the top "Volumes" option, and when I clicked on that, nothing popped up below it, as if "Volumes" was an empty folder (which is obviously wrong). It's worth noting that I haven't noticed any read/write issues with the rest of the system, though MuLab is practically the only program that I use on this Mac that heavily writes data.
I tend to record in small chunks, so I don't believe this is a file size error.
I have not tested with a fully new song yet, as it can take me a long time to get to the point that this song is at and has started failing. I also don't want to sink that much time into a project if I know that those files are going to be unusable anyway.
This does not look like a permissions issue, as for a while the program can save normally, and everything was contained in a folder on the desktop. Everything therefore was saved on the internal SSD of the system.
The really funny thing is that like 95% of the time when this save glitch happens, its right when I pull of a good recording session with my bass. I don't believe the bass itself is the problem, as I record my guitar with the same Scarlett Solo that I also have been recording my guitar into since I got this Mac. I have only noticed this issue with a couple of my recent projects made with MuLab 9. I have produced several albums with MuLab, most of my semi-early stuff and two official albums with M7, and an EP with M9 starting in late 2022. I have only ever seen these specific issues after that EP released in 2023, and so far only with a couple of unfinished projects.
I do have GTune, which doesn't seem to have perfect compatibility with MuLab for some reason, but it is not being used in the projects with this issue.
At some point in the future, I could see if M7 does this as well, but again, I don't want to sink that much time into a project if I know that those files are going to be unusable anyway.
At this point, there could be a handful of possibilities, in order from decreasing likelihood
- Those projects, for whatever reason, are just ruined
- There's something wrong with my saved Racks and/or modified MuLab instruments (some of which were from M7)
- MuLab doesn't like being limited to 4 GB of RAM (which I didn't initially think could be a problem but I guess it's possible)
- There's something wrong with my MacOS install in general that MuLab doesn't like
- MuLab 9, for some reason, doesn't like MacOS 10.14
Statistics: Posted by CobaltHeart — Fri Feb 16, 2024 4:45 am