Title and artist cluttered if no tags present

Bug #424339 reported by unmacaque
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exaile
Fix Released
Low
Unassigned

Bug Description

See also: https://bugs.launchpad.net/exaile/+bug/414581

Exaile 0.31+ r2464

This is less of a bug than a suggestion about usability.

Currently, the full path to the file will be shown as title and artist if the corresponding tags are not set, e.g. "file:///home/user/dir1/dir2/.../audio_file.mp3". This leads to several visible components becoming too cluttered. Please take a look at the attached screenshot.

The result is an oversized notification bubble and cryptic artist and title entries. As you might correctly guess, if you add several untagged mp3s to the playlist, it becomes impossible to distinguish them. And the notification plugins cannot replace empty tags with "Unknown" anymore as stated by the notify-osd plugin.

Moreover, if you open the properties of an untagged file from inside Exaile, the long file name appears in both title and artist field. This leads to think that the file is tagged when in fact it is not. Also, if you unconcernedly press "OK" those tags are written to the file.

My suggestion: of course, untagged files must be identifiable. A lot of space can be saved if the path is stripped from the file name. If you open an .ogg file with no artist and title tags, it already does that (although artist is still cluttered). This could be extended to all types of media files but when there is no artist tag, leave it out. In the properties dialog, leave title and artist empty if they were before.

Revision history for this message
unmacaque (unmacaque) wrote :
Revision history for this message
Steve Dodier-Lazaro (sidi) wrote :

I wonder if this can be made in 0.3.0.1/2 (that is to say, if we can make it pass for a bugfix and not a feature :p).

Changed in exaile:
status: New → Confirmed
importance: Undecided → Low
Changed in exaile:
milestone: none → 0.3.0.1
Revision history for this message
reacocard (reacocard) wrote :

retargeting to 0.3.0.2

Changed in exaile:
milestone: 0.3.0.1 → 0.3.0.2
Revision history for this message
reacocard (reacocard) wrote :

after thinking about this for a while, it's probably too invasive to do as a bugfix. retargeting to 0.3.1.

Changed in exaile:
milestone: 0.3.0.2 → 0.3.1
Revision history for this message
reacocard (reacocard) wrote :

should be fixed in trunk/2787. This handling now happens inline instead of at scan time, and will only use the file basename, not the full path. Might need to reset your db to see the change.

Changed in exaile:
status: Confirmed → Fix Committed
reacocard (reacocard)
Changed in exaile:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.