Let me be blunt

[Red Maw]

I agree with that concept. All I and anyone else really cares about is that there we have a field to the put data we want to into. I will have to look into the CustomX stuff - if it can be renamed so to reflect the contents then that is a perfect solution. While "find Custom1=x" works, "find Artist=x" is much better.

[Barry4679]

The CustomX tags are an ideal solution for this issue. They allow a user to save exactly what data he wants, and I believe I somewhere saw an option to change the label of the fields.

I haven't tried it myself, but it is at Tools|Options|Library|Appearance

Everything is great, until somebody needs more than 5 custom tags.

Or somebody wants a numeric field; ie one which doesn't sort like

1
11
2
3
etc

Some custom date fields would be great also.

[jiri]

Request of more and better Custom fields added as http://www.ventismedia.com/mantis/view.php?id=14365.

Thanks,
Jiri

[MMFrLife]

5 more would be great as long as they are coded to write to the tag like the original 5 (no 'MM only' stuff).

[zee566]

My mp3 library is nearly 300,000 cuts. Can 5 handle it?

[Lowlander]

It should *, it's designed to be faster than MM4.

* Hardware does matter with larger Libraries. Especially hard drive speed of the database can impact how fast MediaMonkey reacts.

[MMFrLife]

5 more would be great as long as they are coded to write to the tag like the original 5 (no 'MM only' stuff).

Also, if you could make them 'multi-item' capable. Is that even possible with the Custom Fields?

10 overall!
(5 plain, 5 multi-item)

equals --> custom fields issue put to rest