-
|
beets as the How is is this information stored? In the database no problem: It can have a "album" table (or similar structure) for this. But what about when the information is written back into the audio files? There is no audio file for the album, only for its tracks! Is the information then duplicated into all tracks of an album? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Beets gathers more info on your albums/tracks than what gets written in the files. That's why there is a database in the first place. For files there are standards for what they may or may not contain as metadata. Some are more flexible than others, but not everything that beets has can be stored in the files. In most cases albums and track share common info, like albumname, MB id's, etc. Those are not 'duplicated' in the files. If there is something specific you are missing in your files that are album fields in beets? |
Beta Was this translation helpful? Give feedback.
-
|
No, no, rather the opposite: The composer field exists on the track, but only sometimes on the album. -- But not a big deal, because now I know how to iterate over tracks in the album fields. 😄 Also, regarding information how and where beets stores what, I found the beets wiki, and there in particular the Concepts page. Good stuff! |
Beta Was this translation helpful? Give feedback.
Beets gathers more info on your albums/tracks than what gets written in the files. That's why there is a database in the first place. For files there are standards for what they may or may not contain as metadata. Some are more flexible than others, but not everything that beets has can be stored in the files. In most cases albums and track share common info, like albumname, MB id's, etc. Those are not 'duplicated' in the files.
If there is something specific you are missing in your files that are album fields in beets?