-
Notifications
You must be signed in to change notification settings - Fork 214
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
Empty audio created on Android in some cases #271
Comments
Well, of course I can't reproduce this... @ProFive Are you able to reproduce it with a device that you own? |
@llfbandit Hi, here is an example of Android logs that might be related to this case. Audio is recorded using record v5.0.4 on a Huawei device Huawei P40 Lite with EMUI 12.0.4 - it should be based on Android 10 I believe. After that it's being played with AudioPlayer
|
I'm experiencing the same issue on older Android devices (API 29). It did not occur with version 4.4.4 but does with version 5.0.4. Interestingly, the issue does not appear on API 34 either. Here's the RecordConfig I'm using: RecordConfig( When audio recorded with this configuration is played using the Just Audio plugin with player.setAudioSource, the error occurs. |
Is it better with version 5.0.5 and record_android 1.1.0? |
Device: Oppo Reno A I'm not sure if this is related to the issue I'm experiencing, but when I attempt to start recording in the record example project under the above conditions, it crashes. The line where it crashes: Error message: For your information, I did not experience this crash on other devices I have (with Android 12 and Android 14). |
same error in android 8 and 9. |
Package version
5.0.4
Environment
Android
Describe the bug
On certain Android devices, the audio file created is of 0 bytes.
No such issues on version 4.4.4
RecordConfig(
echoCancel: false,
noiseSuppress: false,
autoGain: false,
numChannels: 1,
encoder: AudioEncoder.aacLc,
sampleRate: 44100,
)
To Reproduce
I could not reproduce it as the issue didn't occur on any of my devices. It happened on the client's device. I released a new version of the app with 4.4.4 and it started working for everyone who had been facing this issue.
The text was updated successfully, but these errors were encountered: