exaile can't read ogg vorbis file informations and import everything as 'Unknown'

I can't reproduce this, my Vorbis tags show up normally. Perhaps it's a bug in Mutagen (the tagging library that we use); if you can, please try if they show up in Ex Falso or Quod Libet (both also use Mutagen).

Johannes Sasongko <email address hidden> writes:

> I can't reproduce this, my Vorbis tags show up normally. Perhaps it's a
> bug in Mutagen (the tagging library that we use); if you can, please try
> if they show up in Ex Falso or Quod Libet (both also use Mutagen).

Seems to work fine here in quodlibet... I'll try to have a look at where
mutagen is used and where the informations are missing

Thanks,
Marc

maybe it's a problem of encoding... I tried to install a working exaile (0.2.10+debian-1.1), create a database and then install a recent bzr version. The library is correctly populated, but I can't play any songs with special characters:

-----------------------
 play_track ( /usr/lib/exaile/xl/player.py @ 511):
-----------------------
Traceback (most recent call last):
  File "/usr/lib/exaile/xl/player.py", line 539, in play_track
    GSTPlayer.play(self, play_loc)
  File "/usr/lib/exaile/xl/player.py", line 116, in play
    raise Exception('File does not exist: ' + uri)
Exception: File does not exist: /media/Music/Music/Björk/Volta/06 - Vertebrae by Vertebrae.ogg

For regular file, it works as expected : i can listen to my oggs and exaile has meta informations.

Could you point me to the location in the code where the informations are extracted ? Maybe I could try to find out what is going wrong...

Thanks,
Marc

0.2.10 is a lot more broken in terms of encoding issues, so I don't recommend comparing with that.

The tag reading code (which uses Mutagen) is in xl/media, but I never really figured out how they work. I suggest creating a library with a single ogg file and trace through the code, possibly starting somewhere in xl/media/ogg.py.

I can confirm this bug in 0.3.

Exaile seems to read well most tags, but there are some ill-shaped ones in my library that it fails. Specifically, those generated by grip. It generates a ID3v2 tag in the beginning of the file, and about 2kB later there is the vorbis comment.

But there isn't any mention in the standard that the vorbis comment must be exactly in the beginning of the file. And ogg123 and tagtool understand the tag just fine. So the bug is definitely with exaile. I'm attaching a head of a working and of a non-working file.

Exaile currently assume that all files use the tags that are "standard" for their format, eg. id3 for mp3, vorbis comment for ogg and speex, etc. Files that are not compliant with this will have issues, though given the lack of reports about this over the years i expect very few users are actually affected by this, and this is a very old bug, so I'm going to mark this as "wontfix", and if it resurfaces it should be filed in a new, better-organized report.

If you have _correctly_ tagged files and this is still happening, then that is a separate issue and should be filed in a different report.