Yuichiro Tachibana (Tsuchiya)

See this example: https://github.com/whitphx/streamlit-webrtc/blob/f2cd41492da9f14146a32ad6301988d23e516041/pages/media_files_streaming.py#L42 You can consume an RTSP like this.

Yes, this example may help: https://github.com/whitphx/streamlit-webrtc/blob/538e886a5ac2ba74feab262440b162e510044e21/pages/8_media_files_streaming.py#L43 https://github.com/whitphx/streamlit-webrtc/blob/538e886a5ac2ba74feab262440b162e510044e21/pages/8_media_files_streaming.py#L53-L57 https://github.com/whitphx/streamlit-webrtc/blob/538e886a5ac2ba74feab262440b162e510044e21/pages/8_media_files_streaming.py#L121

The example you mentioned (https://github.com/whitphx/streamlit-webrtc/blob/main/pages/8_media_files_streaming.py) uses a callback to process the video frames (`video_frame_callback`). Does using `audio_frame_callback` in this place instead work for you? [The audio filter example](https://github.com/whitphx/streamlit-webrtc/blob/main/pages/3_audio_filter.py) may also...

Hi, thank you for the critical question. Yes, as you said, I recommend the function-based API and would like to deprecate the class-based one. > Is it worth to update...

> I cannot open the camera and then I open the camera Please elaborate it. What does "I cannot open the camera" and "then I open the camera" mean? ---...

At this moment it's not supported as the video source is only limited to WebCam. Let me leave this issue as a feature request.

However, with the current API, the players and the recorders are automatically stopped or closed by the `webrtc_streamer()` component. Removing these APIs also gets rid of this advantage. -> Keep...

This is an example of mixing multiple video tracks: https://github.com/whitphx/streamlit-webrtc/blob/main/pages/6_mix_multi_inputs.py Replacing its "video" to "audio" may work...? Sorry audio is not my expertise...

Thank you for the report! Let me take time to check it.

Thank you for reporting it. It's fixed now.