Originally created by @dedors on GitHub (Oct 22, 2023).
Is your feature request related to a problem? Please describe.
I listen to a book at the day and a episode of a series to fall asleep. I never want to listen to my night books other than 1x. I have to switch speeds every day.
Other usecases maybe: podcasts at higher speed (which may have it's own series or library too).
Describe the solution you'd like
Easy: add option "remember playbackspeed per book"
Describe alternatives you've considered
Advanced (optimal for my usecase): Add a option with a dropdown list:
Remember Playback speed:
- Always (default)
- per Book
- per Series *would be my setting
- per Library
Originally created by @dedors on GitHub (Oct 22, 2023).
### Is your feature request related to a problem? Please describe.
I listen to a book at the day and a episode of a series to fall asleep. I never want to listen to my night books other than 1x. I have to switch speeds every day.
Other usecases maybe: podcasts at higher speed (which may have it's own series or library too).
### Describe the solution you'd like
Easy: add option "remember playbackspeed per book"
### Describe alternatives you've considered
Advanced (optimal for my usecase): Add a option with a dropdown list:
```
Remember Playback speed:
- Always (default)
- per Book
- per Series *would be my setting
- per Library
```
Would you expect this selected playback speed to sync with the server?
@advplyr commented on GitHub (Oct 22, 2023):
Related issue https://github.com/advplyr/audiobookshelf/issues/1785
Would you expect this selected playback speed to sync with the server?
Would you expect this selected playback speed to sync with the server?
yes (but would not matter much)
@dedors commented on GitHub (Oct 22, 2023):
sorry did a bad job in searching with this one
> Would you expect this selected playback speed to sync with the server?
yes (but would not matter much)
Ah okay then this belongs in the server repo. It's unlikely this is added anytime soon if at all because of the UI/UX challenges so I'll put as a dupe of that existing issue
@advplyr commented on GitHub (Oct 22, 2023):
Ah okay then this belongs in the server repo. It's unlikely this is added anytime soon if at all because of the UI/UX challenges so I'll put as a dupe of that existing issue
If it just remember it on the client side, it would be sufficient. At least a lot better than switching all the time.
If that would be easier to implement.
@dedors commented on GitHub (Oct 24, 2023):
If it just remember it on the client side, it would be sufficient. At least a lot better than switching all the time.
If that would be easier to implement.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dedors on GitHub (Oct 22, 2023).
Is your feature request related to a problem? Please describe.
I listen to a book at the day and a episode of a series to fall asleep. I never want to listen to my night books other than 1x. I have to switch speeds every day.
Other usecases maybe: podcasts at higher speed (which may have it's own series or library too).
Describe the solution you'd like
Easy: add option "remember playbackspeed per book"
Describe alternatives you've considered
Advanced (optimal for my usecase): Add a option with a dropdown list:
@advplyr commented on GitHub (Oct 22, 2023):
Related issue https://github.com/advplyr/audiobookshelf/issues/1785
Would you expect this selected playback speed to sync with the server?
@dedors commented on GitHub (Oct 22, 2023):
sorry did a bad job in searching with this one
yes (but would not matter much)
@advplyr commented on GitHub (Oct 22, 2023):
Ah okay then this belongs in the server repo. It's unlikely this is added anytime soon if at all because of the UI/UX challenges so I'll put as a dupe of that existing issue
@advplyr commented on GitHub (Oct 22, 2023):
Duplicate of https://github.com/advplyr/audiobookshelf/issues/1785
@dedors commented on GitHub (Oct 24, 2023):
If it just remember it on the client side, it would be sufficient. At least a lot better than switching all the time.
If that would be easier to implement.