Personally, I don't have much classical music (what doesn't mean I don't like it), but these I do have are just tagged like:
Code: Select all
Artist = "Johann Sebastian Bach"
Title = "Toccata and fuge - Fuge"
Artist = "Wolfgang Amadeus Mozart"
Title = "Eine Kleine Nachtmusik - Allegro"
This is enough for me, but obviously not for many other people. And because MediaMonkey should be fully ID3v2.4 compatible, it would need to integrate more advanced "classical" tags anyway.
I think the biggest problem is "How to show all this information, certainly when Classical and Modern songs are used together?", and that's probably also the problem that the dev's have.
-Allow users to manage/listen to both classical music and pop music in any sitting since many listeners don't listen to one type of music exclusively
It maybe would be very nice to be able to switch the Track Information dialog between Normal (Modern songs) and Classic view, so you only see relevant things.
But then, how show this stuff together in one trackview, while having as much information shown as possible (with limited number of columns and screen width)? That's the problem as far as I can see.
So please classical-music-lovers, can you give an answer to that?
Of course, it might be a lot of work for the devs, but full ID3v2.4 support has been asked so often...
-Be compatible with existing tagging standards (ogg, id3 and ape2) and ensure consistency between the database and tags (note that tags are defined at the track level)
I would suggest to create a solution to put the massive load of information into fewer fields, by combining them into the available fields. E.g. for each tagging standard, it could be user-definable what fields are written to what tags, a bit like I'm doing in WebSourcesTagger (all "tags" can be specified with masks which represent fields). I'm doing this to put all available web information in the more limited fields of MediaMonkey tracks.
-Be compatible with existing music devices (e.g. iPods use the Artist tag for the Performer/Orchestra)
Same solution as above, e.g. For iPod, let all Composer fields be written to the Artist tag (e.g. user-definable, or "baked in").
-Not slow down MediaMonkey or burden MediaMonkey with a cluttered UI
- Speed: to be ID3v3.4 compatible, is there any other solution?
- Cluttered: like I said, maybe a switch on the track information dialog.
The tracklisting/tree problem doesn't go away of course. An "all tag frames" tab could be added to the track information dialog. This would be very advanced, but wouldn't clutter anything. (and could be loaded from the file's tags only if that tab is really opened)
Cheers
Steegy
Personally, I don't have much classical music (what doesn't mean I don't like it), but these I do have are just tagged like:
[code] Artist = "Johann Sebastian Bach"
Title = "Toccata and fuge - Fuge"
Artist = "Wolfgang Amadeus Mozart"
Title = "Eine Kleine Nachtmusik - Allegro"[/code]
This is enough for me, but obviously not for many other people. And because MediaMonkey should be fully ID3v2.4 compatible, it would need to integrate more advanced "classical" tags anyway.
I think the biggest problem is "How to show all this information, certainly when Classical and Modern songs are used together?", and that's probably also the problem that the dev's have.
[quote]-Allow users to manage/listen to both classical music and pop music in any sitting since many listeners don't listen to one type of music exclusively[/quote]
It maybe would be very nice to be able to switch the Track Information dialog between Normal (Modern songs) and Classic view, so you only see relevant things.
[i]But then, how show this stuff together in one trackview, while having as much information shown as possible (with limited number of columns and screen width)? [/i]That's the problem as far as I can see.
So please classical-music-lovers, can you give an answer to that?
Of course, it might be a lot of work for the devs, but full ID3v2.4 support has been asked so often...
[quote]-Be compatible with existing tagging standards (ogg, id3 and ape2) and ensure consistency between the database and tags (note that tags are defined at the track level) [/quote]I would suggest to create a solution to put the massive load of information into fewer fields, by combining them into the available fields. E.g. for each tagging standard, it could be user-definable what fields are written to what tags, a bit like I'm doing in WebSourcesTagger (all "tags" can be specified with masks which represent fields). I'm doing this to put all available web information in the more limited fields of MediaMonkey tracks.
[quote]-Be compatible with existing music devices (e.g. iPods use the Artist tag for the Performer/Orchestra)[/quote]Same solution as above, e.g. For iPod, let all Composer fields be written to the Artist tag (e.g. user-definable, or "baked in").
[quote]-Not slow down MediaMonkey or burden MediaMonkey with a cluttered UI [/quote]- Speed: to be ID3v3.4 compatible, is there any other solution?
- Cluttered: like I said, maybe a switch on the track information dialog. [i]The tracklisting/tree problem doesn't go away of course.[/i] An "all tag frames" tab could be added to the track information dialog. This would be very advanced, but wouldn't clutter anything. (and could be loaded from the file's tags only if that tab is really opened)
Cheers
Steegy