-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
7.0.0-RC4 Does not restore audio device, always speaker #551
Comments
@bkervaski Can you confirm you do not reproduce this issue with 6.0.12 and 7.0.0-RC3 ? |
With 6.0.12 it's working fine, but with 7.0.0 and 8.0.0 it seems the library is setting the AVAudioSession AVAudioSessionPortOverride on it's own terms, not honoring the default state or any state changes. When you terminate a session, it always leaves AVAudioSessionPortOverrideSpeaker. Hope this helps! |
Thank you, I think the issue is on master and incoming 6.0.13, since 7.00 and 8.00 has merged master the issue also occur, possibly due to this changes c49bdc5#diff-59c7d02174607ded42b5b45bc22f8b06 Can you test this 2 version and tell me if you have the issue, it will help to confirm what changes introduced the behavior changes. Example with 15402b1:
|
Both 995eaaf and 15402b1 work the same as 6.0.12. I re-tested 7.0.0 and 8.0.0, both have the issue. One thing that is noticeably different, 7.0.0 and 8.0.0 both initialize the audio for the app in ambient mode, where all the regular audio (i.e., Audio().play() or AudioContext audio) are lower volume than should be until the first call, then the audio is at a normal level. Hope this helps :) |
I also tested with 6.0.13 and this version works like 6.0.12 and does not exhibit the behavior as 7.0.0 and 8.0.0. |
Thank you this help a lot. |
Please test #task/7.0.0 or 7.0.0-RC4 |
Is that related #486, I wonder. |
I tested 7.0.0-RC4 and the same result. I then added cordova-plugin-nativeaudio just to see if I could hack around the issue. What happens is on initial app startup, the volume is low (ambient) and then at the end of the first ios-rtc call the volume is unpredictable based on what happened before the first ios-rtc call. For example, if I play a nativeaudio loop, it plays at non-ambient (normal) sound levels. Then, after the first call, all audio (including the loop) are back to ambient (low volume). If I create an AudioContext and say generate some sounds, on app launch it's ambient. After the first ios-rtc call, it's now normal. On 6.0.13 I can overcome this by simply playing a silent mp3 file on app launch, seems to work. But 6.0.13 has the ontrack() bug, so I have to use the later versions. Is it possible to just disable all audio control in ios-rtc, at least as an option, so we can simply set the state elsewhere and not let ios-rtc manipulate that state? Anyway, hope this helps :) |
Yes via MANUAL_INIT_AUDIO_DEVICE (#503) that is part of 6.0.13, when you install the MANUAL_INIT_AUDIO_DEVICE value willl be false by default. Is that what you looking for @bkervaski ? I also realize that we enforce the output here but we do not restore it on Peer or Media/Track Close for example. |
@bkervaski ontrack() bug should be fixed on master and on 6.0.13-RC2 do you mind testing again with MANUAL_INIT_AUDIO_DEVICE and 6.0.13 (confirm if ontrack fixed). |
@bkervaski can you test 6.0.16 and if still not fixed comment to reopen. See previous comments for fix master and releases. |
Hello here,
not helping, I remember previously in6.0.12 all was ok back then. |
I'm on IOSRTC 8, I'll now try 6.0.16 |
yeah I confirm the audio is still low volume at the end of a session on 6.0.16 |
Please read first!
Please use Public Google Group (mailing list) 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
iOS audio device always left on speaker after session
Steps to reproduce
Expected results
Actual results
The text was updated successfully, but these errors were encountered: