[GH-ISSUE #370] Bug: Compilation Album under Artists. #266

Closed
opened 2026-02-26 02:32:37 +03:00 by kerem · 15 comments
Owner

Originally created by @BernardGoldberger on GitHub (Jul 8, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/370

Windows, Opera, Master.

compilation albums will now list all the songs under the same album, however I noticed 2 issues

  1. The Artist for any individual song shows as "Various Artists".
    image
  2. The songs cannot be found under "Artists", not under "Various Artists", Album Artist" or "Song Artist".
    image

I think that under Artists the Album should be found under Various Artists -> Albums, or under the Album Artist, Similar to https://github.com/phanan/koel/issues/21#issuecomment-211044496. Album Artist should group the entire Compilation under the same Album, see screenshot.
image

And of course thank you @phanan for the adding the support and I know that its still experimental but I figured I will report my findings.

Originally created by @BernardGoldberger on GitHub (Jul 8, 2016). Original GitHub issue: https://github.com/koel/koel/issues/370 Windows, Opera, Master. compilation albums will now list all the songs under the same album, however I noticed 2 issues 1. The Artist for any individual song shows as "Various Artists". ![image](https://cloud.githubusercontent.com/assets/10334679/16701613/d1537532-452e-11e6-960b-c836434b5fe2.png) 2. The songs cannot be found under "Artists", not under "Various Artists", Album Artist" or "Song Artist". ![image](https://cloud.githubusercontent.com/assets/10334679/16701860/a4616e1a-4530-11e6-93b5-33915166d964.png) I think that under Artists the Album should be found under Various Artists -> Albums, or under the Album Artist, Similar to https://github.com/phanan/koel/issues/21#issuecomment-211044496. Album Artist should group the entire Compilation under the same Album, see screenshot. ![image](https://cloud.githubusercontent.com/assets/10334679/16701739/b43cd172-452f-11e6-8d9c-756a5f4bfc04.png) And of course thank you @phanan for the adding the support and I know that its still experimental but I figured I will report my findings.
kerem closed this issue 2026-02-26 02:32:37 +03:00
Author
Owner

@phanan commented on GitHub (Jul 9, 2016):

Hmm, that's weird. This is my screenshot of the same album as in https://github.com/phanan/koel/issues/21#issuecomment-211044496:

image

If possible, can you use a tag editor/scanner and show me your file's tags?

For 2. "Various Artists" is not meant to be searched. If 1. doesn't happen, the artist name shouldn't be "Various Artists" to be searchable to begin with.

<!-- gh-comment-id:231509064 --> @phanan commented on GitHub (Jul 9, 2016): Hmm, that's weird. This is my screenshot of the same album as in https://github.com/phanan/koel/issues/21#issuecomment-211044496: ![image](https://cloud.githubusercontent.com/assets/8056274/16705446/ac75ada0-45bc-11e6-8108-5ecf18f5c8a0.png) If possible, can you use a tag editor/scanner and show me your file's tags? For 2. "Various Artists" is not meant to be searched. If 1. doesn't happen, the artist name shouldn't be "Various Artists" to be searchable to begin with.
Author
Owner

@BernardGoldberger commented on GitHub (Jul 10, 2016):

I used Mp3tag image

In regards to 2 I did try to search for the song artist and the album artist but It wouldn't show up.

Also right click and "Go to Artist" works and it takes me to "Verious Artists" with 10 Albums, but as I said not browsing through Artists
image

I checked the DB and found the following, the Album artist_id is 2
image

which is
image

but the Song contributing_artist_id is also 2
image

which seems to be the issue.

<!-- gh-comment-id:231568691 --> @BernardGoldberger commented on GitHub (Jul 10, 2016): I used [Mp3tag](http://www.mp3tag.de/en/) ![image](https://cloud.githubusercontent.com/assets/10334679/16711445/e8929484-4629-11e6-80ef-de4c12850a88.png) In regards to 2 I did try to search for the song artist and the album artist but It wouldn't show up. Also right click and "Go to Artist" works and it takes me to "Verious Artists" with 10 Albums, but as I said not browsing through Artists ![image](https://cloud.githubusercontent.com/assets/10334679/16711471/83afc346-462b-11e6-9f68-6029098220ea.png) I checked the DB and found the following, the Album artist_id is 2 ![image](https://cloud.githubusercontent.com/assets/10334679/16711488/768dbb90-462c-11e6-9f5d-adbbf9777530.png) which is ![image](https://cloud.githubusercontent.com/assets/10334679/16711490/9ba19794-462c-11e6-8538-8f930eb51556.png) but the Song contributing_artist_id is also 2 ![image](https://cloud.githubusercontent.com/assets/10334679/16711494/edb6cd4c-462c-11e6-9528-6d1a978627c9.png) which seems to be the issue.
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

Can you try backing up the database first and then running php artisan koel:sync --tags=artist,compilation?

<!-- gh-comment-id:231569292 --> @phanan commented on GitHub (Jul 10, 2016): Can you try **backing up the database first** and then running `php artisan koel:sync --tags=artist,compilation`?
Author
Owner

@BernardGoldberger commented on GitHub (Jul 10, 2016):

Completed! 0 new or updated song(s), 8109 unchanged song(s), and 0 invalid file(s).

I checked again and all is the same.

<!-- gh-comment-id:231569496 --> @BernardGoldberger commented on GitHub (Jul 10, 2016): `Completed! 0 new or updated song(s), 8109 unchanged song(s), and 0 invalid file(s).` I checked again and all is the same.
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

That's weird. I guess they use different tags. If it's possible, can you send one of these files into my email me@phanan.net?

<!-- gh-comment-id:231569754 --> @phanan commented on GitHub (Jul 10, 2016): That's weird. I guess they use different tags. If it's possible, can you send one of these files into my email me@phanan.net?
Author
Owner

@BernardGoldberger commented on GitHub (Jul 10, 2016):

Sure, I should point out that this seems to be the case with all the compilations albums I have.

<!-- gh-comment-id:231569905 --> @BernardGoldberger commented on GitHub (Jul 10, 2016): Sure, I should point out that this seems to be the case with all the compilations albums I have.
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

Apparently I'm missing something here. Worth noting that I only have Mac &
iTunes to test around :P

On Sun, Jul 10, 2016 at 12:21 PM, bdgold notifications@github.com wrote:

Sure, I should point out that this seems to be the case with all the
compilations albums I have.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/370#issuecomment-231569905, or mute
the thread
https://github.com/notifications/unsubscribe/AHrt0sVUVRo22IZk3pRfrv3HxuHJPLd6ks5qUHMtgaJpZM4JIaMI
.

<!-- gh-comment-id:231569988 --> @phanan commented on GitHub (Jul 10, 2016): Apparently I'm missing something here. Worth noting that I only have Mac & iTunes to test around :P On Sun, Jul 10, 2016 at 12:21 PM, bdgold notifications@github.com wrote: > Sure, I should point out that this seems to be the case with all the > compilations albums I have. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/phanan/koel/issues/370#issuecomment-231569905, or mute > the thread > https://github.com/notifications/unsubscribe/AHrt0sVUVRo22IZk3pRfrv3HxuHJPLd6ks5qUHMtgaJpZM4JIaMI > .
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

I think I know where the problem is. Will work on the fix real soon. Thanks for reporting @bdgold!

<!-- gh-comment-id:231570182 --> @phanan commented on GitHub (Jul 10, 2016): I think I know where the problem is. Will work on the fix real soon. Thanks for reporting @bdgold!
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

Hm… actually no. This is the result on my end:

image

<!-- gh-comment-id:231570787 --> @phanan commented on GitHub (Jul 10, 2016): Hm… actually no. This is the result on my end: ![image](https://cloud.githubusercontent.com/assets/8056274/16711708/5568b954-469c-11e6-98fb-b4d01804c6cc.png)
Author
Owner

@BernardGoldberger commented on GitHub (Jul 10, 2016):

Hmmm, so I went now and removed the song from the scanned folder and did php artisan koel:sync -v to remove the song and I verified that it doesnt show, the I added the song back and did php artisan koel:sync -v and the song shows up the way it should, I then did php artisan koel:sync -v --tags=artist,compilation just to verify that it was not the issue and everything is good for that song
image

<!-- gh-comment-id:231571339 --> @BernardGoldberger commented on GitHub (Jul 10, 2016): Hmmm, so I went now and removed the song from the scanned folder and did `php artisan koel:sync -v` to remove the song and I verified that it doesnt show, the I added the song back and did `php artisan koel:sync -v` and the song shows up the way it should, I then did `php artisan koel:sync -v --tags=artist,compilation` just to verify that it was not the issue and everything is good for that song ![image](https://cloud.githubusercontent.com/assets/10334679/16711791/df6b4916-463b-11e6-91cb-95fdb788b222.png)
Author
Owner

@phanan commented on GitHub (Jul 10, 2016):

There must be some hiccups during upgrading then. The fault should be on my
part, but in all honesty, I can't guess what it is now :/

On Sun, Jul 10, 2016 at 1:16 PM, bdgold notifications@github.com wrote:

Hmmm, so I went now and removed the song from the scanned folder and did php
artisan koel:sync -v to remove the song and I verified that it doesnt
show, the I added the song back and did php artisan koel:sync -v and the
song shows up the way it should, I then did php artisan koel:sync -v
--tags=artist,compilation just to verify that it was not the issue and
everything is good for that song
[image: image]
https://cloud.githubusercontent.com/assets/10334679/16711791/df6b4916-463b-11e6-91cb-95fdb788b222.png


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/370#issuecomment-231571339, or mute
the thread
https://github.com/notifications/unsubscribe/AHrt0swRRglzdSqgWYt2nGSSbGBvGMy8ks5qUIBAgaJpZM4JIaMI
.

<!-- gh-comment-id:231571520 --> @phanan commented on GitHub (Jul 10, 2016): There must be some hiccups during upgrading then. The fault should be on my part, but in all honesty, I can't guess what it is now :/ On Sun, Jul 10, 2016 at 1:16 PM, bdgold notifications@github.com wrote: > Hmmm, so I went now and removed the song from the scanned folder and did php > artisan koel:sync -v to remove the song and I verified that it doesnt > show, the I added the song back and did php artisan koel:sync -v and the > song shows up the way it should, I then did php artisan koel:sync -v > --tags=artist,compilation just to verify that it was not the issue and > everything is good for that song > [image: image] > https://cloud.githubusercontent.com/assets/10334679/16711791/df6b4916-463b-11e6-91cb-95fdb788b222.png > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/phanan/koel/issues/370#issuecomment-231571339, or mute > the thread > https://github.com/notifications/unsubscribe/AHrt0swRRglzdSqgWYt2nGSSbGBvGMy8ks5qUIBAgaJpZM4JIaMI > .
Author
Owner

@BernardGoldberger commented on GitHub (Jul 11, 2016):

I just realized that when I ran php artisan koel:sync --tags=artist,compilation it did not include --force so I just ran php artisan koel:sync -v --force --tags=artist,compilation and we are all good
image

In the realease notes it should probably say to run php artisan koel:sync --force --tags=artist,compilation

<!-- gh-comment-id:231714645 --> @BernardGoldberger commented on GitHub (Jul 11, 2016): I just realized that when I ran `php artisan koel:sync --tags=artist,compilation` it did not include `--force` so I just ran `php artisan koel:sync -v --force --tags=artist,compilation` and we are all good ![image](https://cloud.githubusercontent.com/assets/10334679/16729890/67710790-473d-11e6-9a91-5ecdbdd8cde2.png) In the realease notes it should probably say to run `php artisan koel:sync --force --tags=artist,compilation`
Author
Owner

@phanan commented on GitHub (Jul 11, 2016):

But it did:

php artisan koel:sync --force --tags=compilation

On Mon, Jul 11, 2016 at 8:00 PM, bdgold notifications@github.com wrote:

I just realized that when I ran php artisan koel:sync
--tags=artist,compilation it did not include --force so I just ran php
artisan koel:sync -v --force --tags=artist,compilation and we are all good
[image: image]
https://cloud.githubusercontent.com/assets/10334679/16729890/67710790-473d-11e6-9a91-5ecdbdd8cde2.png

In the realease notes it should probably say to run php artisan koel:sync
--force --tags=artist,compilation


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/370#issuecomment-231714645, or mute
the thread
https://github.com/notifications/unsubscribe/AHrt0lZUWt5BiPBFo2FJhTTiOXppwNEUks5qUjBkgaJpZM4JIaMI
.

<!-- gh-comment-id:231744772 --> @phanan commented on GitHub (Jul 11, 2016): But it did: > php artisan koel:sync --force --tags=compilation On Mon, Jul 11, 2016 at 8:00 PM, bdgold notifications@github.com wrote: > I just realized that when I ran php artisan koel:sync > --tags=artist,compilation it did not include --force so I just ran php > artisan koel:sync -v --force --tags=artist,compilation and we are all good > [image: image] > https://cloud.githubusercontent.com/assets/10334679/16729890/67710790-473d-11e6-9a91-5ecdbdd8cde2.png > > In the realease notes it should probably say to run php artisan koel:sync > --force --tags=artist,compilation > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/phanan/koel/issues/370#issuecomment-231714645, or mute > the thread > https://github.com/notifications/unsubscribe/AHrt0lZUWt5BiPBFo2FJhTTiOXppwNEUks5qUjBkgaJpZM4JIaMI > .
Author
Owner

@BernardGoldberger commented on GitHub (Jul 11, 2016):

In the release notes it says to run php artisan koel:sync --force --tags=compilation your suggestion to include artist, is what did the trick.

<!-- gh-comment-id:231747785 --> @BernardGoldberger commented on GitHub (Jul 11, 2016): In the release notes it says to run `php artisan koel:sync --force --tags=compilation` your suggestion to include `artist,` is what did the trick.
Author
Owner

@phanan commented on GitHub (Jul 11, 2016):

Oh, right.

On Mon, Jul 11, 2016 at 10:17 PM, bdgold notifications@github.com wrote:

In the release notes it says to run php artisan koel:sync --force
--tags=compilation your suggestion to include artist, is what did the
trick.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/370#issuecomment-231747785, or mute
the thread
https://github.com/notifications/unsubscribe/AHrt0gSemlcIXsEcYj_XJLgP9FS912e_ks5qUlCNgaJpZM4JIaMI
.

<!-- gh-comment-id:231748171 --> @phanan commented on GitHub (Jul 11, 2016): Oh, right. On Mon, Jul 11, 2016 at 10:17 PM, bdgold notifications@github.com wrote: > In the release notes it says to run php artisan koel:sync --force > --tags=compilation your suggestion to include artist, is what did the > trick. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > https://github.com/phanan/koel/issues/370#issuecomment-231747785, or mute > the thread > https://github.com/notifications/unsubscribe/AHrt0gSemlcIXsEcYj_XJLgP9FS912e_ks5qUlCNgaJpZM4JIaMI > .
Sign in to join this conversation.
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#266
No description provided.