If You find your database please compress it and note me with download link so that we can analyze and see if there is something urgent needs to be added/fixed in MMW 4.x as it will be still maintained till MM5 gets stable release.

Unfortunately, I have created a new database, and purged all my recent, onsite backups. I am finished with my tagging spree, and now only have music that is recently added. My database is staying under 50MB, and I am so far unable to cause a failure.

I'll see if I can find another recent backup locally, otherwise I'll have to go to my offsite storage which will take some time. When I get it, I'll see about replicating with the Debug version, while capturing logs and running screen capture video.

I can sum up my procedure to produce a quick failure as compressing an hour of very heavy browsing into 5 minutes. I had about a dozen collections based on folder structure, and I had a tab open for each of them. My main view was based on the path, and had a good 15 settings for "Path does not contain." The entire Library view always took at least 5 seconds to load, and seemed to be the key. Mine had about 40 selected at the peak. Switching away from that before it was fully populated, or doing things to the view while this was populating seemed to cause the most trouble. If it were one of my professional databases, I'd say the program hitting the database wasn't handling query lag gracefully.

Otherwise, I'm looking forward to MMW5. The database improvements will likely help my situation. I'll keep an eye out for the notification that it's available. Until then, Good luck.

Hi,
Compact and Purge is one of MM5 features, along with rebuild database that would help, Also in MMW full text search and re-index along with full optimize helps.

I really need to see that in person to completely understand.

How about this. I was just bopping around my library. I had a good 9 or 10 tabs open. I was switching between them, trying to select an Artist in the middle column before the field had fully populated. (Cause I forget how long it takes for Media Monkey to read that into memory.) Changed the sort order of columns, used the keyboard to locate specific items in a list, and changed my mind several times about what group of files I wanted to play. (The Now playing list was populated, and then re-populated several times in fairly quick succession.)

I changed the middle column in my column view to "Actor" instead of "artist." Suddenly, I have 262 tracks that show up in this view, and none of them have the "Actor" Field populated, Because I do not use the "Actor" Field. I grabbed a screen shot. Then I switched to the tab next to it, and when I went back, it was as empty as it should be.

I closed the generic installation and opened my debug version. I couldn't close the debug version gracefully for several minutes because of some background process. Went back to the generic install, and things seemed to have calmed down. If I click on things, and wait for some some amount of time between doing anything, it doesn't fail as quickly. Unfortunately, I have no way of knowing if MMW is actually processing, because there is no visual feedback. And, it seems that I can overload the "buffer" pretty easily by performing a task before Media Monkey is done processing the previous request.

I spent a solid 5 minutes changing views, double-clicking on tracks, selecting tracks, and changing the sort order. I did absolutely no file modifications at all. There should have been about 7 writes to the database, because I played 7 different tracks. When I loaded the database into another installation, I found that this was the exact case according to the Backup Script.

So, problem solved. I'm just pushing Media Monkey too hard. The database isn't keeping up with what I'm asking Media Monkey to do. If I'm careful with what I'm doing, I know how to avoid problems.

I guess my next question, after opening one of my backup databases with SQLite Spy, is; why is my database over 500MB? I've only got 64k tracks, and I can't have more than a few tens of MBs of text in all my tags. Maybe with graphics, but why would that be stored in the database? It's all very strange.

Hi,
Are you sure that Backup or any other plugin make changes. Can you please try to use clean Vanilla MMW installation for a week and compare DB in the end? I'm not being able to replicate at all.

Just had this problem crop up a couple more times. As usual, it's not repeatable. It seems like the issue happens when I move around between tabs, or browse my library in between tagging and moves.

I've had it happen after just a few file changes, and after several thousand changed files. (Based off of the "Backup 6.0" script popup.)

Any luck with the logs I sent?

Nope, not a corrupted install. Still can't pin anything down, but it just happened again. I Used "Auto Organize" to move an album, and everything moved over on the drive, but the database now shows the file in both locations.

I was starting to think it was the files I was working with, but this is a much more recent addition to the library. Don't see how it could be database fragmentation, as I had done a full Optimization an hour ago. Backup was fresh as well. I was spending a good amount of time bouncing around to different tabs, doing searches, and generally looking through the library.

I haven't reinstalled all of my plugins yet, only the ones I specifically need, as I need them. Right now, I have "Magic Nodes," RegExp Find and Replace," "Discogs Tagger," and "Backup." Very few problems, just the interface annoyances.

Out of curiosity, I plugged the current database back into the old installation, and all the stuff came back. It seems that this was a corrupted install? The only thing I can think of is that the previous install was run on three different computers, and upgraded in place everytime there was an update.

Fresh install, fresh perspective.

I noticed that my tools dialogs looked different. Went through the Options and found "Always open Tools dialogs in standalone windows." I turned that on, and everything looked more familiar, but I started getting some of my wonky behavior. I turned it back off, and everything went back to OK. When I get a chance, I'll put my current database in the old Portable installation, and see what that fixes.

Sitting at 495 files changed according to the Backup 6.0 script. Usually I would start noticing weird behavior.

I optimize when Backup 6.0 reports more than a few hundred files modified. In fact, if anything, I optimize too much.

On a good day, when I was going through easy artists, I could get through a few hundred tracks in half an hour. It was common to see 1000 tracks modified when I ran Backup 6.0. I figured each time the file was modified it counted in that figure.

My process was;

• Auto Tag from web (Discogs)
• Copy all except first Genre from "Genre" to Custom Tag 1, using RegExp Find and Replace.
• Copy "Date" to "Original Date" if not included in album.
• Run Auto-increment track number script, if I needed.
• Run "Add string to end of title" to add "(Live)" to the end of the title, if needed.
• Auto-Organize files to new location.

When you say "DB Fragmentation," do you mean "within the tables of the database," or "the DB file in the filesystem? I suppose either one could explain my issue, but either one would also make me sad. Database fragmentation should never result in lost data, only poor performance.

I'm in the middle of reinstalling from scratch, again. Discogs tagger started crashing, and my usual method of dealing with a crashing plugin didn't work. I'm having problems with it making a connection to Discogs, and I'm trying to make sure it isn't a network access issue. I'll let you know if I start having fewer problems. So far, Installing and copying the files over from my backup isn't working as well as I had hoped. I'm starting that again, so I can install it from scratch, installing individual addons, making all required changes in the settings, and restoring the DB file.

Hi,
problem is most likely not tagging but DB fragmentation.

Thanks to Peke for investigating!

NewtonBoy wrote:Just wanted to make a public apology, and let you know that I was honestly amused that you called me out on my typo.

Sorry if that made you think twice, but you're reading way too much into it. It has nothing to do with "calling out".
It was just a chance to be silly/corny (a kind of humor I shamelessly enjoy). When you made the joke in the other topic about
staying at a Holiday Inn Express, I thought you were a joking around kind of guy. But such is the nature with humor, you
never know.

No worries though, just keep on doing what your doing and if i decide to be humorous, I'll try to make clear the intention.
I try to be careful about typos myself, but we are all bound to make them at times. I've certainly made my share!

And I have had no problems since.

It seems like all my problems are related to how many changes have happened in my database. I've started running the Backup 6.0 script every couple of hours, and paying attention to the number of track changes it has reported. When it gets over a few hundred, I run a full optimize, and things have been fairly smooth. I did do a bulk manual tag edit of 128 files, and it started strange behavior. Ran a backup/optimize, restarted, and everything is smoother again.

I can run the debug version for one of my sessions, but I don't know how much information a couple of hours of heavy tagging would produce, or how much you can get out of it.

Hi,
So, now I need to reread all this post and figure out what happened in MMW see to it fixed.

As of today I can confirm that moving 21k+ of tracks with MMW from one place to another place on NAS worked and failed on single playing track I was listening on other pc thru amp