Question / Help suddenly, every recording corrupts

[thinkpink]

I've been recording numerous files lately, all in .mov container. I have not experienced any issues whatsoever... until today. Suddenly, every attempt at recording video captures ends in a corrupted file. The files are somewhat usable, but especially towards the beginning and end of the file (typical encoding problem symptom), the file is unreadable.

Here's everything I have checked:

• the log file shows nothing wrong, at all; no anomalies show up (please don't ask to see my log file, it's fine)
• this is not related to HDD/SSD problems; I have numerous drives, and the issue repeats on every drive (tested on 5 drives)
• the problem persists despite which hardware/software encoder is used

Any ideas?

 

[Harold]

(please don't ask to see my log file, it's fine)

I guess you don't actually want help then. Log files may seem fine to you, but they may still provide useful info.

 

[Fenrir]

Without a log file, it will be impossible for us to tell what could be going on. If you are concerned about any personal information, the logs are completely anonymous and only contain system hardware specifications. Source and scene names will also show up, but if you are concerned about posting publicly, feel free to send me a PM with the link so it can be examined.

 

[thinkpink]

Unfortunately, the log file told me nothing differently than it ever had, so the answers were not there. This was the reason I said there were no anomalies. If I were to trust the log file, everything should have been running the same as before the issue.

Apparently, the culprit is directly related to overclocking my system components. If the overclocks are removed for the 2 hardware encoders (Quick Sync & normal GPU), the encoding works flawlessly. Return the overclocks to their previous settings, and the encoding once again fails to properly timecode.

I'll return to my previous installation of OBS for now, as there were no problems before 19.0.2.

 

[Harold]

That's all well and good, but we still need to see the logs in order to be able to troubleshoot properly

 

[Osiris]

Just post the logfile!

 

[Fenrir]

Unfortunately, the log file told me nothing differently than it ever had, so the answers were not there. This was the reason I said there were no anomalies. If I were to trust the log file, everything should have been running the same as before the issue.

Apparently, the culprit is directly related to overclocking my system components. If the overclocks are removed for the 2 hardware encoders (Quick Sync & normal GPU), the encoding works flawlessly. Return the overclocks to their previous settings, and the encoding once again fails to properly timecode.

I'll return to my previous installation of OBS for now, as there were no problems before 19.0.2.

You may not think there's anything in there, but you're probably not anywhere near as experienced at reading log files as we are. Just post the log, instead of arguing about it. Please.

 

[Boildown]

If I were you I'd post the log file just to make them shut up about it.

Also post one of your output files that demonstrates the problem, preferably the one that's associated with the log file you post. You'll need to use a filesharing site of some kind for that.