-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Own audio shut down during video conference #749
Comments
@bonjourjoel Try this workwaround by playing a valid silence audio file before, |
Hi, I'm already doing this. I'm using this to start the audio player on a first click on the login button. If I play several sounds, none play, neither the first, nor the second... So It's not the solution. The plugin is taking the audio system for itself, and it's not possible to use it, at least with Web audio api, at least in a normal way. |
This workarround does work for many people, even last week it did solve a
similar issue for an user.
I will try to ask the user to report how they fixed it exactly.
Notice that if you don't have to support ios bellow 14.3 you don't need
this plugin to use WebRTC, unless you want control over audio output.
Le jeu. 26 mai 2022, 13:43, Joel ***@***.***> a écrit :
… Hi, I'm already doing this. I'm using this to start the audio player on a
first click on the login button. If I play several sounds, none play,
neither the first, nor the second... So It's not the solution. The plugin
is taking the audio system for itself, and it's not possible to use it, at
least with Web audio api, at least in a normal way.
—
Reply to this email directly, view it on GitHub
<#749 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACDO7JLUNEEJIWVAX4AU3VL5PWZANCNFSM5W6HKG5A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Could be fixed by #768 please test 8.0.4 |
Ping @bonjourjoel please test 8.0.4 |
YOU MUST read first!
Please use Community Forum for general technical discussions and questions.
extra/renderer-and-libwebrtc-tests.js
file).Note: If the checkboxes above are not checked (which you do after the issue is posted), the issue will be closed, removing this checkbox will result in automatic closed issue.
Versions affected
Description
When the iosrtc is playing a remote video with webrtc audio, the audios of my own application don't play any more. And when the iosrtc session ends, the audios of my application can play again, and i can hear them again.
Steps to reproduce
Play another sound using webkitAudioContext|AudioContext while a webrtc video is playing. And only the sound of webrtc video makes sound.
Expected results
Both should make sound.
Actual results
Only sound for webrtc.
More details:
I will put more details. Sorry if its too much, but this is what i've done and tried. Maybe you can point me my mistake with these informations.
I have installed the plugin using this command:
cordova plugin add cordova-plugin-iosrtc --variable MANUAL_INIT_AUDIO_DEVICE=TRUE
If i don't use this variable TRUE, when i launch my app, all the sounds are very low: They are playing in the ear speaker. Both my sounds and the sounds of webrtc. But when I use this variable TRUE, both sounds play in the normal speaker when i start the app.
Also i am using these commands when i receive the ice state "connected":
initAudioDevices() + turnOnSpeaker(true)
Because if I don't, then the sound of the rtc video conference is playing in the ear piece of the phone. But with these instructions, it seems to play in the speaker, except if an earphone is plugged in and then it plays in the earphone. This behaviour seems fine to me.
But as i said; the audio of my app, doesn't play at all during the rtc sessions.
One more detail that is unrelated, but i don't want to spam your forum, so i'll put it here: I can't find a way to mute temporarily the audio received. In javascript i use HTMLVideoElement.muted = true/false, but it doesn't have any effect with iosrtc. I couldn't find anything that could do it.
Thanks for your time!
The text was updated successfully, but these errors were encountered: