Can't change bitrate in advanced encoder settings while using AVC encoder!

Sgt_Logix

New Member
Hi there guys,
Today, I bought myself some new upgrades for my pc (sweet!), but when I try to change the bitrate, I just can't seem to make it switch. The only two options that it lets me do, is either 1 or 0. I can't really figure out why does this problem occurs, but I hope that I'm not the only one having this problem! Does someone face this issue too? I saw someone post already once on this topic but I guess that no one paid attention to it. I really don't want to switch to StreamLabs OBS and just want to stick with the old guns, which is OBS!
Thanks in advance guys! :)
 

rockbottom

Active Member
I can't really figure out why does this problem occurs, but I hope that I'm not the only one having this problem!

I believe you are

If it worked before the upgrades, you should know where to start troubleshooting.... Weirdness from your log
17:47:05.182: [AMF] Version 2.7.0 loaded (Compiled: 1.4.14.0, Runtime: 1.4.18.0, Library: 1;4;18;0;20.45.01.14;202011131446;CL#2201722).
17:47:05.247: [AMF] <Id: 1> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:05.351: [AMF] <Id: 2> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)

17:47:08.348: DShow: HDevice::ConnectPins: failed to connect pins (0x8004022A):
17:47:12.055: [AMF] <Id: 3> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.075: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:12.120: [AMF] <Id: 4> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.130: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:24.454: adding 21 milliseconds of audio buffering, total audio buffering is now 64 milliseconds (source: Mic/Aux)
17:47:24.454:
17:47:27.776: warning: Could not update timestamps for discarded samples.
17:47:39.571: adding 21 milliseconds of audio buffering, total audio buffering is now 85 milliseconds (source: Mic/Aux)
17:47:39.571:
17:47:47.799: warning: Could not update timestamps for discarded samples.
17:48:07.806: warning: Could not update timestamps for discarded samples.
17:48:27.815: warning: Could not update timestamps for discarded samples.
17:48:47.830: warning: Could not update timestamps for discarded samples.
17:48:59.364: adding 448 milliseconds of audio buffering, total audio buffering is now 533 milliseconds (source: Starting-Overlay)
17:48:59.364:
17:49:01.839: adding 341 milliseconds of audio buffering, total audio buffering is now 874 milliseconds (source: Starting-Overlay)
17:49:01.839:
17:49:02.390: Max audio buffering reached!
17:49:02.390: adding 85 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Starting-Overlay)
 

Sgt_Logix

New Member
I believe you are

If it worked before the upgrades, you should know where to start troubleshooting.... Weirdness from your log
17:47:05.182: [AMF] Version 2.7.0 loaded (Compiled: 1.4.14.0, Runtime: 1.4.18.0, Library: 1;4;18;0;20.45.01.14;202011131446;CL#2201722).
17:47:05.247: [AMF] <Id: 1> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:05.351: [AMF] <Id: 2> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)

17:47:08.348: DShow: HDevice::ConnectPins: failed to connect pins (0x8004022A):
17:47:12.055: [AMF] <Id: 3> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.075: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:12.120: [AMF] <Id: 4> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.130: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:24.454: adding 21 milliseconds of audio buffering, total audio buffering is now 64 milliseconds (source: Mic/Aux)
17:47:24.454:
17:47:27.776: warning: Could not update timestamps for discarded samples.
17:47:39.571: adding 21 milliseconds of audio buffering, total audio buffering is now 85 milliseconds (source: Mic/Aux)
17:47:39.571:
17:47:47.799: warning: Could not update timestamps for discarded samples.
17:48:07.806: warning: Could not update timestamps for discarded samples.
17:48:27.815: warning: Could not update timestamps for discarded samples.
17:48:47.830: warning: Could not update timestamps for discarded samples.
17:48:59.364: adding 448 milliseconds of audio buffering, total audio buffering is now 533 milliseconds (source: Starting-Overlay)
17:48:59.364:
17:49:01.839: adding 341 milliseconds of audio buffering, total audio buffering is now 874 milliseconds (source: Starting-Overlay)
17:49:01.839:
17:49:02.390: Max audio buffering reached!
17:49:02.390: adding 85 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Starting-Overlay)
Okay... Now what? I'm not a professional what so ever in reading the logs. What seems to be the problem? What could be a potential fix?
 

Sgt_Logix

New Member
I believe you are

If it worked before the upgrades, you should know where to start troubleshooting.... Weirdness from your log
17:47:05.182: [AMF] Version 2.7.0 loaded (Compiled: 1.4.14.0, Runtime: 1.4.18.0, Library: 1;4;18;0;20.45.01.14;202011131446;CL#2201722).
17:47:05.247: [AMF] <Id: 1> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:05.351: [AMF] <Id: 2> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)

17:47:08.348: DShow: HDevice::ConnectPins: failed to connect pins (0x8004022A):
17:47:12.055: [AMF] <Id: 3> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.075: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:12.120: [AMF] <Id: 4> Unable to set converter transfer characteristic, error AMF_NOT_FOUND (code 11)
17:47:12.130: [AMF] Exception occurred while updating capabilities: Invalid Parameter
17:47:24.454: adding 21 milliseconds of audio buffering, total audio buffering is now 64 milliseconds (source: Mic/Aux)
17:47:24.454:
17:47:27.776: warning: Could not update timestamps for discarded samples.
17:47:39.571: adding 21 milliseconds of audio buffering, total audio buffering is now 85 milliseconds (source: Mic/Aux)
17:47:39.571:
17:47:47.799: warning: Could not update timestamps for discarded samples.
17:48:07.806: warning: Could not update timestamps for discarded samples.
17:48:27.815: warning: Could not update timestamps for discarded samples.
17:48:47.830: warning: Could not update timestamps for discarded samples.
17:48:59.364: adding 448 milliseconds of audio buffering, total audio buffering is now 533 milliseconds (source: Starting-Overlay)
17:48:59.364:
17:49:01.839: adding 341 milliseconds of audio buffering, total audio buffering is now 874 milliseconds (source: Starting-Overlay)
17:49:01.839:
17:49:02.390: Max audio buffering reached!
17:49:02.390: adding 85 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Starting-Overlay)
Solution found! I just reverted back to a driver before this version that is new and it worked like a charm! I guess that AMD bugged it out in this new update. Thanks for your help btw. :)
Appreciate the help!
 

ShoryukenPizza

New Member
Someone help? :(
I was just googling this and this issue popped up for me when I went to randomly check my bitrate. I also run AMD too. On Output > Output Mode "Advanced" > View Mode > "Advanced", if I change my Video Adapter from my GPU to CPU then back to my GPU, I'm able to change it from 1 to any number. If I close OBS and reopen it, it's back at Target Bitrate = 1. I'd personally hate to downgrade back to 20.9.1 and I'm not sure if this value is an accurate representation in OBS nor am I certain when this change occurred.
Last stream: https://obsproject.com/logs/89wvoHwyuFX6CSjI
Opening OBS today: https://obsproject.com/logs/zO-A8Wf78IGPGNg-
 

rockbottom

Active Member
Sounds like you have 2 options, stick with the optional driver that AMD clearly screwed up or roll back to a driver that works.
 

ShoryukenPizza

New Member
Sounds like you have 2 options, stick with the optional driver that AMD clearly screwed up or roll back to a driver that works.
Rolled back even further. Seems to have fixed the issue. Before I rolled back, I was getting skipped frames like crazy. Thanks.
 
Top