obsproject / obsproject/obs-studio
after the encoder has been initialized warnings when using stream encoder for recording
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
30.2.0-rc1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/IzjRZUMB8cqzbjpC
OBS Studio Crash Log URL
No response
Expected Behavior
No warnings in the log file and initialize the encoder once.
Current Behavior
These warning log lines are generated
10:00:34.328: encoder 'advanced_video_stream': Cannot apply a new video_t object after the encoder has been initialized
10:00:34.328: encoder 'advanced_video_stream': Cannot set the scaled resolution after the encoder has been initialized
10:00:34.328: encoder 'advanced_video_stream': Cannot enable GPU scaling after the encoder has been initialized`
Steps to Reproduce
- Have replay buffer and recording start when the stream starts
- use the same encoder for recording and streaming
- start streaming
Anything else we should know?
It looks like OBSBasic::StartStreaming calls AdvancedOutput::SetupOutputs twice, once via AdvancedOutput::SetupStreaming and once via AdvancedOutput::StartRecording
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 with OBSBasic::StartStreaming and trace the two AdvancedOutput::SetupOutputs calls described through SetupStreaming and StartRecording. Reproduce the shared stream-and-recording setup from the issue and compare the resulting log with the linked OBS log. Done means the encoder is initialized once and the three warnings no longer appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- audio-video-rtc, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100