I'm getting seemingly random "Access violation 007E6871 ..." errors when playing M4A files. I'm not doing anything else - MM is just playing the playlist.
MM doesn't crash though - it just carries on as normal after the Error Reporting dialog.
Using:
Glider skin; Win2003 server sp2; 2GB mem; Intel core2 6400; Soundmax audio drivers.
Alpha 6 - Access violation 007E6871 when playing M4A files
Moderator: Gurus
-
Guest
-
Guest
Re: Alpha 6 - Access violation 007E6871 when playing M4A fil
I experienced this exact behavior. I think it relates somehow to the install of MM3A6 and the corresponding database update. I finally uninstalled MM3A6, then located & deleted both the directory in which it was installed and the database file (mm.db, found in documents and settings/user/local settings/application data/mediamonkey). I then reinstalled MM3A6 and had it scan in all my music files, forcing it to build the new database from scratch rather than update it. I haven't had one of the errors since, and they were regular errors before the reinstall.Anonymous wrote:I'm getting seemingly random "Access violation 007E6871 ..." errors when playing M4A files. I'm not doing anything else - MM is just playing the playlist.
MM doesn't crash though - it just carries on as normal after the Error Reporting dialog.
Using:
Glider skin; Win2003 server sp2; 2GB mem; Intel core2 6400; Soundmax audio drivers.
Good luck, Danny
-
Guest
and with flac files http://www.mediamonkey.com/forum/viewtopic.php?t=19362Anonymous wrote:Thanks for that tip Danny - I'll give it a try and report back.
Also of note, is that I've been playing MP3s, not M4As, for the last 2 days and have not had the error. So it seems to only happen with M4As.
I did what you suggested Danny, but no change. Worth a try though. It still errors and halts playback. They should have got the message by now, so I just click "Don't Send" and carry on.
Currently evaluating a migration from MM4 (4.1.31.1919 on Win7 SP1/16Gig RAM/intel) to MM2024 (latest Debug version on Win11 24H2/16GB RAM/intel)
**If you're wondering why I'm still on MM4: It still has more useful-to-me plugins; and I prefer the GUI's responsiveness, panes spreadable over multi-monitors flexibility, and predictability (all coz it's more Windows-native). I also hate "flat design" for its visual inefficiency. For me, MM4's benefits are still > MM5, and MM5's downsides < MM4. There still appears to be way less MM5 plugins -- even after all this time. MM5 docs for plugin developers seem very undeveloped to me -- which makes me uninclined to invest into learning how to improve MM5 for my own wants.