sorry that i abuse this thread for my issues...
i have investigated the same issue! if MM crashes or i have to close it with the task manager not all
data is stored in the database after relaunch from MM.
i have saw the following settings are not stored: (examples)
- song additions to playlists
- playcounts and last played date
- new entries in database
some times is also only a part, which is lost. this happens when i want to close MM and MM hangs on closure
prozess. then i have to kill MM trough task manager and only a part of the data is lost.
for declaration porposes: this issue affects only the data from the current session. its look like MM stores all
data in a transaction log or somehing. (i can see an journal file in the database location) and stores the data
on closure prozess. and on opening prozess the journal will be purged. is this possible?
if i start no journal exists, after same changes the journal kb-size is growing up. and will deleted after a few seconds.
if the crash happens on closure there is a "huge" journal file left with maybe 400kb or more. could it be, that the journal
writeback to database is malfunction in this situation?
i'm using now the newest beta release but this happens also with the earlier releases.