i've been using/testing MM3 since the first RC and i gotta say i haven't been experiencing any problems at all and device sync seems a lot smoother too so im pretty happy
one thing that bothers me though is the relatively high cpu and mem usage in comparison to 2.x
i was wondering if this is something temporary and that once a 'final' build is made the code will get optimized a bit or if 3.0 is really that much heavier than 2.x
more then likely the code for debuging is causing the higher usage. when the code is removed in the final it might drop the usage some.
roving cowboy / keith hall. My skinshttp://www.mediamonkey.com/forum/viewto ... =9&t=16724 for some help check on Monkey's helpful messages at http://www.mediamonkey.com/forum/viewto ... 4008#44008MY SYSTEMS.1.Jukebox WinXp pro sp 3 version 3.5 gigabyte mb. 281 GHz amd athlon x2 240 built by me.) 2.WinXP pro sp3, vers 2.5.5 and vers 3.5 backup storage, shuttle 32a mb,734 MHz amd athlon put together by me.) 3.Dell demension, winxp pro sp3, mm3.5 spare jukebox.) 4.WinXp pro sp3, vers 3.5, dad's computer bought from computer store. )5. Samsung Galaxy A51 5G Android ) 6. amd a8-5600 apu 3.60ghz mm version 4 windows 7 pro bought from computer store.
