obsproject / obsproject/obs-studio
FFmpeg Opus audio codec supports up to 256 kbps, not 320.
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.0.0
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/4SmMmetrlR4yaIca
OBS Studio Crash Log URL
No response
Expected Behavior
Tried to stream using WHIP, which only supports the FFmpeg Opus codec, but was unable to do an error. After further testing, I realized that any audio bitrate above 256 kbps, is unsupported by OBS. when the FFmpeg Opus codec is being used.
Current Behavior
Prevents stream/recording from starting giving this error: Failed to open AAC codec: Invalid Argument. If I had to guess, this means OBS is defaulting back to AAC for 320 kbps, but then some argument fails because Opus is being used.
Steps to Reproduce
- In either record / stream tabs choose the FFmpeg Opus audio codec. I recommend using record because for streaming you have to switch your stream method to WHIP specifically.
- Change audio output channels to be >256 kbps.
3.Click record / stream.
...
Anything else we should know?
No response
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 reproducing the issue in OBS Studio 32.0.0 using the FFmpeg Opus codec and the attached OBS log. Compare recording or WHIP streaming at audio bitrates above 256 kbps, then trace the codec-opening path that produces the reported AAC invalid-argument error. Done means the intended higher bitrate starts successfully without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100