WebM Files are glitchy and pixelated now in OBS

[CamOnTheCob]

Hello, I recently updated to the new version of OBS (previously I was using a version from a few months ago). Now all my WebM files and animations have random glitches/artifacts/pixelation as they play in OBS. This gets passed on to my stream; my viewers noticed it as well. Did something with a recent OBS update change the way WebM files are played, and how do I fix it? Thanks

 

[Phaeleh]

Did you find a fix for this at all? It's been bugging me since I updated OBS.

 

[CamOnTheCob]

Did you find a fix for this at all? It's been bugging me since I updated OBS.

Unfortunately no. I sent it to the developers, and they said they couldn’t replicate it so they closed it. I think that was a mistake to close it, because the newer version of OBS clearly isn’t compatible for Web-M for a lot of PCs anymore, including ours

 

[Phaeleh]

Unfortunately no. I sent it to the developers, and they said they couldn’t replicate it so they closed it. I think that was a mistake to close it, because the newer version of OBS clearly isn’t compatible for Web-M for a lot of PCs anymore, including ours

Thanks for the reply! Sorry to hear they couldn't replicate it and it's been dismissed. It's been bugging me as I use webm for a load of background visuals on BRB screens etc, so guess I'll have to try and use the original source files and hope my computer doesn't self combust. Hopefully they resolve it at some point.

 

[redhotsonic]

My webm was working fine until today. The only thing I did differently today was I finally got off my bottom and updated OBS to 30.2.3.

I updated my NVIDIA Driver (3080TI), used hardware or no hardware acceleration (Ryzen 3950X, 16GM RAM), re-rendered the webm, nothing would work and OBS would just keep glitching it out. All other video files worked but not webm without glitching (and I need webm for the alpha tansparency without the need for using a massive AVI file).

But I found a fix quite quickly and easily. The fix... is to downgrade. I just went back to the version I was using (in my case, 30.1.2) and now the webm is playing with no glitches; even with it's alpha transparency. Lesson learned; don't update unless absolutely necessary.

 

[CamOnTheCob]

My webm was working fine until today. The only thing I did differently today was I finally got off my bottom and updated OBS to 30.2.3.

I updated my NVIDIA Driver (3080TI), used hardware or no hardware acceleration (Ryzen 3950X, 16GM RAM), re-rendered the webm, nothing would work and OBS would just keep glitching it out. All other video files worked but not webm without glitching (and I need webm for the alpha tansparency without the need for using a massive AVI file).

But I found a fix quite quickly and easily. The fix... is to downgrade. I just went back to the version I was using (in my case, 30.1.2) and now the webm is playing with no glitches; even with it's alpha transparency. Lesson learned; don't update unless absolutely necessary.

Thanks for the update on this! I’m going to hold out until the next OBS update, and if it still isn’t fixed then I’ll just revert back to the prior version of OBS you mentioned. The devs closed my prior ticket because they couldn’t replicate the issue, but hopefully if enough people speak up about it then they’ll acknowledge this glitchy Web-M thing is a widespread problem

 

[Fenrir]

As a note, we need more information on how to actually reproduce the problem with the webm files. I don't doubt that what is being reported is accurate, but unless we can reliably reproduce the issue, there is not much we can do.

Are any of these files being loaded from a non-SSD or network location? Have they been tested on another PC from a clean scene collection with no other sources? Tested without any third-party plugins loaded?

If possible, please provide logs from the latest working version of OBS, and the version that the issue started appearing in.

 

[CamOnTheCob]

As a note, we need more information on how to actually reproduce the problem with the webm files. I don't doubt that what is being reported is accurate, but unless we can reliably reproduce the issue, there is not much we can do.

Are any of these files being loaded from a non-SSD or network location? Have they been tested on another PC from a clean scene collection with no other sources? Tested without any third-party plugins loaded?

If possible, please provide logs from the latest working version of OBS, and the version that the issue started appearing in.

Hello, thanks for the reply! All of my WebM files are being loaded from my SSD. I also set up a new scene collection and tested it, and the issue still persists. As well as updated to Windows 11. I'm not sure how to turn off my plugins, but I doubt these are the issue since I only have 4: transition table (for audio during certain scene transitions), freeze filter, win capture audio (I don't use this anymore), and StreamDeck Elgato. The WebM issue occurs in every source in every scene. Here's my log file: https://obsproject.com/logs/GPNbq6kLYU4G3mPj

 

[Fenrir]

Please test the things I mentioned. They might not seem related to you, but testing as clean of a setup as possible is extremely important to identifying what is going on.

Steps that should be followed:

- Create a new, empty scene collection (Scene Collection -> New)
- Restart OBS before making any other changes
- Add the source that is experiencing issues
- Observe if the issue is still present or not

If the issue is still present, then please follow:

- Run OBS in Safe Mode (Help -> Restart in Safe Mode)
- Re-check the issue in the clean scene collection

Then please provide the log file from where the issue still occurs.

 

[CamOnTheCob]

Please test the things I mentioned. They might not seem related to you, but testing as clean of a setup as possible is extremely important to identifying what is going on.

Steps that should be followed:

- Create a new, empty scene collection (Scene Collection -> New)
- Restart OBS before making any other changes
- Add the source that is experiencing issues
- Observe if the issue is still present or not

If the issue is still present, then please follow:

- Run OBS in Safe Mode (Help -> Restart in Safe Mode)
- Re-check the issue in the clean scene collection

Then please provide the log file from where the issue still occurs.

Thanks Fenrir, I followed all these steps exactly in the order you mentioned, and the issue still persists. These are my log files after running in safe mode with a new scene selection: https://obsproject.com/logs/nftllbwdUbp1gMeG . I used a sample Web-M with the new scene selection after restarting OBS in safe mode, and it shows random pixelation and glitches.

 

[rockbottom]

How much latency is added here? I don't use OneDrive but it can't be anywhere near as performant as a local drive.

18:09:02.572: [Media Source 'Alien WebM']: settings:
18:09:02.572: input: C:/Users/User/OneDrive/Desktop/Transitions & Scenes/Alien Green Screen.webm

Your log is incomplete but look at the end of it for this stat in the Profiler Results. It's more than likely lagging.
21:51:09.604: ┣tick_sources: min=0 ms, median=0.028 ms, max=578.284 ms, 99th percentile=1.823 ms

 

[koala]

The local Onedrive directory is an ordinary local directory on your SSD. Same performance. It's cloud-mirrored in rsync-like fashion.

 

[CamOnTheCob]

How much latency is added here? I don't use OneDrive but it can't be anywhere near as performant as a local drive.

18:09:02.572: [Media Source 'Alien WebM']: settings:
18:09:02.572: input: C:/Users/User/OneDrive/Desktop/Transitions & Scenes/Alien Green Screen.webm

Your log is incomplete but look at the end of it for this stat in the Profiler Results. It's more than likely lagging.
21:51:09.604: ┣tick_sources: min=0 ms, median=0.028 ms, max=578.284 ms, 99th percentile=1.823 ms

The file is local, I’m not sure why it says OneDrive (that’s just what I use to back up my stuff). Just to be sure, I moved the file to a local C drive and re-tested it, and it still glitches. Tbh I’m sure what you mean about the lag part, but this issue only started appearing after going past OBS version 30.1.2 and I haven’t made any changes to the PC which would increase lag beyond my prior levels. Something in the OBS updates altered the way the WebM files are displayed.

 

[rockbottom]

Gotcha. I see that somebody above already tried disabling HW decoding with the same result. I guess just rollback for now, hopefully the issue(s) are found/addressed while v31 is being vetted.