Make MM Suitable for classical CDs

[olddog]

MM in its present form is not suitable for classical music. Besides several shortcomings I have mentioned in other threads, the MOST irritating fault in MM is that all custom fields - UNLIKE the regular fields (Properties-Basic) - tend to loose their data at the drop of a hat, or at any other unusual event or excuse. I don’t need to be a hacker or programmer to understand that if the regular fields act in a certain way, then it can’t take all that much programming to make the custom fields behave similarly, instead of being totally unreliable. WHY the difference???

Does anyone here know of a similar program that is more up to handle classical music than MM? I have tried Musicmatch, foobar2000 and WinMedPlayer, they aren’t any better either.

Oh yah, before anyone points this out – the “Composer” field (Properties – Details) is not only useless for use in classical music because it can not be included as a column in the library or play lists, it is actually counterproductive because it does interfere with (prevents) the naming of a custom field as “Composer”.

[olddog]

It appears that there is no interest here to make MM classical musik friendly.

[jiri]

Well, we are certainly interested in making MM more useful for classical music collections. There already were some discussions here about what is needed to achieve this (fields to be added, etc.). It's only a matter of priorities, so I can't say now for sure in which version this will be implemented.

As for custom fields, they shouldn't disappear if you first add your audio CDs to library (i.e. you aren't editing it in My Computer node where MM doesn't save it anywhere).

Jiri

[ch1525]

I would love to see this made somewhat of a priority too. It is so frustrating how Classical music collections are so disregarded by all of the media player programs.

If MediaMonkey became better able to support Classical collections, it would give the program an extra edge on the competition. There are more people out there that care about this issue than the developers seem to realize. Thanks.

[olddog]

As for custom fields, they shouldn't disappear if you first add your audio CDs to library (i.e. you aren't editing it in My Computer node where MM doesn't save it anywhere).
Jiri

No, they don't disappear, they just loose all data at any opportunity (if used as columns in the library view), with and without first clicking on "File - Add to library". And having to remember to add every new disk to the library first is a pain in the you-know-where, especially since I then also have to remember to delete all that double data after ripping. It's a rather "round and about" design that doesn't make sense to me.

And as I pointed out originally, other fields (such as Artist, Album, Title, etc.) do not loose their data, only the custom fields do, WHY the difference???