Replies: 1 comment
-
What filesystem is your library on? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 need some help on how to get out of this mess. I have an album by David Bowie whose title is the literal character '★'
When it is imported in beets, it causes grief with both the file and folder names. The '★' is obviously not a legal character in folder or filename. So after import in Beets, it cannot create either folder or filename so it drops them into the Artist root folder like so:
Reading the docs, there's an
%asciify{}template function. However, that also doesn't appear to work because '★' is not an ASCII character, it's unicode.As part of my troubleshooting, I have manually tagged all of the tracks with the album name of "Blackstar" (instead of the symbol formerly known as Prince). I then tried to
beet import -L path:/music/David Bowie/Blackstarand we're right back where we started (with the same problem). the-Loption is supposed to import AS-IS, no?So, how do I fix this mess? If I run
beet ls -a artist:"David Bowie"I see this result:So, oddly enough, the album is stored in the DB as the symbol, but the file and foldernames remain problematic.
I have
asciify_paths: yesinconfig.yamland my paths looks like this:How do I clear out the database entry with the symbol and force Beets to re-import them with the word instead of the symbol? I would expect
-Lor the%asciify{}to workpls help? TIA
Beta Was this translation helpful? Give feedback.
All reactions