Recording files are 'corrupted' in OBS 28.0.1

[SauceMaster3000]

Hello!

I upgraded to OBS 28.0.1 because I wanted to try out some new features and with a few seconds-long test recordings everything seemed to be fine.

But after I recorded for real, I found out that the video was shown with weird metadata in the Windows Explorer:

I thought Windows was being Windows and checked the file with MediaInfo and everything seemed to be fine:

However when I used OBS 27.x (same settings, unchanged) it was always shown right in the Windows Explorer so it seemed strange.
Then I tried to open the file with Premiere Pro as I wanted to edit it and it had no video, just audio.
So something got corrupted (?) or is broken with how OBS 28 handles things now.
Maybe some plug-in is the problem, or a setting that I set which didn't cause a problem with v27 but now causes a problem with v28, or something entirely different.

Of course I attached the log file as well. It's the recording starting at 02:57:05.350 and stopping at 03:35:04.459

Since then I've been trying to recreate the problem but it just won't. I'm worried that it will reoccur if I want to record for real again.

I would really appreciate it if somebody can help me out, because I'm losing my mind.

 

[SauceMaster3000]

I wanted to edit but the 10 minute limit exceeded.

I just tried to open the 'corrupted' file with Vegas 19 but the whole program just freezes and doesn't respond at all. I have to manually kill it in the Task Manager. But a non-corrupted test file with the normal metadata in the Windows Explorer does not create any problems with Vegas, so it definitely is something with OBS 28.

I also have been doing some recording tests and finally I have another 'corrupted' file. It seems like it happens randomly:

I recorded 11 files in the last ~ 20 minutes. One got 'corrupted'. 1 in 11. I don't like those odds for my files getting corrupted.

The worst part is there is no way to see until the video is finished so I literally can't record until I can find the solution for this problem.

 

[PaiSand]

Latest stable OBS version is 28.0.3
Latest RC version 28.1

Do not use 28.0.1

 

[SauceMaster3000]

Normally OBS always notifies me when there is an update. Now I feel dumb. Thanks.

But what problem caused this weird behaviour? Didn't read/see any specifics about it in the changelog.
Or was it the one with m3u8?
"Fixed a bug where m3u8 wouldn't work with certain video encoders [Jim]"

That's only one that makes sense, even though I use ts.