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

Support "weight" parameter in requests #943

Open
Jalle19 opened this issue Feb 15, 2022 · 4 comments
Open

Support "weight" parameter in requests #943

Jalle19 opened this issue Feb 15, 2022 · 4 comments
Labels
enhancement non-spec feature requests not part of SAT>IP specification

Comments

@Jalle19
Copy link
Collaborator

Jalle19 commented Feb 15, 2022

Currently there is no way for minisatip to distinguish "unimportant" adapter usage (such as EPG scanning, mux scanning) from actual adapter usage (streaming a channel). tvheadend has an option to send a "weight" parameter to the SAT>IP server, which can be used to distinguish the nature of the stream.

Currently I have to "proxy" minisatip instances with a tvheadend instance just to get this feature. It would be great if we could implement it in minisatip even though it's not part of the SAT>IP specification.

@Jalle19 Jalle19 added enhancement non-spec feature requests not part of SAT>IP specification labels Mar 28, 2022
@lars18th
Copy link
Contributor

lars18th commented Feb 22, 2023

Hi @Jalle19 ,

Please, could you explain more about this? What's the paremeter and how it works. Perhaps I'll try to implement it.
Perhaps the same could be used for my request #908

Regards.

@Jalle19
Copy link
Collaborator Author

Jalle19 commented Feb 23, 2023

The idea comes from tvheadend, where each "subscription" has a "weight". This means a new subscription can take presedence over an existing one if its weight is higher. This is useful to de-prioritize e.g. EPG scans.

I've since worked around this in a different way so this is in no way critical anymore.

@lars18th
Copy link
Contributor

Hi @Jalle19 ,

Thank you for the explanation. Perhaps this could be supported using my proposal described in #1052 ?

Anyway, could you please share a request with the subscription weight using TVHE? I want to see how it pases the data over the SAT>IP request. Or it is only supported using other protocols?

@Jalle19
Copy link
Collaborator Author

Jalle19 commented Feb 24, 2023

IIRC it's weight=X, where X is between 1 and 200. 100 is standard streaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement non-spec feature requests not part of SAT>IP specification
Projects
None yet
Development

No branches or pull requests

2 participants