obsproject / obsproject/obs-studio
Problem with Dynamic bitrate
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 10
Other OS
No response
OBS Studio Version
29.0.2
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/8XekGd40spYnWT7v
OBS Studio Crash Log URL
No response
Expected Behavior
Dynamic bitrate => it should adapt the bitrate to my connection.
In OBS 27.X it worked perfectly.
Current Behavior
Since I use the version 29 of OBS, when I use dynamic bitrate, the bitrate stop working after a certain time and the connection stop to work (OBS show 0 kb/sec with a green status)
Steps to Reproduce
- Use dynamic bitrate
- Start a stream
- After a certain time, dynamic bitrate will stop to work and show 0 kb/sec
Anything else we should know?
It stopped to work here :
16:50:21.683: [rtmp stream: 'simple_stream'] bitrate decreased to: 3000
16:50:21.700: [qsv encoder: 'simple_video_stream'] Failed to reconfigure
16:50:25.724: [rtmp stream: 'simple_stream'] bitrate increased to: 3200, done
16:50:25.724: [rtmp stream: 'simple_stream'] going back to prev bitrate
16:50:25.724: [rtmp stream: 'simple_stream'] bitrate decreased to: 3000
16:50:25.733: [qsv encoder: 'simple_video_stream'] Failed to reconfigure
16:50:29.762: [rtmp stream: 'simple_stream'] bitrate increased to: 3200, done
16:50:32.480: [rtmp stream: 'simple_stream'] going back to prev bitrate
16:50:32.480: [rtmp stream: 'simple_stream'] bitrate decreased to: 3000
16:50:32.500: [qsv encoder: 'simple_video_stream'] Failed to reconfigure
16:50:36.497: [rtmp stream: 'simple_stream'] bitrate increased to: 3200, done
16:51:07.489: socket_thread_windows: Received FD_CLOSE, 30724 ms since last send (buffer: 0 / 430080)
16:51:07.489: socket_thread_windows: Aborting due to FD_CLOSE, error 0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked OBS log and the dynamic bitrate sequence around the RTMP stream, QSV encoder reconfiguration failures, and Windows socket FD_CLOSE. Trace the dynamic bitrate and encoder reconfiguration entry points from those log messages. Done means dynamic bitrate continues adapting during a stream without reaching 0 kb/sec or losing the connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100