Question / Help Audio Bitrate capped at 160.

AntonKnee

New Member
Hi I use obs for recording and recently I found out that you can change your audio bitrate and that it improves the quality of the audio. Anyways when I tried to adjust it the highest option is 320. I have looked on youtube and the forum and not found any solutions.
 

Attachments

  • Capture.JPG
    Capture.JPG
    31.5 KB · Views: 1,523

koala

Active Member
Go to Settings->Output->Streaming and uncheck "Enforce streaming service encoder settings". Audio track 0 is fixed to 160 if this is enabled, since track 0 is the default streaming track.
 

cedarrapidsboy

New Member
Thank you for posting this. It solved my problem. Audio bitrate was capped at 160 Kbps even though I had it configured for 5.1 output and 480 Kbps on the Audio page and Output->Audio tab, respectively.

Is this a known bug (I cannot find it in the tracker)? It seems like a bug since this affects local recordings while the option is on the streaming interface. The surround sound guidance does not mention it, though it does mention increasing the bitrate.
 

koala

Active Member
It's no bug, it's the consequence of the duality of streaming and recording. OBS doesn't know if you intend to stream only or record only or both. So it has to prepare for both.One track goes out for streaming, so OBS has to prepare this track within the constraints of the streaming service. If you record this track as well for recording, you inherit these constraints.

You can always choose the track that is affected by streaming (in the output->streaming tab), it does not need to be track 1. And you can always choose the tracks that are written to your recordings (in the output->recording tab), does not need to include the track chosen for streaming.
 

cedarrapidsboy

New Member
It's no bug, it's the consequence of the duality of streaming and recording. OBS doesn't know if you intend to stream only or record only or both. So it has to prepare for both.One track goes out for streaming, so OBS has to prepare this track within the constraints of the streaming service. If you record this track as well for recording, you inherit these constraints.

You can always choose the track that is affected by streaming (in the output->streaming tab), it does not need to be track 1. And you can always choose the tracks that are written to your recordings (in the output->recording tab), does not need to include the track chosen for streaming.

Thanks for that context. I of course never considered the use case of simultaneously streaming and local recording. This helps!
 
i have the same problem, but i don't seem to understand the answers provided in the forum. go setting , then streaming and do what? ucheck enforce. my obs doesnot say that. please help
 
Thank you for posting this. It solved my problem. Audio bitrate was capped at 160 Kbps even though I had it configured for 5.1 output and 480 Kbps on the Audio page and Output->Audio tab, respectively.

Is this a known bug (I cannot find it in the tracker)? It seems like a bug since this affects local recordings while the option is on the streaming interface. The surround sound guidance does not mention it, though it does mention increasing the bitrate.
can you help me so my problem as well. when i tried to increase it 320 it say it will be set to 160 because it is the limit set. i don't see the reason. please help
 

MrGhost

Member
can you help me so my problem as well. when i tried to increase it 320 it say it will be set to 160 because it is the limit set. i don't see the reason. please help
What I am seeing with the TS chunk download I get from Rumble downloads (which .tar file is only thing you get when using a 3rd party downloader) is a varying bitrate around 160. This didn't change with the use of the AAC encoder for me. I had to install iTunes to get the AAC encoder option or Core audio AAC in OBS. Still after this I still got chunks that hovered around 160kbps for total bitrate - data rate. I don't know how the chunks are summed. I am told they are summed so that we can watch one while another downloads, which would be a straight sum and that would mean that we are getting basically 160 audio back. However when I use Rumble to download the stream replay from my own content page I get an mp4 (no chunks) which states that it is 320 or therabouts (I think it was actually slightly different on average than 320) kbps audio (total bitrate - data rate in Windows File Explorer detail view). So is Rumble just giving back what it is told is streamed by OBS and encoding the chunks with that 320 setting? Or is each chunk around 160 like we see in the chunks so the audio is just a deception that we are getting as mp4 file downloaded after the replay is completed by the website? I don't know.
 
Last edited:
Top