You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2019. It is now read-only.
Here's my use case. I want to be able to listen to a presentation on one connection and provide real-time interpretation into a different language on a second connection. It's crucial that I keep bandwidth to an absolute minimum, because there could be many listeners -- but also because the listeners might be in the same venue as the speaker, sharing a single wi-fi connection. One-way, audio-only broadcast is the obvious way to go. The part I don't understand is whether the scaling will work directly, device-to-device.
Edit: Oops, I see now that it says "Android devices not tested." I would be happy to help test, if you give me detailed instructions.
The text was updated successfully, but these errors were encountered:
i have tested this with two android devices (tabled and phones), while they connected to web rtc broadcast that was created on windows lvia firefox. it was extremly laggy and they kept disconnecting.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here's my use case. I want to be able to listen to a presentation on one connection and provide real-time interpretation into a different language on a second connection. It's crucial that I keep bandwidth to an absolute minimum, because there could be many listeners -- but also because the listeners might be in the same venue as the speaker, sharing a single wi-fi connection. One-way, audio-only broadcast is the obvious way to go. The part I don't understand is whether the scaling will work directly, device-to-device.
Edit: Oops, I see now that it says "Android devices not tested." I would be happy to help test, if you give me detailed instructions.
The text was updated successfully, but these errors were encountered: