Feature request...Tagging

[Jlee]

How about adding the ability to display and change tag values for ANY field in the MC database, even custom fields (except read only ones of course)? Given King Sparta's extensive plug in exploits I'm guessing that the MC SDK already provides for this so it should not be too big a deal.

What could prove more tricky though is adding the ability to update multiple tags at once e.g. changing the genre for a whole artist / album.

[Promixis]

The MC API allows for this - as NR allows you to change the rating of a song. But, I don't see the need for this functionality from the PPC. It would require a lot of work which in IMHO is better done while sitting in front of MC.

[Cocophone]

I think it would be helpful to be able to change tags from my PPC.

I would like to make changes to certain tags, for example, genre.

I would also like to make changes to certain "CUSTOM" tags that I have created in Media Center.

Mostly, the tags would be short one word or maybe two to three word tags.

But, most important would be the ability to change any tag that exists in "MY" Media Center database. It would not be as useful if the ability to change tags were limited to a few preselected tags.

[Jlee]

I agree Cocophone. It's not about using the PPC as a means for tagging your library, it would just be useful to correct certain tags when you encounter mistakes. Genre is the obvious one but the problem with that is that you normally need to change a whole album / artist. Another, example is a custom field I have for 'Live' tracks; some are missed and it would be nice to be able to correct them.

The system I have at the moment is to note the details down on a bit of paper and do it when I'm next sat at my PC. I wish I could think of something better. Perhaps if there were just one custom field (e.g. called NetRemote) that we could update for the currently playing track? That custom field would become my notepad so I'd type something like 'fix genre'. Then a VS in MC would list all tracks where that custom field is not blank.

[Ben S]

I'll see what I can do for post 1.0.

Thanks Lee!