hi, im testing this plugin, when i seem to convert the m4a files to mp3 my ram shoots up to 1.5gb (media monkey using 1.5gb of ram??) and completes the convert and seems to work but my whole computer just freezes up and pretty much dies till i kill the media monkey process with task manager.
does anyone else have this problem?
thanks
m4a Beta testing problems
Moderator: Gurus
Used it for ripping 2 CDs. That's all I could do before it froze MM3. I couldn't close MM3, so required reboot. Same thing happened with next CD. So gave up. Will wait for next release.
Pete, from Wellington, New Zealand.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.
confirmed, I've also had the ram shoot up from about ~600m to well over 2 gig. It seems to mainly happen whenever it has a problem with volume levelling...
Speaking of the m4a performance, it's rather erratic. Sometimes it both plays the (unprotected) m4a flawlessly, other times it freezes. Re-loading MM3 will oftimes correct the problem.
Volume levelling analysis on these m4a's is also unpredictable. It will sometimes calculate fine, other times (even on the same song) freeze up, and/or throw an Access Violation in some ...AAC...dll. Once the DLL has thrown the exception, the plugin is hosed and I can't play any m4a's at all - they are all treated as inaccessible until I restart MM.
This is consistent with MM3's issues with handling unrecognized files - I think the main thing the devs need to work on here is how to tell when their thread has gotten "hung up" so the rest of the application doesn't come to a grinding halt, and chew up CPU. It seems like it should fail after a certain number of tries.
Speaking of the m4a performance, it's rather erratic. Sometimes it both plays the (unprotected) m4a flawlessly, other times it freezes. Re-loading MM3 will oftimes correct the problem.
Volume levelling analysis on these m4a's is also unpredictable. It will sometimes calculate fine, other times (even on the same song) freeze up, and/or throw an Access Violation in some ...AAC...dll. Once the DLL has thrown the exception, the plugin is hosed and I can't play any m4a's at all - they are all treated as inaccessible until I restart MM.
This is consistent with MM3's issues with handling unrecognized files - I think the main thing the devs need to work on here is how to tell when their thread has gotten "hung up" so the rest of the application doesn't come to a grinding halt, and chew up CPU. It seems like it should fail after a certain number of tries.