Closed the-confessor closed 3 years ago
It's true; tracks are always numbered beginning at 1. To see where this behavior came from, it might be worth reading up on #1493 and the discussion that led up to it.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Thanks for the reference.
I did not realize that beets uses the track number to document the index in the release. For ripped CDs I have always seen tracks indexed per disc.
I feel that indexing HTOA as track 1 obscures the original context a little. If I look at a list of digital files and see a track 0 then I know that, while it was technically the first track of the release, and my media player may treat it as such, it wasn't intended to be presented as the opening track.
I do think that beets could still index HTOA of the first disc on a release as track 0. I understand there wouldn't be a means of identifying any later track as originating from an HTOA, but the track numbering beets uses for discs beyond the first is already deviating from the track numbering on the original format, and I wonder how often HTOA on later discs even occurs. (I know of one example - Muse's Hullabaloo Soundtrack.).
It seems like the rationale was: since we can't always identify an HTOA track, let's never identify it.
Aaaaand I just discovered the per_disc_numbering configuration option. Which explains everything I figured out via this issue thread. RTFM.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
1571 # Problem
When importing a release where the first track was originally an HTOA track on a CD, beets wants to identify the HTOA track as track 1 and every subsequent track as the actual track number + 1.
I have most often seen the HTOA track referred to as "track 0".
Is beets intentionally handling these differently, or is this a bug?
Some examples:
Setup
My configuration (output of
beet config
) is: