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

flac files with vorbis comments: umlauts (äöü...) interpreted incorrect #272

Open
ChristianS99 opened this issue Nov 22, 2024 · 2 comments

Comments

@ChristianS99
Copy link

ChristianS99 commented Nov 22, 2024

Bug Report

Some files with umlauts in vorbis comments are shown correctly in library and sometimes not, see screenshot:

all files from example screenshot contain same byte sequence (c3 bc), which is/should be "ü", but for some it's not interpreted as utf8 as it seems.

Setup Description

Version of Odyssey

1.3.2

Android Version

14, 13

Device Manufacturer and model

FP4, FP5

Reproducible

always the same, but differs from file to file

Expected Behaviour

vorbis comments should always be interpreted as utf8

Actual Behaviour

they are not

@ChristianS99
Copy link
Author

Screenshot_20241122-074840
smaller screenshot

@ChristianS99 ChristianS99 changed the title flac files with vorbis comments and umlauts (äöü...) wrong flac files with vorbis comments: umlauts (äöü...) interpreted incorrect Nov 22, 2024
@gnome17
Copy link
Member

gnome17 commented Dec 2, 2024

Hi,
this is most likely not a problem of odyssey but more how your android system is reading the ID tags from your music files. I have this problem myself from time to time. And like for you it appears to be kind of random and not for all files with accents or german special letters.

I would recommend that you try to tag your media files again. For example you could IDV3.2 tags with UTF8 encoding and see if this helps.

Sorry that we can't provide more help but odyssey doesn't do any tag parsing and just reads the data from the media database that the android system stored there.
So my current assumptions would be that the information is already wrong in the media db and so there is nothing we can do.

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

No branches or pull requests

2 participants