flacflac wrote:Thanks for clarifying, Sindre.
Mixmaster, why would you want that? Imagine you have 5 lossless albums, someone decides to update the album art inside the tags - this requires a complete rewrite of gigabytes of data. Much easier to just put it into the folder and have the file owner decide whether he/she wants to actually embed that, no?
Because then the art moves with the track, not the folder. If you use the folder.jpg method you liter you hard drive with these tiny files all of the same name. In reality, the user cannot decide right now, the user is forced to write these files to their hard drive then, if they want to embed them into the tags, use another tool to do it. Instead I'm going to just use a better tool and tell my users to stop updating art. Unfortunately, I cannot modify their rights because one checkbox is being used for two completely different things. The first is updating tags and the other is saving a jpeg to the folder in which the tracks are. These are very different operations controlled by the same flag. Really we should pull the album art out of that checkbox and give it its own checkbox (the fact that it is the same as the updating tag is what made me assume that art was saved to the tags in the first place). Then we should add two more checkboxes that are used to decide where the album art is saved (tag or folder). Make those checkboxes and not a radio button so the admin can chose to do none, both, one or the other.
FWIW, it shouldn't matter too much how big the files are. The data is not being sent across the internet, it's just a local save. The only data that should be pulled across the network when updating tags is the new information, the art or whatever tag is being modified.
________