Hi,
Found a pretty strange bug on Cubase 13 that I’ve not come across in previous versions on Mac OS 14.2.1 Sonoma on an M2 Max Macbook Pro.
While a Cubase project is opened from an external drive, it will not be possible to write to that drive either within cubase (importing new files to the audio pool or bouncing audio regions as new files) or using Mac OS because the drive is reported as having zero space free.
The bug is simple to replicate:
Project files are stored on an external SSD drive formatted to FAT32
Open a project that is stored on that drive
As soon as the project is loaded, the system reports zero bytes available on the drive. So I can’t bounce files down, can’t import files to the audio pool folder, can’t even copy files to that drive outside of Cubase using the finder.
Close project, the free space that was reported before opening on cubase is available again.
I’ve attached screenshots of the same drive before opening the project file in Cubase.
Sometime times Mac OS doesn’t recognise the free space again, and this is fixed by running a First Aid repair in the Disk Utility but does not seem to work while the project is active. I’m not sure if this is a FAT32 thing, but I’ve formatted this drive FAT32 as it floats between different systems with different Operating Systems and FAT32 offers maximum compatibility.
I’ve had Cubase 12 installed on this mac book pro and didn’t have this issue before, it’s something that popped up on Cubase 13.