roylayer

Thanks for the info on balancing. As fate would have it, I _will_ have the same amount of data on the other layer (assuming that I can completely fill one layer with video) since I use BurnToTheBrim to completely fill up a DVD. So, any idea what the magic number should be? I agree that my request is funny. I already have many binders of discs (CD and DVDs) and am getting ready to convert my old homemade video tapes to disc. I figure that double layer costs a little more than twice as much per byte as single layer (for the media I use). I felt like I had to take extreme measures to keep my storage under control! ;-) "I may wish to re-evaluate things?" LOL. You are probably right, but it is a sickness. ;-) To be honest, DVDShrink/backups are only a small fraction of the video DVDs that I burn. Since the disc is only a backup, I hope that I don't have to use it anyway, and DVDShrink's quality (to DVD5) is very good in case that I do. I figured that it might be worth shrinking it just a little more to fit onto one layer rather than shrink to 4.37GB and have a layer break for sure on DL.

Yes, I realize that this is an unusual request. Yes, I realize that 2 single layer discs are cheaper than 1 dual layer. At this point, I am happy with the extra cost vs. the savings in storage space. I have burned discs like this many times with video content that will obviously fit on one layer (2 GB for example), and they work fine. Thanks for commenting on my strange request. It will be interesting to see what comes of it.

Good question! I have started burning DL discs in order to save disc storage space. Their price has finally come down enough to make it worthwhile.

I've been using DVDShrink to back up my DVDs to DVD5s for a long time. Now, I want to create DL DVDs that have the VIDEO_TS files from DVDShrink + other data files. What I would like to do is to tell DVDShrink to create the VIDEO_TS files at a total size to fit on one layer so that I do not have to worry about layer breaks. Then, other data files would fit on the 2nd layer. (All of my standalone DVD players play discs like this with no problem.) So, my question (at long last) is: What size should I specify in DVDShrink so that all of its output files will fit on one layer when burning a DL disc with IMGBurn? Any help is appreciated!

Too many strange things were happening, so I finally bought a new burner. Guess what? No problems now! So it looks like all of my problems on this thread were actually due to a burner that was in the processing of self-destructing.

Believe it or not, my failed Verbatims were made in Singapore. Very strange! Here's another oddity that happened in connection with this exercise: Yesterday, I went to erase two DVD-RWs, but the burner failed with both of them. Since the only thing that I've changed recently is the firmware, I reverted to my old firmware, and then they erased with no problem. Arghh!

Thanks, LUK. I will play around with that setting. Imgburn sure is flexible. I like that!

OK. I just successfully burned a TDK disc with the exact same contents, under the exact same conditions that failed with my last Verbatim disc. Here are the tests that I've done so far: Test# Disc Type Reboot File system Full Contents Result 1 Verbatim n iso9660+udf y video_ts error in finalizing - lead in and out 2 Verbatim n iso9660+udf y files error in finalizing - lead out 3 TDK y udf n files ok 4 Verbatim y udf n files error in finalizing - lead out 5 TDK y udf n files ok. (identical files to test 4) Reboot: Whether I rebooted before burning. (Note: Extraneous tasks were shut down for all tests.) Full: I normally use a program called Burn to the Brim to fill up discs as much as possible. "y" means space was 100% used. "n" means that I filled it to about 98% capacity. From these tests, it sure looks like the burner likes TDK and not Verbatim. That is strange because Verbatim seems to be one of the prefered brands in this forum. Some possibilities: 1) Maybe the real manufacturer of the Verbatims is different for their 3 packs than for their spindles. I've seen things like that happen with CD-Rs. 2) Maybe Verbatim has changed their manufacturer from a good one to a bad one recently. 3) Maybe my Sony burner simply works better with TDKs. That seems strange because their documentation says that Verbatim is a prefered brand for their drive. (Of course, possibilities 1 and 2 could have negated that.) OTOH, TDK is one of the brands that works consistently well for my single layer burns using the same burner, so maybe that isn't surprising. I thought you guys might be interested in my findings. I'll let you know if I learn anything more. Roy P.S. Sorry for the bad format of the "test table." They showed up in separate columns when I composed the note, but the rows were collapsed when I posted it. (I guess this BBS doesn't handle tabs well.)

I successfully burned my first DL disc... a TDK! Then I tried a similar burn with a Verbatim, and it failed. Score so far: TDK - 1 out of 1, Verbatim - 0 out of 3. I am running more tests now and will let you know what I find out.

Good, I didn't think DVD ROM files should be affected by the layer break. Thanks for that. I tried to close the disc manually, but nothing seemed to happen - no message... nothing! I haven't tried building an ISO first. That is a good idea. I will give that a try.

Next (failed) experiment: After updating my drive's firmware to BYX5, I tried burning another Verbatim DL disc. This time, I tried a straight data disc (i.e. no video_ts folder). Very similar result, although this time I only got the "lead out" error, not the "lead in" one. The disc has mpeg4 files on it that my standalone Philips DVD player can play, so I tested the disc in it. As far as I can tell, all of the files are playable on it. However, the DVD burner in PC does not even recognize the disc. Here is the log: I 08:46:55 ImgBurn Version 2.1.0.0 started! I 08:46:55 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 08:46:55 Drive D:\ (FAT32) does not support single files > 4 GB W 08:46:55 Drive I:\ (FAT) does not support single files > 4 GB W 08:46:55 Drive Q:\ (FAT32) does not support single files > 4 GB W 08:46:55 Drive T:\ (FAT32) does not support single files > 4 GB I 08:46:55 Initialising SPTI... I 08:46:55 Searching for SCSI / ATAPI devices... I 08:46:55 Found 1 CD-RW and 1 DVD?RW! I 08:47:10 Operation Started! I 08:47:10 Building Image Tree... I 08:47:10 Checking Directory Depth... I 08:47:10 Calculating Totals... I 08:47:10 Preparing Image... W 08:47:10 ISO9660 Directory: [name omitted] W 08:47:10 ISO9660 File: [name omitted] [more directory and file messages] I 08:47:11 Checking Path Length... I 08:47:11 Image Size: 8,872,951,808 bytes I 08:47:11 Image Sectors: 4,332,496 I 08:47:11 Operation Successfully Completed! - Duration: 00:00:00 I 08:48:27 Operation Started! I 08:48:27 Building Image Tree... I 08:48:27 Checking Directory Depth... I 08:48:27 Calculating Totals... I 08:48:27 Preparing Image... W 08:47:10 ISO9660 Directory: [name omitted] W 08:47:10 ISO9660 File: [name omitted] [more directory and file messages] I 08:48:27 Checking Path Length... I 08:48:27 Image Size: 8,505,982,976 bytes I 08:48:27 Image Sectors: 4,153,312 I 08:48:27 Operation Successfully Completed! - Duration: 00:00:00 I 08:52:17 Operation Started! I 08:52:17 Building Image Tree... I 08:52:17 Checking Directory Depth... I 08:52:17 Calculating Totals... I 08:52:17 Preparing Image... W 08:47:10 ISO9660 Directory: [name omitted] W 08:47:10 ISO9660 File: [name omitted] [more directory and file messages] I 08:52:17 Checking Path Length... I 08:52:17 Image Size: 8,505,982,976 bytes I 08:52:17 Image Sectors: 4,153,312 I 08:52:35 Operation Successfully Completed! - Duration: 00:00:18 I 08:52:35 Operation Started! I 08:52:35 Source File: -==/\/[bUILD IMAGE]\/\==- I 08:52:35 Source File Sectors: 4,153,312 (MODE1/2048) I 08:52:35 Source File Size: 8,505,982,976 bytes I 08:52:35 Source File Volume Identifier: TV I 08:52:35 Source File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER! I 08:52:35 Source File Implementation Identifier: ImgBurn I 08:52:35 Source File File System(s): ISO9660, UDF (1.02) I 08:52:35 Destination Device: [1:0:0] SONY DVD RW DRU-710A BYX5 (F:) (ATA) I 08:52:35 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x, 4x) I 08:52:35 Destination Media Sectors: 4,173,824 I 08:52:35 Write Mode: DVD I 08:52:35 Write Type: DAO I 08:52:35 Write Speed: 2.4x I 08:52:35 Link Size: Auto I 08:52:35 Test Mode: No I 08:52:35 BURN-Proof: Enabled I 08:52:35 Optimal L0 Data Zone Capacity: 2,076,656 I 08:52:35 Optimal L0 Data Zone Method: ECC Block Boundary I 08:53:31 Filling Buffer... I 08:53:32 Writing LeadIn... I 08:53:34 Writing Image... I 08:53:34 Writing Layer 0... (LBA: 0 - 2076655) I 09:14:38 Writing Layer 1... (LBA: 2076656 - 4153311) I 09:35:47 Synchronising Cache... I 09:35:49 Closing Track... I 09:35:50 Finalising Disc... W 09:36:11 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out E 09:39:07 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead Out I 09:39:07 Image MD5: ca2b3d6f0e9c7d598e4206013539c020 I 09:39:07 Operation Successfully Completed! - Duration: 00:46:32 I 09:39:07 Average Write Rate: 3,280 KB/s (2.4x) - Maximum Write Rate: 3,413 KB/s (2.5x) ------ This is frustrating. I am going to try burning to another brand, but the consensus here seems to be that Verbatim is one of the best, and it is also recommended by Sony for this drive. Does anyone have any other ideas?

I haven't burnt more than 20 Dual Layers but this message would worry me, the other discs that you burnt successfully - did they have this message too ? Like I said it might be nothing but you seem to be like me and would rather not see an expensive dual layer coaster ! If your firmware was quite old it could be as easy as the update blu suggested and you have already performed. I don't know much about DL discs, but the disc I was burning had a VIDEO_TS folder that was 4.19 GB. Thus, it seems that it should fit on one layer and not need to be split. I was assuming that Imgburn would be smart enough to do the split on some other data file where it wouldn't be as noticeable as when watching the video DVD portion of the disc. I thought that the "Unable to find any cells that could be used for the layer break" message refered to not being able to find any such cells to split the video since it didn't need to split the video. Am I assuming too much?

Thanks, Les. I have already upgraded my drive with the BYX5 firmware mentioned on that site (although I downloaded it from Sony since I am paranoid). I was just waiting to see what you and others thought before trying it again with the new firmware. I guess it's time to potentially sacrifice a new disc. ;-) I'll test it out tomorrow. Roy

I tried burning my first double layer DVD+R last night. Things went well all the way up until the disc finalization. Specs: Dell pentium 4 2.53 GHz, 1.5 GB RAM, windows xp sp 2, imgburn version 2.1.0.0, sony dru-710a, firmware by03. Verbatim DVD+R DL, burned at 2.4x. Here is the log: I 22:09:19 ImgBurn Version 2.1.0.0 started! I 22:09:19 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) W 22:09:19 Drive D:\ (FAT32) does not support single files > 4 GB W 22:09:19 Drive I:\ (FAT) does not support single files > 4 GB W 22:09:19 Drive Q:\ (FAT32) does not support single files > 4 GB W 22:09:19 Drive R:\ (FAT32) does not support single files > 4 GB W 22:09:19 Drive T:\ (FAT32) does not support single files > 4 GB I 22:09:19 Initialising SPTI... I 22:09:19 Searching for SCSI / ATAPI devices... I 22:09:19 Found 1 CD-RW and 1 DVD?RW! I 22:26:13 Operation Started! I 22:26:13 Building Image Tree... I 22:26:13 Calculating Totals... I 22:26:13 Preparing Image... I 22:26:13 Image Size: 8,543,600,640 bytes I 22:26:13 Image Sectors: 4,171,680 I 22:26:13 Operation Successfully Completed! - Duration: 00:00:00 I 22:41:54 Operation Started! I 22:41:54 Corrected conflicting settings for DVD Video disc. I 22:41:54 Building Image Tree... I 22:41:54 Corrected file system selection for DVD Video disc. I 22:41:54 Checking Directory Depth... I 22:41:54 Calculating Totals... I 22:41:54 Preparing Image... W 22:41:54 ISO9660 Directory: [name omitted] W 22:41:54 ISO9660 File: [name omitted] [... snipped other directory/file messages] W 22:42:04 Unable to find any cells that could be used for the layer break! I 22:42:04 Checking Path Length... I 22:42:04 Image Size: 8,543,633,408 bytes I 22:42:04 Image Sectors: 4,171,696 I 22:42:04 Operation Successfully Completed! - Duration: 00:00:09 I 22:46:10 Operation Started! I 22:46:10 Building Image Tree... I 22:46:10 Checking Directory Depth... I 22:46:10 Calculating Totals... I 22:46:10 Preparing Image... W 22:41:54 ISO9660 Directory: [name omitted] W 22:41:54 ISO9660 File: [name omitted] [... snipped other directory/file messages] W 22:46:14 Unable to find any cells that could be used for the layer break! I 22:46:14 Checking Path Length... I 22:46:14 Image Size: 8,543,633,408 bytes I 22:46:14 Image Sectors: 4,171,696 I 22:46:46 Operation Successfully Completed! - Duration: 00:00:36 I 22:46:46 Operation Started! I 22:46:46 Source File: -==/\/[bUILD IMAGE]\/\==- I 22:46:46 Source File Sectors: 4,171,696 (MODE1/2048) I 22:46:46 Source File Size: 8,543,633,408 bytes I 22:46:46 Source File Volume Identifier: PLP I 22:46:46 Source File Application Identifier: IMGBURN V2.1.0.0 - THE ULTIMATE IMAGE BURNER! I 22:46:46 Source File Implementation Identifier: ImgBurn I 22:46:46 Source File File System(s): ISO9660, UDF (1.02) I 22:46:46 Destination Device: [1:0:0] SONY DVD RW DRU-710A BY03 (F:) (ATA) I 22:46:46 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x) I 22:46:46 Destination Media Sectors: 4,173,824 I 22:46:46 Write Mode: DVD I 22:46:46 Write Type: DAO I 22:46:46 Write Speed: 2.4x I 22:46:46 Link Size: Auto I 22:46:46 Test Mode: No I 22:46:46 BURN-Proof: Enabled I 22:46:46 Optimal L0 Data Zone Capacity: 2,085,856 I 22:46:46 Optimal L0 Data Zone Method: ECC Block Boundary I 22:47:25 Filling Buffer... I 22:47:26 Writing LeadIn... I 22:47:28 Writing Image... I 22:47:28 Writing Layer 0... (LBA: 0 - 2085855) I 23:08:37 Writing Layer 1... (LBA: 2085856 - 4171695) I 23:29:51 Synchronising Cache... I 23:29:54 Closing Track... I 23:29:55 Finalising Disc... W 23:30:04 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead In W 23:34:07 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Session Fixation Error Writing Lead Out E 23:34:17 Finalise Disc Failed! - Reason: Session Fixation Error Writing Lead Out I 23:34:17 Image MD5: d8e04ae7323f5fdef66571a791605d96 I 23:34:18 Operation Successfully Completed! - Duration: 00:47:31 I 23:34:18 Average Write Rate: 3,280 KB/s (2.4x) - Maximum Write Rate: 3,413 KB/s (2.5x) -------------- This DVD has a VIDEO_TS folder plus other folders to fill out the unused space from the video DVD. I have burned similar DVDs (DVD-R and DVD+RW) successfully with imgburn. Interestingly, the DVD video portion of the disc seems to play find in my standalone DVD player. I can play the audio tracks (FLAC) fine in my MediaMonkey application, and I can access the files via Windows Explorer. However, Advanced Checksum Verifier (an MD5 checksum utility) hangs when it tries to read the first file that it tries to check. I read old messages in the forum that were similar to my problem, but I didn't see any definite solutions. I tried manually closing the disc via tools / drive / close / disc, but nothing seemed to happen. I have just upgraded the drive's firmware to BYX5, but I don't want to try burning again until I hear what you guys have to say. (I bought a 3 pack of Verbatim's just to do some testing before buying a spindle, so each disc is very expensive!) Do you guys have any ideas why it might have failed or should I just try it again with the new firmware? Thanks!

Great! I am sure that changing something as basic as the supported character set would cause all sorts of nighmares in coding. I'm probably can't even begin to imagine! Thanks again.

Thanks for the quick reply! Yes, I think that the "fat minus sign" is very strange too! Unfortunately, that is only the tip of the iceberg. I will also have folders with city names like Munich (except spelled with the unicode symbol with 2 dots above the u.) and other unicode characters like that. Any idea when the new version will be released? (I am a developer myself, so I know how much you must hate getting a question like that.) ;-) Many thanks for a great tool!

When burning a non-video DVD, some files are inaccesable after the burn. Here is the folder name: Roxy Music?Glasgow 2001-06-11 (SECC Arena) The burned folder on the DVD has a little square character in place of the first "?". If you look closely at that character, it is slightly longer than the standard dash/minus sign (as shown later in the folder name). So, I believe that the character is part of an extended character set, not the standard ASCII character set. When I click on the folder on the DVD, I can see the files, but if I try to open any of them, nothing happens. This is true when using Build mode with the UDF file system and with UDF + ISO9600 file systems. My setup: Windows XP, service pack 2. ImgBurn 2.1. So, here is my question: Is there anyway to force ImgBurn to handle the extended character set correcly? Thanks!