OBS Recordings "freezing" midway through the recording session with no apparent crashes.

[DualBlades]

Pretty much exactly as the title says, for some reason my OBS recordings are recording for the full length, but "stopping" midway through. For example, I recorded a near two-hour long game earlier, and only about the first hour and twenty minutes actually recorded. After that point, the recording shows a single frame for the remainder of the duration, and the audio stops as well, but the recording itself still lasts through until I chose to end it. I've tried getting help on this issue before, but nothing seems to fix it. It always happens about an hour and some change in as well.
Any help is greatly appreciated, I can include a video showing exactly how the recording looks on my end, and will include the log file that has the session is occured in (the first recording session), and then two subsequent ones in which the recordings did not freeze.
Thank you!

 

[DualBlades]

- YouTube

Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

www.youtube.com

Here is an instance of how it looks from the previous time I tried to receive help. I am currently working on uploading the instance from today, and will include it when it is finished.

 

[koala]

Unfortunately, it's not possible to see anything about encoder settings and lost frame statistics in your log, because you use custom ffmpeg output, and ffmpeg output logs almost nothing. A common issue for a recorded video containing no further footage beyond some point in time is severe encoder overload. The issue may be related to improper custom ffmpeg settings. Use simple output mode instead.

 

[DualBlades]

These are the settings as they are currently, haven't touched them yet. It looks like it's already on simple, unless you mean a different section. I don't know OBS well enough to know if this is the right place to look to change that.

Unfortunately, it's not possible to see anything about encoder settings and lost frame statistics in your log, because you use custom ffmpeg output, and ffmpeg output logs almost nothing. A common issue for a recorded video containing no further footage beyond some point in time is severe encoder overload. The issue may be related to improper custom ffmpeg settings. Use simple output mode instead.

 

[PaiSand]

Please run the Auto-configuration Wizard (tools menu) and apply the settings it suggest, then restart OBS (yes, restart it)
Do not change the settings.
Now please perform a test stream/recording for more than 30 seconds doing as you normally do, including playing games, full camera or whatever you normally do.
Look inside Help menu. Upload the current log file and paste the url to the log in here. Click on the Analize button to start troubleshooting common issues.

Now you can try another quality setting from the presets. Repeat.
Check the videos if they are fine or have an issue. Upload the log file of the video with issues.

 

[DualBlades]

Please run the Auto-configuration Wizard (tools menu) and apply the settings it suggest, then restart OBS (yes, restart it)
Do not change the settings.
Now please perform a test stream/recording for more than 30 seconds doing as you normally do, including playing games, full camera or whatever you normally do.
Look inside Help menu. Upload the current log file and paste the url to the log in here. Click on the Analize button to start troubleshooting common issues.

Now you can try another quality setting from the presets. Repeat.
Check the videos if they are fine or have an issue. Upload the log file of the video with issues.

Alright, I did that. The only issue it seems to have is the file type output from the recordings.

https://obsproject.com/logs/h6-CnfhUQTRM1DdN

Unfortunately, the issue doesn't happen every time I record, probably once every ten or so recordings, and only on ones exceeding about 1.5 hours in length, so it's not really replicable when I want it to be. The best I could do is wait for it to occur again, but I'm trying to avoid losing footage any more than I have to, so that isn't a super preferred option if there is any more troubleshooting that could be done in the interim.

 

[rockbottom]

Does the drive you were attempting to record Lossless to still have sufficient free space after recording for 90 minutes? Does it start to overheat?
Does it have DRAM or is it DRAMless? If there's no DRAM on board, that could be causing the issue you are experiencing as the drive is no longer able to sustain the required write speed.

 

[DualBlades]

Does the drive you were attempting to record Lossless to still have sufficient free space after recording for 90 minutes? Does it start to overheat?
Does it have DRAM or is it DRAMless? If there's no DRAM on board, that could be causing the issue you are experiencing as the drive is no longer able to sustain the required write speed.

Currently it writes to a 2TB SSD M.2, with somewhere between 1-2GB of DRAM. There's about 1TB on there at any given time, and the most space I've ever had a recording use up is about 500GB, so I don't think it's running out of space, unless it's creating more during its recording process and condensing it afterward. It shouldn't be overheating either (at least not as far as I'm aware) since some of the games I play run off that drive, and they don't have any noticeable issues performance-wise or anything of the sort. That said, I'm not very tech-savvy, so I could be entirely wrong.

 

[rockbottom]

What model is it? Samsung markets several drives as having DRAM when that is not the case, they have flash.

 

[rockbottom]

Pro models all have DRAM

 

[DualBlades]

Pro models all have DRAM

970 EVO Plus NVMe® M.2 SSD 2TB​

 

[rockbottom]

It's DRAMless but maintains decent performance. Your drive is bigger & will perform better but you can see where the sustained write performance drops on the 500GB model when the SLC Cache is spent. If you have another NVMe that is not doing anything, try writing to it.

How about OBS v27, did you have trouble with it?

 

[DualBlades]

It's DRAMless but maintains decent performance. Your drive is bigger & will perform better but you can see where the sustained write performance drops on the 500GB model when the SLC Cache is spent. If you have another NVMe that is not doing anything, try writing to it.

How about OBS v27, did you have trouble with it?

The only other drives on the PC are a SATA 3 2TB Drive (wdc wd2003fzex-00srla0) and a 500GB (Crucial MX500 500GB 3D NAND SATA 2.5-inch 7mm (with 9.5mm adapter)) Internal SSD. I used to do all the recording onto the second 2TB drive before getting this new one.
I've been having this issue for a while now (though coincidentally, I can't remember if it happened before getting the new M.2 or not), probably within the last 8 or 9 months, give or take. Maybe even longer than that. Not sure what OBS version it started in, but it's been persistent through all the different updates.

 

[rockbottom]

MX-500 is too small for long recordings. The other looks like a WD Black? Maybe, if empty.

Do you still have the 2TB laying around or was it DOA?

Best to record, especially lossless, to a dedicated drive.

 

[DualBlades]

Do you still have the 2TB laying around or was it DOA?

You mean the EVO Plus or the WD Black? They're both still in, but the WD is nearly full. I use it as the primary storage for the system.
I was considering looking into a new dedicated drive for recordings a few months ago, as I'm starting to run out of space on the computer and files are beginning to encroach onto the current "dedicated" recording hard drive. Not sure what would be the best option though for that, given the size of the output files.
This was the current top pick if I were to get one: https://www.amazon.com/SAMSUNG-Internal-Gaming-MZ-V8P2T0B-AM/dp/B09JHKSNNG?th=1

 

[rockbottom]

Gotcha, you were recording to the Black before installing the 970. I thought you may have removed a 2TB that could have been placed back in service.

The 980 Pro is fine, I have 3 of them in my system. No complaints.

 

[werejiggy]

Pretty much exactly as the title says, for some reason my OBS recordings are recording for the full length, but "stopping" midway through. For example, I recorded a near two-hour long game earlier, and only about the first hour and twenty minutes actually recorded. After that point, the recording shows a single frame for the remainder of the duration, and the audio stops as well, but the recording itself still lasts through until I chose to end it. I've tried getting help on this issue before, but nothing seems to fix it. It always happens about an hour and some change in as well.
Any help is greatly appreciated, I can include a video showing exactly how the recording looks on my end, and will include the log file that has the session is occured in (the first recording session), and then two subsequent ones in which the recordings did not freeze.
Thank you!

Did you ever figure this out?
I have 3 totally different systems that started doing this.
Using Mkv.
It was fine previously and started doing it the other day on all 3 and i changed nothing.

 

[werejiggy]

@DualBlades
One more question for you, was your system sitting at a lock screen?
That is the only thing at all that I changed was instead of just leaving them (power mode set to always on) logged in and wide open was using the lock screen.
However I just checked the 3 I set last night again, one definitely screwed up again, one did not mess up and recorded the full 4 hours it was set to, I'm starting to wonder if maybe it's just the particular site I'm using, I did notice once I think yesterday that it froze and I had to refresh while the system was fully on anyway.

Were you using browser as your source? And was whatever you were recording did the feed change at all? I'm starting to think it's the way the site feeds in. Some sites I had no issues at all with but the browser source I'm currently using is different and I'm starting to think that may be the actual issue somehow when the camera feed from the site changes sometimes.

 

[werejiggy]

Still haven't figured this out. Seems to be the browser source might be the issue and I can't figure out any rhyme or reason to why it freezes after a while.