-
Notifications
You must be signed in to change notification settings - Fork 6k
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
java.io.EOFException: ExoPlayer does not play short AAC File #6700
Comments
Thanks for the report - I'm able to repro in the demo app at 2.10.8 with the media you provided. I'll dig deeper into what's going on here next week. |
I think this is happening because the file contains an incomplete ADTS frame at the end - so during the scan to setup the seeking, we're expecting to read 326 bytes but only 236 are available. How was this file produced? It seems it might have been sliced from a larger file using e.g. Unix We probably shouldn't completely fail playback in this case though (given we successfully play the file when not using constant bitrate seeking) - I'll send a change that makes this slightly more robust. |
I record files from online streams, I slice the file when I stop the recording. I don't check if the frame is complete or not. |
Fixes issue:#6700 sample_cbs_truncated.adts test file produced using `$ split -b 31795 sample_truncated.adts` to remove the last 10 bytes PiperOrigin-RevId: 283530136
This should be fixed on the dev-v2 branch now. |
This parameter is a little confusing, especially as the behaviour can be surprising if the intended use-case isn't clear. This change moves the description of the parameter into the class javadoc, adds context/justification and slims down each method's javadoc to refer to the class-level. Related to investigating/fixing issue:#6700 PiperOrigin-RevId: 283724826
Fixes issue:#6700 sample_cbs_truncated.adts test file produced using `$ split -b 31795 sample_truncated.adts` to remove the last 10 bytes PiperOrigin-RevId: 283530136
This parameter is a little confusing, especially as the behaviour can be surprising if the intended use-case isn't clear. This change moves the description of the parameter into the class javadoc, adds context/justification and slims down each method's javadoc to refer to the class-level. Related to investigating/fixing issue:#6700 PiperOrigin-RevId: 283724826
When I try to play an AAC File under 30 seconds ExoPlayer throws java.io.EOFException if "FLAG_ENABLE_CONSTANT_BITRATE_SEEKING" is set.
Currently I use version 2.9.3. I tried also with 2.10.8 and it still reproduces
Device(s) and version(s) of Android being used
Samsung Galaxy s8+ Android 8
Lg Q6 Android 8.1
I sent the report and AAC File on email at dev.exoplayer@gmail.com
The text was updated successfully, but these errors were encountered: