Originally created by @JamesDean3 on GitHub (Apr 27, 2022).
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When using these new features as we know there can be problems that cause the app to crash or something to go wrong some where along the way, often times that will make us lose our current position in our audiobook and not have the correct position reported anywhere.
Describe the solution you'd like
A clear and concise description of what you want to happen.
The "Recent Listening Session" does a great job at telling us how long we listened to something and how long ago it was we listened to it, but if it were to put what our current progress through the audiobook was, we would be able to find our placement after running in to any unexpected issues that caused the app to crash.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've tried to use the information given in the "Recent Listening Session" to figure out my placement in the audiobook, but I haven't been successful. That and possibility remembering the chapter is the only solutions I can think of.
Additional context
Add any other context or screenshots about the feature request here.
Once things are more stable then I imagine this feature won't be quite as useful, since the actual designated spot should show the current time your at, but I can still see it being useful, for example, you fall asleep and forget to put the sleep timer on, you can see the last place you started at and find your place by moving forward instead of backwards, which could possibility cause you to hear something you would have rather not heard yet.
Thank you for your work in this project, I think it is turning out great
Originally created by @JamesDean3 on GitHub (Apr 27, 2022).
### Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When using these new features as we know there can be problems that cause the app to crash or something to go wrong some where along the way, often times that will make us lose our current position in our audiobook and not have the correct position reported anywhere.
### Describe the solution you'd like
A clear and concise description of what you want to happen.
The "Recent Listening Session" does a great job at telling us how long we listened to something and how long ago it was we listened to it, but if it were to put what our current progress through the audiobook was, we would be able to find our placement after running in to any unexpected issues that caused the app to crash.
### Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've tried to use the information given in the "Recent Listening Session" to figure out my placement in the audiobook, but I haven't been successful. That and possibility remembering the chapter is the only solutions I can think of.
### Additional context
Add any other context or screenshots about the feature request here.
Once things are more stable then I imagine this feature won't be quite as useful, since the actual designated spot should show the current time your at, but I can still see it being useful, for example, you fall asleep and forget to put the sleep timer on, you can see the last place you started at and find your place by moving forward instead of backwards, which could possibility cause you to hear something you would have rather not heard yet.
Thank you for your work in this project, I think it is turning out great
I posted this feature request in the wrong github, I copied and pasted it into the correct github, you can find it here
@JamesDean3 commented on GitHub (Apr 28, 2022):
I posted this feature request in the wrong github, I copied and pasted it into the correct github, you can find it [here](https://github.com/advplyr/audiobookshelf/issues/532)
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 @JamesDean3 on GitHub (Apr 27, 2022).
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When using these new features as we know there can be problems that cause the app to crash or something to go wrong some where along the way, often times that will make us lose our current position in our audiobook and not have the correct position reported anywhere.
Describe the solution you'd like
A clear and concise description of what you want to happen.
The "Recent Listening Session" does a great job at telling us how long we listened to something and how long ago it was we listened to it, but if it were to put what our current progress through the audiobook was, we would be able to find our placement after running in to any unexpected issues that caused the app to crash.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I've tried to use the information given in the "Recent Listening Session" to figure out my placement in the audiobook, but I haven't been successful. That and possibility remembering the chapter is the only solutions I can think of.
Additional context
Add any other context or screenshots about the feature request here.
Once things are more stable then I imagine this feature won't be quite as useful, since the actual designated spot should show the current time your at, but I can still see it being useful, for example, you fall asleep and forget to put the sleep timer on, you can see the last place you started at and find your place by moving forward instead of backwards, which could possibility cause you to hear something you would have rather not heard yet.
Thank you for your work in this project, I think it is turning out great
@JamesDean3 commented on GitHub (Apr 28, 2022):
I posted this feature request in the wrong github, I copied and pasted it into the correct github, you can find it here