nohitter151 wrote:Much easier to remember the criticisms over the compliments

fair call!

You already complained about them a long time ago when I first made this skin: http://www.mediamonkey.com/forum/viewtopic.php?f=9&t=30102&p=197487&hilit=rating#p197486 [/quote] Hahaha That was me! and I still don't like them, but I take exception to your use of the word "complained" - in the contex...

This seems to be the same issue I reported here although perhaps I reported it differently?? Same result though. A full optimization never seems to end, or if I left it long enough i.e. overnight and half the next day it finished, but doing it again after completion doesn't get any faster it goes in...

MM3 didn't allow to cancel and would also fail on occasion for me. I normally would run the DB_Audit addon before optimizing the database to ensure it would run. Yes correct, with MM3 the option to cancel during the process is greyed out. With MM4 it isn't but that doesn't matter it does seem to be...

This is same for me. I have submitted a debug log showing this occurring on my system.

Opening Support ticket and attaching compresses debug log should help show us what is going on and where slowdown is. Also Maintain Library in MM3 before Import in MM4 could help. Hi Peke I will do a debug and send it in today My MM3 library was "maintained" before import into MM4, as I said in MM3...

Just to re-cap... My MM3 library of over 100k tracks took a couple of minutes for Full File Maintenance to happen. I kept on top of this. After installing MM4 and importing the MM3 data I noticed the performance was very sluggish so I ran file maintenance. This ran overnight for over 8 hours but nev...

Using File Maintenance, full optimization, the process cannot be stopped.
The cancel button is not live and all other functions, volume control, pause, stop, minimise etc are also locked.
Music continues to play and change tracks.

My apologies, this issue seems to have resolved itself.
I compacted the database with File Maintenance overnight, re-booted and can now access and configure the plugin without the problem happening.
Obviously something screwed up in my setup.

As above, editing the configuration of out_wasapi.dll causes mediamonkey to lock up and generates an error pop-up. I have completed the request for information and sent to support. I had to use Task Manager to exit MM I am able to reproduce this every time I try to edit the configuration for out_was...

I had this issue with a later update to MM3. The install seemed to find an old MM2.5 install on another drive other than C: and proceeded to extract info for the current install from this. Once I realised what was happenning I uninstalled 2.5 and re-installed MM3 and the problem had gone. For some r...

Isn't it DJ software, I'm sure I have seen this before??

nohitter151 wrote:Just installed 1303 on a 64 bit Windows 7 and did not observe either of those problems.

Well lucky you!

Would not install to default directory e.g. c:\program files (x86) wanted to install to e:\mediamonkey - manual settings installed ok
Broken tools menu - no script sub menu available, re-install to 1300 and all ok

It's in the User Control Panel (top left of screen) and then the Board Preferences tab.