MediaMonkey forum

Hey:

My Cl.txt is filled with alot of data, which is very confusing because I don't know what I should be checking to order to remove(?) the extended characters. Is there anyway for it to just list artist, title & field that has the extended characters? Or maybe just a list of the fields which have extended characters, so you can turn on those options?

Nyn

Yeah it's pretty messy. You shouldn't need to remove them. It's more for debugging if you are still having errors. However if you PM me the log I will double check it and point out the extended characters.
Their are some that probably should be removed if they are there i.e. #<number less than 32>;

Check your mediamonkey.ini under PropertiesPanel for entries ...Extended for the fields that have been flagged as having extended charaters in them.
They are automatically flagged during the install check.
They will also show up checked in the options when you select them [EDIT] If you replace "Check Extended Character Handling in options" in CL.txt with something like "~" you can import it into excel seperating the title-artist-field and the actual text.

I emailed it to you, the PM locked up when I tried to paste so much text. And yes all the fields are marked to process for extended.

EDIT: I think I know what the problem is, all the fields in question contain a '&'. I am in the process of using the Replace a String script to replace the character, once I'm done I'll rerun the CheckDropDowns to see if this fixes these fields. I think I am going to have to take this script out of my Customization section and add it to my Editing section, because each new release causes me to edit more tracks, reminds me of Bex's scripts.

Nyn

try changing line 1279 to this: It appears to have fixed the issue on my system - haven't tested all extended characters - but the few I tested seemed to work ok now.

Also, I'd like to see if I can have your panel do a refresh whenever the tags are changed by a another process - whether manual editing through track properties - or if it's done by my RCFW script. MM seems to have an event for this (http://www.mediamonkey.com/wiki/index.p ... Properties) - could you look at it an see if it makes sense to include in your script? thx

@onenonymous I wouldn't have thought that change would work for html but it seems to, nice find.

I deliberately avoided using onproperties because of the non specific way it works.
With other scripts and the real properties panel able to change thousands of tracks at a time its either a case of refreshing the panel thousands of times or re-reading thousands of tracks to see if it needs refreshing.
Hopefully just selecting another track and reseleting the track is sufficient for now when you know you have updated one of the fields outside of the panel?

@Nyn, stop fixing them. 99.9% of them are supposed to be there. Only reason to check for them is so that the html part of the panel is able to display them.

MoDementia wrote:
@Nyn, stop fixing them. 99.9% of them are supposed to be there. Only reason to check for them is so that the html part of the panel is able to display them.

But if I don't fix them, then the debug log will be clogged with junk that I have to wade through to find problem tracks. And for once, I would like to install an update without CRAP in my tags that blows up the script. Of course, it would be a lot easier to accomplish if ZvezDan's Find & Replace script allowed you to replace text with a blank value , and I'm not in the mood to ask for help in that forum because his responses always make me feel stupid. And I think I have a little OCD because I hate having disorder in my tags....

Besides, fixing these saves from the task of finding bio info for the Artists Comment field, which is turning out to be a more daunting task than I realized.

New Version

' 27-07-08 Version 3.2
' Removed Extended character handling
' Changed file type to unicode (onenonymous find)
' Fixed error on null artist for comments

MoDementia wrote: ' Removed Extended character handling

What does this mean for the illiterate end-user??

Nyn

nynaevelan wrote:

MoDementia wrote: ' Removed Extended character handling

What does this mean for the illiterate end-user??

Nyn

Changing the file type to unicode removed the need to worry about the extended characters. MM handles them, it was the previous version of the script that had problems.

Ok, thanks for the explanation...

Nyn

I have been working on the script and I'm pretty sure I have I have discovered a bug.

Now Playing Mode and the "Custom Fields" panel don't work together with the multi select code I added
If anyone has been using this combination I'm pretty sure they would have noticed it and posted here already; so hopefully it hasn't effected anyone.

Just a heads up until I get a fixed version released.

I've been in Select Mode while editing files so I've not had the opportunity to use Now Playing Mode in a while.

nyn

New Version (Final)

' 27-07-08 Version 3.3
' Multi Selection for User Defined Panels
' Fixed bug Now Playing and Custom Fields Panel

How come the Custom Fields panle is the only panel with the option to "Enable Multi Selection", all the other panels have "Extended Character Handling"?

EDIT: BTW, the feature works, they just has the wrong description.

Nyn

nynaevelan wrote:How come the Custom Fields panle is the only panel with the option to "Enable Multi Selection", all the other panels have "Extended Character Handling"?

EDIT: BTW, the feature works, they just has the wrong description.

Nyn

Thanks Nyn, too busy worrying if it worked rather than reading labels