-
Notifications
You must be signed in to change notification settings - Fork 450
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Quick embed metadata failing #3323
Labels
bug
Something isn't working
Comments
Is the file stored in the root folder and not inside of a subdirectory? |
It is inside of a subdirectory, I shortened the upper path for privacy reasons. Real path would be something like EDIT: After reading what you referenced to I can confirm: the file is stored in the root folder of the library I added and the audiobook is single-filed. |
advplyr
added
the
awaiting release
Issue is resolved and will be in the next release
label
Aug 24, 2024
Fixed in v2.13.0. |
github-actions
bot
removed
the
awaiting release
Issue is resolved and will be in the next release
label
Aug 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When trying to quick embed metadata into a (test) file I get the error
ENOTDIR, ERROR: [AudioMetadataManager] Target directory is not writable
and the metadata is not embedded.
What did you expect to happen?
Metadata to be embedded and if this fails for a message to pop up. Here just nothing happened and at first I thought it finished properly.
Steps to reproduce the issue
Audiobookshelf version
v2.12.3
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
Sorry in advance if something is not perfect, this is my first bug report.
This is on a Qnap QTS TS-877. I mounted a shared folder /share.../.../ to /data. I checked permissions, but they are all 777 or 666 and from within the containers shell using "docker exec -it sh" I can access and move/copy everything.
Important: This bug only occurs if the version is higher than 2.11.0. If I downgrade to 2.11.0 everything just works fine.
The text was updated successfully, but these errors were encountered: