unfa
Member
Hi!
I have a weird problem, that creeped up before, but now it really became annoying.
For one profile I use OBS says I don't have enough disk space to capture, no matter what Output path I specify.
But on a different profile - that uses the same Output path capture works without issues.
I've also seen that before OBS constantly shown that I have 0 minutes of disk space remaining, even though the disk has 20 GB of free space. Same thing happens if there's 120 GB of free disk space.
I'm using Btrfs on Manjaro Linux, so maybe OBS is having trouble determing the free disk space, though this seems like a bug because it only affects one profile.
I'll try to make a new profile from scratch, but I'm using 444 H.264 encoding and multitrack uncompressed audio - so it's a bit tricky to configure.
And I don't want to have to do this over again if OBS starts having issues again.
have anyone experienced such behavior?
I have a weird problem, that creeped up before, but now it really became annoying.
For one profile I use OBS says I don't have enough disk space to capture, no matter what Output path I specify.
But on a different profile - that uses the same Output path capture works without issues.
I've also seen that before OBS constantly shown that I have 0 minutes of disk space remaining, even though the disk has 20 GB of free space. Same thing happens if there's 120 GB of free disk space.
I'm using Btrfs on Manjaro Linux, so maybe OBS is having trouble determing the free disk space, though this seems like a bug because it only affects one profile.
I'll try to make a new profile from scratch, but I'm using 444 H.264 encoding and multitrack uncompressed audio - so it's a bit tricky to configure.
And I don't want to have to do this over again if OBS starts having issues again.
have anyone experienced such behavior?
