by bkenobi69 » Tue May 28, 2013 9:31 am
This is related to the issues people are having with MMA, but I'm wondering if I could help by tweaking something in MMW. Basically, if I select a large playlist to sync from MMW to MMA via a wifi sync, I have found that if the list generation process in MMW takes too long, MMA tends to time out and display a "sync failed" dialog. For reference, I used DebugView to watch what MMW was doing. From my limited testing, it appears that MMA consistently times out after ~20 seconds in my setup if MMW hasn't responded. If I start with a static playlist (or auto, it doesn't matter) that has over 400 tracks, it will take longer than 20 seconds to generate the list and respond to MMA. I can consistently (no failures at all) sync if MMW only has a 400 track list, but I consistently fail if the list is large (600-1200 in my tests).
So, perhaps there is something that I can do with MMW to improve my list generation time. It was suggested that I could put MMW on the file server, but if the list is being generated from the database then MMW should be on the fastest machine which is where MMW is at the moment. Most of my tracks are FLAC. While I'm not going to change that, would other formats be quicker? Is there something that can be done on the MMW developer side to keep MMA aware that MMW is still working? Other thoughts?
Windows 7 64-bit MMW 4.1.0.1638 (local database)
Windows XP 32-bit file server
Gigabit network
Droid4 ICS 4.0.4
MMA 1.0.4.0133
This is related to the issues people are having with MMA, but I'm wondering if I could help by tweaking something in MMW. Basically, if I select a large playlist to sync from MMW to MMA via a wifi sync, I have found that if the list generation process in MMW takes too long, MMA tends to time out and display a "sync failed" dialog. For reference, I used DebugView to watch what MMW was doing. From my limited testing, it appears that MMA consistently times out after ~20 seconds in my setup if MMW hasn't responded. If I start with a static playlist (or auto, it doesn't matter) that has over 400 tracks, it will take longer than 20 seconds to generate the list and respond to MMA. I can consistently (no failures at all) sync if MMW only has a 400 track list, but I consistently fail if the list is large (600-1200 in my tests).
So, perhaps there is something that I can do with MMW to improve my list generation time. It was suggested that I could put MMW on the file server, but if the list is being generated from the database then MMW should be on the fastest machine which is where MMW is at the moment. Most of my tracks are FLAC. While I'm not going to change that, would other formats be quicker? Is there something that can be done on the MMW developer side to keep MMA aware that MMW is still working? Other thoughts?
Windows 7 64-bit MMW 4.1.0.1638 (local database)
Windows XP 32-bit file server
Gigabit network
Droid4 ICS 4.0.4
MMA 1.0.4.0133