Question / Help OBS Not letting me record for "not sufficient disk space" despite space free

[stoigeboiii]

I keep getting the message "There is not sufficient disk space to continue recording" despite the fact that I have 4.29TB free on the hard drive I am trying to record to. Even have 334gb free on my local C disk. So now I'm wondering why this is happening. I've tried switching where it records to a different external drive and it still isn't working. I'm not sure why it's doing this. Only started happening when I updated OBS.

 

[Banyarola]

Make sure the path is correct in SETTINGS/RECORDINGS/RECORDING PATH

 

[RunawayRobot]

I'm having the same issue, plenty of space in the drive listed in the path. Triple checked/updated the path and still getting the same issue.

 

[Aika]

Hello, same issue here, tried on 2 differents disks with more than 900 gigs...
But ! The live is working..

 

[R1CH]

Does it work correctly if you launch OBS as administrator?

 

[Aika]

It's already starting as Admin... :/

 

[dinglesworld]

I'm experiencing the same problem. I have 140G free on the drive I'm saving my stream locally on. I have admin privileges, the path is correct, and I've reinstalled OBS. This issue only started happening after I was prompted to upgrade to the newest version. Could this be a known issue with the latest release? Come on devs, someone has to have cracked this nut!

 

[R1CH]

Are you sure the recording path is valid, the folder exists and is writable by your user account? Unfortunately the disk space check got moved before the path check, so an invalid path will show the disk space error instead.

 

[Aika]

Everything is ok...
Something must cause it to always make it false..

 

[flayou senpai]

go to settings, output (make sure that the output mode is simple)
select the recording path again and hit apply, it won't work unless you do it in the simple mode :D

 

[R1CH]

There is a known bug where if you use FFmpeg custom output, the regular output path is checked instead. Turn off the custom output, set a valid path, then go back to custom.

 

[Aika]

There is a known bug where if you use FFmpeg custom output, the regular output path is checked instead. Turn off the custom output, set a valid path, then go back to custom.

Perfect, it did the trick !
Thanks

 

[RunawayRobot]

This worked for me as well, thank you!

 

[Datboiiii]

There is a known bug where if you use FFmpeg custom output, the regular output path is checked instead. Turn off the custom output, set a valid path, then go back to custom.

DID NOT WORK FOR ME :(

 

[Zero0Core]

I keep getting the message "There is not sufficient disk space to continue recording" despite the fact that I have 4.29TB free on the hard drive I am trying to record to. Even have 334gb free on my local C disk. So now I'm wondering why this is happening. I've tried switching where it records to a different external drive and it still isn't working. I'm not sure why it's doing this. Only started happening when I updated OBS.

So I figured this out the hard way OBS uses / for path not \ unlike windows and if you switch the \ to / in the path assuming you copied the path or wrote it yourself it should work just fine. Also you can not tell it to save to a path that does not exist, so if you set it to D:/Videos/Recordings but there is no such directory it will give you that error. In my case I had both problems first I had not created the Directory I was trying to send it to and then on top of that since I manually typed in the Path I had used \ instead of / so it looked like this D:/Videos\Recordings Which the software could not understand even after I created the Folders.

 

[Drumseltzer]

I've got a seemingly different problem entirely on my mac.
I can't even change the path, even thogh I've got an empty 2TB hardrive connected and over 200gb free on my internal HD. Any ideas? Also, I don't know if this is related, but my camera connectd with NDI isn't showing on screen either.

 

[R1CH]

Most settings can't be changed if an output is active, such as NDI output, virtual camera, recording, streaming, etc.

 

[SaygetheSavage]

I keep getting the message "There is not sufficient disk space to continue recording" despite the fact that I have 4.29TB free on the hard drive I am trying to record to. Even have 334gb free on my local C disk. So now I'm wondering why this is happening. I've tried switching where it records to a different external drive and it still isn't working. I'm not sure why it's doing this. Only started happening when I updated OBS.

I hope I’m not too late and I hope this fixes it for someone else. I spent entirely too much flipping settings on and off and attempting to record a full video as I have a 32GB USB. I got the error with more than enough space. Here is what I did

Go to SETTINGS>OUTPUT>RECORDING>ENCODER and then change what you have. For example I had NVIDIA NVENC H.264 set and it was just a bit too much for my pc so I went the next best down which was NVIDIA NVENC HEVC. Keep in mind these NVIDIA options I believe are only for pc’s with NVIDIA cards I only used this as an example as I have a NVIDIA card. If you aren’t sure what your pc can run cause there are many options to choose from I recommend a YouTube search on OBS settings for a lower quality pc, never the less it will still run well :) I hope I saved someone some time I really hope this works for you and don’t forget to apply your setting when you select the one you want.

 

[hokeson]

Hi, is there a way how to show how much free space there is and how much minutes can be recorded? it is better to know in advance then while recording to get a message there is no more space. thx

 

[sashamoth]

I'm not sure if this is of any help, but I've gotten this issue myself twice now, and me not being tech savvy enough I just started deleting recordings from my OBS recordings file thinking it would do the trick. Sometimes when I save a replay, it isn't able to be opened or viewed at all, but it still appears in the same file as other recordings that are just fine. Each time I've gotten this issue, (and I tried everything else) it only went away after I deleted the corrupted recording both from the OBS recordings file and the recycle bin. Only then was I able to turn on the replay buffer again. Hope this is of help.