Custom audio bandwidth
It seems Jami tries to optimize auto and video qualitity, which is probably the best default.
But what is one supposed to do, or to configure (up-front) when using a often intermittently weak and/or slow remote connection (of possibly quite good volatile but never continuously perfect quality)?
Ideally, I guess there would need to be a button to switch the preference over to "Minimize bandwidth/data requirements" for this situation.
But with the many codec selections available in the audio/video settings, is there maybe already some workaround possible?
Idea that emerged from the discussion:
Have a single preference instead of the current
- Videobitrate setting,
- missing Audiobitrate setting,
- and hardcoded Codec preference and parameters.
Bandwidth Usage
- minimized (frugal)
Adaptive (greedy) up to
- 64 kB/s
- 128 kB/s
- 256 kB/s
- 512 kB/s
- 1MB/s
- unthrottled
(Individual codec selection (i.e. to enable/disable specific codecs) would have to stay in the advanced/media settings.)
Activity
Um, yes, I'm sorry, I don't know which codecs I would have to select and which to deselect.
For the moment I'm looking only at the audio codecs, because video is way to much for the connection anyway.
What would the person with the bad connection have to configure, and would the other side also have to configure the same?
Thanks!
Edited by Ring ThingI mean the audio codes listed under the Account->Media Settings, suspecting opus or speex-8000 might be best for bad connections.
Could you provide some info? Maybe order the listing in the settings according to the most suitable for low-bandwidth situations first? So one could deselect the below ones, to not use increased quality.
Thank you. If you say it is already as good as possible for bad connections, it was probably the codec list (order) that made me unsure about the defaults.
If one side only has fixed speex-8000 active on one side, could that avoid those recovery distortions, and instead work more continuously with an overall lower quality, but a more reliable and still decent quality?
I will also try that.
If one side has only speex-8000 active, and the other side uses the defaults, it seems to work (at least locally, and only shortly after refreshing the online state)
Will have to see how speex-8000 works for calls over to the flaky connection.
Just as it has also been my experience in the past, unfortunately, the audio call did not go through right away (other issue numbers). Same with messages keeping the circle symbol.
So it took a couple of tries with both sides fiddling with the apps in foreground, switiching offline/online, and when it finally worked, I did have the opus codec enabled again on my side. Since I've seen unreliable calling and messaging before, I'm not yet convinced it really only failed this time due to only having speex-8000 enabled on my side.
Does the playstore variant (other side) have speex-8000 enabled by default? If yes, I guess the problems should not have been caused by me having only that speex-8000 codec active.
I think UI wise it could be best to merge all the Videobitrate, Codec selection and settings and the missing Audiobitrate settings into a single
Bandwidth Usage Setting
- minimized
Adaptive (greedy)
- 64 kB/s max.
- 128 kB/s max.
- 256 kB/s max.
- 512 kB/s max.
- 1MB/s max.
- unthrottled
Edited by Ring ThingYeah, a quality comparison, even if just local, could be nice.
The practical benefit I see independently from test calls though, is to allow making one or multiple parallel calls work without having annoying glitches or clogging bandwidth or QoS limitations that limit or conflict with other uses.
mentioned in issue #920 (closed)
added media settings typefeature request labels
