Page 1 of 1

Trouble when ripping with MM 4.0.7.1502-05

Posted: Sun Oct 07, 2012 9:15 am
by stereofool
Sorry if this isn't in the right place, but I couldn't figure out if this is a 'bug' issue (???), or am I doing something wrong with this newer version?

When I have tried MM Betas 4.0.7.1502-05 (on 3 different Windows 7 computers)...while trying to rip CD's to HDD (FLAC 0 compression)...in every instance the ripping 'freezes' at track 1, and the program becomes 'not-responding'.

I can revert to MM 4.0.6.1501 and ripping proceeds smoothly, every time...any thoughts?

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Sun Oct 07, 2012 10:47 am
by Lowlander
Capture this failure in a debug log (step 4b) with the debug version of MediaMonkey 4.0.7.1505 and send it to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Mon Oct 08, 2012 1:03 am
by Ludek
Thank you for reporting this, there was really a problem, will be fixed as http://www.ventismedia.com/mantis/view.php?id=9787

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Mon Oct 08, 2012 3:48 am
by Dan33185
Hesitated to report this as I thought maybe I just had a few bad discs, glad to see it wasn't just me, look forward to a fix.

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Mon Oct 15, 2012 10:19 pm
by rusty
Fyi, this is fixed in build 1506. Can you confirm that it's working for you?

-Rusty

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Sat Oct 20, 2012 6:40 pm
by Dan33185
Just ripped a few cds with more than 1 track ripped each, no problems so far.

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Wed Nov 21, 2012 10:42 pm
by rom
Im having exactly the same problem with new CD in perfect condition. There is always 1 track (up to 5-6 tracks) that just get skipped (MM just freezes momentarily while ripping the track(s) in question). im using the latest version (4.0.7.1511). is there any fix for it?

Re: Trouble when ripping with MM 4.0.7.1502-05

Posted: Wed Nov 21, 2012 11:22 pm
by Lowlander
You should capture this in a debug log (step 4b) and send it to support so the developers can analyze what is causing this on your system: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=69