I have large collection of music (with correct id3 tags) and there are some albums which can't be added to database. Seems there is some errors in id3 tags. When scanner finds such files - scanner puts this files into queue. On next cycle scanner again having error and again puts bad files into queue. And so on...

Can you add error counter? if song can't be added 3 (or more) times then it must be skipped.

>
>> This is part of log:
>> http://BLOCKED.COM/error.log
>>
>> Two bad .mp3 files:
>>
>> 5Mb http://BLOCKED.COM/10-InEleganceClosure.mp3
>>
>> 6Mb http://BLOCKED.COM/09-DrivingDownTheVoid.mp3
>>
>> I think that when such bad files is more than ten - queue filled up and
>> scanning process going into loop.
>>
>> P.S.: error message says something like:
>>
>> Could not process F:\Music\+Gothic & Metal\End Of You\Mimesis [2008]\10 -
>> In Elegance (Closure).mp3: nonnegative number needed
>> Parameter name: count - re-queueed.

> Ok, I am getting the same behavior. I have traced the issue down to the
> UltraID3 library. When it tries to read the MPEG header frames, it blows
> up. Unfortunately, their library is closed source so I can't get into it
> to see where its problem is. The guys at HundredMilesSoftware tell me that
> they have a new beta release v0.9.6.6 and I plugged it in to see if it
> would resolve the problem but they have changed they're public types and
> members and now several other features aren't backwards compatible.
>
> I will dig in some more to see if I can uncover some more intel on this
> problem.
>
> --Neal
>

Alright, after a few hours I have coded up my own ID3 Tag - header frame
parser so I could analyze the frames manually and I have found the problem.
See the attached screenshot which I have highlighted the variables in memory
from the frame dump. There is some long gibberish encoded in the Album and
Title tags of your tracks.

For example, the track: "In Elegence (Closure)" is being stored in the
header frame as: "In Elegence (Closure)\0\0\0\0\0\0\0\0\0\0\0\0\0\". The
backslash is a special character for the C# programming language (and most
languages) so the compiler is expecting special instructions and the
trailing Zero is not valid.

Ok, so I can't use the UltraID3 library with these files, which would mean
the only alternative would be to take my primitive ID3Tag reader prototype
and use it through out the CMS so I think I'm just going to leave things
alone since I don't have the time to create an ID3Tag library that would be
half as good as the one from HundredMilesSoftware.

But I will reduce the re-tries to quit after 1 minute or less of processing.

Hope this helps,
--Neal

PS: I'm going to post this thread in the forum so others can benefit from
the discovery.