-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
JitsiMeetJS.events.conference.TRACK_AUDIO_LEVEL_CHANGED not working in react-native #2193
Comments
It's not supported. The getContributingSources API is not implemented in RN and polling for audio levels using getStats has too high of a performance impact. IIRC we use WebAudio for detecting local levels, and WebAudio is not supported in RN either. |
这是来自QQ邮箱的假期自动回复邮件。
您好,我最近正在休假中,无法亲自回复您的邮件。我将在假期结束后,尽快给您回复。
|
Please post in English so we can understand you. |
Hello, I want to get the current speaker now. I tried DOMINANT_SPEAKER_CHANGED. But not as expected, when I was in the web environment, it took me a long time to get a feedback. Can you help me, Thanks. |
hi @saghul , i know this one not supported for React native, so i used third party lib to get audio level change of local track: react-native-sound-level , its working on ios, but android not working, maybe conflict with jitsi track and i saw very low performance in android. Are the have any way to get audio level of local track? |
This Issue tracker is only for reporting bugs and tracking code related issues.
Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.
Description
I cannot accept the audio level of the local audio stream ,But I can receive remote audio level.
react-native version:0.68.1
react-native-webrtc version: 1.100.1
Current behavior
not working
Expected Behavior
Received audio level
Possible Solution
Steps to reproduce
Environment details
The text was updated successfully, but these errors were encountered: