Skip to content
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

Large m4b recognized but no playback #636

Closed
ss000kk opened this issue Aug 6, 2017 · 9 comments
Closed

Large m4b recognized but no playback #636

ss000kk opened this issue Aug 6, 2017 · 9 comments

Comments

@ss000kk
Copy link

ss000kk commented Aug 6, 2017

Hi.. I created a single m4b file 742mb in size and 25 hours long. While the file is recognized by MAP it won't play it back. Other apps will play it but I would like to be able to listen to it in MAP. I hope this will be fixed in a future release. Thanks a lot for the great work with MAP!

App-Version: 3.4.0
Phone Name: BLU Vivo XL
Android Version: 5.1 lollipop

@hjst
Copy link

hjst commented Sep 4, 2017

I'm getting the same problem in 3.4.2.2 with one of my books: the new Audible Stephen Fry reading of Sherlock Holmes, which is a single 72h (!) m4b file.

Is there any hope for this, or should I find a way to split the file by chapter?

@hjst
Copy link

hjst commented Sep 4, 2017

Ugh, can't edit on mobile: meant to add that I'm on Android 6.0.1, and the visible symptoms of this issue are when you press play (in any chapter) the button graphic changes to the pause icon — but the timestamp doesn't advance — then a few seconds later the button reverts to the play icon (i.e. it doesn't crash the app).

@PaulWoitaschek
Copy link
Owner

Can you upload the file so I can look into it?

@foosinn
Copy link

foosinn commented Dec 29, 2017

I have the same issue. If you want i can send you an ebook link via email.

App-Version 3.6.1
LineageOS 7.1.2

@PaulWoitaschek
Copy link
Owner

Yes that would be great @foosinn

@foosinn
Copy link

foosinn commented Jan 5, 2018

Should be in your inbox @PaulWoitaschek

@PaulWoitaschek
Copy link
Owner

google/ExoPlayer#3670

@os97673
Copy link

os97673 commented Jun 25, 2019

It looks like ExoPlayer's bug has been fixed Jan 19, 2019. Time to close this one?

@PaulWoitaschek
Copy link
Owner

Yep. Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants