I'm deliberately not saying that because I think it unsound to rely on subjective measures of 'logical' and 'friendly'. I'm saying it will work for everyone but only folks who want non-/standard/ interpretation need adapt.spacefish wrote:So basically you're saying that this method will work for everyone but only folks who want multiple artists parsed in a logical and friendly manner (i.e. Queen & David Bowie, not Queen/David Bowie), will need to adapt. Please correct me if I'm wrong.
As ever, each user must decide whether the work is worth it. The solution means more user work than currently only because the requirements include more data.Is it worth the extra work (because there will be a lot more with your method than there is currently)
I've seen no method that better minimises that work. Though of your proposed multi-field input method you say "nothing new would open" I don't see how that is possible. I think users want a solution that works within the existing workflow inc. direct keying into the track list, assisted by the drop-down and copy'n'paste, and would not appreciate having to use multiple fields presented either as list columns or Properties dialog controls.
As much as possible - but no more. MM cannot mindread so the user is going to have to specify separators for MM to interpret existing custom-separated data.to update exception tables and separator options manually? I don't think it is. I believe the program should do as much of the work as possible.
Fine - have a Mark as Separator command/key - but let's not mistake that as an alternative to an Options table.Yes, some values for separators will need to be entered initially by the user but designed into the work flow of adding/editing properties, rather than a separate options table
Sorry, forcing multi-artist-entering users into a Properties dialog is not acceptable IMO.Multi-field method: I don't have that multi-artist separator defined? Add + here next to the artist (tandem to the artist field in the properties window;
Um, MM knows only because your proposal forces the user into explicitly telling it. I for one do not have the time to fiddle about slice and dicing one string into multiple input controls on every track.Since this method only assigns one artist per artist field, I don't have to worry about the + in the next band's name. MM knows it's only one artist because it's in an artist field.
No - use key/button to add the current separator.Your method: I don't have that multi-artist separator defined? Cancel out of properties
No decision required - you just hit the key/command to add it. That's a rare case and far less work than your slice and dice every time.Next time I have an artist with + in their name though, I have to decide whether or not to add them to the exception table too
I think not. In my proposal, once you've chosen your separators and set special artist names, MM will automatically show your whole library multi-artisted. If I understand your proposal correctly, the user must slice and dice on every track individually.Lot more steps in your method
In the exceptions Options, ideally modeless.OOPS I selected too many letters now how do I fix it?
Last.FM Node