(will have to remember that in future)No please do not. Which is fine, i'm not complaining or anything, but it might be worth mentioning, in case this is not normal behaviour. And I also noticed during the problematic scan (I got a chance to look at it briefly - it was on stage 4, ~20000 files scanned) that the ram usage was well over 500mb at this point. I don't know how winamp is built, so I don't know if this is likely or not, but I can mention that my winamp 5.6 is on average at 40mb of memory or so, but I have seen it on more or less idle states at well over 100mb. And why some have no problems at all with bigger libraries (different memory/os perhaps). It could also explain why people seem to get it only after a fair bit of scanning. Like the fact that it seems to give in (both on 5.56 and 5.6) of some kind of exhaustion. Can this be a memory issue? It would explain plenty of things. With the time it takes to scan with this thing, combined with the annoying job of editing filenames, I would not want to test such a thing. This can't be a problem, can it? I mean, Winamp indexes/plays stuff with japanese characters just fine. The only "unorthodox" filenames I currently leave unchanged is japanese titles. I got extra picky with this after this winamp problem. It goes like this:Īnd if there is unorthodox symbols in filenames/path, I edit them away and keep them only in the tag. It is a simple structure which I try keep free from strange symbols etc. Might also be an idea to provide some of the filepaths (or the structure of them) to get an idea of how your library + files are configured (may help, may not).Right. I really want to use this feature can someone shed some light on this? At a glance, it would seem like Winamp "gets tired" after lots of songs have been scanned at once, and then crash, but I don't know how viable accusation that is :PĮxcept for the parts in bold, the problem stays the same. So it never were problems with files - it is a problem with Winamp. Sad thing is that the scan actually passed when only thoose two albums were in. I figured the scan choked on theese albums, so for test I cleared my winamp, and put only theese two albums in, and scanned. I looked what song would be in this position and once again, it was the first song of an album. I removed this album from my library - scanned again. Turns out, it was the first song of an album. it was 12000 something (don't remember now) and I looked in another tool, which can follow the path structures, what album song lied there. Even ran that nifty little tool "mp3val" on my library. After it first happened, I went over my library to make sure nothing had strange characters in filenames etc. It gets flawlessly to step 4/4 every time, then sometime in the scan comes the windows error that winamp crashed. I delete the 3 files it creates (cddbplm.pdb, cddbplm.idx, cddbplm.gcf) between each try, as instructed, (or it fails to initialize). It crashes only at the stage 4/4, at seemingly random location, and if "more info" is clicked it mentions nde.dll <- on 5.6 it mentions instead "msvcr90.dll" Exactly the same fashion as my first post, albeit with some details changed.įor a reminder of my report (becouse it is still valid) and some explanation of the changes (see the bold parts), I quote my post from there instead of bumping that thread: Imported music, then scanned, whilst computer completely idle (my library takes forever to scan, so I just leave it)Īnd bang it crashed again. Installed ONLY one plugin, and that is the official last.fm plugin. I did a complete fresh install, removing all traces on winamp first. before I upgraded I posted this thread: and was told to upgrade.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |