Logging timestamps is still possible when OBS is not streaming or recording

[markmacode]

• Operating System: Windows 10, 64-bit
• OBS version: 25.0.8

Steps to reproduce

1. Start recording.
   1.1. If using CSV output format and no log file currently exists, press a hotkey to make a log file.
2. Stop recording and keep OBS open.
3. Press a hotkey again (or press hotkeys many times).

Some notable things

• In the Default output format it will put "(not recording)" at the end of the timestamp, which is a good enough indication that the timestamp is invalid.
• In the CSV output format, when these timestamps are added in the file, it logs data like this: 441925:44:47,event, with no indication that the timestamp is invalid (other than the fact that a 400,000 hour in a recording is probably a sign that the timestamp is invalid).
• If you move, rename or delete the original log file, invoking this bug will create a new log file in the original location with the original name but only with invalid timestamps.
• All this buggy activity is silent, if someone has OBS open all the time in the background, depending on their InfoWriter hotkeys they could be generating more invalid timestamp data than normal data.

[partouf]

Thanks for the bugreport, will see next iteration what I can do about this