beetbox / beetbox/beets

Disable multiple tag names for free-form tag formats

Open
#350 39 comments 2 reactions 0 assignees View on GitHub
bug mediafile
Dominant language
Python
Stars
15.7k
Forks
2.1k
Avg merge
4d 21h
Merged PRs (30d)
31

Description

I don't know if this comes from beets or if it's me configuring ncmpcpp poorly.
I got this line in .ncmpcpp/config :
song_columns_list_format = "(5)[red]{n}(5f)[green]{l} (25)[cyan]{a} (40)[]{t|f} (25)[red]{b}"
This is the default way to display the songs in the column format in ncmpcpp except that I added the track number: (5)[red]{n}
The issue is that tracks are displayed that way :
![track](https://f.cloud.github.com/assets/1104190/871594/4f367d4e-f84f-11e2-9f86-0efad2f1c4bd.PNG)
If I go into the ncmpcpp tag editor :
![tags](https://f.cloud.github.com/assets/1104190/871601/85cfa13c-f84f-11e2-97ec-1d129b90fb9d.PNG)
Of course all those tracks were imported with beets,
it seems like a strange format. Is that a bug from beets mistagging the tracks or a ncmcpp rendering issue ?

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported configuration with beets-imported tracks and compare the stored tags with how ncmpcpp displays them. The issue does not name a beets file or test; trace the free-form tag formatting path and determine whether beets writes multiple tag names or ncmpcpp renders them incorrectly. Done means the source of the duplicated names is identified and the requested behavior for free-form tag formats is specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.