View Issue Details

IDProjectCategoryView StatusLast Update
0014605MMW v4Burning / Disc Handlingpublic2018-06-13 23:08
Reporterpeke Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status assignedResolutionopen 
Target Version4.1.21 
Summary0014605: External CD-Rom Drives: RIP/BURN Engine unmounts Drive
DescriptionDuring Burn Engine initialization MMW repeatedly unmount/mount USB CD-ROM making it unavailable for access. It can take up to 15 Seconds and after Engine inits drive. After Engine Init Drive is accessible for RIP/BURN Process and CD is ripped/burned correctly.

NOTE: Same thing happen while Audio CD listening so MMW can throw Gray tracks on track change.

Current Workaround: Wait till engine is initialized 15-20 Seconds in Track Selection of RIP Wizard till there was no more umount/mount and drive is mounted and initialized.
Additional InformationFPA-571-36757
TagsNo tags attached.
Attached Files
PrimoTestBug.rar (62,086 bytes)
Fixed in build

Activities

Ludek

2018-01-03 10:20

developer   ~0049477

Last edited: 2018-01-03 11:10

I've just tested with my external BD/CD/DVD drive (LG) and I couldn't replicate the issue.

Based on the info from the ticket it looks that the issue might be related to a particular CD, probably only mixed-mode CD ? From the video it looks like TOC is reading repeatedly because of TOC read failure, but yes, debug log would be useful to see more.

Also, you could try the latest 32-bit demo of PrimoBurner (http://download.primoburner.com/4.7.1/Demo/Windows/PrimoBurner.4.7.1.x86.Demo.zip ) to see whether engine upgrade might help to resolve the issue? You could compare with sample apps from v 3.6.9 (our current PrimoBurner) from FTP. If 3.6.9 samples exhibits the issue and the latest don't then it is obvious that engine update would solve the issue. But watching 0006184:0044301 the upgrade of the engine would be rather for MM5 -- because of a lot of API changes and the amount of work (and risk) involved.

peke

2018-01-11 11:40

developer   ~0049503

Both our and New version have same behavior.

READTOC and ReadMediaInfo reads CD without problems (Attached file with output), but READCDText and COPYCD app as soon as they try to access the drive it gets disconnected and fail with error.

In MMW it works as MMW constantly tries to retry to read rest of TOC so eventually when it reads all it can RIP CD with no problem.

User is willing to repeat further tests if needed.

Ludek

2018-01-11 11:49

developer   ~0049504

OK, based on the info it looks that the issue is when Primo/MMW tries to read CD-Text. i.e. disabling CD-text reading could be the workaround for the user?

This can be achieved by editing MediaMonkey.ini and changing ReadCDText value from 1 to 0 for all the drives.

Assigned back to you to try the workaround.

peke

2018-01-14 12:58

developer   ~0049509

Setting ReadCDText=0 fixes RIP issue.

Further analyze I've found that his external drive is actually an internal drive inside 5.25" enclosure.

Enclosure he have is https://www.owcdigital.com/products/mercury-pro-optical and drive in enclosure is http://www.lg.com/us/burners-drives/lg-GH24NSC0-internal-dvd-drive.

Having found that information it is questionable if maybe an enclosure is teh middle problem which unmounts from PC?

I'll ask User to make reports to OWC in order to escalate the problem.

Ludek

2018-01-15 09:50

developer   ~0049516

ok, so it is clear that the issue appears when reading CD-Text. It is unclear whether it is related to Primo engine only, because the other software might not attempt to read CD-Text at all? One way or the other we can hardly do something about this. The only "solution" is to disable CD-Text reading for that drive. So it is about adding KB article (if not already covered by a KB?).

peke

2018-06-13 23:08

developer   ~0050534

Possible relations in https://www.mediamonkey.com/forum/viewtopic.php?f=24&t=90178