Thanks,
I understand these differences, but if MC can store Artist, Genre, Year etc, why could they not store Composer?
I've been involved in a number of discussions about providing better online tag database content for classical music.
JimH has asked for ideas but the discussion gets bogged down when a number of people dogmatically push their own method as the only rational one. JimH then retreats as any sensible person would.
One problem is that some people want to preserve full compatibility to other devices such as iPhones or other music player software. Those people want to stuff the Composer value into the Artist, Album or (track) Name tags. And these people don't agree on how Composer, Work Name, Performer and movement name should be stored in the lowest common denominator set of tags.
Even the people who favor using the Composer tag don't agree on the form of that name or the form and placement of the Work Name, Performer and movement name information.
I figured out the way I wanted my tags to be used and used JRiver's excellent tagging tools to hand edit the tag info when I rip each CD. It takes me about 1 minute to gets the tags right for a typical classical CD with 3 works by a single composer. A multi-composer, multi-performer CD might take 5 minutes to get the tag info done.
When I was ripping my CD collection in 2006, I often used 2 DVD drives so that I could overlap the tag editing with the time JRiver needed for the actual ripping operation.
(I have used dBpoweramp which populates the Composer tagbut I found that editing the tags it produced was more work than just doing it by hand in JRiver.)