cheers,

That is part of the design I struggled with – the flow of the fields make sense in one context (single track) but perhaps not in another

Surely it doesn’t matter which order the fields are in for a single track? You’ve got to enter it all anyway. On the other hand, for albums, it’s important to enter all the common info first. I don’t even see why there’s this concept of having to “apply common info”; the only case I can think of where the artist wouldn’t be common to the album is where it’s a compilation, and there are other ways of working that (a differently-composed “compilation” window which has a different order).

What do you mean about “anti-leech”?

Trying to retrieve the file using GetRight on Windows yesterday (yeah, I know) resulted in GetRight grabbing an INDEX.HTM file with “this file is protected by Anti-Leech” in the title. Who knows. It’s working fine through wget on Solaris right now.

– Chris

use case:
Lets say we have few albums from the same artist, but the spelling of their name doesn’t match which process to having few folder of the same artist in the library. e.g. Nirvana, nirvana and NIRVANA.

In order to correct it now there is a need to alter each album separately. Wouldn’t it be nicer to select all the tracks, and in the dialog be able to apply only the artist name over the selected tracks, leaving the album name and year in tact.

Thanks for the update Aaron.