-
Notifications
You must be signed in to change notification settings - Fork 251
Description
Hi, I just manage to spot a difficult to reproduce problem on Android.
Steps I did to see the problem
- Upload a acc to AWS S3 using react-native-audio to record the AAC and RN XMLHttpRequest to serve
- Be sure that it is serve from aws S3 (no cloudfront in beetween) with content type AAC
- Use react-native-audio-streaming to play the content
- See it does nothing
Sometimes, with some file or after a delay (?? not sure about it) It does manage to play the file, but sometimes it fail, so it is hard to reproduce. Note that the same file work perfectly on iOS
Debug message
As I was able to find a bugging case on a real android device (ZTE Axon Pro Android 5.0.2 and kernel 3.10.49 on a Qualcomm810 processor), I did get the following pidcat bug (with redacted private header that content private metadata).
This seems to be related to this line:
https://github.com/vbartacek/aacdecoder-android/blob/master/decoder/jni/aac-decoder/aac-decoder.c#L427
I'm pretty noob with aac, but I read somewhere in the net that it can be because my file as an ADIF header instead of an ADTS and thus vbartacek/aacdecoder-android can't read it
Hope you have enough info to help me.
