Customizing custom field

hhggrr · Post by **hhggrr** » Mon Sep 25, 2006 10:41 pm

I am using a custom field and need to create an autoplaylist with it but the only conditions I am getting are for text fields (contains, starts with, etc.). Is there a way to change the custom field property to numeric (between, >-, =. <=)?

This is what I want to try to do: The custom field is the Billboard Top 100. I am filling it with the Billboard position the song got that year (Top 100 of each year) I want to create an autoplaylist which shows me the songs with values from 1 to 10 in that field.

fncll · Post by **fncll** » Mon Sep 25, 2006 11:23 pm

Based on a search, it appears that MM doesn't currently support numeric custom fields... that being said, if you aren't using the BPM field you might could use that since it's numeric...

Or maybe original year, if you don't use that, but it doesn't seem to be an option when creating autoplaylists??

rovingcowboy · Post by **rovingcowboy** » Mon Sep 25, 2006 11:36 pm

this requires a script to be made to read the information in the field.

and put it in order then list it in the autoplaylist.

unless you only go in to each of your songs and type the number in to field your self.

then you can make an auto playlist for each number and tell it to sort
for that number only. you would have 10 auto playlists and each would have the songs in for that number. you would have to use the orginal year tag in the properties for the songs and tell the auto playlist to look
for that year in any text field.

the trouble is it would find songs titled with years in them too.
like the songs of dec 1963 oh what a night. or 1982, or 1985,

but you would get lots of lists that way.

so it is better to get a script that will seperate out the information you have in the custom field and add it to the proper playlist.

Post by **Lowlander** » Tue Sep 26, 2006 9:09 am

Custom fields do support numeric values. The problem is that the advanced search/auto-playlists don't allow numeric operations on a custom field (like bigger than).
Seems like a wish to me.

rovingcowboy · Post by **rovingcowboy** » Tue Sep 26, 2006 9:22 am

Lowlander wrote:Custom fields do support numeric values. The problem is that the advanced search/auto-playlists don't allow numeric operations on a custom field (like bigger than).
Seems like a wish to me.

oh i thought he was adding the date and the billboard rating in the same field?

which is why i said it needed to be done in a script. i did not read it as he was only doing the number for the rating.

sorry about that.

hhggrr · Post by **hhggrr** » Tue Sep 26, 2006 10:38 am

Well, I figured I could go change the properties of the custom field in the MediaMonkey.mdb file but that was a no no. After I changed it to a numeric type and then opened MM my tracks were no longer available in the library so I had to undo that.

Maybe something else can be "tweaked" but I am not that knowledgeable to find out.

BTW, thanks for the responses!

Post by **Lowlander** » Tue Sep 26, 2006 11:12 am

You can't change the behavior in MediaMonkey. It would be up to the developers to add support for custum fields being numeric and allow numeric operations.

Thru scripts (MagicNodes?) you might be able to create views (lists of songs) with numeric operations on the custom fields, but you can't do this in MediaMonkey itself.