3 results found
36 votes17 comments · bliss · Admin →
An error occurred while saving the comment
17 votes12 comments · bliss · Admin →
An error occurred while saving the commentPeter Monks commented
I notice it's been two and half years since this issue was originally raised, and just want to add my voice to it. This is a major gap in Bliss' capabilities, and greatly hinders all aspects of the app, since metadata, album art, etc. is all predicated on Bliss linking to the correct release. Please consider moving this to the top of the product's backlog.
3 votesPeter Monks shared this idea ·
Please consider adding this as a matter of some urgency. On macOS it's quite easy for Bliss to inadvertently create a folder or file with a name that means that it subsequently cannot be processed in any way, by any tool.
For example, the filename "Mötley Crüe" on an AFP mounted remote drive, served by Linux (as is common in home NAS devices, for example), cannot subsequently be opened, deleted, renamed, or moved by anything on macOS.
Luckily in this case I was able to use the NAS device's web interface to delete the offending folder, although of course it came straight back again the next time I backed up my music collection to that device.
Providing a way to limit Bliss to the basic 127-bit ASCII character set for all filename & path elements would be ideal in my situation, with conversions from accented characters to their unaccented equivalents in all cases e.g. "Mötley Crüe" → "Motley Crue".