dbminter

I've been burning optical discs since 2000, the early days of CD-R. I've never cared a jot about PIE, PIF, and jitter values. As long as they pass Verify/Read tests, that's good enough for me. And if they're DVD Video discs, a play of all contents on a standalone DVD player. The PIE/PIF/jitter values probably don't really come into play in terms of how long a disc will last before it's not readable. A disc will simply become unreadable based on the quality of its dye/metallic oxide. And it's an all or nothing situation, usually. Cheap media will become completely unreadable after like a year or so. Some media will have just a few sectors become unreadable, but if you're not using CMC discs, you generally don't have to worry about discs dying unless your burner doesn't like the dye on that particular disc. Which you'll generally know if it doesn't the minute Write or Verify fails for a particular brand.

M-Disc will, most likely, long outlive the user.

Yes, I believe every single burn has some amount of PIE/PIF/jitter. If it's low, it can generally be ignored. If it's high, then you start to worry.

What were the CD images of? Audio CD's or data discs like some kind of software installers or game discs? If they're Audio CD's or game discs, you probably won't have much luck copying their contents. You can't do it without special ripping software for Audio CD's. And some game CD's require the actual disc to run. And if they're some like Playstation or other console hardware discs, you'd need the images themselves as copying the contents won't necessarily copy all the contents. (Long story.) If they're just plain old data CD's, you can copy the contents to another location and put all the copied contents to an ISO in Build mode. If you have the space on a DVD, copy the CD ISO's to the image, too, as archive copies. If they're not just plain data CD's, you can do like LUK said and archive the ISO's. Then, you can use some kind of virtual drive software to load each CD ISO as a virtual drive for accessing. Even if they are plain old data CD's, you can still archive them to one disc and mount each CD as a virtual drive each time you want to access the files on the discs. You said the CD's are ISO's, which indicates they probably aren't Audio CD's or console game discs.

That's probably a drive or disc issue. Try another drive. Preferably, get a USB one you can easily hook up and disconnect afterwards. TSSTCorp drives have been known to be problematic sometimes. Or the drive may simply be at a point where it's getting old. If a different drive can't read the disc, the issue is most likely the disc has gone bad. The PS2 is almost 21 years old since initial release, so it wouldn't surprise me if a disc has become unreadable, particularly if it was well played.

I have noticed this is related to another issue I had posted about. I didn't know the 2 were apparently correlated, but one crash appears to cause the other. There was another issue I'd posted where in the Disc Layout Editor, dragging and dropping a folder would actually import an entirely different folder on the same drive. It seemed to be a random issue, but I managed to trigger it after one of these crashes where the characters get changed to either Chinese characters, a single bracket, or a lower case D. (Those last 2 were new additions I discovered could happen in addition to the random Chinese characters.) @LIGHTNING UK! If you want me to try out some kind bug enabled logging version of ImgBurn, I'm willing to give it a shot to try and isolate this issue. While I've not been able to determine what causes it, I've had it happened at least once a day every day for the past few days. So, it seems I can reliably expect it to happen at some point. You said this logging would probably be some kind of resource intensive operation, but I'm willing to try it if you are. Just let me know. Thanks!

I wasn't honestly sure that would help. It makes sense, though, because I had read somewhere USB 2.x was too slow for Blu-Ray burning. That's why I went with a USB 3.0 enclosure, just to be certain. And, it makes sense, somewhat. Semaphore timeout errors are a communication drop between the USB bridge and the motherboard on the PC. I suppose data could be coming in too slow for the device and dropping communication, resulting in errors. But, as long as it works, who cares why the problem went away, right?

I use the LG WH16NS60 in a Vantec USB 3.0 enclosure. The NS60 is an internal drive, but you can use it in a USB 3.0 enclosure. The drive itself is about $80 and the enclosure is about half that, so, yes, it's an investment. The NS40 is cheaper, but it does not properly write to BD-R/RE DL media. I've been using the NS60 for years with those Verbatim BD-R you're using with few failures that weren't the result of a dying drive. I use BD-R for a lot of data backups, no BD movies. Their large size is great for system images backups. I can backup my entire Windows partition to 2 BD-R.

At this point, if it still fails, I'd blame the used BD burner. You're using the quality Verbatim VERBAT-IM BD-R, so it's not a disc quality issue. You're burning single layer BD-R; multiple layer BD-R recording can be unreliable depending on what BD model you have. (For instance, the only BD-RE DL burner I've reliably used is the LG WH16NS60.) You've switched to a USB 3.0 port. So, at that point, I'd look into trying a different BD burner.

I was just going to say the same thing. I think most, if not all, Audio CD's don't have disc labels. Though it can't be done automatically, you could change the name of the target save file to, say, Beatles, and the appropriate extension for it and any extra files you're generating along with the image will have that name. Audio CD's are unique beasts. They were created like a decade before CD's started being used for data in PC's. So, they're proprietary hardware with a proprietary format on them that the CD player reads. PC's were later made to play audio CD's as part of the CD process as a selling point for the hardware. Data CD's, with disc labels, came along later. This is why you need unique software for ripping tracks off of audio CD's. It needs a specialized translating layer between the hardware and the "software" (the audio CD) to convert the raw data the CD can read into a container format.

You know? I have to give CMC credit where it's due. I generally only disparage CMC because they cost me like $2,000 troubleshooting issues before someone told me about them. Plus, they make so much junk. However, THUS far, with the DataLife Plus/AZO Verbatim and TY Pro, CMC has NOT switched manufacturing processes to maximize profit by slapping their good names on their junk media.

Funny thing was I felt worse with side effects from the COVID-19 vaccine than I did with the actual COVID! I was down for a day with severe cold like symptoms, much worse than the ones I had with the actual COVID. Plus a bout of really bad shakes for like 30 minutes about 12 hours after injection.

Yes, Blu-Ray killed special features on DVD, for the most part. The BBC Doctor Who DVD's still have the extras that are on the Blu-Ray releases, but the BBC is a standout in today's market. As a means of hopefully forcing people onto Blu-Ray, the studios released bare bones affairs of DVD's and put all the extras on the Blu-Ray releases. They hoped to force people into adopting Blu-Ray over DVD to sell again what they'd already sold people on once before; didn't work.

Since you eventually got the burns to complete after a few hours, though that shouldn't be the case, of course, it's not a CMC media issue. I'm surprised it eventually resumed and worked, though. TY is one of the top two manufacturers out there. The other is Verbatim when they don't farm out to CMC, even though CMC now OWNS Verbatm...

Yes, it depends on how much data you've written to these CD-R's. If it stayed at 24x and you wrote an entire CD-R full of data, I'd be wary. But, if you didn't fill an entire disc, it may only have reached 24x by the time it got to finishing writing data.

Your issue is probably this: I 02:08:32 Destination Media Type: CD-R (Disc ID: 97m26s66f, CMC Magnetics Corp.) CMC Magnetics makes the worst optical media out there. Over half the problems we see on this board are caused by it and generally miraculously cleared up when you don't use the junk media. I would guess some kind write issue occurred and the communication was dropped. This particularly happens with errors over USB. Write rate simply drops to 0 and nothing ever happens after that over USB. Your cheapest best is to try changing the USB cables and/or use a different port. The next thing I'd try is using better quality media. Try the AZO/DataLife Plus CD-R from Verbatim. NOT the Verbatim Life Series you find in stores. Those are the CMC junk You can generally only find the AZO/DataLife Plus stuff in online stores like Office Depot or Amazon.com.

If you did not use a DVD-RW, which you probably didn't because you said specifically you used DVD-R, then the files can't be erased. DVD-R is WORM media, which stands for Write Once, Read Many. So, you can only write to them once. IF you did use DVD-RW or even DVD+RW, you can just write to it again and those contents will be erased and replaced by the subsequent write.

I never found the higher quality of Blu-Ray worth the price. While, yes, it is higher than DVD, upscaling DVD players like the PS3 can also achieve similar quality, so why bother? My big beef is how Blu-Ray players don't navigate like DVD's. For instance, you're supposed to be able to resume playback of Blu-Rays, yet, more than half of them don't support this feature like DVD's do. On the PS3, the Enter button also serves as Pause during playback of DVD's. This does not work on Blu-Rays. You can copy a Blu-Ray that fits on a DVD to a DVD and get it to play, but you cannot copy a DVD to a Blu-Ray disc and get it to play. Ridiculous!

The BBC is still good at releasing new series Doctor Who and classic series animated reconstructions on DVD. I prefer DVD's to Blu-Ray because DVD's navigate easier than Blu-Rays do in Blu-Ray players.

Hank and Peggy were so full of themselves, and completely oblivious to the fact! Bobby was pretty much the most well adjusted one, but Hank never could see past what he thought were failures in his own son. Peggy, at least, tried to nurture him. I will only get things on physical media. I refuse to stream anything. Movies, songs, TV shows. I must own a physical copy or I won't pay. Steams can be taken away from you at any time the license expires or the rights holder simply doesn't want you to have it anymore, like if it becomes politically incorrect.

Still love King Of The Hill even after all this time, BTW. I miss the reruns on Adult Swim.

You can always add USB 3.0 cards to your PCIe slots. Before I had a PC with USB 2.0 on it, I put in an expansion card to get USB 2.0 ports like 20 years ago.

That might explain why your USB BD drive is dropping communications, resulting in a semaphore timeout error. Semaphore timeout errors are a result of USB communication errors. USB 2.x is generally not fast enough to keep with the throughput required for a BD drive, which need USB 3.0 enclosures. But, you said you were burning fine before, so that's probably not the case.

Also, how long have you been using this Pioneer BD drive? You said you were burning BD-R fine and then it started acting up, which leads me to believe it's most likely the drive at fault. While Pioneer used to make the longest lasting drive I ever had (A BD that lasted for 2.5 years.) Pioneer's quality control has fallen off a cliff. Now you get about the usual 7 months lines span of something like, say, an LG BD drive. Not to mention the nagging 8x Ritek DVD+RW formatting failures that have plagued the firmware for the past 5 years and Pioneer refuses to do anything about, despite my repeated telling them the problem and how to fix it.

Oh, you're probably right! I do have a job that loads automatically on start of ImgBurn to set all my default options. And I bet the job has the previous setting saved in it where I had that option checked before. That's why it keeps getting reset. I didn't think about that one.