obsproject / obsproject/obs-studio

AMD encoder overload cannot be recovered

Open
#13,670 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

32.1.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/UNesMqXQoYrNBmGV

OBS Studio Crash Log URL

No response

Expected Behavior

Playing 4K video while live streaming/recording simultaneously causes the AMD encoder to overload (as expected), but if video playback is closed, the encoder should recover from the overload state.

Current Behavior

If it enters an overload state, it can never return to normal unless encoding is completely stopped. According to Windows Task Manager, the encoder usage is even lower than normal after overload, and there is a lot of frame drop caused by encoding lag.

Steps to Reproduce
  1. Start encoding.
  2. Try playing or encoding multiple things simultaneously to trigger encoder overload.
  3. Turn off things that cause overload.
  4. OBS is perpetually in an overload state.
Anything else we should know?

GPU: AMD RX 9070 XT
Driver: Adrenalin Edition 26.6.4
Encoding settings:
Image
Image

Normal:
Image
Triggered overload:
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the overload on Windows 11 with an AMD RX 9070 XT, then inspect the linked OBS Studio log for encoder and frame-drop details. The issue is done when stopping the workload lets encoding recover without restarting encoding and frame drops return to normal.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
audio-video-rtc, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.