by AnthonyM1229 » Sat May 26, 2018 9:22 am
I figured I'd give 1867 a try after I read about Issue 0014820 that tries to correct long load times. MM has always taken around a minute or longer to load for me, but I always thought it's because I have such a huge music library (now over 300k tracks). However, my environment is significantly different: Windows 7 x64, using MM in Portable mode, and no anti-virus (Windows Defender is disabled).
I wasn't expecting much, but didn't think it'd hurt to try anyway, to see if I'd have any decrease in loading times. Well, as it turns out, 1867 causes issues for me. I was greeted with several memory access violation errors on startup, and had to forcefully terminate MM from my task manager. So, I installed the Debug version of 1867 and fired up DebugView. I sent at least one error report with my forum user name @gmail.com as a contact address.
I suspected issues with the MegaDJ extension (
http://mediamonkey.com/forum/viewtopic. ... lit=megadj), an extension crucial to my MM experience. Like Magic Nodes, it creates its own node that populates child nodes I created (which function as custom playlists with weighted random shuffling and other criteria). I also made changes to my local copy of the script that make MM switch my playlists on a schedule, and either my changes or the original script, or both, require the script to be loaded on startup. (As a side note, I've been meaning to write a post of some features I'd love to see in MM5, and that would definitely include something replicating MegaDJ's functionality. I still hope to get around to making that post eventually.)
So, I temporarily disabled MegaDJ, and restarted MM. But I still received an access violation error on startup. So, maybe something else is going on? Upon request, I have a ZIP file containing my final debug log and an ELF log that I can send. Should I also file a support ticket? In the meantime, I've reverted to 1864, because I need my music functioning properly, but I'll be happy to test a new update if necessary.
I figured I'd give 1867 a try after I read about Issue 0014820 that tries to correct long load times. MM has always taken around a minute or longer to load for me, but I always thought it's because I have such a huge music library (now over 300k tracks). However, my environment is significantly different: Windows 7 x64, using MM in Portable mode, and no anti-virus (Windows Defender is disabled).
I wasn't expecting much, but didn't think it'd hurt to try anyway, to see if I'd have any decrease in loading times. Well, as it turns out, 1867 causes issues for me. I was greeted with several memory access violation errors on startup, and had to forcefully terminate MM from my task manager. So, I installed the Debug version of 1867 and fired up DebugView. I sent at least one error report with my forum user name @gmail.com as a contact address.
I suspected issues with the MegaDJ extension (http://mediamonkey.com/forum/viewtopic.php?f=2&t=33850&hilit=megadj), an extension crucial to my MM experience. Like Magic Nodes, it creates its own node that populates child nodes I created (which function as custom playlists with weighted random shuffling and other criteria). I also made changes to my local copy of the script that make MM switch my playlists on a schedule, and either my changes or the original script, or both, require the script to be loaded on startup. (As a side note, I've been meaning to write a post of some features I'd love to see in MM5, and that would definitely include something replicating MegaDJ's functionality. I still hope to get around to making that post eventually.)
So, I temporarily disabled MegaDJ, and restarted MM. But I still received an access violation error on startup. So, maybe something else is going on? Upon request, I have a ZIP file containing my final debug log and an ELF log that I can send. Should I also file a support ticket? In the meantime, I've reverted to 1864, because I need my music functioning properly, but I'll be happy to test a new update if necessary.
