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]: add graphic audio to match provider list #3251

New Issue
Closed
opened 2026-04-25 00:14:31 +02:00 by adam · 4 comments
adam commented 2026-04-25 00:14:31 +02:00
Owner
Copy Link
Copy Source

Originally created by @djcprone on GitHub (Mar 4, 2026).

Type of Enhancement

None

Describe the Feature/Enhancement

There's a lot of well known GraphicAudio titles that aren't on audible. It would be awesome to have them in the provider list for matching for those cases.

There's a scraper at https://github.com/binyaminyblatt/graphicaudio_scraper that can be used alongside ABS and linked to via custom metadata provider but it would be awesome to have it built in like the other big names.

Why would this be helpful?

Save hours of manual meta data entering and editing.

Future Implementation (Screenshot)

Add Graphicaudio.net to provider dropdown in match tab of edit window

Audiobookshelf Server Version

2.32.1

Current Implementation (Screenshot)

No response

Originally created by @djcprone on GitHub (Mar 4, 2026). ### Type of Enhancement None ### Describe the Feature/Enhancement There's a lot of well known GraphicAudio titles that aren't on audible. It would be awesome to have them in the provider list for matching for those cases. There's a scraper at https://github.com/binyaminyblatt/graphicaudio_scraper that can be used alongside ABS and linked to via custom metadata provider but it would be awesome to have it built in like the other big names. ### Why would this be helpful? Save hours of manual meta data entering and editing. ### Future Implementation (Screenshot) Add Graphicaudio.net to provider dropdown in match tab of edit window ### Audiobookshelf Server Version 2.32.1 ### Current Implementation (Screenshot) _No response_
adam added the enhancement label 2026-04-25 00:14:31 +02:00
adam closed this issue 2026-04-25 00:14:31 +02:00
adam commented 2026-04-25 00:14:31 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Mar 4, 2026):

You will need to run this service yourself as a Custom Metadata Provider or point it at a URL from someone else hosting it. https://www.audiobookshelf.org/guides/custom-metadata-providers

We don't provide any scraping because it can easily get out of date as the metadata source changes how their website is set up.

@nichwall commented on GitHub (Mar 4, 2026): You will need to run this service yourself as a Custom Metadata Provider or point it at a URL from someone else hosting it. https://www.audiobookshelf.org/guides/custom-metadata-providers We don't provide any scraping because it can easily get out of date as the metadata source changes how their website is set up.
adam commented 2026-04-25 00:14:32 +02:00
Author
Owner
Copy Link
Copy Source

@djcprone commented on GitHub (Mar 4, 2026):

You will need to run this service yourself as a Custom Metadata Provider or point it at a URL from someone else hosting it. https://www.audiobookshelf.org/guides/custom-metadata-providers

We don't provide any scraping because it can easily get out of date as the metadata source changes how their website is set up.

Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA. I wasn't necessarily saying add the scraper, just trying to define the goal. I was hoping it was a thing you guys could just add without it being overly complicated for you.

I'm grateful ABS exists and that you thought to add the custom metadata provider option in the first place. Thank you for the reply!

@djcprone commented on GitHub (Mar 4, 2026): > You will need to run this service yourself as a Custom Metadata Provider or point it at a URL from someone else hosting it. https://www.audiobookshelf.org/guides/custom-metadata-providers > > We don't provide any scraping because it can easily get out of date as the metadata source changes how their website is set up. Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA. I wasn't necessarily saying add the scraper, just trying to define the goal. I was hoping it was a thing you guys could just add without it being overly complicated for you. I'm grateful ABS exists and that you thought to add the custom metadata provider option in the first place. Thank you for the reply!
adam commented 2026-04-25 00:14:32 +02:00
Author
Owner
Copy Link
Copy Source

@nichwall commented on GitHub (Mar 4, 2026):

Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA.

We use public APIs that do not change (I.e. location or content). For anything that does not provide a public API (like Graphic audio) we use our Custom metadata spec that projects can build against so it can be used as a metadata source for Audiobookshelf, which is what that project has done by having an Audiobookshelf configuration.

Unless there is a well defined public API that doesn't change over time, Graphic Audio will need to remain as a custom metadata provider.

@nichwall commented on GitHub (Mar 4, 2026): > Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA. We use public APIs that do not change (I.e. location or content). For anything that does not provide a public API (like Graphic audio) we use our Custom metadata spec that projects can build against so it can be used as a metadata source for Audiobookshelf, which is what that project has done by having an Audiobookshelf configuration. Unless there is a well defined public API that doesn't change over time, Graphic Audio will need to remain as a custom metadata provider.
adam commented 2026-04-25 00:14:32 +02:00
Author
Owner
Copy Link
Copy Source

@djcprone commented on GitHub (Mar 4, 2026):

Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA.

We use public APIs that do not change (I.e. location or content). For anything that does not provide a public API (like Graphic audio) we use our Custom metadata spec that projects can build against so it can be used as a metadata source for Audiobookshelf, which is what that project has done by having an Audiobookshelf configuration.

Unless there is a well defined public API that doesn't change over time, Graphic Audio will need to remain as a custom metadata provider.

Fair enough, thank you!

@djcprone commented on GitHub (Mar 4, 2026): > > Yeah that was my intention in the meantime anyway. I don't know how the backend of things work, like how you get the data from the providers you already have in the dropdown menu currently like audible and what not, so I didn't know what would be involved in adding GA. > > We use public APIs that do not change (I.e. location or content). For anything that does not provide a public API (like Graphic audio) we use our Custom metadata spec that projects can build against so it can be used as a metadata source for Audiobookshelf, which is what that project has done by having an Audiobookshelf configuration. > > Unless there is a well defined public API that doesn't change over time, Graphic Audio will need to remain as a custom metadata provider. Fair enough, thank you!
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#3251
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?