AlbertEinstein Posted July 21, 2018 Posted July 21, 2018 (edited) I had just started burning a new project onto a single-sided 25GB BD-R disc. The next to last log message in the "live" log window was "Filling Buffer ... (80 MiB)" followed by "Failed to open file: XXX". The software paused and I know why it couldn't find the file. I moved it into a sub-folder on my hard drive at the last minute like I do sometimes and forget to move it in your disc layout editor so that it was valid. This caused the error. I thought it would be safe to simply cancel the entire operation and start over versus seeing more of these errors if I had moved any other files into different folders. So, I cancelled the first burn. But on my second attempt to burn the project to the same disc I got even more bad news: W 20:01:59 Failed to Write Sectors 0 - 31 - Reason: Medium Format Corrupted W 20:01:59 Retrying (1 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (2 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (3 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (4 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (5 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (6 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (7 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (8 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (9 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (10 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (11 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (12 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted I thought for sure that cancelling a burn during the buffer filling stage would not permanently damage the BD-R since not even the lead-in had been written from what I can tell. The writing lead-in occurs right after the filling buffer step, so why is my BD-R disc permanently damaged? Is it possible the BD-R disc was bad already and I just didn't realize it? Or does your software verify the BD-R media is good from the very beginning? Edited July 21, 2018 by AlbertEinstein
LIGHTNING UK! Posted July 21, 2018 Posted July 21, 2018 Post the full log from both burn attempts please.
AlbertEinstein Posted July 21, 2018 Author Posted July 21, 2018 (edited) ; //****************************************\\ ; ImgBurn Version 2.5.8.0 - Log ; Friday, 20 July 2018, 20:34:14 ; \\****************************************// ; ; I 19:22:45 ImgBurn Version 2.5.8.0 started! I 19:22:45 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200) I 19:22:45 Total Physical Memory: 15,656,864 KiB - Available: 12,768,268 KiB I 19:22:45 Initialising SPTI... I 19:22:45 Searching for SCSI / ATAPI devices... I 19:22:45 -> Drive 1 - Info: HL-DT-ST BD-RE WH10LS30 1.02-A0 (D:) (SATA) I 19:22:45 Found 1 BD-RE! I 19:56:38 Project Successfully Saved! I 19:56:38 File Name: C:\Users\SkyLake1\AppData\Roaming\ImgBurn\Project Files\DVDs.ibb I 19:57:05 Operation Started! I 19:57:05 Building Image Tree... I 19:57:05 Calculating Totals... I 19:57:05 Preparing Image... I 19:57:05 Contents: 114 Files, 16 Folders I 19:57:05 Content Type: Data I 19:57:05 Data Type: MODE1/2048 I 19:57:05 File System(s): UDF (2.50) I 19:57:05 Volume Label: DVDs I 19:57:05 Size: 24,975,351,786 bytes I 19:57:05 Sectors: 12,195,055 I 19:57:05 Image Size: 24,976,883,712 bytes I 19:57:05 Image Sectors: 12,195,744 I 19:57:05 Operation Successfully Completed! - Duration: 00:00:00 I 19:57:28 Operation Started! I 19:57:28 Building Image Tree... I 19:57:28 Calculating Totals... I 19:57:28 Preparing Image... I 19:57:28 Contents: 114 Files, 16 Folders I 19:57:28 Content Type: Data I 19:57:28 Data Type: MODE1/2048 I 19:57:28 File System(s): UDF (2.50) I 19:57:28 Volume Label: DVDs I 19:57:28 Size: 24,975,351,786 bytes I 19:57:28 Sectors: 12,195,055 I 19:57:28 Image Size: 24,976,883,712 bytes I 19:57:28 Image Sectors: 12,195,744 I 19:57:38 Operation Successfully Completed! - Duration: 00:00:09 I 19:57:38 Operation Started! I 19:57:38 Source File: -==/\/[bUILD IMAGE]\/\==- I 19:57:38 Source File Sectors: 12,195,744 (MODE1/2048) I 19:57:38 Source File Size: 24,976,883,712 bytes I 19:57:38 Source File Volume Identifier: DVDs I 19:57:38 Source File Volume Set Identifier: 4CF49F2E00BA16CF I 19:57:38 Source File Application Identifier: ImgBurn v2.5.8.0 I 19:57:38 Source File Implementation Identifier: ImgBurn I 19:57:38 Source File File System(s): UDF (2.50) I 19:57:38 Destination Device: [0:0:0] HL-DT-ST BD-RE WH10LS30 1.02 (D:) (SATA) I 19:57:38 Destination Media Type: BD-R I 19:57:38 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x I 19:57:38 Write Mode: BD I 19:57:38 Write Type: DAO I 19:57:38 Write Speed: 4x I 19:57:38 Hardware Defect Management Active: No I 19:57:38 BD-R Verify Not Required: Yes I 19:57:38 Link Size: Auto I 19:57:38 Lock Volume: Yes I 19:57:38 Test Mode: No I 19:57:38 OPC: No I 19:57:38 BURN-Proof: Enabled I 19:57:38 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 19:57:56 Filling Buffer... (80 MiB) E 20:00:13 Failed to open file: 'S:\celebrities\Jessica-Simpson.jpg' E 20:00:13 Reason: The system cannot find the file specified. I 20:00:13 Synchronising Cache... W 20:00:14 Potential 'WaitImmediateIO' Deferred Error - (1/3) - Unable to Recover TOC W 20:00:14 Synchronise Cache Failed! - Reason: Unable to Recover TOC E 20:00:26 Synchronise Cache Failed! - Reason: Unable to Recover TOC W 20:00:34 User opted to skip the 'Close Track/Session/Disc' functions. E 20:00:34 Failed to Write Image! E 20:00:34 Operation Failed! - Duration: 00:02:56 I 20:00:34 Average Write Rate: N/A - Maximum Write Rate: N/A This is the 2nd failed burn log file: I 20:01:42 Operation Started! I 20:01:42 Building Image Tree... I 20:01:42 Calculating Totals... I 20:01:42 Preparing Image... I 20:01:42 Contents: 110 Files, 16 Folders I 20:01:42 Content Type: Data I 20:01:42 Data Type: MODE1/2048 I 20:01:42 File System(s): UDF (2.50) I 20:01:42 Volume Label: DVDs I 20:01:42 Size: 24,974,451,473 bytes I 20:01:42 Sectors: 12,194,614 I 20:01:42 Image Size: 24,975,966,208 bytes I 20:01:42 Image Sectors: 12,195,296 I 20:01:42 Operation Successfully Completed! - Duration: 00:00:00 I 20:01:51 Operation Started! I 20:01:51 Building Image Tree... I 20:01:52 Calculating Totals... I 20:01:52 Preparing Image... I 20:01:52 Contents: 110 Files, 16 Folders I 20:01:52 Content Type: Data I 20:01:52 Data Type: MODE1/2048 I 20:01:52 File System(s): UDF (2.50) I 20:01:52 Volume Label: DVDs I 20:01:52 Size: 24,974,451,473 bytes I 20:01:52 Sectors: 12,194,614 I 20:01:52 Image Size: 24,975,966,208 bytes I 20:01:52 Image Sectors: 12,195,296 I 20:01:58 Operation Successfully Completed! - Duration: 00:00:06 I 20:01:58 Operation Started! I 20:01:58 Source File: -==/\/[bUILD IMAGE]\/\==- I 20:01:58 Source File Sectors: 12,195,296 (MODE1/2048) I 20:01:58 Source File Size: 24,975,966,208 bytes I 20:01:58 Source File Volume Identifier: DVDs I 20:01:58 Source File Volume Set Identifier: 4CF4A03900BA1516 I 20:01:58 Source File Application Identifier: ImgBurn v2.5.8.0 I 20:01:58 Source File Implementation Identifier: ImgBurn I 20:01:58 Source File File System(s): UDF (2.50) I 20:01:58 Destination Device: [0:0:0] HL-DT-ST BD-RE WH10LS30 1.02 (D:) (SATA) I 20:01:58 Destination Media Type: BD-R I 20:01:58 Destination Media Supported Write Speeds: 2x, 4x, 6x, 8x I 20:01:58 Write Mode: BD I 20:01:58 Write Type: DAO I 20:01:58 Write Speed: 4x I 20:01:58 Hardware Defect Management Active: No I 20:01:58 BD-R Verify Not Required: Yes I 20:01:58 Link Size: Auto I 20:01:58 Lock Volume: Yes I 20:01:58 Test Mode: No I 20:01:58 OPC: No I 20:01:58 BURN-Proof: Enabled I 20:01:58 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x) I 20:01:58 Filling Buffer... (80 MiB) I 20:01:59 Writing LeadIn... W 20:01:59 Failed to Write Sectors 0 - 31 - Reason: Medium Format Corrupted W 20:01:59 Retrying (1 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (2 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (3 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (4 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (5 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (6 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (7 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (8 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (9 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (10 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (11 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (12 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (13 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (14 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:01:59 Retrying (15 of 20)... W 20:01:59 Retry Failed - Reason: Medium Format Corrupted W 20:02:00 Retrying (16 of 20)... W 20:02:00 Retry Failed - Reason: Medium Format Corrupted W 20:02:00 Retrying (17 of 20)... W 20:02:00 Retry Failed - Reason: Medium Format Corrupted W 20:02:00 Retrying (18 of 20)... W 20:02:00 Retry Failed - Reason: Medium Format Corrupted W 20:02:00 Retrying (19 of 20)... W 20:02:00 Retry Failed - Reason: Medium Format Corrupted W 20:02:00 Retrying (20 of 20)... W 20:02:00 Retry Failed - Reason: Medium Format Corrupted W 20:02:13 Retrying (21)... W 20:02:13 Retry Failed - Reason: Medium Format Corrupted W 20:02:13 Retrying (22)... W 20:02:13 Retry Failed - Reason: Medium Format Corrupted W 20:02:14 Retrying (23)... W 20:02:14 Retry Failed - Reason: Medium Format Corrupted W 20:02:15 Retrying (24)... W 20:02:15 Retry Failed - Reason: Medium Format Corrupted W 20:02:16 Retrying (25)... W 20:02:16 Retry Failed - Reason: Medium Format Corrupted W 20:02:17 Retrying (26)... W 20:02:17 Retry Failed - Reason: Medium Format Corrupted W 20:02:17 Retrying (27)... W 20:02:18 Retry Failed - Reason: Medium Format Corrupted W 20:02:18 Retrying (28)... W 20:02:18 Retry Failed - Reason: Medium Format Corrupted W 20:02:44 Retrying (29)... W 20:02:44 Retry Failed - Reason: Medium Format Corrupted W 20:02:46 Retrying (30)... W 20:02:46 Retry Failed - Reason: Medium Format Corrupted W 20:02:47 Retrying (31)... W 20:02:47 Retry Failed - Reason: Medium Format Corrupted W 20:02:47 Retrying (32)... W 20:02:47 Retry Failed - Reason: Medium Format Corrupted W 20:02:48 Retrying (33)... W 20:02:48 Retry Failed - Reason: Medium Format Corrupted E 20:02:49 Failed to Write Sectors 0 - 31 - Reason: Medium Format Corrupted I 20:02:49 Synchronising Cache... W 20:02:50 Potential 'WaitImmediateIO' Deferred Error - (1/3) - Unable to Recover TOC W 20:02:50 Synchronise Cache Failed! - Reason: Unable to Recover TOC E 20:02:55 Synchronise Cache Failed! - Reason: Unable to Recover TOC W 20:03:02 User opted to skip the 'Close Track/Session/Disc' functions. E 20:03:02 Failed to Write Image! E 20:03:02 Operation Failed! - Duration: 00:01:04 I 20:03:02 Average Write Rate: N/A - Maximum Write Rate: N/A My 3rd attempt using a brand new virgin BD-R disc was successful. Edited July 21, 2018 by AlbertEinstein
dbminter Posted July 21, 2018 Posted July 21, 2018 The thing I noticed that was odd, to me anyway, was why did neither log seem to indicate, that I could find, what the DID of the BD-R was.
AlbertEinstein Posted July 21, 2018 Author Posted July 21, 2018 (edited) The thing I noticed that was odd, to me anyway, was why did neither log seem to indicate, that I could find, what the DID of the BD-R was. I don't even know what a DID is so... ... I couldn't tell you. My burner has been disconnected for a few days and this "assumed" blank BD-R was already in it. Maybe it was a failed burn from when I last tried to use the burner and I just never took it out and marked it as bad. Hence, my question about whether ImgBurn actually verifies the media is good from the start! I thought the software would verify good media as one of it's first steps. Maybe it verifies some meta-data that gives the impression it's good. Edited July 21, 2018 by AlbertEinstein
dbminter Posted July 21, 2018 Posted July 21, 2018 DID is Disc ID. It tells who manufactured the disc. It's generally a line in the log that I usually see. So, I didn't see it going over the logs and I was curious as to why it wasn't there.
AlbertEinstein Posted July 21, 2018 Author Posted July 21, 2018 (edited) I went back through my "ImgBurn.log" text file and checked all of the "Destination Media Type: BD-R" entries in the log file. Some of them have just the 'BD-R' description while others have the actual manufacturer's name in parentheses. For example, "Destination Media Type: BD-R (Disc ID: RITEK-BR2-000)". I had to go back about 13 entries in my log file before I came across the 'RITEK' entry. I didn't see a correlation between having more specific data on the Disc ID and being a successful burn. In other words, the last successful burn I just did described the disc only as "BD-R". It was an Optical Quantum branded disc. The failed one came with an inkjet printer label on top, so I know that it came from my stack of these Ri-DATA: https://www.newegg.com/Product/Product.aspx?Item=N82E16817132086 Edited July 21, 2018 by AlbertEinstein
dbminter Posted July 21, 2018 Posted July 21, 2018 I was wondering if the absence of the DID entry might be indicative of a possible problem with your drive. However, on further consideration, it seems more likely that those Optical Quantum discs may simply not have a DID present on them. I'm guessing if ImgBurn doesn't find a DID label on the media, it doesn't return anything? I've never seen a media format corrupted error before, so I can't say what it means. Maybe it was the Ritek discs that were the problem. However, that doesn't address your initial concern. If ImgBurn does any kind of writing to discs at the gathering of files stage. Were you creating an image file or writing these files on the fly to the BD-R? If you were writing on the fly, I can see it writing a packet of files, gathering some more, and then writing those while gathering some more. That might explain why some content was written to the disc. If you were creating an image file first and that was when the gathering of files was done, then nothing would have been written to an inserted disc because no access to the drive was being performed.
AlbertEinstein Posted July 21, 2018 Author Posted July 21, 2018 (edited) @dbminter, I just write my folders and files to disc on the fly most of the time since it saves ... time. But, one thing I do know, from my experience with burning BD-R using ImgBurn, is that I could have simply continued the burning process by skipping the file that was not found. Or, I could have moved the missing file back into the original folder that it was in when it was added to the disc layout editor, and ImgBurn, would have resumed burning the disc without issues. I've done this before and was very pleased at the flexibility of such a scheme. Being able to fix authoring errors mid-burn is a wonderful ability. Two thumbs up for that. I wish I would have just tried putting the files back where they were to begin with. Instead, I tried stopping the burn all together. I probably won't do that next time given this bad experience. EDIT: But just to answer your question and to re-iterate what I said before, the live log window said filling buffer when I cancelled the burn. It never specifically stated that it had begun (or finished) writing a lead-in and I know that has to be done first thing in the burn-process, does it not? When I say 'done first thing' I mean literally altering the physical media. Edited July 21, 2018 by AlbertEinstein
dbminter Posted July 21, 2018 Posted July 21, 2018 I'm no expert, but I would have to say that if anything is done before Writing LeadIn to prepare a disc for writing, it must be super quick.
LIGHTNING UK! Posted July 22, 2018 Posted July 22, 2018 Your drive shouldn't have needed to do anything at that stage and probably just errored out on the command to sync the cache - it would have been empty. The fact the drive isn't displaying any sort of MID/DID for the disc is a bit weird. Can you put a new disc in the drive and copy + paste everything from the box on the right when you're in Write mode please?
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 (edited) HL-DT-ST BD-RE WH10LS30 1.02 (SATA) Current Profile: BD-R Disc Information: Status: Empty State of Last Session: Empty Erasable: No Free Sectors: 12,219,392 Free Space: 25,025,314,816 bytes Free Time: 2715:27:17 (MM:SS:FF) Next Writable Address: 0 Supported Write Speeds: 2x, 4x, 6x, 8x Format Capacities: DT: 0x01 - NB: 12219392 (0x00BA7400) - TDP: 151552 FT: 0x00 - NB: 11826176 (0x00B47400) - TDP: 12288 FT: 0x32 - NB: 11826176 (0x00B47400) - TDP: 12288 FT: 0x32 - NB: 7369728 (0x00707400) - TDP: 151552 FT: 0x32 - NB: 12088320 (0x00B87400) - TDP: 4096 Performance (Write Speed): Descriptor 1... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 8,991 KB/s (2x) Descriptor 2... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 17,982 KB/s (4x) Descriptor 3... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 26,973 KB/s (6x) Descriptor 4... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 44,879 KB/s (10x) - WS: 35,964 KB/s (8x) Is there missing data still? This data is for a brand new Optical Quantum 25GB BD-R I just pulled off a newly opened spindle of 25 discs. #2 off the stack. I bought this spindle over a year (or more) ago. It's interesting to me that the label that hugs the spindle says these are for "1-4x SPEED" but there's a couple of descriptors above showing that it will burn at 6x and 8x also. You gotta love a producer that under promises and over delivers. Edited July 22, 2018 by AlbertEinstein
dbminter Posted July 22, 2018 Posted July 22, 2018 Many drives are capable of writing BD-R media capped at lower maximum write speeds at higher rates. For instance, my Verbatim BD-R are rated at 6x, but the Pioneer BDR-29M writes them at about 12x max.
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 Many drives are capable of writing BD-R media capped at lower maximum write speeds at higher rates. For instance, my Verbatim BD-R are rated at 6x, but the Pioneer BDR-29M writes them at about 12x max. But the real question is do those Verbatim media have media descriptors for those faster speeds? I'm assuming that no matter what the burner brand is it has to have a media descriptor. I'm guessing this is something along the lines of the manufacturer guaranteeing a minimum safe burn speed on the label but having extra descriptors for those who have a capable burner? Or are just adventurous.
dbminter Posted July 22, 2018 Posted July 22, 2018 I don't know for sure, but I would guess there isn't a write descriptor on the media for anything more than its highest maximum rate. The ability of the drive to write at higher rates of speed is down to the write strategy in the burner's firmware.
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 (edited) I don't know for sure, but I would guess there isn't a write descriptor on the media for anything more than its highest maximum rate. The ability of the drive to write at higher rates of speed is down to the write strategy in the burner's firmware. But that's what I'm asking. Your saying that your Verbatim BD-R rated at 6X on the label (or physical media surface) can be burned at 12x on your Pioneer drive. Have you used ImgBurn to see the highest rated burn speed per the actual descriptors on the media itself and not just the packaging or physical media surface print? Or are you saying that the burner's firmware can write faster than the fastest rated descriptors pre-written on the media if it wants too? Edited July 22, 2018 by AlbertEinstein
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 (edited) I just tried writing to this virgin BD-R (referenced in above post) and the software/system/burner froze up at the "Reserving Track" step. I waiting for about 5 minutes to see if anything changed (it never did) and then unplugged my SATA power cable from the physical BD-R burner so that ImgBurn didn't try to do something that permanently damages this disc also. I closed ImgBurn (well actually had to kill the process), reconnected the SATA power cable to the BD-R burner, rebooted Windows 10 and now the drive is not even recognized by the system. This burner is going on 9 years old now (purchased at the end of 2010), IIRC. "It's dead Jim!"? Edited July 22, 2018 by AlbertEinstein
dbminter Posted July 22, 2018 Posted July 22, 2018 My BD-R are physically labeled as 6x. Don't know what the actual write descriptors on the disc are because I don't care! I only care about what speeds I can get from the drive. So, I haven't checked the actual write descriptors on one of these BD-R in ImgBurn and it's not something that interests me to do so.
dbminter Posted July 22, 2018 Posted July 22, 2018 If your drive is 9 years old, it's well beyond twice the life span I've gotten from my best Pioneer. So, yeah, I'd say it's given up the ghost. As for the other thing about write speeds, it does seem a drive is capable of writing a media at greater than its highest listed write descriptor. It seem the drive manufacturer has tested that media at higher rates and they weren't corrupted by the faster writes. So, they "rate" them in the write strategies at higher that available writes in the write descriptors.
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 My BD-R are physically labeled as 6x. Don't know what the actual write descriptors on the disc are because I don't care! I only care about what speeds I can get from the drive. So, I haven't checked the actual write descriptors on one of these BD-R in ImgBurn and it's not something that interests me to do so. I was just curious if the drive was able to write faster than the rated speed of the media because it's an extra special drive or because there were faster media descriptors on the media already, but it's no big deal.
dbminter Posted July 22, 2018 Posted July 22, 2018 Actually, I had a cause to just now write a BD-R so I thought I'd check it out while I was at it. There actually are write descriptors on the disc, so ImgBurn is returning, for beyond 6x. However, it may be that write descriptors are returned by the drive itself and not necessarily the media. I don't know. I mean, why would they print 6x on the media and the packaging when it can actually write at twice that rate? It would be more of a selling point on the package to list higher rated speeds if they really are available.
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 (edited) Actually, I had a cause to just now write a BD-R so I thought I'd check it out while I was at it. There actually are write descriptors on the disc, so ImgBurn is returning, for beyond 6x. However, it may be that write descriptors are returned by the drive itself and not necessarily the media. I don't know. I mean, why would they print 6x on the media and the packaging when it can actually write at twice that rate? It would be more of a selling point on the package to list higher rated speeds if they really are available. Good question, maybe it's the same reason Intel and AMD sell overclockable processors. They sell them guaranteed to work at a rated speed but if you are an enthusiast and want to try your hand at faster speeds you can (on the overclockable models, that is). In other words, as a producer of goods, you always want to under promise and over deliver, versus over promising and under delivering. That's the absolute worst thing you can do. But like you I'm just not sure whether those media descriptors are created on the fly by the drive itself or they are already pre-written to the media. Maybe somebody else can clear this up for us. **EDIT**: I think your absolutely right though. Those media descriptors appear to be for the hardware itself and not the media. Edited July 22, 2018 by AlbertEinstein
AlbertEinstein Posted July 22, 2018 Author Posted July 22, 2018 Alas, after another reboot, my LG burner lives on. I think it was just playing dead so I would let it live out the rest of it's days in peace. I've put it back to work and it's approximately half way through another successful burn (fingers crossed).
dbminter Posted July 22, 2018 Posted July 22, 2018 Sometimes, something as unlikely as simply powering off and restarting Windows does wonders. Sometimes it does diddly!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now