Excellent build! I've now power-ripped ~20 CDs using both the G: and H: drives. MC has performed flawlessly. The timing of the messages and the window updates now occurs in a "sensible order" that is consistent every time. It feels right. Specifics:
1. Thx for handling the WM_LBUTTONDBLCLK message. It might have made you laugh when you read it, but it's another one of the slick things that make the program feel special when I use it.
2. Thx also for handling blank fields in the Tag Info combo boxes! Last night I felt like I'd lost an important tool. Tonight, I'm truly happy to have it back, and now it's more powerful since I can also blank-out fields using only mouse commands. I didn't realize that would be as useful as it is.
3. As I mentioned, power-ripping now works perfectly.
4. My comment about "Perhaps there is an extra read during Digital Secure?" can be dismissed. Each CD/track can be read at different speeds for many reasons; I apparently ran across a series of slower CDs. Or perhaps you fixed something.
Either way, I'm getting the rip performance I've come to expect on this PC.
Again tonight, I've been trying to break the software as well as trying to use it. I haven't been able to!!! (limited of course to the areas I use.) I saw from another posting that .274 was a designated release. I sincerely hope you replace it with .275 ASAP, or perhaps a .276 that is even more finely tuned. The sequence and timing of the CD/DVD reads, the table lookups, the YADB lookup, the rip queuing and everything is now *very* disciplined. Regardless of when I do what, MC does sensible things in the right order... often behind the scenes and more quickly. So please register my vote to make this build the release build.
I'd like to bring up the "delayed-write" issue one last time. We know of one known bug from delayed-write that was posted shortly after one of my postings. As I review the MC bug list, I see things that seem related to the delayed-write concept. When I think about the code, I wonder how many places need to check the DelayedWritePending flag and how many are still undiscovered. You've done a *fantastic* job pulling this release together, so please take this suggestion in the positive light I offer it: if there is some magic place in the code where you could have an option to disable Delayed-Write, there would be two benefits. For anal-retentives like me, I can tolerate a few delays in pursuit of perfection. For you... you get a work-around check-box should unforeseen problems develop. If you analyze an error to be related to delayed-write, you could have the user turn it off while you correct the problem, thus relieving many unnecessary headaches and late night programming sessions. FWIW, IMHO, programmer-to-programmer.
Back to my music... and a great version of MC9 to go with it.
JimH, a while ago you were looking for a slogan. Suggestion:
Play everything you love