This was fixed in 1402. Please confirm whether it works for you.

http://www.ventismedia.com/mantis/view.php?id=8077

Thanks.

-Rusty

Thanks. Tracked at http://www.ventismedia.com/mantis/view.php?id=8077 .

-Rusty

jiri wrote:There are still scripts listed in the debug log, is it that they are just present in the scripts.ini file? Please try to disable them completely. Also, have you tried to start with a clean DB?

Jiri

Error does not go away when I completely remove the scripts folder but it does with a clean database. So I put my db back in order to try to clean it and find what is causing the error, but when I rebooted the error didn't pop up. This is very weird.

There are still scripts listed in the debug log, is it that they are just present in the scripts.ini file? Please try to disable them completely. Also, have you tried to start with a clean DB?

Jiri

I removed the plugins and scripts and the same error and it produced a Microsoft crash report each time I close MM and I have to kill the session in the taskbar: http://dl.dropbox.com/u/13254132/player ... cripts.LOG

Nyn

Unfortunately the log doesn't help in this case. Please try to remove _all_ the scripts and plug-ins in order to try whether it fixes the issue (which it should). Note that all should be removed (at least temporarily), including scripts in MM folder and in user's folders. I.e. no 'Scripts: Read script -' and 'Going to load input plugin' lines should appear in the debug log after the clean up. In case it fixed the issue, you can try to return plug-ins/scripts one-by-one in order to find out which one is causing the problem.

Jiri

I updated to 1398 and now the problem is back, here is a copy of the debug log: http://dl.dropbox.com/u/13254132/wasapi ... tracks.LOG

jiri wrote:Could you please try to make sure it's really so? I think that you'd be the very first having such kind of problem with the WASAPI plug-in. And I don't see any reason why this plug-in should cause any problem.

Thanks,
Jiri

I've tried but I cannot reproduce it, so I am going to assume the error could be related to user error. I will try to document it if the error returns. This error occurred on my work machine where I do not install all builds or consistently do any testing or changes.

Nyn

Could you please try to make sure it's really so? I think that you'd be the very first having such kind of problem with the WASAPI plug-in. And I don't see any reason why this plug-in should cause any problem.

Thanks,
Jiri

It did for me, and the only thing I did was change my output plugin back to the directsound plugin and remove the script orphans from my ini file. I do not think it was the script orphans that were causing it because the vbs files were not available just the left over setings in the ini file, which I always seem to have in any of my ini files.

Nyn

Are you sure the difference is to add/remove out_wasapi.dll plug-in in Plugins folder? I.e. the issue appears when the plug-in is there and disappears when it isn't?

Jiri

Two things:

1. I removed the scripts I didn't realize I had some remnants from my mm3 installation, but that didn't change anything.
2. At some point I must have changed my output to the wasapi plugin, once I removed that the error message went away.

Nyn

nynaevelan wrote:I am also getting this message on my work machine, I upgraded from 1393 to 1397. Here is the log: http://dl.dropbox.com/u/13254132/player ... zation.LOG


Nyn

I see in the log that you have some script which creates temp tables like TmpDelSugg2TSC during MM startup, does the problem appear also if you start MM without any scripts?

I am also getting this message on my work machine, I upgraded from 1393 to 1397. Here is the log: http://dl.dropbox.com/u/13254132/player ... zation.LOG


Nyn

I have noticed very strange things happening with my tracks in the database.

The song information in Mediamonkey is all mixed up.

Some songs have completely wrong metadata listed in Mediamonkey, though, their ID3 tags seem fine.
In the MM library a song would have the Title, Artist, Album,etc of a completely different song. The filename and the ID3 tags are correct though, so MM is getting it's wires crossed somewhere.