All Activity

Also, I just messed around with ImgBurn with the same CDI file (Mortal Kombat Gold) and it passed a 'Verify' on the CD-R I burned with Padus DiscJuggler once I put the "pfctoc.dll" file (i.e. https://download.imgburn.com/pfctoc.zip ) into root of ImgBurn install directory on my Linux setup. but just to see what would happen after removing that file, it throws a error that it can't read the CDI file like expected. so if I do decide to burn another Dreamcast CDI file I might try ImgBurn as that should have no trouble adjusting write speed down to 8x like Padus DiscJuggler does (maybe DiscJuggler won't have this issue on Windows or older burners(?)) and I prefer ImgBurn in general. but on that Dreamcast wiki page I noticed it says, "ImgBurn is usually very reliable with burning DiscJuggler CDI files, but on rare occasions there may be incompatible discs requiring the use of the original DiscJuggler software." ; I wonder if anyone has ever actually had any issues with ImgBurn burning CDI files as the quote says 'may be'?

UPDATE: a small update to my previous comment... I was just burning a Dreamcast game on my Sep 1999 mfg date console and I can definitely say CD-RW does not work as I burned the same CDI file using Padus DiscJuggler to CD-RW disc and the console acts like the disc does not even exist. but I burn that same CDI file to a CD-R (Verbatim (the cheaper 'CMC Magnetics Corp' media code) at pretty much max speed as it took 3min10sec to burn pretty much a full CD-R) and it works.

I am a bit late... but I see that game you want (i.e. "Spirit of Speed 1937") on Archive site and you can try using Padus DiscJuggler software if you want as while I nearly exclusively use ImgBurn in general, Padus DiscJuggler is the official software for ".CDI" files which CDI files are what you need for using on real Dreamcast hardware. I was looking into this stuff a moment ago and found the last released version of Padus DiscJuggler (i.e. https://dreamcast.wiki/DiscJuggler ) on my Linux setup and it seems okay. just in some brief testing I burned a game to CD-RW just to see what my Dreamcast would do and it does not even see the CD-RW disc. I recently brought out my Dreamcast as it was collecting dust for many years as I tried one of my burned CD-R's (Mortal Kombat Gold), which I burned June 2004 on some generic 'CMC Magnetics Corp' media (as there is no brand name on the disc), and... the game still loads up but I noticed in the game it does not take long before the sound goes out in regards to punches/kicks etc but the background music is still okay. so either my copy degraded, or... it 'may' have been like that back when I first burned it. I 'may' try reburning that same game from a CDI image I found online just to see if it's any better. I tried comparing the original one I burned from June 2004 to the burned CDI image to CD-RW and ImgBurn shows for the June 2004 burned CD-R... "Size: 661,381,120 bytes". the one I just tested is... "Size: 736,954,368 bytes". even looking at basic 'data' section of the disc (not the Audio part) shows "378,216,295 bytes" on NEW disc. the June 2004 one shows... "352,110,505 bytes". I heard there was a couple of different versions of this game, so 'maybe' that's why. the file I downloaded says 'Re-release'. but I can't really say for sure. but I said screw it and decided to burn it to a Verbatim CD-R (one of the usual cheaper 'CMC Magnetics Corp' ones) at 8x (seems DiscJuggler did not take my 8x write speed setting as it appears it's burning it pretty much full speed as it only took 3min10sec to finish writing it and it's basically a full disc) on my 'Sony Optiarc 7240s' and see if that issue I had with the June 2004 copy went away and... it seems to work with no more audio missing issue with kicks/punches etc as it works as expected. so I am leaning towards that previous copy was flawed, not in burning quality but the data itself(?). TIP: from what some claim, burning Dreamcast games slow is probably a good idea. most modern-ish burners don't seem to burn CD-R's any slower than 8x though. but I most likely burned that CD-R from June 2004 on a burner I still have (Liteon 24102b) as I never had a DVD burner until I think 2005-2006. p.s. my console has to be one of the earlier models as it's got a Sep 1999 mfg date on it as the console was released Sep 9th 1999 here in USA (I noticed the console does not seem to keep the data you setup for long as powering it off for not long and back on seems to ask to set date again etc). I most likely bought mine in 1999 or 2000 at the latest.

ASUS's current internal BD model, BW-16D1HT, is the one I use in a VanTech 3.0 Gen 1 enclosure. The WH16NS40 from LG is another possibility although last time I used one over 5 years ago, it failed to write BD DL media 9 times out of 10, backed up by other users who experienced the same thing on this board. Pioneer's current 213 model is ALMOST there. It's a year and a half old and needs to conquer a few firmware slow writes. For instance, it, too, only writes 4x to 8x DVD+R DL. I put in for a return on the external ASUS BD drive.

Hello again! Thanks for posting an update regarding your tests. My return just finished processing, so I haven't even gotten a chance to look at other drives. I'll certainly pass on the external ASUS. That said, are there any internal drives that come highly recommended (and can be placed into an enclosure)?

Another reason not to get that drive: it writes at only 4x to 8x DVD+R DL discs. If you're going to go with the ASUS, get the internal model and put it in a VanTec or Other World Computer USB 3.0 enclosure.

Be aware that I've just begun testing one of these external ASUS drives and right out of the bat, I notice it's a slower reader. Took 5 minutes to read 300 MB off of a pressed data CD.

Yes, I was more concerned about on-the-fly decoding which would apply to any kind of audio file (.flac, .mp3 etc.) when burning an Audio CD. Of course, if we already have .wav files there's no on-the-fly decoding involved. However, it's quite possible these .wav files have been decoded with the exact same method as on-the-fly decoding. So I guess the question remains: does one need to be careful of filter/decoder settings when decoding/extracting files to .wav? Here are some further LAV Audio settings which may affect the final .wav output:

madFLAC isn't perfect. There have been some FLAC I've come across that it would not process, so I converted them to uncompressed WAV for input.

While it seems madFLAC is pretty standard with ImgBurn, while not as convenient, I use Foobar2000 to convert FLAC back to standard WAV temporarily anytime I want to burn a standard Audio CD. but on Linux it appears I don't have much choice as, at least to my knowledge, madFLAC can't be setup on ImgBurn on Linux. so my ImgBurn is just on a basic installation which it can directly use WAV files without issue. so I guess the general point is... even if you can't get any special stuff (madFLAC etc) working with ImgBurn, as long as ImgBurn installs and it's basic function works, you can do what I do to create a standard Audio CD with ImgBurn.

Thank you again for this valuable information! I am going to try to use mechapwn on a spare slim PS2 so it can run ps1 backups. Then I will try the discs again and let you know if that works!

I don't use LAV. I use madFLAC to do my FLAC processing to make Audio CD's in ImgBurn. In all the time, like 15 years or so, I've been using madFLAC, I've never had it interfere with any audio processing in ImgBurn or any other audio/video application I've used.

To copy CD Audio discs, you use the Read function as defined in the first link in the first Guide I pasted:

Wait... aren't Audio CDs a special case? I mean, there's an entire procedure about how to carefully and reliably rip Audio CDs using specialised software like EAC (Exact Audio Copy)? Surely it isn't as simple as making ISO copies? The above comment is strictly about Audio CDs which I think are somewhat different than standard data discs like CD-ROM or DVD-Video.

Hello everyone! Hope you are all doing great. Here's a possibly silly and quite belated concern: I've started burning Audio CD's again, using .cue files that point to .flac files. If I am getting it correctly, the system uses the default FLAC decoder to decode the files on-the-fly, and pass them to ImgBurn for burning. My concern is what the decoder might be doing to the audio. In this case, the excellent LAV Filters (its tray icons appear during burning). In the attached, you can see a few options that may affect audio output, namely Mixing and Clipping protection. In the current configuration, Mixing shouldn't be an issue. So, the question here is: can the LAV Filter settings (or any other DirectShow filter that may be used during Audio CD burning) interfere with what actually ends up in the CD, or is this all irrelevant and taken care of centuries ago? Thanks

The PS2 laser assembly base unit would be newer than the ones in the PS1. In theory, that would mean better read compatibility. I know that certain DVD-R could be played on the PS2 for things like DVD Video. I used to do it as far back as 2002, but, even then, random skips and playback problems would occur because the PS2 was simply designed before the creation of DVD-R. However, future PS2 models improved playback compatibility with DVD-R, which means that as the lasers got newer, they got better at reading recorded discs. Which would bolster the idea that as the PS2 improved, it would have better playback for CD-R.

Thank you for your response! How would I do a quality check on the burnt discs? I have heard that (if you can get them to read PS1 backups), PS2s have better lasers that are more equipped to deal with burnt discs. Do you know if there is truth to this?

Hi I've been in the process of archiving a bunch of my old PC games and a good chunk of them use Multi-Mode CDs. Now basically track 0 is the data track with all the files, and every other track is a dedicated music track. However when I rip the disc It does indeed produce a bin and cue with all of the tracks. However all tracks past the data track are completely blank. I've tested this with a few different disc drives and games that use this method and they all show the same result. Any idea why this may be occurring? I'd give game examples but they none of them are English games.

That's a great track record! Hopefully I can get to that point with a new drive. For me, it's primarily movie backups which strikes single layered discs as an option since there isn't enough space. I'll keep you posted on the situation once I've tested everything. Thanks again for the help!

Yeah, that's the ASUS I have bookmarked to try out in November. Someone else on this board had tried it out and it seemed to do the trick for solving their issue. I just never have had any BD-R DL before. Just BD-RE DL. I needed rewritables for monthly system backups so I could reuse the discs and my backups were all larger than a BD-RE SL. I've since moved to USB SSD's because they're much larger and read and write much faster. I also as a matter of "trust" that I only use DL media when I have to. Like for those backups I mentioned or DVD+R DL for DL DVD Video discs. When you go beyond one layer, you double the chances of having a read issue, right at the layer change(s) most often than not, as seemed to be happening in your case. So, I could have saved space with BD-R DL discs for backups which also would have read and written faster than the rewritable DL's, but I didn't want to run the risk of, years later down the road, a backup being unreadable. So, I stuck with single layer BD-R. To put it into perspective, in the 10 years or so I've been burning BD-R's for backups, I only just a few weeks ago encountered my first that wouldn't read. And that was something I "knew" years ago when I wrote it. The drive was dying and there was a recovered read error during Verify on burn. I performed a manual Verify on that same disc and it passed that time. However, that drive that burned it was replaced shortly after that due to various Verify failures on future burns. I should have burned the data again in the replacement drive while I had live copies, but I didn't. Thankfully, it was temporary files that I managed to recover from other sources a few weeks ago, so I didn't lose anything.

@dbminter Thanks for your response! Checking the firmware was the first thing I did and I can confirm it's the most recent version. I saved all the packaging just in case, so I'll be returning the drive today. Is this the ASUS Drive you're referring to? If so, I'll pick it up once my return has processed. You mention having never burned an BD-R DL before. Is this moreso due to preference, or is there an advantage I'm not unaware of (besides it being rewritable, of course)?

The actual drive in the OWC setup is an LG. I'm not familiar with that particular brand, but I do know the WH16NS40 did not properly write to BD-R DL and BD-RE DL. 9 times out of ten, they would fail verifies. Now, that was some years ago, so a firmware update to LG drives like the NS40 might have fixed it. The issue wasn't present in the NS60, but LG discontinued that model. You could try seeing if there's a firmware update for your drive. In Write mode, right click on the drive from the drop down menu and select the last option in the context menu, the one to check for a firmware update. Install the latest one if there are any and try again. If that doesn't work, the only thing to try is a different drive. Preferably not an LG model. I use ASUS's BD internal drive in a VanTech USB 3.0 enclosure, but I've not tested any DL BD discs in it. If you're going to use your own external enclosure with a BD drive, you will need a USB 3.x enclosure; 2.x won't do. ASUS makes an external BD drive, but I've yet to test it. I intend on getting one probably in December, but I don't have any BD-R DL to test it with. I've never even burned a BD-R DL before, only BD-RE DL.

Hello all! Long time user, first time poster. I've been through the ringer with this and have combed over old form posts and FAQs to no avail, so I'm hoping y'all can help me resolve this. What I'm using: Verbatim BD-R DL 50gb 8x OWC Mercury Pro 16X Blu-ray Drive What I'm trying to burn: 3x Project4K ISOs The story: Originally, I used my old drive (Samsung External Blu-ray Writer TSST SE-506CB/RSBD 6X USB 2.0 Slim) and everything went well for the first two ISOs ("SW" & "EM"). However, when I tried burning the third ISO ("JD"), I received a L-EC Uncorrectable Error message. After some research, I determined it was the drive. This theory was further proven when I tried to burn the first two ISOs ("SW" & "EM") again, only to receive I/O Errors. So, I replaced the drive (OWC Mercury Pro 16X Blu-ray Drive) and tried burning the "JD" ISO again with success (both with the burn and verification). However, just to be sure, I attempted another burn with the "SW" and "EM" ISOs and still receive an I/O Error (log below for both). It's worth noting that I've tried burning these at all supported speeds listed by Imgburn (2x, 4x, 6x) as well as with AWS with the same result. I'm not sure what else to do and would appreciate all suggestions. Thank you all for your time and be well. The log: I 21:44:57 ImgBurn Version 2.5.8.0 started! I 21:44:57 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 21:44:57 Total Physical Memory: 6,164,744 KiB - Available: 3,217,080 KiB I 21:44:57 Initialising SPTI... I 21:44:57 Searching for SCSI / ATAPI devices... I 21:44:58 -> Drive 1 - Info: HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB 2.0) I 21:44:58 Found 1 BD-RE XL! I 21:45:23 Operation Started! I 21:45:23 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K77.ISO I 21:45:23 Source File Sectors: 21,983,296 (MODE1/2048) I 21:45:23 Source File Size: 45,021,790,208 bytes I 21:45:23 Source File Volume Identifier: 4K77 I 21:45:23 Source File Volume Set Identifier: 4D955102014F6FAF I 21:45:23 Source File Application Identifier: ImgBurn v2.5.8.0 I 21:45:23 Source File Implementation Identifier: ImgBurn I 21:45:23 Source File File System(s): UDF (2.50) I 21:45:23 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 21:45:23 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 21:45:23 Destination Media Supported Write Speeds: 2x, 4x, 6x I 21:45:24 Destination Media Sectors: 24,438,784 I 21:45:24 Write Mode: BD I 21:45:24 Write Type: DAO I 21:45:24 Write Speed: 4x I 21:45:24 Hardware Defect Management Active: No I 21:45:24 BD-R Verify Not Required: Yes I 21:45:24 Link Size: Auto I 21:45:24 Lock Volume: Yes I 21:45:24 Test Mode: No I 21:45:24 OPC: No I 21:45:24 BURN-Proof: Enabled I 21:45:24 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 21:45:53 Filling Buffer... (80 MiB) I 21:45:53 Writing LeadIn... I 21:45:54 Writing Session 1 of 1... (1 Track, LBA: 0 - 21983295) I 21:45:54 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 21983295) I 21:45:54 Writing Layer 0... (LBA: 0 - 12219391) I 22:09:05 Writing Layer 1... (LBA: 12219392 - 21983295) W 22:09:41 Failed to Write Sectors 12498976 - 12499007 - Reason: Write Error W 22:09:41 Retrying (1 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (2 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (3 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (4 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (5 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (6 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (7 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (8 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (9 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (10 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (11 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (12 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (13 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (14 of 20)... W 22:09:41 Retry Failed - Reason: Invalid Address For Write W 22:09:41 Retrying (15 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (16 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (17 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (18 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (19 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:09:42 Retrying (20 of 20)... W 22:09:42 Retry Failed - Reason: Invalid Address For Write W 22:15:56 Retrying (21)... W 22:15:59 Retry Failed - Reason: Invalid Address For Write W 22:16:11 Retrying (22)... W 22:16:11 Retry Failed - Reason: Invalid Address For Write W 22:16:12 Retrying (23)... W 22:16:12 Retry Failed - Reason: Invalid Address For Write W 22:16:19 Retrying (24)... W 22:16:19 Retry Failed - Reason: Invalid Address For Write W 22:16:20 Retrying (25)... W 22:16:20 Retry Failed - Reason: Invalid Address For Write W 22:16:20 Retrying (26)... W 22:16:20 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (27)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (28)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:21 Retrying (29)... W 22:16:21 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (30)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (31)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:22 Retrying (32)... W 22:16:22 Retry Failed - Reason: Invalid Address For Write W 22:16:23 Retrying (33)... W 22:16:23 Retry Failed - Reason: Invalid Address For Write W 22:16:23 Retrying (34)... W 22:16:23 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (35)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (36)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:24 Retrying (37)... W 22:16:24 Retry Failed - Reason: Invalid Address For Write W 22:16:25 Retrying (38)... W 22:16:25 Retry Failed - Reason: Invalid Address For Write E 22:16:41 Failed to Write Sectors 12498976 - 12499007 - Reason: Write Error E 22:16:41 Next Writable Address: 0 I 22:16:41 Synchronising Cache... W 22:16:45 User opted to skip the 'Close Track/Session/Disc' functions. E 22:16:45 Failed to Write Image! I 22:16:45 Exporting Graph Data... I 22:16:45 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_9-45_PM_VERBAT-IMf-000_4x.ibg I 22:16:45 Export Successfully Completed! E 22:16:45 Operation Failed! - Duration: 00:31:21 I 22:16:45 Average Write Rate: 13,541 KiB/s (3.1x) - Maximum Write Rate: 17,917 KiB/s (4.1x) I 22:18:27 Operation Started! I 22:18:27 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 22:18:27 Source File Sectors: 22,447,264 (MODE1/2048) I 22:18:27 Source File Size: 45,971,996,672 bytes I 22:18:27 Source File Volume Identifier: 4K80 I 22:18:27 Source File Volume Set Identifier: 586DB1C6015683D8 I 22:18:27 Source File Application Identifier: ImgBurn v2.5.8.0 I 22:18:27 Source File Implementation Identifier: ImgBurn I 22:18:27 Source File File System(s): UDF (2.50) I 22:18:27 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 22:18:27 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 22:18:27 Destination Media Supported Write Speeds: 2x, 4x, 6x I 22:18:27 Destination Media Sectors: 24,438,784 I 22:18:27 Write Mode: BD I 22:18:27 Write Type: DAO I 22:18:27 Write Speed: 4x I 22:18:27 Hardware Defect Management Active: No I 22:18:27 BD-R Verify Not Required: Yes I 22:18:27 Link Size: Auto I 22:18:27 Lock Volume: Yes I 22:18:27 Test Mode: No I 22:18:27 OPC: No I 22:18:27 BURN-Proof: Enabled I 22:18:27 Write Speed Successfully Set! - Effective: 17,984 KB/s (4x) I 22:18:58 Filling Buffer... (80 MiB) I 22:18:59 Writing LeadIn... I 22:19:00 Writing Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 22:19:00 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 22:19:00 Writing Layer 0... (LBA: 0 - 12219391) I 22:42:10 Writing Layer 1... (LBA: 12219392 - 22447263) W 22:45:32 Failed to Write Sectors 13809728 - 13809759 - Reason: Write Error W 22:45:33 Retrying (1 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (2 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (3 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (4 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (5 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (6 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (7 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (8 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (9 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (10 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (11 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (12 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (13 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (14 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (15 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (16 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (17 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (18 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (19 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:45:33 Retrying (20 of 20)... W 22:45:33 Retry Failed - Reason: Invalid Address For Write W 22:56:26 Retrying (21)... W 22:56:29 Retry Failed - Reason: Invalid Address For Write E 22:56:32 Failed to Write Sectors 13809728 - 13809759 - Reason: Write Error E 22:56:32 Next Writable Address: 0 I 22:56:32 Synchronising Cache... W 22:56:34 User opted to skip the 'Close Track/Session/Disc' functions. E 22:56:34 Failed to Write Image! I 22:56:34 Exporting Graph Data... I 22:56:34 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-18_PM_VERBAT-IMf-000_4x.ibg I 22:56:34 Export Successfully Completed! E 22:56:34 Operation Failed! - Duration: 00:38:07 I 22:56:34 Average Write Rate: 12,269 KiB/s (2.8x) - Maximum Write Rate: 17,923 KiB/s (4.1x) I 22:58:05 Operation Started! I 22:58:05 Source File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 22:58:05 Source File Sectors: 22,447,264 (MODE1/2048) I 22:58:05 Source File Size: 45,971,996,672 bytes I 22:58:05 Source File Volume Identifier: 4K80 I 22:58:05 Source File Volume Set Identifier: 586DB1C6015683D8 I 22:58:05 Source File Application Identifier: ImgBurn v2.5.8.0 I 22:58:05 Source File Implementation Identifier: ImgBurn I 22:58:05 Source File File System(s): UDF (2.50) I 22:58:05 Destination Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 22:58:05 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 22:58:05 Destination Media Supported Write Speeds: 2x, 4x, 6x I 22:58:05 Destination Media Sectors: 24,438,784 I 22:58:05 Write Mode: BD I 22:58:05 Write Type: DAO I 22:58:05 Write Speed: MAX I 22:58:05 Hardware Defect Management Active: No I 22:58:05 BD-R Verify Not Required: Yes I 22:58:05 Link Size: Auto I 22:58:05 Lock Volume: Yes I 22:58:05 Test Mode: No I 22:58:05 OPC: No I 22:58:05 BURN-Proof: Enabled I 22:58:05 Write Speed Successfully Set! - Effective: 26,976 KB/s (6x) I 22:58:36 Filling Buffer... (80 MiB) I 22:58:36 Writing LeadIn... I 22:58:44 Writing Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 22:58:44 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 22:58:44 Writing Layer 0... (LBA: 0 - 12219391) I 23:14:29 Writing Layer 1... (LBA: 12219392 - 22447263) I 23:27:38 Synchronising Cache... I 23:27:42 Closing Track... I 23:27:43 Finalising Disc... I 23:28:19 Exporting Graph Data... I 23:28:19 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-58_PM_VERBAT-IMf-000_MAX.ibg I 23:28:19 Export Successfully Completed! I 23:28:19 Operation Successfully Completed! - Duration: 00:30:14 I 23:28:19 Average Write Rate: 25,905 KiB/s (5.9x) - Maximum Write Rate: 26,740 KiB/s (6.1x) I 23:28:19 Cycling Tray before Verify... W 23:28:27 Waiting for device to become ready... I 23:29:02 Device Ready! I 23:29:06 Operation Started! I 23:29:06 Source Device: [0:0:0] HL-DT-ST BD-RE BH16NS40 1.05 (D:) (USB) I 23:29:06 Source Media Type: BD-R (Disc ID: VERBAT-IMf-000) I 23:29:06 Source Media Supported Read Speeds: 2x, 4x, 6x, 8x I 23:29:06 Source Media Supported Write Speeds: 2x, 4x, 6x I 23:29:07 Source Media Sectors: 22,447,264 I 23:29:07 Source Media Size: 45,971,996,672 bytes I 23:29:07 Image File: C:\Users\david\OneDrive\Desktop\Star Wars\4K80.ISO I 23:29:07 Image File Sectors: 22,447,264 (MODE1/2048) I 23:29:07 Image File Size: 45,971,996,672 bytes I 23:29:07 Image File Volume Identifier: 4K80 I 23:29:07 Image File Volume Set Identifier: 586DB1C6015683D8 I 23:29:07 Image File Application Identifier: ImgBurn v2.5.8.0 I 23:29:07 Image File Implementation Identifier: ImgBurn I 23:29:07 Image File File System(s): UDF (2.50) I 23:29:07 Read Speed (Data/Audio): MAX / MAX I 23:29:08 Read Speed - Effective: 3x - 8x, 8x - 3x I 23:29:08 Verifying Session 1 of 1... (1 Track, LBA: 0 - 22447263) I 23:29:08 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 22447263) I 23:29:08 Verifying Layer 0... (LBA: 0 - 12219391) I 23:45:16 Verifying Layer 1... (LBA: 12219392 - 22447263) W 23:45:25 Failed to Read Sectors 12219392 - 12219423 - Reason: L-EC Uncorrectable Error W 23:45:33 Failed to Read Sector 12219392 - Reason: L-EC Uncorrectable Error W 23:45:33 Sector 12219392 maps to File: \BDMV\STREAM\00021.m2ts W 23:49:16 Retrying (1)... W 23:49:25 Retry Failed - Reason: Timeout on Logical Unit E 23:49:27 Failed to Read Sector 12219392 - Reason: L-EC Uncorrectable Error E 23:49:27 Sector 12219392 maps to File: \BDMV\STREAM\00021.m2ts E 23:49:28 Failed to Verify Sectors! I 23:49:29 Exporting Graph Data... I 23:49:29 Graph Data File: C:\Users\david\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_10-58_PM_VERBAT-IMf-000_MAX.ibg I 23:49:29 Export Successfully Completed! E 23:49:29 Operation Failed! - Duration: 00:20:21 I 23:49:29 Average Verify Rate: 20,048 KiB/s (4.6x) - Maximum Verify Rate: 36,105 KiB/s (8.2x) I 23:49:31 Close Request Acknowledged I 23:49:31 Closing Down... I 23:49:31 Shutting down SPTI... I 23:49:31 ImgBurn closed! HL-DT-ST_BD-RE_BH16NS40_1.05_THURSDAY-APRIL-4-2024_9-45_PM_VERBAT-IMf-000_4x.ibg

Without doing quality checks on the burnt discs, it's hard to know if your drive has burnt them nicely. Assuming it has and the error rates are really low, it's a case of the laser in your PS1 not liking them - possibly just not liking any burnt discs in general. If it can't read the disc nicely, you'll get stuttering. I seem to recall that it is possible to tweak the laser power and improve things, but you do have to be careful or you could make things worse

Hello, Recently, I have been attempting to make some backup versions of PS1 game discs. I tried this initially with the standard Verbatim CD-Rs. I tried writing Silent Hill to a disc and my ps1 couldn't make it through the initial cut scene (I am using FPSXBoot). Then I learned that those (made by CMC Magnetics) are not very good so I bought some Verbatim Datalife+ discs and tried again. This worked better, but FMV cutscenes are still stuttering and/or not working. Spoken dialogue cuts in and out. Some actions, such as inspecting items, take a very long time to do. I am using an LG WH16NS40 disc writer/reader (you can see the details in the program log below). I know that these are meant for Blu-ray discs, but I assume they should be fine for CDs. Does anyone know how I can write PS1 games more successfully on these discs? Like I said, the games work... okay... but the lack/interruption of audio is annoying and I would like them to run smoother. Thanks