- I don't know how you determine the missing songs, but would it be helpful to generate an array with the size according to the number of songs (e.g. dim array(20) as boolean) and set entry 8 and 12 as true, when track 8 and 12 are in the database. So, after checking which tracks are there it is very easy to get those songs which are missing. You just have to loop through the array and look for those entries which are not set to true.

- I have some albums where one or two songs have no track number. In that case the script crashes with error #7 (not enough memory) in line 134, column 3

- While integrating new songs into my library i sometimes have the same songs in different places, but with the same tag information. In that case the script also crashes with error #457 (something like 'key already associated'.

- By the way: Sorting the node list would be great to find album information

it only does one track before the missing (this is in the authors note bit)

- I don't know how you determine the missing songs, but would it be helpful to generate an array with the size according to the number of songs (e.g. dim array(20) as boolean) and set entry 8 and 12 as true, when track 8 and 12 are in the database. So, after checking which tracks are there it is very easy to get those songs which are missing. You just have to loop through the array and look for those entries which are not set to true.

tbh, im not sure how it works! (alot of trial and error!!!)
Yea, that does sound a better way of doing it, and I might change to that in a later version. (will keep this in mind)

- I have some albums where one or two songs have no track number. In that case the script crashes with error #7 (not enough memory) in line 134, column 3

I know about this, and again, its in the authors notes

- While integrating new songs into my library i sometimes have the same songs in different places, but with the same tag information. In that case the script also crashes with error #457 (something like 'key already associated'.

arrr! didnt know about this! I will look into it! thanks!

- By the way: Sorting the node list would be great to find album information

Yep, I want it to do that as well!

I hope I could help a bit... good luck

Regards

Maaspuck

YOu have been, and thanks, I will need it!

@Eyal

Hi guys
It's working fine with all albums that do not have more than one consecutive missing songs.

Updated:
v0.3 (15/07/07)
* Did a bit of moving/renameing/recoding/comming on the script.
* It can list all the albums now (From TaggingingInconsistencies, see comments with ***)
* Rewritten the algorithm, which calculates the missing track.
* Overcame/fix/got working a another "What works". (Two or more in a row missing)
* Sorted albums in a different order (it was out of how many was missing, now by the arist, album)

Great! It's working fine for me now, even with various artists albums.

Two things I noticed:

1) The script will crash if 2 tracks of an album have the same track#.

2) I have some various artists albums where I forgot to change the Artist-Album field to "Various". This result in every track listed as an album in the node. It's not the problem, your script is reacting as expected, except it crash.

Its working now? YEY! (ive done something right )
so it is working with your tracks which start at 101? (if its not, I think if the value of J was changed to to "101" instead of "1"), *im not sure, I will have to edit some of my songs/tracks*

1.) as I dont have same track#, I couldn't tested it out, so a thank you

2.) I havent yet tag my Artist-Albums yet (they are the same as artist), again, thank you, I will be looking into this! Crashes, hu? with a msgbox or does it "loop out", and MM stops working/responsing?

But overall it's fast and I like it.

Well thank you!
Its half the reason why I made it (other half is that I needed something to do it )