Open corticalstack opened 2 years ago
Hello. Thank you for the detailed report and trying a different STUN server too. However, I don't have any clues for now, sorry.
FYI, I deployed the code snippet you posted above to Streamlit Sharing cloud and tested it, then the problem didn't occur. In my environment, the app shows the "Recording..." message 2 or 3 seconds after clicking the "START" button.
@whitphx thanks for testing end feeding back. Was the test done as localhost or deployed to cloud? Chrome browser? Windows/Linux? Tested both locally, and deployed as web app on Azure, and both deployment scenarios slow. Will test with other client devices and browsers.
@corticalstack Sorry for being late to reply. It was both on local and Streamlit Cloud. Browser: Brave (same engine to Chrome). OS: macOS
It's a bit weird that locally hosted app has the same connectivity problem... but sorry, I don't have a direct answer to it now.
Hi,
Using streamlit-webrtc to record audio-only, for speech-to-text use case. Note the code snippet below. Between the call to instantiate the webrtc_audio_recorder and setting of status indicaotr as "Recording") takes about 30 seconds.
I've seen another (closed) issue where the stun server was changed. I've tried, still slow. When running locally without the explicit rtc_configuration it is fast to initialise, however the use case demands cloud-hosted, soassume stun config is required, and this is where it is very slow.
Grateful for any recommendations, and thanks for such a great package.