You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a single music folder. Each folder therein is for a different release, and looks something like
Artist - [1980 EP] Album Title {2014 Somelabel CNUM123 Deluxe SACD}{FLAC 24-96}
The first {}-block in the above is a pretty big example; typically it might be {CNUM123} or {WEB}. I don't have a standard format for this block, but it's information that typically won't exist in the tags. I'd like to keep it. How best should I do this?
Sometimes the second block will be {CBR 320} or {VBR v0}, but mostly just plain {FLAC} (16b if not specified).
I played around with the 'inline' filter to generate the second {}-block from tags (because a. this seems more inline with the intended use of beats; and b. some folders may be incorrect) by looking at format, bitrate, bitrate_mode, bitdepth, samplerate, encoder_settings, but it was exploding in complexity -- is this the correct way I should do this?
I like the yaml config's extensibility, but I'm also aware that I'll most likely get the most out of beets by following its opinions as much as possible, and it occurred to me mid-scripting that I'm already getting pretty far away from that.
FWIW: this library is far too large for any manual directory formatting to take place first.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a single music folder. Each folder therein is for a different release, and looks something like
Artist - [1980 EP] Album Title {2014 Somelabel CNUM123 Deluxe SACD}{FLAC 24-96}The first {}-block in the above is a pretty big example; typically it might be {CNUM123} or {WEB}. I don't have a standard format for this block, but it's information that typically won't exist in the tags. I'd like to keep it. How best should I do this?
Sometimes the second block will be {CBR 320} or {VBR v0}, but mostly just plain {FLAC} (16b if not specified).
I played around with the 'inline' filter to generate the second {}-block from tags (because a. this seems more inline with the intended use of beats; and b. some folders may be incorrect) by looking at
format,bitrate,bitrate_mode,bitdepth,samplerate,encoder_settings, but it was exploding in complexity -- is this the correct way I should do this?I like the yaml config's extensibility, but I'm also aware that I'll most likely get the most out of beets by following its opinions as much as possible, and it occurred to me mid-scripting that I'm already getting pretty far away from that.
FWIW: this library is far too large for any manual directory formatting to take place first.
Beta Was this translation helpful? Give feedback.
All reactions