Originally created by @Klaesy on GitHub (Jun 16, 2022).
Currently the app automatically rolls back 30 seconds after resuming playback. That is fine when you are somewhere halfway in a story, but not when you just finished a Chapter and stop playback just after the start of a new Chapter. It's usually not very useful or desirable to hear the last 30 seconds of a Chapter.
That's why I am proposing that the rollback doesn't go past Chapter markers. So if a new chapter started within the rollback time it doesn't fully rollback but instead starts playback at the Chapter marker.
Originally created by @Klaesy on GitHub (Jun 16, 2022).
Currently the app automatically rolls back 30 seconds after resuming playback. That is fine when you are somewhere halfway in a story, but not when you just finished a Chapter and stop playback just after the start of a new Chapter. It's usually not very useful or desirable to hear the last 30 seconds of a Chapter.
That's why I am proposing that the rollback doesn't go past Chapter markers. So if a new chapter started within the rollback time it doesn't fully rollback but instead starts playback at the Chapter marker.
I think this makes sense. The auto-rewind is also too sensitive. On a road trip and using navigation if the directions being announced is longer than a few seconds it triggers the rewind, which happens frequently back-to-back.
I think we need to re-define the auto-rewind functionality.
@advplyr commented on GitHub (Jun 17, 2022):
I think this makes sense. The auto-rewind is also too sensitive. On a road trip and using navigation if the directions being announced is longer than a few seconds it triggers the rewind, which happens frequently back-to-back.
I think we need to re-define the auto-rewind functionality.
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 @Klaesy on GitHub (Jun 16, 2022).
Currently the app automatically rolls back 30 seconds after resuming playback. That is fine when you are somewhere halfway in a story, but not when you just finished a Chapter and stop playback just after the start of a new Chapter. It's usually not very useful or desirable to hear the last 30 seconds of a Chapter.
That's why I am proposing that the rollback doesn't go past Chapter markers. So if a new chapter started within the rollback time it doesn't fully rollback but instead starts playback at the Chapter marker.
@advplyr commented on GitHub (Jun 17, 2022):
I think this makes sense. The auto-rewind is also too sensitive. On a road trip and using navigation if the directions being announced is longer than a few seconds it triggers the rewind, which happens frequently back-to-back.
I think we need to re-define the auto-rewind functionality.
@advplyr commented on GitHub (Jul 3, 2022):
Added in 0.9.50-beta