Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track Numbering(metadata) #3298

Open
Blackbear199 opened this issue Feb 18, 2022 · 10 comments
Open

Track Numbering(metadata) #3298

Blackbear199 opened this issue Feb 18, 2022 · 10 comments

Comments

@Blackbear199
Copy link

Back Again,

for multi cd albums
folder structure before import.

  • Album Artists
    • Album Name
      • CD1
        • Disc Number =>1/3,Track number starting at 1
      • CD2
        • Disc Number =>2/3,Track number starting at 1
      • CD3
        • Disc Number =>3/3,Track number starting at 1

$Disc$Track. $Title (i dont think the format has anything to do with the issue)

what i expected is
101. Title
....
115. Title
201. Ttitle
...
214. Title
301. Title
...
317. Title

what i get is..

  1. Title
    ...
  2. Title

when i view it in my media player its one long list of tracks rather than split into 3 discs with each starting at track 1 for numbering.
in each disc folder in mp3tag i set the disc number and renumbered the tracks like this before import.
i cant remember if headphone changed the disc numbers to 1 or left them unedited(i fixed all the tags again with mp3tag), for sure it renumbered all the tracks in the metadata..

@rembo10
Copy link
Owner

rembo10 commented Feb 18, 2022

Hm, the tagging is done by beets. Headphones just passes is it the location and a musicbrainz album id. I'll look into it though, maybe there's a configuration option we can pass, and i think the library might even try to read a beets config.

You could try that out in the meantime:
https://beets.readthedocs.io/en/stable/reference/config.html

@Blackbear199
Copy link
Author

was doing some reading myself,
found this post regarding this and to use the inline plugin?

https://www.reddit.com/r/musichoarder/comments/ft6946/beets_and_multiple_cds/

@Blackbear199
Copy link
Author

@rembo10
Copy link
Owner

rembo10 commented Feb 18, 2022

Yeah see if creating a beets config with that option does anything

@rembo10
Copy link
Owner

rembo10 commented Feb 18, 2022

I'll still check on my end if we can pass some kind of config option to the autotagger

EDIT: It doesn't look like it but it does look like it reads the config

@Blackbear199
Copy link
Author

took me a bit to find a multi cd to download to test.
all cd and track numbers were correct in metadata.

$Disc$Track. $Title

also got all the filenames correct.
hopefully u can add this to the settings page,savces alot of work.
even add a note to edit toe beets.yml file if thats not possible.

@Blackbear199
Copy link
Author

Blackbear199 commented Feb 18, 2022

Yeah see if creating a beets config with that option does anything

i missed what you said about creating the yml file.
i didnt have to create,enabled the feature in /headphones/lib/beets/config_default.yml

@rembo10
Copy link
Owner

rembo10 commented Feb 19, 2022

Ah yeah - you are running headphones as the headphones user without a home directory right? I was going to see if you could create the config.yaml to see if it was picked up by beets without having to modify the headphones source, but it's good that it at least works that way....

@Blackbear199
Copy link
Author

its runs on my nas(Thecus)
everything is installed as a module.
3rd party delevoper created a install module for headphones,at that time the python libaries were included with this installer
now we have separate python2 and python3 modules.
when i updated headphones i edited the start script to use python3
i searched everywhere and cant find the beet binary,it has to be there somewhere.

@rembo10
Copy link
Owner

rembo10 commented Feb 22, 2022

I'm not sure I understand. The beets binary wouldn't be installed since it's just the library being bundled, but you could run it as python headphones/lib/beets/__main__.py?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants