advplyr

You may be still mapping to an old database because if this is a fresh install then you would be prompted to set a password.

Yes, this project is very active. You will have to check the server logs to see what the crash is. The best place for support is in the Discord or on Github because there are many people helping to answer questions there.

The podcast episode schedule has to be adjusted on each individual podcast. There is no global setting for podcast schedule. To adjust the schedule press edit on a podcast and go to the "Schedule" tab.

Hey the database changed to sqlite. At the moment you will have to open the database and go to the "users" table and remove the password hash in the column "pash". I'm not sure how familiar you are with databases but the easiest way is probably to get a software that gives you a GUI. There are many ways

I'm trying to reproduce this issue but unable. Are you able to reproduce this? If so, can you give me steps to reproduce?

Anyone with issues during the migration to v2.3.0 please follow the instructions for v2.3.1 https://github.com/advplyr/audiobookshelf/releases/tag/v2.3.1

I'm pushing a patch soon that fixes a few bugs with the previous release. Make sure to check the release notes because you will need to manually delete the `/config/absdatabase.sqlite` before upgrading so the migration can run again.

Sure, you can put a feature request in github

Are you making sure to put the "https://" part of the server address? If you join the Discord/Matrix server there are also many more users on there with various setups that are helping others.

I haven't but you could try going into settings on your device and disabling battery optimization for the app. I think the battery optimization on some devices can kill the background process.

Thanks for asking, I haven't set anything up yet.

This is currently not being worked on. I've made a few attempts at it but unfortunately the way I built the web client makes this very difficult to implement. Possibly may require a rewrite of the client so it hasn't taken priority. The issue to follow for this is https://github.com/advplyr/audiobookshelf/issues/385

There is a bug in the iOS app. You can delete those bad sessions for now

Abs is using 744 for permissions. For me it's the rootshare to windows that is the issue, I need the rootshare to have owner permissions but haven't looked into that yet.

I noticed this yesterday with a podcast folder that was created and wasn't sure if it was a one-off issue. Every folder/file that is created by abs should have the permissions set the same and use the UID/GID in your config. Maybe I forgot to set them for the podcast folders/episode files.

That entire library item is missing. You most likely need to remove it and scan your library again. There should be an issues page showing and there is a remove all button that will remove all those missing library items.

Someone else mentioned this too but this is already how it works. I put a gif of it here: https://github.com/advplyr/audiobookshelf-app/discussions/366#discussioncomment-3560825 I mention that the UI right now is not ideal and I intend to make it more clear that you are dragging the progress bar.

For the seek bar we are also working on having the track on the notification use the chapter track setting if you have that enabled. I'm not sure if you are aware of that setting but you can enable use chapter track which will convert the progress bar to be for each chapter instead of the entire audiobook. The notification doesn't respect that setting yet though, you can track that issue here: https://github.com/advplyr/audiobookshelf-app/issues/239 Agreed, Android permissions have been a nightmare to work with.

You can adjust the jump back amount to up to 30 seconds. We plan on adding some form of history on when you took various actions such as play/pause/seek so you can see your playback time and jump back to it if you made an error. That should help with accidental changes. You can also lock the player now but that doesn't lock the progress bar shown on the lockscreen yet though. I'm not sure how PlexAMP detects vehicle movement unless it is getting some extra permissions from you.

Not sure about donations yet. You are correct on the number of days you have listened and I agree it is confusing. I'm open to suggestions on stats. I built the page off of a design that was requested: https://github.com/advplyr/audiobookshelf/discussions/167

I think I closed most of the goodreads requests in github but it has been mentioned a lot. Goodreads won't be supported because they discontinued their public API and Abs is not going to do any web scraping itself. If someone built out a solid reliable Goodreads api that was free and public we would implement it.

I think this github request opened today is relevant to what you're saying https://github.com/advplyr/audiobookshelf/issues/870 but not regarding the folder structure. There was another issue brought up a while ago about folder structure for something like this but no good solution was found. Abs is not going to pull in your folder structure correctly and I don't see that being supported until we figure out a way to allow customizing the folder scanner. I think your best option is to either put the books in a folder structure for the sub-series and add the overarching series manually in the UI, or vice-versa. I want to add that I'm open to solving this since it's been brought up a few times but no one has put forward a solid solution. If you have ideas and want to chat about it the discord server is very active.

How did that book get scanned in? Looking at that folder structure I think abs would scan that in as an audiobook named "D01" with 1 audio file. You'll need to remove those D01 folders or rename them CD01. Abs will detect the disc folders if they are CD01, CD02, etc.

This is great, thanks for the overview and the screenshots. I will make note of this feature.

Unfortunately that metadata will only be filled in if you download the episode from audiobookshelf. The match feature only matches the podcast metadata and not the individual episodes. This is something we still need to build out and I forgot about it actually since there is no github issue opened for that yet.