4.0.6: Failure to Rip (Works with 4.0.3)

[simonbrads]

Sorry, I didn't get the exact strings, because I was more interested in getting my stuff done. But I guess the developers will know what I'm talking about.

Tried to rip my first CD since upgrading to 4.0.6: The Smashing Pumpkins: Oceania.

During the last track, a dialog popped up saying (something close to) "Error ripping track 13; this dialog will auto dismiss in 10 seconds". Dialog went away, rip finished, and an almost identical dialog popped up (just not auto dismissing). Checked with CUETools: track 13 ripped incorrectly.

Tried again: track was ripped identically, and a third time. And there were no obvious read errors: the rip didn't pause or retry at any point.

Reverted back to 4.0.3 (again: 4.0.5 didn't work for me, either, but for a different reason!), and the entire CD ripped perfectly (CUETools verified) first time.

I have the feeling that MM's core functionality is being compromised in favour of new (and, to me, unimportant) functionality. I guess I'll be sticking with 4.0.3 for quite a while, as it seems to work perfectly for me -- if I stick with CUETools for rip verification!

[MMuser2011]

Please have a look here: http://www.mediamonkey.com/forum/viewto ... 8&p=342189
Maybe it is a similar problem?

[Lowlander]

A debug log would be useful as from 4.0.3 to 4.0.6 has had some bug fixes in this area: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

[RyboFlavin]

I came here to report the same problem with 4.0.6. Of the 15 CD's that I tried to rip, 14 of them failed to rip starting with track #10 or later.

As a test, I replaced the file "hpCDBurn.dll" with the 6/12/2012 10:37PM version (just as I had to do in order to get v.4.0.5 to work) and this completely resolves the problem with v.4.0.6 as well.

The difference between 4.0.5 and 4.0.6 is that every track failed to rip using 4.0.5, but only the tracks after #9 seem to be failing with 4.0.6.

I am ripping using 320 CBR, secure read, and on the fly encoding. I would be happy to post a debug log, but I'm not sure how to obtain it.

[simonbrads]

RyboFlavin: See the link in Lowlander's post, right before yours. (I'd do a debug log myself, but I just don't have time right now. Going through a hectic period!)

At least it's not just me seeing these things, anyway. I have to say, if you're going to be doing a bunch of ripping, I'd suggest installing 4.0.3, as that ripped through my entire collection without any problems whatsoever. (On the other hand, I've problems with every released version since that!) Secure read is fine. Just make sure you don't use the AccurateRip verification, as that corrupts every track ripped!

Then again, you seem to have a pretty good workaround of your own, so fair enough. If your confidence is low, use CUETools to verify what you've ripped. (I do this as a matter of course, anyway.)