|
|
I made it private because I didn't want for anyone to see my screenshots, but only you. But now I don't see the screenshots attached at all. Did you receive them? |
|
|
I can cofirm that once the 'Audio CD' node added sub to the root node in Media Tree shows correct info after inserting the CD => The node is added with the Audio CD info BUT, the same node under the Folders node fails to update the info. WORKAROUND: Collapse the Folders node and expand it again. |
|
|
MM4 and Windows Explorer don't need any workarounds for such thing. And as I mentioned such workaround helps only to refresh the tracklist, but not the label of the disk. For that you need to restart the program, which hardly could be called a workaround. |
|
|
image.png (25,759 bytes) |
|
|
Sure, as I wrote it is just a refresh issue under the Folders node (per my image above), to be fixed... EDIT: For me collapsing the Folders node and re-expanding refreshes the label fine for all drives. |
|
|
Re screenshots: No, I don't see any of your screenshots. I don't think that one can attach screenshot to a private note or an private issue. At least I can't |
|
|
Fixed in 5.0.4.2650 |
|
|
You shouldn't change the original summary of this issue. The problem is not only with Audio CDs, but with all removable drives. I don't know if your mentioned update will have fixed it for such drives as well. I have one quite long animated screenshot proving that, I will attach it in the next post. |
|
|
I forgot to include the view of the Medias table for MM4 and MM5 in the animated screenshot. I have them added as individual screenshots. As you could see from these screenshots, MM5 has problem not only with not detecting label of a drive and files in the tracklist, but: 1. it has wrong serial number and label stored in the Medias table; 2. it has all tracks added to the same drive, even when I replaced "discs" (you should look the whole animated screenshot until the end). screenshot.20.png (20,496 bytes) screenshot.19.png (19,770 bytes) |
|
|
It all should be already fixed in 5.0.4.2650. Please re-test in 5.0.4.2650 (once is availbale) and re-open in case you still see issues (or enter it as another issue). |
|
|
Verified 2661 Unable to replicate. |
- Anonymous
