Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Albums with the same name by different artists are grouped together #220

Closed
nfisher1226 opened this issue Jun 30, 2021 · 10 comments
Closed
Labels

Comments

@nfisher1226
Copy link

Bug Report

Setup Description

Version of Odyssey

Android Version

Device Manufacturer and model

Bug Description

Description

Reproducible

Expected Behaviour

Actual Behaviour

Log

@nfisher1226
Copy link
Author

Affects both Play Store and F-Droid versions of Odyssey. When I start in Artist view and select an album to play, if there is another album in my collection by a different artist but with the same album title, the tracks of the two different albums will play intermingled together.

Example:
Playing "Lotus" by Soen plays track one from "Lotus" by Santana, followed by track one of "Lotus" by Soen, so on and so forth.

Especially problematic if one has multiple "Greatest Hits" compilations by different artists.

@gnome17
Copy link
Member

gnome17 commented Jun 30, 2021

Thanks for reporting it.

I can confirm your observation. Definitely not what we had in mind.

As a workaround you could access the album via the integrated filebrowser. That should still work.

For future bug reports please use our template and don't enter the text as a comment afterwards ;)

@gnome17 gnome17 added the bug label Jun 30, 2021
@gnome17
Copy link
Member

gnome17 commented Jun 30, 2021

Which android version are you using?

@nfisher1226
Copy link
Author

Running Android 11, kernel 4.14.113

Sorry for the bug report ettiquette. Hopefully I won't be filing more bugs.

@gnome17
Copy link
Member

gnome17 commented Jul 1, 2021

We are certain now it is an android 11 related issue.

If you want we could provide you an apk with a workaround until we have a proper fix in place.

@nfisher1226
Copy link
Author

If a fix is in the works, I'll just sit tight and watch this bug report. Of course, if you need testers I would be glad to volunteer.

@gnome17
Copy link
Member

gnome17 commented Aug 1, 2021

A quick status update:
We are currently in the final testing stages of a hopefully proper fix for this issue.

After that we will prepare a new release.

@gnome17
Copy link
Member

gnome17 commented Aug 23, 2021

So finally we released a new version that should fix the issue you discovered.

Should be available via the Play Store within the next hours and should be available via FDroid within a week or so.

Many thanks for reporting the issue :)

I will close the issue now. If the issue is still present after the update feel free to reopen the Issue again.

@gnome17 gnome17 closed this as completed Aug 23, 2021
@Saroumane
Copy link

Saroumane commented Sep 2, 2021

Hello, just updated to 1.2.0 via Fdroid, I see no fix here.
IMG_20210902_122702
(Android 11 on Pixel 3a)
Edit : sorry I misread the fix in the changelog, it's a different problem.

@gnome17
Copy link
Member

gnome17 commented Sep 2, 2021

As you already pointed out this is another issue. Please create a new issue or update an existing one and add as many details as you could. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants