Winamp ML import

[DJay]

Hi,
First of all thanks for the effort you put into this project, keep it up.
As for my problem, I copied what I think are all the necessary files from the Winamp ML folder and everything looks good except for what was most important to me, which was statistics. No "Play count" and "Rating" on tracks, so also empty in "Most Played", "Top Played", etc. Is there any other way to import in such a way as to keep this data? My dB is over 25 years old

[dro]

I'd really need to know what version of winamp you were trying to import from. As the import action I offer (accessed via the empty local library window or by going through media library window -> library button -> import -> import legacy (external) db) just needs to be pointed at an existing winamp settings folder (usually %appdata%\winamp) & as long as it's in the appropriate format then it should work.

I've only really tested the import action with copies of the local library from 5.63 to 5.666 specifically though I was given a set of main.dat/main.idx files last year from newer revision & my local library plug-in was able to import them without issue. If it's from a much older local library instance then it's most likely the layout of the columns might not be in the order that I'm expecting which would then prevent the import from seeing all of the data.

If needed you can message me a copy of the existing main.dat/main.idx from the winamp install you're trying to import so I can then check them out & if needed fix my importer &/or generate an appropriate copy of the library.dat/.idx files wacup uses for you to use with it.

[DJay]

I did the import via WACUP import legacy and it's better, but a lot of statistical data was lost in the process. In "Never Played" I have 9021 items vs. 1039 in Winamp out of 14860 in total. More than half of the ratings were also lost, 350 vs. 761.
I'm using Winamp v5.9.2, but I probably started with v1.x. I sent you the files via PM, take a look when you have a free moment. I'd be grateful.

[dro]

I've been able to get it to import it with what appears to be the expected total number of records (14860) along with the view specific numbers you've noted. However there's something odd going on with the import action depending on where the files are being accessed from which I'm trying to figure out at the moment which seems to be the likely explanation of why things didn't seem to import correctly.

[DJay]

This is good news. I have the files in c:\Users\Me\AppData\Roaming\Winamp\Plugins\ml\

[dro]

Have replied to your pm with hopefully complete db files for you to work with.

For you setup the location of the files wasn't an issue but part of my testing had me trying to use a read-only folder & that was helping to show part of the problem since it prevented the conversion of the existing db files to the newer nde based format that I use before being processed for the import action. However the import shouldn't have been attempting to mess with the files & not doing that resolves the incomplete / full failures that I'd been able to replicate as part of the import plus it also makes the importing to be somewhat quicker.

[DJay]

I'll answer here. Now everything is in the right place, thanks. I refreshed the metadata for all items and everything still looks fine. I remembered one thing, after I did the import legacy via WACUP the original db files in the Winamp folder was overwritten with an empty one. A backup of the files was created (I made my own anyway) but it was still a disturbing experience.

[dro]

I refreshed the metadata for all items and everything still looks fine.

That's good to know.

I remembered one thing, after I did the import legacy via WACUP the original db files in the Winamp folder was overwritten with an empty one. A backup of the files was created (I made my own anyway) but it was still a disturbing experience.

That's not meant to be happening & is related to the problem I found yesterday which stems from changes I'd made for my primary db file handling a while back but I missed by not fully re-testing for legacy db imports in missing that it was converting them to the newer format when that was never the intent of that mode. It should be fully resolved when the next build is ready to go up with them treated as a read-only action to avoid modification.