Questions about setting minimum channel quality, locking sliders, and presets

TeamSpeak 3 Server Permissions
, , , ,
1

Hello
TeamSpeak Server version 3.17.8 on Linux

We have a few direct questions about channel creation permissions and the user interface. Please let us know if these configurations are possible:

  1. We can use i_channel_create_modify_with_codec_maxquality to set a maximum limit. Is there an official permission to set a minimum quality number for the slider so users cannot drop it too low?

  2. We noticed that i_channel_create_modify_with_codec_latency_factor_min does not set a minimum limit for the quality slider. What is the exact purpose of this permission?

  3. Is it possible to completely lock the quality slider at a specific number for users during channel creation?

  4. Is it possible to completely disable or deactivate the Voice Mobile and Custom preset options so users cannot click them?

Are these features currently possible in TeamSpeak? If they are possible, how can we do them?

Please check our attached screenshot. Thank you!

knt
knt388×498 46 KB

2

  1. There is no minimum setting for the audio quality.

  2. i_channel_create_modify_with_codec_latency_factor_min is a deprecated setting and is not used for many years now.

  3. No you can not

  4. Those only move the slider either to the left or to the right, they are not doing anything else in this case. (In other cases they would change the codec as well)

2 Likes
4

I understand, but this creates a huge contradiction. If this permission is still active in the list, it should fulfill its purpose because we actually need it right now. If it became useless or harmful over time, it should have been completely removed from the system. Why are we forced to ‘forget’ or ignore permissions that we already know and see in the client? Leaving an inactive permission in the official list just causes confusion for server administrators.

@LeonMarcelHD

5

This permission was never used for minimum qualify settings.

As the name suggests it was a latency which could be added to increase the Audio quality. During further development of the client and computer hardware it was no longer necessary and was therefore deprecated.

We can’t just remove permissions on the fly this process needs to be carefully executed to guarantee full compatibility (e.g. when loading backups etc…). I’ve raised this issue internally to add some kind of notice to all deprecated permissions, however this is from my point of view not a critical issue.

Limiting users to have a minimum audio quality is/could/was something causing issues for users with very low hardware specifications or weak mobile connections, especially back in the days of the TS3 release.

And forcing them to use a higher codec is kinda like serving a family size pizza to a single person.

TL;DL

No need to be sad/angy. The option you need was never implemented in the first place.

2 Likes