Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move 'heavy lifting' to server (from client) #1228

Open
oliv3r opened this issue Apr 30, 2024 · 1 comment
Open

Move 'heavy lifting' to server (from client) #1228

oliv3r opened this issue Apr 30, 2024 · 1 comment

Comments

@oliv3r
Copy link

oliv3r commented Apr 30, 2024

Currently, the server has a fixed config, and the client will just have to comply. E.g. if the server decides a (computationally heavy) codec is used, the client will have to support it. If the client doesn't support a sample rate, the client has to resample.

While this can be the default behavior, it would be nice that if a client doesn't support resampling, the client will request a stream in a specific configuration, and the server will do the resampling. Obviously the server would have to be somewhat smart, to not resample every stream for every client when those are the same settings.

Likewise, if a client only supports ogg or PCM, the client should be able to request a stream in a format it supports.

This would remove some dependency pressure on the client (#1227) and also help with low-resource clients.

@SantiagoSotoC
Copy link

Wouldn't it be better for the clients to inform which formats they support and then the user can choose which stream to send to the group that is most optimal.
If this only applies to dynamic configurations, by means of the api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants