Victor Gaydov

@baranovmv I did a few benchmarks and have an interesting observation. Please take a look at the `Jitter + Niq + Losses` plot in the end of reports in this...

**WIP** benchmark for prototyping new jitter meter algorithm: https://github.com/roc-streaming/qa/tree/main/reports/20250214_gh712_jitter_sim It includes current jitter meter implementation ported from C++ to python, and a few tests that get jitter and peak jitter...

Pull request merged. Here is the comment for resize(): ``` //! Change ring queue capacity. //! @remarks //! After this call, capacity() is equal to the new value, and size()...

Hi, thanks, I guess @singsian could take it, as he/she commented first. @OdenDillenkoffer Feel free to take a look at other help-wanted issues, there is plenty of them :)

@apithikkat Thank you, you're welcome!

@sprinkuls Sure, thanks!

Implementation merged, for tests I've created a separate issue: #792

@rishilss99 Thanks!

``` D: [alsa-sink-USB Audio] roc_audio: latency monitor: latency=8576 target=8640 fe=1.00006 trim_fe=1.00006 adj_fe=1.00006 D: [alsa-sink-USB Audio] roc_audio: depacketizer: ts=1687038435 loss_ratio=0.00010 D: [alsa-sink-USB Audio] roc_audio: latency monitor: latency=8832 target=8640 fe=0.99992 trim_fe=0.99992 adj_fe=0.99992...

``` [debug] roc_audio: depacketizer: ts=1327130041 loss_ratio=0.00049 [debug] roc_audio: latency monitor: latency=8064 target=8640 fe=1.00018 trim_fe=1.00018 adj_fe=0.91891 [debug] roc_audio: latency monitor: latency=9344 target=8640 fe=1.00014 trim_fe=1.00014 adj_fe=0.91888 [debug] roc_audio: latency monitor: latency=8704 target=8640...