starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 08:46:00 +03:00

[GH-ISSUE #200] When moving files around, playlists songs are not kept #143

New issue

Closed

opened 2026-02-26 02:32:16 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @tomcodes on GitHub (Jan 22, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/200

I have around 4000 files in library and have reorganized all of them. I noticed all the songs I had added to playlists have been lost (but the playlists are kept).

It would be interesting to keep songs in playlists even when files are moved.

I understand song_id is generated based on the path of your song so it might be complicated to generate song_id based on something else, like a fingerprint of the track.

I will try to look into it.

Originally created by @tomcodes on GitHub (Jan 22, 2016). Original GitHub issue: https://github.com/koel/koel/issues/200 I have around 4000 files in library and have reorganized all of them. I noticed all the songs I had added to playlists have been lost (but the playlists are kept). It would be interesting to keep songs in playlists even when files are moved. I understand song_id is generated based on the path of your song so it might be complicated to generate song_id based on something else, like a fingerprint of the track. I will try to look into it.

kerem closed this issue

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

kerem commented

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

Author

Owner

@phanan commented on GitHub (Jan 22, 2016):

When you move the songs around manually, there's no way to keep track of them. Even desktop applications will fail to do so.

@phanan commented on GitHub (Jan 22, 2016): When you move the songs around manually, there's no way to keep track of them. Even desktop applications will fail to do so.

kerem commented

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

Author

Owner

@tomcodes commented on GitHub (Jan 25, 2016):

I think there would be a way by fingerprinting tracks based on their headers, instead of their relative path. What do you think? Is it worth investigating?

@tomcodes commented on GitHub (Jan 25, 2016): I think there would be a way by fingerprinting tracks based on their headers, instead of their relative path. What do you think? Is it worth investigating?

kerem commented

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

Author

Owner

@phanan commented on GitHub (Jan 25, 2016):

Can't say I'm familiar with such a technique, but doesn't it require opening every file with each scan (if feasible at all)? That would be a hell of memory consumption I think. Let's not over complicate this.

@phanan commented on GitHub (Jan 25, 2016): Can't say I'm familiar with such a technique, but doesn't it require opening every file with each scan (if feasible at all)? That would be a hell of memory consumption I think. Let's not over complicate this.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#143

No description provided.

Rows
Columns