<div class="gmail_quote">2009/3/31 Matt 'Murph' Finnicum <span dir="ltr"><<a href="mailto:mattfinn@gmail.com">mattfinn@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><div></div><div class="h5">On Tue, Mar 31, 2009 at 5:15 PM, Michael Pujos <span dir="ltr"><<a href="mailto:pujos.michael@laposte.net" target="_blank">pujos.michael@laposte.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Jeff Mitchell a écrit :<br>
> Michael Pujos wrote:<br>
><br>
>> Jeff Mitchell a écrit :<br>
>><br>
>>> Album: Crazy Techno vol 2<br>
>>> Album Artist: Ministry of Sound<br>
>>> Artist: TechnoDude<br>
>>> Track Title: Blowing Your Mind<br>
>>> Featuring: John Blaze<br>
>>><br>
>>> This isn't a far-fetched example by any means -- in fact, it's quite<br>
>>> common -- but clearly "John Blaze" belongs in TPE2, not "Ministry of<br>
>>> Sound". So where do you put "John Blaze" if you've filled TPE2 with<br>
>>> "Ministry of Sound"? Will anyone show it if you put it in TCOM or TOPE?<br>
>>><br>
>>> There is only one purely cross-player solution to the Album Artist<br>
>>> problem in ID3, which is, don't do it.<br>
>>><br>
>> In you example above, i'd put John Blaze in a custom tag (TXXX frame)<br>
>> since there's no standard frame for the "Featuring" credit.<br>
>><br>
><br>
> Which proves my point. Now you're putting information in custom tags,<br>
> which are totally fine for one player, but are not cross-player<br>
> compatible (unless they hack in support for each others' frames).<br>
><br>
> </blockquote></div></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><div class="h5">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Except if you make the app custom tag aware, but it's quite a bit of<br>
work and not many players took that route.<br>
<br>
><br>
>> No problem putting as much info as you want in the filename, but it's<br>
>> useful to also have that info in tags for sorting / displaying purposes.<br>
>> The simplest solution IMHO is to follow the WMP/itunes de-facto standard<br>
>> (TPE2), or the foobar2000 one<br>
>> (<a href="http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Encouraged_Tag_Standards" target="_blank">http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:Encouraged_Tag_Standards</a>).<br>
>> foobar2000 maps Album Artist to the first defined tag in this list:<br>
>> "album artist" (custom frame), "artist", "composer", "performer". For<br>
>> Album Artist, it ignores TPE2 which can serve other purposes (like it's<br>
>> real signification).<br>
>><br>
><br>
> You should actually read my previous email.<br>
><br>
> --Jeff<br>
><br>
><br>
<br>
I thought it did :)<br>
The point was just that users will be grateful if you follow some<br>
(potentially half-baked) standard that works rather than thinking you<br>
got it better than everyone else and implementing<br>
your own speific solution (NIHS syndrome).</blockquote><div> <br></div></div></div>I don't think it's a good idea to just decide to do nothing. Album Artist / Various Artists support is very important to people trying to manage a large collection. <br>
<br>Using a custom tag would not negativly affect other players, would it? Maybe Amarok should just use a custom tag untill the standard is written (at which point it could easily translate the custom tag into the standardized version).<br>
<br>I also think the foobar2000 standard is a very good way to deal with it in the mean time. Again, it's misusing the tags a bit, but I'm sure that most users will appreciate it and I'm sure it could be updated when the real standard comes out.<br>
<br>You could even have an option or two to decide how to deal with this if you wanted to force the decision onto the user. But just not having the support shouldn't be acceptable for Amarok.<br><br>--Murph<br></div>
<br>_______________________________________________<br>
Amarok mailing list<br>
<a href="mailto:Amarok@kde.org">Amarok@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/amarok" target="_blank">https://mail.kde.org/mailman/listinfo/amarok</a><br>
<br></blockquote></div><br>I completely agree with Murph. There needs to be a better option for handling various artists. If custom tags is the only feasible way to solve this, shouldn't someone be working on it? Handling of custom tags would go a long way towards helping with my collection, and I would be excited to work on something like this as part of my GSoC project.<br>
<br>As Michael said: (I can't get the >'s to work right o.O)<br>"Except if you make the app custom tag aware, but it's quite a bit of<br>
work and not many players took that route." <br><br>This is exactly what I'm looking for! I would love to help Amarok handle various artists better and I'm pretty sure one of the reasons GSoC was created was to solve problems being put aside because they require "quite a bit of work".<br>
<br>Sure, although some users may be satisfied with the current handling, and others might not want to be bothered with custom tagging, if this is something a good number of users want (and I'm getting that impression from this discussion), the option to support it should not be ignored.<br>
<br>-Kevin<br> <br><br>