Buffer/cache to prevent redownloading content on auto-rewind. #159

Closed
opened 2026-04-24 23:10:08 +02:00 by adam · 3 comments
Owner

Originally created by @DDriggs00 on GitHub (May 23, 2022).

Is your feature request related to a problem? Please describe.

When resuming after more than a couple seconds, the player skips back a few seconds. When this happens, it takes some time to resume, presumably to re-download the part to be replayed.

Describe the solution you'd like

Keep a cache/buffer going back the maximum length of auto-rewind, so there will not be a requirement to re-download any content on resuming playback.

Originally created by @DDriggs00 on GitHub (May 23, 2022). ### Is your feature request related to a problem? Please describe. When resuming after more than a couple seconds, the player skips back a few seconds. When this happens, it takes some time to resume, presumably to re-download the part to be replayed. ### Describe the solution you'd like Keep a cache/buffer going back the maximum length of auto-rewind, so there will not be a requirement to re-download any content on resuming playback.
adam added the enhancement label 2026-04-24 23:10:08 +02:00
adam closed this issue 2026-04-24 23:10:09 +02:00
Author
Owner

@DieselTech commented on GitHub (May 25, 2022):

To add on to that: In my opinion if a book is 'on deck' it should stay transcoded and ready to until it's marked as finished.

I'm seeing the long wait times without even skipping around. Just starting up a session again after not playing it for a while makes it wait. It looks like FFmpeg is only using a single thread during all of this, so on a multi-hour book it will take time to finish.

@DieselTech commented on GitHub (May 25, 2022): To add on to that: In my opinion if a book is 'on deck' it should stay transcoded and ready to until it's marked as finished. I'm seeing the long wait times without even skipping around. Just starting up a session again after not playing it for a while makes it wait. It looks like FFmpeg is only using a single thread during all of this, so on a multi-hour book it will take time to finish.
Author
Owner

@advplyr commented on GitHub (May 25, 2022):

In the majority of cases the item is not getting transcoded anymore, it is getting direct played on your device.

Unless you are using Flac, Opus, Ogg, or other less supported audio formats then it is direct playing the audio file. I'm not sure how to handle buffering or caching a direct play since all of that is handled natively via the browser or via the audio player on your mobile device.
I'm sure there is something we can do here but I haven't dug into it yet.

@advplyr commented on GitHub (May 25, 2022): In the majority of cases the item is not getting transcoded anymore, it is getting direct played on your device. Unless you are using Flac, Opus, Ogg, or other less supported audio formats then it is direct playing the audio file. I'm not sure how to handle buffering or caching a direct play since all of that is handled natively via the browser or via the audio player on your mobile device. I'm sure there is something we can do here but I haven't dug into it yet.
Author
Owner

@advplyr commented on GitHub (Aug 7, 2022):

There is an open issue for keeping the transcode which if implemented might solve your issue https://github.com/advplyr/audiobookshelf/issues/768

That being said direct play should be working for the majority of cases. There was a bug with firefox and direct play m4b but that should be fixed now also.

@advplyr commented on GitHub (Aug 7, 2022): There is an open issue for keeping the transcode which if implemented might solve your issue https://github.com/advplyr/audiobookshelf/issues/768 That being said direct play should be working for the majority of cases. There was a bug with firefox and direct play m4b but that should be fixed now also.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf-app#159