Well I'm glad it's working for you now

AND there's now a "Find Protected" node on the left. Honest, it wasn't there before!

Doh, I just realized they're showing up in the main window. I swear they didn't before (yeah, yeah, I know).

Lowlander wrote:

Trixmoto wrote:Like a few of my scripts, there is a report to run which populates the node in the background, then you can click on the node to few the results.

Right -- I assumed that to mean a node on the tree control on the left-hand side of the MediaMonkey window. I see nothing new there, and none of the existing nodes seem to contain anything about protected files.

Is that not where this "node" is?

OK, I feel stupid. I installed this script (couldn't find the installer, but figured it out), got it to run -- now where is the output? It asked me if I wanted to view the results; clicked "OK", nothing happened. Tried this again, closed/reopened MediaMonkey, ran it again, same result.

Windows 7, fully patched.

Ideas?

hey I'm kinda new to MM and it's growing on me. I was trying to use this script while reading up on all the posts about it and I eventually got it to work...somewhat. It scanned my whole library and it found the tracks that had protection on them. However, when it came to the end of its scan, this message came up.


Error #5 - Microsoft VBScript runtime error
Invalid procedure call or argument: 'Left'
File:"C:\Program Files\MediaMonkey\Scripts\Auto\FindProtected.vbs", Line 67, Column: 8

(don't know how to put a screen shot of it in this forum so somebody help me out! lol)

So, I opened up the script file, went to the line it said to go to and had no clue what to change. I only have limited knowledge of VB when it comes to trying to understand everything that's going on in, well, any of these scripts (and i tip my hat to those who write them). But, can someone please tell me what I need to do in order to fix this error!

I might have to try and come up with a more robust way of checking, but so far this is the best I've found.

trixmoto wrote:I don't know why the "Find Protected" script is not working, but as you appear to be using a non-english version of Windows I imagine you will need to translate "Protected" within the script.

I am using an English Version of Windows. (I am in the US.)
I will check the .vbs file, however I have no idea where it is so I will have to do a search. I am guessing that it will be in the MediaMonkey system folder, but I will scan my library folder as well.

thanks for the attention to this.
-fk

Well they are completely different scripts doing completely different things so I think it's unlikely that there is any connection. I imagine that you don't have any tracks with linked images which don't exist, and therefore the "Missing Album Art" script is correctly not showing any results. I don't know why the "Find Protected" script is not working, but as you appear to be using a non-english version of Windows I imagine you will need to translate "Protected" within the script.

nohitter151 wrote:Why install the missing art script when MM already does that natively under Files to edit | Missing album art?

I installed the Missing Art Script when the Find Protected Script didn't work as a test. Since neither script seems to be working with my Library than something must be awry.

-fk

I'm not sure, but I think the "Files To Edit" node lists tracks which don't have any artwork tags. My "Missing Album Art" script looks at artwork tags which link to external files and checks that the files exist, listing any tracks which have broken links.

Why install the missing art script when MM already does that natively under Files to edit | Missing album art?

trixmoto wrote:Is your operation system language different from English? If so you might need to open the .vbs file in a text editor and translate the "Protected" string.

The system language is English.
I have run the scan numerous times and still no dice. (nice script by the way)
I also installed the Missing Album Art script, ran the scan, and came up empty.

It is a puzzlement.
-fk

Is your operation system language different from English? If so you might need to open the .vbs file in a text editor and translate the "Protected" string.