mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #1503] [Feature request] More ID3 Tags for better rich smart playlist #863
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#863
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @gelokatil on GitHub (Sep 14, 2022).
Original GitHub issue: https://github.com/koel/koel/issues/1503
I know that it has been commented on other occasions but I would like to propose that more ID3 tags be added to be able to create much more specific and rich smart playlists.
From my point of view I think it would be very useful to be able to create a playlist based on the physical path of the mp3 file, the directory more specifically. Currently if you have the music organized in albums everything is fine but surely many (myself included) will have directories with loose mp3s from different artists and different albums all mixed.
Also related to the creation of smart playlists, I find it useful to be able to use the ID3 tags of year and musical genre as filters.
Greetings
@phanan commented on GitHub (Sep 15, 2022):
Please read my reason for not supporting paths as a smart playlist's criterion here #1493.
@gelokatil commented on GitHub (Sep 15, 2022):
With all due respect, I don't quite agree with your reasoning. Koel is very user friendly in many aspects but to install/deploy it you have to have some knowledge about what you are doing and once you have it up and running you have to copy your music to where you have decided to install the service or you have to mount your shared resource by smb or nfs or link your S3 bucket, the option you have chosen.
I accept that maybe it is a functionality that is not useful for a large majority (I really do not think so, I do not believe that everyone has their music perfectly organized on discs and does not have any directory or directories with mixed music from multiple artists, albums, etc..)
In any case, I think it's a wonderful project and I appreciate all the time you dedicate to it and I fully understand that you have to assess and decide the time you invest to improve it day by day. :)
What do you think about adding the ID3 tags of music genre and year?
@qstar-inc commented on GitHub (Sep 19, 2022):
I understand and agree that users shouldn't have any context on the file location, but there should be more integration for other ID3 tags. On a typical MusicBrainz data import, there are so many tags; pretty sure some of them can be of good use.


Wait, year/genre tag doesn't exist?
@phanan commented on GitHub (Sep 21, 2022):
Year and genre are actually on my private roadmap :)