idic5 Posted April 21, 2017 Posted April 21, 2017 I had an apparently good burn of a DL DVD ( verbatim) from a dvd image, but an hour into the movie, it froze. this was duplicated on a couple different players as well as on the computer. THE image plays ok in that area, so it is a bad burn. My concern is not the burn, as I know it can happen once in a while, but how is it that VERIFY succeeded and it was still a bad burn? 1) burn said succeeded 2) verify said succeeded, 3) disc played ok until a certain area was encountered in the movie. Since I was going burn many discs and distribute them , I wanted to be sure they are good burns. Is there some good VERIFY parameters ( or write parameters) to ensure that the burn is in fact good? version 2.5.8.0
LIGHTNING UK! Posted April 21, 2017 Posted April 21, 2017 This isn't a bug. If the verify operation succeeds, it shows the disc was read correctly and in full on the drive that burnt it at that moment in time. It doesn't mean it'll be perfectly readable in all drives. To get an idea of the actual quality of the burn, you'd need to PIPO scan it using appropriate hardware. Do not mess with any of the options, they will not help here.
dbminter Posted April 21, 2017 Posted April 21, 2017 What I don't understand is something I've had happen a few times. A burn will complete without errors, it will Verify without errors, yet the disc is unreadable. You insert it into a player and it won't recognize. And when I insert it back into an optical drive to try and check the disc, the optical drive light flashes forever, meaning the disc is not readable. I've never understood that one.
LIGHTNING UK! Posted April 21, 2017 Posted April 21, 2017 Verify wouldn't pass if the disc was unreadable. That's not to say the drive couldn't burn, eject, reinsert, recognise the disc and successfully verify it, eject, reinsert and then fail to recognise the disc. If verify passes, at that specific moment in time, it was fine. It just means it's fluke if your burner will see the disc or not. If it worked the first time, chances are it'll eventually recognise it again if you eject + reinsert enough times.
dbminter Posted April 21, 2017 Posted April 21, 2017 My empirical evidence says otherwise. I know it makes no sense, but none of my 5 DVD players would recognize these discs and all 3 of my optical discs, 2 SATA's and one USB, would flash their lights forever attempting to recognize them. It sounds impossible, it makes no logical sense, but it was never said that the improbable can't happen. I've had it happen to me 3 times. ImgBurn is always set to Eject after writing, so it should have "cleared" the drive of anything after writing. Now, I think all these discs were DVD+RW's. It's possible, and really the only logical solution, that they wrote fine, were readable on Verify, but on eject after Verify, they "died" because they're random access memory and could have been "destroyed" with each read of sectors from it. Reads shouldn't affect writing, but it's the only logical explanation. The discs were close to dying and the laser power, though set to read, was hot enough that it destroyed the sector(s) necessary to recognize the disc as a loadable disc.
LIGHTNING UK! Posted April 21, 2017 Posted April 21, 2017 I did say it was readable at that *moment in time*. If you'd fired up Explorer and tried to browse the disc straight after it had verified (without ejecting / reinserting the disc again), the files should have shown up. It's impossible to predict other 'weird goings on' related to media being used.
mity Posted October 6, 2018 Posted October 6, 2018 hi, i have problems with burn. The program hangs tightly when writing,the drive is constantly lit diode. Took from the seller two banks of 50 pieces BD-R 50gb one was recorded without problems, the second is hung, the Bida problem with the buffer, put other programs wrote, then tried Img also wrote, then again such trouble. Tried in different systems both on XP and on W7. Even has tried on clean. When I wrote the first Bank in the settings nothing changed and it was written all at once and quickly.Why so long not update and fix bugs and bugs? I ordered 50gb drives again recently. Try one and if not move permanently to another program,if it is to wag your nerves I will change the BD drive. I 21:31:56 ImgBurn Version 2.5.8.0 started! I 21:31:56 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 21:31:56 Total Physical Memory: 8 354 840 KiB - Available: 4 546 068 KiB I 21:31:56 Initialising SPTI... I 21:31:56 Searching for SCSI / ATAPI devices... I 21:31:57 -> Drive 1 - Info: Optiarc DVD RW AD-7700S 1.71 (F:) (SATA) I 21:31:57 -> Drive 2 - Info: ASUS SBW-06D2X-U D301 (G:) (USB 2.0) I 21:31:57 Found 1 DVD±RW/RAM and 1 BD-RE XL! I 21:32:14 Operation Started! I 21:32:14 Building Image Tree... I 21:32:14 Checking Directory Depth... I 21:32:14 Calculating Totals... I 21:32:14 Preparing Image... I 21:32:14 Checking Path Length... I 21:32:14 Contents: 91 Files, 5 Folders I 21:32:14 Content Type: Data I 21:32:14 Data Type: MODE1/2048 I 21:32:14 File System(s): ISO9660, UDF (1.02) I 21:32:14 Volume Label: [Not Configured] I 21:32:14 Size: 49 079 530 034 bytes I 21:32:14 Sectors: 23 964 666 I 21:32:14 Image Size: 49 080 434 688 bytes I 21:32:14 Image Sectors: 23 965 056 I 21:32:14 Operation Successfully Completed! - Duration: 00:00:00 I 21:32:50 Operation Started! I 21:32:50 Building Image Tree... I 21:32:50 Checking Directory Depth... I 21:32:50 Calculating Totals... I 21:32:50 Preparing Image... I 21:32:51 Checking Path Length... I 21:32:51 Contents: 92 Files, 5 Folders I 21:32:51 Content Type: Data I 21:32:51 Data Type: MODE1/2048 I 21:32:51 File System(s): ISO9660, UDF (1.02) I 21:32:51 Volume Label: [Not Configured] I 21:32:51 Size: 49 948 923 403 bytes I 21:32:51 Sectors: 24 389 175 I 21:32:51 Image Size: 49 949 835 264 bytes I 21:32:51 Image Sectors: 24 389 568 I 21:32:51 Operation Successfully Completed! - Duration: 00:00:00 I 21:33:17 Operation Started! I 21:33:17 Building Image Tree... I 21:33:17 Checking Directory Depth... I 21:33:17 Calculating Totals... I 21:33:17 Preparing Image... I 21:33:17 Checking Path Length... I 21:33:17 Contents: 92 Files, 5 Folders I 21:33:17 Content Type: Data I 21:33:17 Data Type: MODE1/2048 I 21:33:17 File System(s): ISO9660, UDF (1.02) I 21:33:17 Volume Label: eg10p4 I 21:33:17 Size: 49 948 923 403 bytes I 21:33:17 Sectors: 24 389 175 I 21:33:17 Image Size: 49 949 835 264 bytes I 21:33:17 Image Sectors: 24 389 568 I 21:33:19 Operation Successfully Completed! - Duration: 00:00:01 I 21:33:19 Operation Started! I 21:33:19 Source File: -==/\/[BUILD IMAGE]\/\==- I 21:33:19 Source File Sectors: 24 389 568 (MODE1/2048) I 21:33:19 Source File Size: 49 949 835 264 bytes I 21:33:19 Source File Volume Identifier: eg10p4 I 21:33:19 Source File Volume Set Identifier: 4B7BAC27017427B0 I 21:33:19 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 21:33:19 Source File Implementation Identifier: ImgBurn I 21:33:19 Source File File System(s): ISO9660; UDF (1.02) I 21:33:19 Destination Device: [0:0:0] ASUS SBW-06D2X-U D301 (G:) (USB) I 21:33:19 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000) I 21:33:19 Destination Media Supported Write Speeds: 2x; 4x I 21:33:19 Destination Media Sectors: 24 438 784 I 21:33:19 Write Mode: BD I 21:33:19 Write Type: DAO I 21:33:19 Write Speed: MAX I 21:33:19 Hardware Defect Management Active: No I 21:33:19 BD-R Verify Not Required: Yes I 21:33:19 Link Size: Auto I 21:33:19 Lock Volume: Yes I 21:33:19 Test Mode: No I 21:33:19 OPC: No I 21:33:19 BURN-Proof: Enabled I 21:33:19 Write Speed Successfully Set! - Effective: 17 983 KB/s (4x) I 21:33:23 Filling Buffer... (80 MiB) I 21:33:26 Writing LeadIn... I 21:33:48 Writing Session 1 of 1... (1 Track, LBA: 0 - 24389567) I 21:33:48 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 24389567) I 21:33:48 Writing Layer 0... (LBA: 0 - 12219391) I 22:04:54 Writing Layer 1... (LBA: 12219392 - 24389567)
jdh5968 Posted October 11, 2018 Posted October 11, 2018 (edited) Maybe that drive doesn't support that disc. Edited October 11, 2018 by jdh5968 Err for typin`
Ch3vr0n Posted October 11, 2018 Posted October 11, 2018 Use quality blanks, not the cheap ritek crap you are now, like verbatim datalife plus.
mity Posted November 15, 2018 Posted November 15, 2018 On 10/11/2018 at 12:27 PM, jdh5968 said: Maybe that drive doesn't support that disc. no, support. Drive burn ok disks
Ch3vr0n Posted November 15, 2018 Posted November 15, 2018 That doesn't negate the fact that you're using cheap crappy blanks. Just because it burns the disc, doesn't mean it did a good job at it and that the end result will be readable.Use better quality blanksVerstuurd vanaf mijn Nexus 6P met Tapatalk
Recommended Posts