Quick Question
I’m currently browsing your website
https://evostream.com/low-latency-streaming-on-aws-cloud/ and I’m kind of lost. Could you please help me to clarify how can we use your technology in our case?
The case is as follows:
we have a service (website) with two kind of users:
1) those who generate audio/video stream with a laptop with a stock webcams
2) those who watch it
Generally, we do not know how many of them will be in each group, but we can assume that there will be several times more “watchers” than “generators”.
Generators schedule “events” and invite watchers to attend them. Only invited watchers can view the stream from a particular event.
A couple of things more:
– we’d like both generators and watchers not to use any additional software (only browser)
– we’d like not to pass streams through our server to be scalable.
What can your technology offer in this case?
1 Answers
Hello techq!
Here is the list of options you can do in your case:
- Use of EMS Web UI or EMS console to add the streams in EMS
- Use of Websockets or WebRTC to watch the streams (These are web-based only)
You can do pullStream API for this so that the streams will be added to the EMS. You may do the pullStream command using the EMS Web UI or console. References: (please read) http://docs.evostream.com/ems_how_to_guide/addlive http://docs.evostream.com/ems_api_definition/pullstream http://docs.evostream.com/ems_web_ui_user_guide/add_inbound_stream2) those who watch it
If the stream is already pulled, you can now watch the streams over the Websockets or WebRTC. References: (please read) http://docs.evostream.com/ems_how_to_guide/websockets http://docs.evostream.com/ems_how_to_guide/webrtc http://docs.evostream.com/ems_user_guide/protocolsupport#html5-web-sockets http://docs.evostream.com/ems_user_guide/protocolsupport#peer-to-peerPlease let me know if you have further inquiries. You may look into our documentation here: http://docs.evostream.com/. Thank you for trying our technology! Warm regards, Erika