this error has been fixed you don't say what version of monkey your using.?

if your using older then mm3.2 then get that one.

see if it will fix the error if not then you might try one thing but windows 7 people might have to find a different program that will work on win7. but try speeding up your decoder priority. since you have xp sp3 you can use the program called "Priority Static control " i found it on majorgeeks.com when you set it up you will need to left click on the tray icon to get the panel up to set the prioritys with.

but you also need the program running that you want to adjust. now becareful with this program don't tell it to adjust any of the windows processes they might just mess up your computer cause they don't like being messed with. but this decoder.exe does not do that if you only speed it up to high priority. you will also get faster ripping doing that. and converting anything that decoder.exe runs will be faster. still like i said only in high priority should it be run. i have tried it in realtime and got tons of crashing until i got in to safe mode and changed it back to high. so decoder wants less then a realtime setting but more then the normal setting.


that is the only thing i can think of that will help you because that will get the decoder through its jobs faster and might be finished before you close the laptop lid, that way.

I've just started using MM, but I'm running XP sp3. I only see this error when I need to close the laptop lid. I always stop the song that's playing, but I forget the volume of tracks is being normalized in the background. Once I reopen the laptop and dismiss the error, it picks up where it left off and continues running.

Just got a new Dell XPS 410 (Duo Core 2, 2.4Ghz) with Vista Premium already installed, loaded 3.0.0.1020 and asked it to import my Music directory. Within 20 seconds I started getting the "Decoder.exe have stopped working message".

This is very easy to reproduce and I am wondering what type of debug I can provide specifically on this problem. Let me know and I will get it done.

Ashenden

This is partly why I'm not a big fan of huge 'all in one - cross talk' threads.

Too much blah, blah to skim through to find little threasures like that post about your finding in regards to tagging and album/track gains. You may want to copy the post to a new Topic here, so we can share findings within this particual subject.

I have just started testing Album Level playback, and will do so over the next few days. Hope to find it satisfactory for now, as I do not feel like doing another 5 day session.

Thank you for sharing the info. I appreciate it.

DiddeLeeDoo, this may or may not be important to you, but you should at least be aware of this...

http://www.mediamonkey.com/forum/viewto ... 7307#77307

While I think the back ground processing is awesome, something is not quite right with the analysis calculations and tags.

I was just sitting here, quietly celebrating that the AutoAnalyzing finally is finished after 5-6 days.!! Time to explore MM3 further.

One way to help the developers might be to share trouble files, so they can have a set of files available to them to test the decoder routine. I believe http://www.rapidshare.com/ is an easy way to upload trouble files, and share the link to the MM Team.

http://download.sysinternals.com/Files/DebugView.zip will show you what's going on. More can be read about bug reporting at http://www.mediamonkey.com/forum/viewtopic.php?t=69

I have the same problem with decoder.exe crashing when i'm analyzing tracks, or even allow mediamonkey to play for a long time.

How do I make a debug report ?

AMD Athalon Xp 2800+
1GB ram
Windows Vista Business

It looks like that this morning Teknojnky.

After about 20 hours run, it must have hit a bad file and the Auto Leveling stopped. I restarted MM and the same thing happened after some minutes.

I then disabled auto leveling, and started 14 separate instances of leveling before bedtime, and found two of them had stopped due to errors this morning.

1x DRM, and 1x general error.

I believe errors should simply be written to a log file that can be read after everything is finished.

Error dialogs during it's run, can mean that a whole nights auto leveling can be lost due to a silly DRM message or something like that.

I suspect it has more to do with corrupted tags and/or problems reading certain types of file tags.

@Teknojnky

It's time like this you want the most powerful processor around.

Have had a very good run with the Automatic Analyzing on a Pentium 2.8. Done around 15 hours constant analyzing at Highest Priority, without any kind of crash. This while playing music. Mind you, I have the Player hidden.

Later this week I'll try on a AMD based computer to see if I can get a similar run there.

So far it seems to me that most crashes is due to the GUI, and LAN.. Not really sure yet.. takes time to figure out..

Anonymous wrote:

PetrCBR wrote: I'm have no problem with MM3 in Vista. Have you tried run MM3 with admin rights ?

Just tried running it with Admin rights, still the same problem. I will try the other workarounds.

Sorry, wasn't logged in.

PetrCBR wrote: I'm have no problem with MM3 in Vista. Have you tried run MM3 with admin rights ?

Just tried running it with Admin rights, still the same problem. I will try the other workarounds.

If you disable the background analyze unknown volume files, then you can use MM3 normally.

I've found that background analysis and scan for duplicates are very unstable and/or slow.

I did mange to get my entire library re-scanned in the new database, its currently @ 210 megs for the DB file. 660+ gigs of mixed formats, mostly mp3 and flac but several other common types too.

Ashenden wrote:Yep, got the same problem running 3.0.0.1017 on my Vista OS. I guess I'll have to be a bit patient (or run the script above) before I can use my newly acquired Lifetime License.

And all I wanted was a good media manager that would run under Vista.....

I'm have no problem with MM3 in Vista. Have you tried run MM3 with admin rights ?

I think I read somewhere that the SendKeys command is non functional in Vista, or was it IE7... not sure.

that shl.SendKeys("%d") line simply send Alt D to close the window.
Maybe shl.SendKeys("%{F4}") will be better. As it is a general close command, but again, I think something have changed with the SendKeys command all together in Vista|IE7