[GH-ISSUE #315] More available metadata

kerem commented

2026-02-26 02:32:30 +03:00

Owner

Originally created by @alex-phillips on GitHub (Apr 22, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/315

Would you be willing to accept a PR that allows koel to read and store additional metadata than what it currently stores? i.e., year, disc number, genre? I'd be happy to implement, but would want to know if you'd be willing to merge before doing the work.

I'm loving using koel's backend / api, but would love access to additional information. I can incorporate these additional fields into the frontend as well if you'd like.

Originally created by @alex-phillips on GitHub (Apr 22, 2016). Original GitHub issue: https://github.com/koel/koel/issues/315 Would you be willing to accept a PR that allows koel to read and store additional metadata than what it currently stores? i.e., year, disc number, genre? I'd be happy to implement, but would want to know if you'd be willing to merge before doing the work. I'm loving using koel's backend / api, but would love access to additional information. I can incorporate these additional fields into the frontend as well if you'd like.

kerem closed this issue

2026-02-26 02:32:30 +03:00

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@phanan commented on GitHub (Apr 23, 2016):

I'm not against it, but what's the point of storing data that you won't be using? Audio tags can be very messy (for example Genre), when I prefer to keep the data minimal.

@phanan commented on GitHub (Apr 23, 2016): I'm not against it, but what's the point of storing data that you won't be using? Audio tags can be very messy (for example Genre), when I prefer to keep the data minimal.

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@alex-phillips commented on GitHub (Apr 23, 2016):

I'd like to eventually fully replace iTunes with koel but I believe iTunes had a really good handle on managing meta data. I think adding what I believe is the essentials it brings koel closer to bridging that gap.

@alex-phillips commented on GitHub (Apr 23, 2016): I'd like to eventually fully replace iTunes with koel but I believe iTunes had a really good handle on managing meta data. I think adding what I believe is the essentials it brings koel closer to bridging that gap.

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@phanan commented on GitHub (Apr 23, 2016):

Koel is not meant to replace iTunes actually, at least in meta data
management, because meta data in Koel are only stored in the database and
not tied to the files.

On Sat, Apr 23, 2016 at 8:33 PM, Alex Phillips notifications@github.com
wrote:

I'd like to eventually fully replace iTunes with koel but I believe iTunes
had a really good handle on managing meta data. I think adding what I
believe is the essentials it brings koel closer to bridging that gap.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/phanan/koel/issues/315#issuecomment-213733197

@phanan commented on GitHub (Apr 23, 2016): Koel is not meant to replace iTunes actually, at least in meta data management, because meta data in Koel are only stored in the database and not tied to the files. On Sat, Apr 23, 2016 at 8:33 PM, Alex Phillips notifications@github.com wrote: > I'd like to eventually fully replace iTunes with koel but I believe iTunes > had a really good handle on managing meta data. I think adding what I > believe is the essentials it brings koel closer to bridging that gap. > > — > You are receiving this because you commented. > Reply to this email directly or view it on GitHub > https://github.com/phanan/koel/issues/315#issuecomment-213733197

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@alex-phillips commented on GitHub (Apr 23, 2016):

I agree. But koel does store the data in a unified and accessible manner. Similar to how XBMC does this. It also doesn't write to the files directly. I understand that koel doesn't manage writing the meta data to the file, but I feel that if you wanted to then use some other software to write the meta data later, it's extremely easy to harness koels storage and write the data to the file.

@alex-phillips commented on GitHub (Apr 23, 2016): I agree. But koel does store the data in a unified and accessible manner. Similar to how XBMC does this. It also doesn't write to the files directly. I understand that koel doesn't manage writing the meta data to the file, but I feel that if you wanted to then use some other software to write the meta data later, it's extremely easy to harness koels storage and write the data to the file.

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@alex-phillips commented on GitHub (Apr 23, 2016):

Also, if you feel these additions could be handled in a plug in instead, I wouldn't be against that. I'm assuming laravel has support for plug-ins with its own data base migrations?

Not entirely sure yet about how the front end would handle plug-ins though...

@alex-phillips commented on GitHub (Apr 23, 2016): Also, if you feel these additions could be handled in a plug in instead, I wouldn't be against that. I'm assuming laravel has support for plug-ins with its own data base migrations? Not entirely sure yet about how the front end would handle plug-ins though...

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@kirkegaard commented on GitHub (Apr 28, 2016):

Im not sure if this is the right place to post this but it seemed to be a similar issue.

I have a bunch of m4a files from iTunes, but it seems like koel doesnt know how to read the id tags on these files. I dont know if m4a uses a different format for id tags. But creating mp3 versions of the files seems to work though. Would it be possible to read metadata from m4a files as well?

@kirkegaard commented on GitHub (Apr 28, 2016): Im not sure if this is the right place to post this but it seemed to be a similar issue. I have a bunch of m4a files from iTunes, but it seems like koel doesnt know how to read the id tags on these files. I dont know if m4a uses a different format for id tags. But creating mp3 versions of the files seems to work though. Would it be possible to read metadata from m4a files as well?

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@phanan commented on GitHub (Apr 28, 2016):

Koel uses getID3 for tag reading, which has support for a lot of different formats – m4a files included. You may want to check with that repo.

@phanan commented on GitHub (Apr 28, 2016): Koel uses [getID3](https://github.com/JamesHeinrich/getID3) for tag reading, which has support for a lot of different formats – m4a files included. You may want to check with that repo.

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@alex-phillips commented on GitHub (Apr 30, 2016):

PR here for metadata as well as my reasoning behind including them: https://github.com/phanan/koel/pull/318

@alex-phillips commented on GitHub (Apr 30, 2016): PR here for metadata as well as my reasoning behind including them: https://github.com/phanan/koel/pull/318

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@Amunak commented on GitHub (Jul 26, 2018):

Adding on to this, how hard would it be to just save all the metadata and let the user decide which ones they want to display, sort by and such? Or at least having a selection of saved tags globally in the config (.env).

Like, currently Koel assumes that everyone has "regular" music with properly filled in artists and albums, but it fails completely (in usability) when you have, for example, tons of different music with a few songs of each artist or album - you'd then have to remember and search for every song manually.

I use custom ID3 tags to solve this issue when playing locally - I add the custom tags into FooBar2000 as a custom column and sort, filter or group by that. Would be great if Koel could support such use cases as well. I was honestly disappointed that an application with like 400 megs of dependencies can barely display five data points about each song and search that very crudely.

@Amunak commented on GitHub (Jul 26, 2018): Adding on to this, how hard would it be to just save all the metadata and let the user decide which ones they want to display, sort by and such? Or at least having a selection of saved tags globally in the config (.env). Like, currently Koel assumes that everyone has "regular" music with properly filled in artists and albums, but it fails completely (in usability) when you have, for example, tons of different music with a few songs of each artist or album - you'd then have to remember and search for every song manually. I use custom ID3 tags to solve this issue when playing locally - I add the custom tags into FooBar2000 as a custom column and sort, filter or group by that. Would be great if Koel could support such use cases as well. I was honestly disappointed that an application with like 400 megs of dependencies can barely display five data points about each song and search that very crudely.

kerem commented

2026-02-26 02:32:31 +03:00

Author

Owner

@JBlond commented on GitHub (Aug 7, 2022):

m4b support would also be nice

@JBlond commented on GitHub (Aug 7, 2022): m4b support would also be nice

Rows
Columns

[GH-ISSUE #315] More available metadata #231