Winamp Playlist Generator: reset database causes crash

[redstang]

Hello,

in both 5.61 and now 5.62, the playlist generator fails to initialize and advises to reset the database. Upon going into the config popup for 'Nullsoft Playlist Generator v1.7', if I click the 'Reset Database...' button Winamp immediately crashes.

Please advise - is there another way to reset the database? Is there a newer version of the playlist generator (couldn't find one).

Thanks.

(running Windows 7 64bit)

[edit - issue resolved]

I found another post about the db files in the plugins\gracenote directory, was able to find it and deleted all the files there and was then able to rescan. Now working ok.

[rrozema]

I have the same issue repeatedly on 2 pcs, one using winamp v5.61 and one using v5.621. Both run windows 7 64 bit (Dutch). I can not use the view similar tracks functionality at all because I can not reset the database. I do have a rather lage collection of mp3's, 43618 tracks. Whenever I try to view similar tracks, I am told to reset the database and when I do, winamp crashes after having asked whether I am sure I want to do that.

I don't know which files to delete (and even so, that is not a fix, it's a work-around).


Gebeurtenisnaam van probleem: APPCRASH
Naam van de toepassing: winamp.exe
Versie van toepassing: 5.6.1.3133
Tijdstempel van toepassing: 4d88ec8b
Naam van foutmodule: ml_plg.dll
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 4d88eca1
Uitzonderingscode: c0000005
Uitzonderingsmarge: 00007252
Versie van besturingssysteem: 6.1.7601.2.1.0.256.1
Landinstelling-id: 1043
Aanvullende informatie 1: 0a9e
Aanvullende informatie 2: 0a9e372d3b4ad19135b953a78882e789
Aanvullende informatie 3: 0a9e
Aanvullende informatie 4: 0a9e372d3b4ad19135b953a78882e789

[sturobb]

Same issue

Hopefully someone can respond to this thread soon. I too have a large datebase of MP3's and I need to reset the playlist generator as it shows failed to initialize. When I press the reset button I am told to close out the program. Please help.

[muppet]

I just this problem too.

@sturobb: Have you cleaned all the files in your Application Data\Winamp\Plugins\Gracenote directory? That fixed it for me. It happens on a regular basis though, damnit.

[MisterMagoogle]

This may help you.

While Winamp is not running, try deleting the cddbplm.pdb cddbplm.idx cddbplm.gcf and elists.db files. That will start with a clean slate, then try rescanning.

The files will be located in...

%AppData%\WInamp\Plugins\Gracenote Where %appdata% is a shortcut to the 'Application Data'/'User Settings' folder. You can click on the Start button > click the Run icon and put %AppData%\WInamp\Plugins\Gracenote in the Open box and click OK. That should bring you to the Gracenote data folder in 'Application Data'/'User Settings'.

The actual path will vary with the current Windows version you are using. Example...

Windows Vista & Win7
c:\users\UserName\AppData\Roaming\Winamp\Plugins\Gracenote

For others reading this thread and using an earlier version of Windows...
Windows 2000 Windows XP
C:\Documents and Settings\UserName\Application Data\Winamp\Plugins\Gracenote

For some Win XP & 2000 users the files may be located in
C:\Program Files\Winamp\Plugins\Gracenote


Known bug, alas.

You'll have to delete the database files...

Close Winamp

In Windows Explorer, go to the Winamp\Plugins\Gracenote folder

Delete these 3 files only:

cddbplm.gcf :
search-ms:displayname=Search%20Results%20in%20HP%20(C%3A)&crumb=filename%3A~<cddbplm.gcf%20OR%20System.Generic.String%3Acddbplm.gcf&crumb=location:C%3A%5C
cddbplm.pdb :
search-ms:displayname=Search%20Results%20in%20HP%20(C%3A)&crumb=filename%3A~<cddbplm.pdb%20OR%20System.Generic.String%3Acddbplm.pdb&crumb=location:C%3A%5C
cddbplm.idx :
search-ms:displayname=Search%20Results%20in%20HP%20(C%3A)&crumb=filename%3A~<cddbplm.idx%20OR%20System.Generic.String%3Acddbplm.idx&crumb=location:C%3A%5C
elists.db:
search-ms:displayname=Search%20Results%20in%20HP%20(C%3A)&crumb=filename%3A~<elists.db%20OR%20System.Generic.String%3Aelists.db&crumb=location:C%3A%5C

Reopen Winamp

Make sure there's an internet connection available, and Winamp is not being blocked by a firewall.

Restart the Playlist Generator scan, and let it complete 100%, without interrupt.

The bug is fixed for the next release.

Also, if you're using a proxy connection, then it isn't going to work until 5.51 (another known bug, already fixed internally).

If you have a new install of 5.5 or later then Winamp stores its settings, and I assume these files in %appdata%\Winamp

[Sasakr]

I'd like to use this feature but the process always causes the Winamp crash. I tried to delete the files mentioned above but it didn't helped. It always fails at the same progress level - 113 of 421 files.

How to make it working?

[MrSinatra]

the problem may be with the files themselves, (run them thru mp3tag and mp3val) or even possibly with the language, in either the tags or the app.

i assume you are using 5.63?

[Sasakr]

Yes, I have the latest version 5.63.

What do you mean: "run them thru mp3tag"? What should I exactly do, please?

But I run them thru mp3val, there were three files that stopped the scan, so I deleted them to let it finish the scan. After scan, I let it fix the corrupted files.

But it didn't help, creating of the database in Winamps still causes crash at the same progress. Change of the language also doesn't help.

[MrSinatra]

u probably didn't need to delete them, only move them temporarily. its prob due to a diacritic or something like that.

do u know which file it stops on?

have you tried doing it in 50 song groups?

mp3tag spots bad tags, the way mp3val spots bad headers.

[Sasakr]

Of course I didn't actualy delete them, I moved them into different directory temporarily.

What do you mean? The database creating in Winamp or the scan in mp3val? All I know about the database creating process is what you can see in the screenshot. I dunno which file is causing it.

How to choose 50 songs only? Winamp automatically scans all files in my music directory. You mean I should delete my winamp media library, then add just a small group of songs and try to make the database? Good idea, gonna try it.

How exactly should I make the correction process in mp3tag? I'm a bit confused of this program.

Thank you.

[Aminifu]

Hi Sasakr,

In addition to (or instead of) corrupt media and/or database files, you may be having the problem some have with Winamp trying to use too much memory during the scan. You can monitor the memory usage with the Windows Task Manager. Look in the "Working Set (Memory)" column. Also enable the "Peak Working Set (Memory)" column, this lets you see the maximum amount of memory Winamp will momentarily attempt to use. If the memory usage climbs over a critical level the scan will fail. This point varies from user to user depending on the amount of memory available when the scan starts.

If this is your problem, the work-around is to do the scan in stages. Monitor the memory usage and stop the scan before the critical level is reached. Shutdown Winamp, then restart it and restart the scan. The scan picks up from where it was stopped. It could take several stages to complete the scan this way.

Even if you get this Playlist Generator working, some users are not happy with the playlist that is generated. I use this "Gracenote" supported feature in Winamp and the "MusicIP Mixer" app. I prefer the results from MusicIP Mixer.

The thread linked below discusses this issue (there are more threads).

http://forums.winamp.com/showthread.php?t=340577

Post #8 in the thread linked below provides a link for downloading MusicIP Mixer.

http://forums.winamp.com/showthread.php?t=343397

[Sasakr]

Thank you, but RAM is definitely not a problem. Winamp memory usage peak is 121 MB and there are still more than 2 GB of free RAM.

I tried this: I stop the scan just before it crashes and then restart Winamp. Start a new scan, but it makes the whole new scan from the beginning... and crashes as usualy.

NOw I'm trying MusicIP Mixer but it seems it will need a few weeks to analyse all files :-D

[Aminifu]

Thank you, but RAM is definitely not a problem. Winamp memory usage peak is 121 MB and there are still more than 2 GB of free RAM.

I tried this: I stop the scan just before it crashes and then restart Winamp. Start a new scan, but it makes the whole new scan from the beginning... and crashes as usualy.

NOw I'm trying MusicIP Mixer but it seems it will need a few weeks to analyse all files :-D

Maybe the problem is on the "Gracenote" end of things. You could use the Windows Resource Monitor - Networking tab to monitor the communication. It is a weird issue. I have not done an initial scan in some time, but it works for me, as I add new files to my collection.

Anyway, I think you will like the "MusicIP Mixer" better. Sorry I forgot to mention that the initial scan is slow. Gracenote's is also, when it works. I assume your files have the basic metadata tags; artist, title, genre, etc.

Furthermore, I'm still looking for an automatic playlist generator that can do a better job than I can do manually, imo. I normally only use the automatics when I'm feeling lazy (and they do help me sometimes by selecting files that I had forgot I have).

[Sasakr]

Yes, the scan is extremely slow. It have taken a few hours of 100 % load of my 4 core CPU to analyse 1500 out of my 6500 songs. It's gonna take a few days I guess.

Some tags are wrong but I'm gonna fix them, especialy genre tags which have never been important to me.

Yeah, it's difficult to find a good settings to let it create "expected" playlists. Check my in the attachment. But I guess it will never be better than human's choice :-)

And you can see my CPU load when analysing files. Extreme!

[Aminifu]

I had about 6,000 files when I did my initial scan. I let it run (by itself) overnight while I was sleeping and it was done the next day.

If you want to reduce the load on your system while you are running other apps, there are settings on the general preferences tab.

If you care to know more about how MusicIP works, I've provided a link to an Wikipedia article below. From what I understand, the scan makes an acoustic fingerprint of the songs which makes the scan slow. Tags are not used during the scan, but can be important when mixes are made.

http://en.wikipedia.org/wiki/AmpliFIND

After you've had some time with it, please post back and let me know what you think.