Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 981304 - GNOME and Rhythmbox does not read APE tags from MPC files.
Summary: GNOME and Rhythmbox does not read APE tags from MPC files.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-04 12:38 UTC by Dawid Zamirski
Modified: 2013-10-19 18:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-19 18:45:31 UTC


Attachments (Terms of Use)

Description Dawid Zamirski 2013-07-04 12:38:17 UTC
Description of problem:
Not sure which component to fill this bug against as multiple applications are affected so it should probably be filled against some library instead (gstreamer, taglib?). Anyway, in Fedora 19, some GNOME applications no longer read APEv2 tags from MPC files. For example, choosing properties on an MPC file and Audio tab shows fields such as Artist, Album etc as Unknown. Rhythmbox also does not recognize tags in those files. It used to work in earlier versions of Fedora and at around Alpha/Beta of F19 - I don't remember exactly when it stopped working. Other application like Decibel, Exaile, Clementine and EasyTag do recognize those tags properly but I guess they are using some other library to read them.

I have gstreamer-plugins-* and gstreamer1-plugins-* as well as taglib-extras installed on my system and up to date.

Comment 1 Dawid Zamirski 2013-10-19 18:45:31 UTC
It seems to be working fine in F20 beta.


Note You need to log in before you can comment on or make changes to this bug.