Two oddities/bugs to report:
KNOWN PROBLEM, NEW CONTEXT: Existing problem is MC silently changing Filename value without changing physical file just happened during ripping. I wasn't playing anything. Inserted new CD, MC did YADB lookup and started to rip. Then on Track 1 it reported the long error that essentially means "can't find/open file". What file? The CD track? Or the new file it has just created via ripping? Don't know, but clicked to continue and it did. The file actually was ripped OK.
Then I needed to edit the name of one track that YADB had completely wrong, and BAM the problem happened to this track. I tried to paste in the correct file name but MC kept reverting to the wrong name, immediately renaming what I pasted. So I dragged the physical file into the Recently Ripped view, but it wouldn't play. Looking at the Filename field, the Album and Name part of the path were BLANK in the field, while the drive letter and upper part of the path were OK. So I presume MC was again instantly trying to rename the Filename field. The solution was to delete the now-two instances of the track from the Recently Ripped view. Then I could drag the file back in and it worked. I still had to rename the bad title, but typing slowly, that worked.
But a whole lot of work just to rip 12 tracks from one CD.
NEW PROBLEM, in recent builds: Sorting in the Recently Ripped view on the Disc column, if there is NO value in the field, it won't sort -- very odd. Example: I ripped a 2-CD set. After the first CD was ripped, I selected all tracks and put "1" in the Disc field, no problem. After the second CD ripped, I wanted to put "2" in the Disc field of its tracks. So I click the Disc column to sort, to get all the "1" values together, and all the BLANK values together, making it easy to select the BLANK values and type in "2". Nope, won't sort. I can sort on other fields, but clicking the head of the Disc column does nothing.
One guess: The BLANK Disc values are NULL values, perhaps no field at all, and the sort code somehow ignores such records. Because... If I manually select the BLANK Disc tracks, then type in "2", they instantly sort. Seems like a bug.
