Did they finally fix the bug where if you have less than ~40gb storage the recording will just randomly die for no reason with no notice, it is unimaginably annoying
Further, it's an inexplicable issue with the API; any consumer of SCK is vulnerable to the issue. I'd regard it as Apple's issue to fix, since there is no good reason for frames to randomly stop streaming just because you have less than ~40 GB of disk space free.
Any solution on the OBS side that tried to detect a frozen stream and restart it would not only be a hack and quite possibly lead to greater issues, but could also have privacy implications if we cannot positively identify that the stream was not stopped intentionally (which we cannot).
- have reasonably low storage
- start recording
- couple seconds or minutes later the video on the preview gets frozen and stops being recorded, while audio continues; recording status unchanged
- the freeze usually happens in the moment of switching between apps, allthough this isn't required at all
yes maintainers do it for free for years which deserves recognition but this exact issue existed for years and has been reported in many ways, without any change, and no other apps have ever behaved this way on my devices
My personal MacBook had 8GB of free storage (4.2GB after my test recording). I experience issues with programs like xcode failing to compile or crashes when I open too many files, pages hasn't been able to save a file since the machine had 15GB+ free.
I just download, installed, and recorded 10 minutes of desktop footage with a webcam overlay and audio. Nothing unexpected happened. I watched all 9 minutes and 28 seconds of it and it looks and sounds exactly as I would expect.
I spent my time doing this and writing this comment not to belittle you or your experience, though at this point I would ask you what do you expect to happen?
You did not post an existing bug report, or write one yourself. You've provided no evidence that anyone who contributes meaningfully to the project has experienced or even heard about this issue, let alone anyone who operates the project or consumes it from macos has any notion it is an issue.
Again, I believe this is a real issue. But there is no information here to go off of, especially with my experience, that points to anyway to meaningfully improve an OSS project in regards to your experience. If nobody with the requisite experience is asking the right questions, this will not get fixed. It starts with those people having any information to start with.
The most my homedir has ever grown in one year is 3.2 GB, and I don't really go out of my way to keep things tidy. I'd be very pissed off if things started pestering me to clear stuff up years before it actually became a problem.
lol! This comment made my night. In short: low available disk space, lots of projects requiring disk space.
No I don't see OS notifications about low disk space (at least on my macbook), some 3rd party applications give me notifications about low disk space though. I can confirm that all of my USB-C ports work! I have 2 local drives and a remote NAS that backup all the 'critical' data from my machine.
Unlike other operating systems I've had experience with, macOS is the most capable of operating in a (near) 'disk full' state. Where something like Windows will go from crying about the available disk space, to failing opening explorer, macOS will continue running just fine for general usage.
> Wonder what other aspects of your life you choose to live so dangerously close to the edge as well?
As for this: I've spent the last year living in India, where most people I've met think they are invincible, so I roll the dice every day!
I used to get the OS out of space warning a lot from macOS. I used to have a 128GB SSD, and Adobe would fill up the drive with cache in the Application Support folder frequently. My newer MBP has a larger SSD, but I also manage the storage much closer now.
This experience I have of low disk space is only on Sequoia which I haven't seen give an OS notification until 5gb left, which again doesn't happen often.
Over the following year, roughly 20 releases later, my disk was full. Xcode generates a ton of hidden cruft in the DerivedData folder during every build/release that I wasn't even aware of! I spent a couple days googling and trying free & paid disk space analyzers (sidenote: I didn't realize how good we have it in Windows-land, there are so many good free tools but in Apple-land they are all so frustrating to use and most of them are totally useless for this particular case). Eventually, I found an Apple forum thread explaining where Xcode hides its generated build data, it was like 8GB of stuff per build! I set a calendar reminder for every 12 months to clean this folder.
I can't move anything else to an external drive really because what's left is necessary for build environment. I don't use the Mac for anything except development, so I've literally removed everything and it's down to barebones but it's still a struggle. If I had known I would have invested another $150 for the 512GB version.
We need the money.