IngJohEricsson

OK, this looks more reasonable. I have to look into what causes the problems with the plugin

Can you by (with the plugin example) chance also log the RTP bitrate, i.e the bitrate that comes from the video encoder ? Or alternatively post the entire log ?

You should get a quite verbose log on stdout, if you collect it the. I should be able to dig up the necessary info (I hope) /Ingemar Hämta Outlook för...

Thanks for the log. I plotted a graph. It looks like the video encoder internal rate control is quite sluggish. It lags more than 2 seconds behind the target bitrate....

OK, thanks. In the vaapi example it looks like an I-frame is generated every 4 seconds or so. You can perhaps try and set keyframe-period=100 , the spikes should then...

OK, You can perhaps try with these additional parameters -rateincrease 1000 -ratescale 0.2 as additional parameters after -maxrate 10000 in the sender.sh script This will make the rate increase slower...

OK. Yes, one should expect more sparse peaks. I was hoping that it would reduce the drops but that does not work. Not sure what more can be done. It...

Hi Yes, it should be possible to add a hysteresis function that inhibits video rate updates until the target bitrate increases or decreases more than e.g +/- 5% . This...

Hi Sam. As SCReAM adapts against the detection of increased queue delay you'll indeed get the behavior as shown in your figure. The reason is that once the queue starts...

Hi I have now added a -hysteresis option that should reduce the amount of small rate changes quite considerably . For instance with -hysteresis 0.1 the bitrate must increase more...