starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Enhancement]: Build in Audible DRM removal #1538

New Issue
Closed
opened 2026-04-24 23:49:17 +02:00 by adam · 7 comments
adam commented 2026-04-24 23:49:17 +02:00
Owner
Copy Link
Copy Source

Originally created by @therecluse26 on GitHub (Nov 20, 2023).

Describe the feature/enhancement

This repo allows the user to find their Audible file's activation bytes and generate/run ffmpeg to strip Audible's DRM: https://audible-tools.kamsker.at/

It'd be fantastic if you could just bundle this in as a feature so that you can just directly import an Audible audiobook file and have Audiobookshelf strip the DRM during the upload process.

PS: your site's background bookshelf is extremely based.

Originally created by @therecluse26 on GitHub (Nov 20, 2023). ### Describe the feature/enhancement This repo allows the user to find their Audible file's activation bytes and generate/run ffmpeg to strip Audible's DRM: https://audible-tools.kamsker.at/ It'd be fantastic if you could just bundle this in as a feature so that you can just directly import an Audible audiobook file and have Audiobookshelf strip the DRM during the upload process. PS: your site's background bookshelf is extremely based.
adam added the enhancement label 2026-04-24 23:49:17 +02:00
adam closed this issue 2026-04-24 23:49:17 +02:00
adam commented 2026-04-24 23:49:18 +02:00
Author
Owner
Copy Link
Copy Source

@emigrating commented on GitHub (Nov 20, 2023):

I personally use Libation for my Audible backups and don't really see why a media server software should offer the same functionality.

I mean, sure, it's very easy to get around the DRM Audible utilizes, but this is just scope creep IMO and you end up with a jack of all trades, master of none kind of product. AFAIK, neither Plex nor Jellyfin (or any of the other servers) offer a way for you to rip your BDs natively?

Just my $0.02 worth though.

@emigrating commented on GitHub (Nov 20, 2023): I personally use Libation for my Audible backups and don't really see why a media _server_ software should offer the same functionality. I mean, sure, it's very easy to get around the DRM Audible utilizes, but this is just scope creep IMO and you end up with a jack of all trades, master of none kind of product. AFAIK, neither Plex nor Jellyfin (or any of the other servers) offer a way for you to rip your BDs natively? Just my $0.02 worth though.
adam commented 2026-04-24 23:49:20 +02:00
Author
Owner
Copy Link
Copy Source

@therecluse26 commented on GitHub (Nov 20, 2023):

@emigrating I disagree. I think that one of the most common use cases for using something like Audiobookshelf is to regain true ownership over purchased Audible books, and I'd bet that a substantial portion of this app's user base has to go through the painful task of manually ripping DRM from their Audible files before uploading. I think it's unfair to characterize a convenience feature that would benefit a large portion of your users as "scope creep," especially when the code for the feature already exists.

If I made a PR to integrate this feature, would it be worth my time to build or would it be rejected?

@therecluse26 commented on GitHub (Nov 20, 2023): @emigrating I disagree. I think that one of the most common use cases for using something like Audiobookshelf is to regain true ownership over purchased Audible books, and I'd bet that a substantial portion of this app's user base has to go through the painful task of manually ripping DRM from their Audible files before uploading. I think it's unfair to characterize a convenience feature that would benefit a large portion of your users as "scope creep," especially when the code for the feature already exists. If I made a PR to integrate this feature, would it be worth my time to build or would it be rejected?
adam commented 2026-04-24 23:49:21 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Nov 20, 2023):

There are currently no plans for DRM removal to be included within ABS. There are already a number of other tools which do this.

It could be a plugin (like how Calibre does it), but there is not a timetable on when plugin support will be added

@nichwall commented on GitHub (Nov 20, 2023): There are currently no plans for DRM removal to be included within ABS. There are already a number of other tools which do this. It could be a plugin (like how Calibre does it), but there is not a timetable on when plugin support will be added
adam commented 2026-04-24 23:49:21 +02:00
Author
Owner
Copy Link
Copy Source

@emigrating commented on GitHub (Nov 20, 2023):

one of the most common use cases [...] is to regain true ownership over purchased Audible books,

Could be, but reading posts on social media about ABS it seems like more people are using it to easily share "their" books with friends and family rather than as a front-end to their Audible library back-up (where the UX is, let's be honest, not up to par with Audible currently - no Android Wear support, Android Auto is real wonky, there's no Alexa skill, title postition logging oftentimes doesn't update properly when going from app to web or vice versa).

this app's user base has to go through the painful task of manually ripping DRM [even though the code is readily available].

Try using Libation. Not only is it not painful (you can set it up to automatically check and "liberate" your files as and when you purchase new books) but I'd say it offers a better experience than ABS would be able to do without a lot of backend work.

As for feature or scope creep, I'd say this is a textbook example of such a thing. It's kinda like producing a bread slicing machine, then you realize some people like their bread toasted, so you add a toaster oven to the existing slicer. Fine, not a big deal, toasters are already a thing, it's easy to add. Then, someone says they only eat PB&J sandwiches while their brother only eats grilled cheese, so you add both of these features. And the ball is in motion to end up with a chinese machine that does everything badly rather than excel at one or a few things.

If I made a PR to integrate this feature, would it be rejected?

Sorry if this didn't come across previously, I have nothing to do with this project as such. I was just offering my thoughts on the subject.

Again, this is just my 2 cents and I wouldn't even try to block a PR if it came along (as long as it didn't cause other bugs or attack vectors), I'd just not use it myself.

It could be a plugin (like how Calibre does it), but there is not a timetable on when plugin support will be added

Yes, this would be a perfectly acceptable solution IMO.

@emigrating commented on GitHub (Nov 20, 2023): > one of the most common use cases [...] is to regain true ownership over purchased Audible books, Could be, but reading posts on social media about ABS it seems like more people are using it to easily share "their" books with friends and family rather than as a front-end to their Audible library back-up (where the UX is, let's be honest, not up to par with Audible currently - no Android Wear support, Android Auto is real wonky, there's no Alexa skill, title postition logging oftentimes doesn't update properly when going from app to web or vice versa). > this app's user base has to go through the painful task of manually ripping DRM [even though the code is readily available]. Try using Libation. Not only is it not painful (you can set it up to automatically check and "liberate" your files as and when you purchase new books) but I'd say it offers a better experience than ABS would be able to do without a lot of backend work. As for feature or scope creep, I'd say this is a textbook example of such a thing. It's kinda like producing a bread slicing machine, then you realize some people like their bread toasted, so you add a toaster oven to the existing slicer. Fine, not a big deal, toasters are already a thing, it's easy to add. Then, someone says they only eat PB&J sandwiches while their brother only eats grilled cheese, so you add both of these features. And the ball is in motion to end up with a chinese machine that does everything badly rather than excel at one or a few things. > If I made a PR to integrate this feature, would it be rejected? Sorry if this didn't come across previously, I have nothing to do with this project as such. I was just offering my thoughts on the subject. Again, this is just my 2 cents and I wouldn't even try to block a PR if it came along (as long as it didn't cause other bugs or attack vectors), I'd just not use it myself. > It could be a plugin (like how Calibre does it), but there is not a timetable on when plugin support will be added Yes, this would be a perfectly acceptable solution IMO.
adam commented 2026-04-24 23:49:21 +02:00
Author
Owner
Copy Link
Copy Source

@therecluse26 commented on GitHub (Nov 20, 2023):

@emigrating I appreciate your thoughts. I haven't used Libation, but I'll give it a shot.

If Audiobookshelf does add plugin support in the future, I'd be happy to develop this as one @nichwall

@therecluse26 commented on GitHub (Nov 20, 2023): @emigrating I appreciate your thoughts. I haven't used Libation, but I'll give it a shot. If Audiobookshelf does add plugin support in the future, I'd be happy to develop this as one @nichwall
adam commented 2026-04-24 23:49:22 +02:00
Author
Owner
Copy Link
Copy Source

@therecluse26 commented on GitHub (Nov 20, 2023):

One last thing on the "scope creep" point. Audiobookshelf has e-book support. That feels like a much larger instance of scope creep than what I'm suggesting.

@therecluse26 commented on GitHub (Nov 20, 2023): One last thing on the "scope creep" point. Audiobookshelf has e-book support. That feels like a much larger instance of scope creep than what I'm suggesting.
adam commented 2026-04-24 23:49:22 +02:00
Author
Owner
Copy Link
Copy Source

@Sapd commented on GitHub (Nov 21, 2023):

Btw. a feature like this can bring the developer, the project owner and possibly users into a difficult legal position.
For example in JDownloader some random guy did a PR for something like this, and their CI build it; JDownloader was then sued and had to pay a fine.

See also https://www.linux-magazin.de/ausgaben/2014/04/recht/ (article in German).

I would also advise everyone developing such a feature, to check the laws in their respective country.

@Sapd commented on GitHub (Nov 21, 2023): Btw. a feature like this can bring the developer, the project owner and possibly users into a difficult legal position. For example in JDownloader some random guy did a PR for something like this, and their CI build it; JDownloader was then sued and had to pay a fine. See also https://www.linux-magazin.de/ausgaben/2014/04/recht/ (article in German). I would also advise everyone developing such a feature, to check the laws in their respective country.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1538
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?