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

How to play the same stream on multiple devices in local network. #10

Open
juhacz opened this issue Oct 30, 2023 · 4 comments
Open

How to play the same stream on multiple devices in local network. #10

juhacz opened this issue Oct 30, 2023 · 4 comments

Comments

@juhacz
Copy link

juhacz commented Oct 30, 2023

Is it possible to watch the same stream on two devices simultaneously on the network with the same running engine? It doesn't work for me. When I watch a stream on device A, trying to play the same stream on device B fails.
On the website https://wiki.acestream.media/Engine_HTTP_API I read that in the address to engine you must also provide the "pid" parameter, which identifies the playback device, e.g.
http://192.168.100.130:8020/ace/getstream?infohash=8f92d328d2e5a8a83f04bd6f3dxxxxx&pid=40518239 when I do it manually it still doesn't work.

@vstavrinov
Copy link
Owner

See

https://wiki.acestream.media/Engine_HTTP_API#Player_ID

So this restriction is by design. As far as I know there is some solution for payed licence exists. But on my own I am on the way for kubernetes solution where every client will be served by single dedicated replica of the container. Dinamic number of replicas would be orchestrated by kubernetes.

@juhacz
Copy link
Author

juhacz commented Nov 6, 2023

Thank you. I created a new container, and I solved the problem.

@L3KTRO
Copy link

L3KTRO commented Nov 28, 2023

See

https://wiki.acestream.media/Engine_HTTP_API#Player_ID

So this restriction is by design. As far as I know there is some solution for payed licence exists. But on my own I am on the way for kubernetes solution where every client will be served by single dedicated replica of the container. Dinamic number of replicas would be orchestrated by kubernetes.

So, you can publish your Kubernetes solution? or a light tutorial 👍

@vstavrinov
Copy link
Owner

Unfortunately, there is no native (i.e. internal, own) kibernetus solution as it has no such metric as number of connections per instance that could be used as resource limits for autoscaling. To release this solution, it is necessary to create an external service to monitor this parameter and custom metrics. This work is something I am interested in, but I don't know when I can begin. Now I am using two permanent instances that meet my needs at least for now.

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

No branches or pull requests

3 participants