Peppero01 Posted October 27, 2006 Share Posted October 27, 2006 Hi, I've been using PGCEdit to make my ISO's and was just wondering if it's okay to make a layer break at a cell that is labeled as "LU" (language unit). Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 27, 2006 Share Posted October 27, 2006 Blu will help with this I'm sure, but you're probably better off asking in the IFO Editors forum at Doom9.org ! Out of interest, is that the only option you're given? Link to comment Share on other sites More sharing options...
Peppero01 Posted October 27, 2006 Author Share Posted October 27, 2006 (edited) Well, no--according to PGCEdit, that sector just happens to be nearest to the "optimal" LB point. Me, being wary, did not use it as a LB on my first burn, but instead used the sector below it (which was a segement of video showing the "FBI Warning" and NOT an LU). However, this caused 2 coasters with an I/O error. So this will be my third attempt and here's hoping I pick a LB point that will burn. If this one fails, I blame it on the media Edit: And just for reference... Edited October 27, 2006 by Peppero01 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 27, 2006 Share Posted October 27, 2006 I very much doubt the I/O error is anything to do with the layer break position. Post the log so we can see what's happening and what the exact error was. Link to comment Share on other sites More sharing options...
Peppero01 Posted October 27, 2006 Author Share Posted October 27, 2006 (edited) Sorry--I didn't have a chance to save the log as ImgBurn locked up both times the error was displayed. I was also thinking the I/O error couldn't have been because of the layer break point, but I just re-built the ISO with PGCEdit, selected a different point to break the layer, and it's been (so far) burning fine--if it errors out again, I'll make sure to post the log. But, for now, I still think it's the media I'm using that's causing the I/O. RiData isn't the most reliable--they were bought by a friend of mine when I specifically asked for Verbatim (oh well). The LU breaking point was more out of curiosity because I'm kind of wondering if putting the VTSM 3 LU on one layer and then putting the rest of the VTSM 3 files on an entirely separately layer will cause any issues. Edited October 27, 2006 by Peppero01 Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 27, 2006 Share Posted October 27, 2006 It's very rare for the entire program to lock up, most the code is done in thread - especially the burning stuff - so the GUI one should always be responsive. Did you have to terminate the process or something? Maybe even do a full reset of the comp? Link to comment Share on other sites More sharing options...
Peppero01 Posted October 27, 2006 Author Share Posted October 27, 2006 (edited) Nothing as drastic as resetting or terminating. I just chose to "End Task." Anyway... the third burn did wind up erroring out. Except, this time, I got a completely different error. The burn finishes, but it can't close the disc and I get this: "Finalise disc failed! Device: [1:0:0]_NEC_DVD+-RW ND-6650A 103C (D:)(ATA) Reason: Write Error" And... here's the log: I 18:07:32 ImgBurn Version 2.1.0.0 started! I 18:07:32 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2) I 18:07:32 Initialising SPTI... I 18:07:32 Searching for SCSI / ATAPI devices... I 18:07:32 Found 1 DVD-ROM and 1 DVD?RW! I 18:07:32 Operation Started! I 18:07:32 Source File: G:\Unsorted\EVANGELION_VOL_3_PLATINUM.ISO I 18:07:32 Source File Sectors: 3,430,666 (MODE1/2048) I 18:07:32 Source File Size: 7,026,003,968 bytes I 18:07:32 Source File Volume Identifier: EVANGELION_VOL_3_PLATINUM I 18:07:32 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR ? 1993 E.YOUNGDALE ? 1997 J.PEARSON/J.SCHILLING I 18:07:32 Source File Implementation Identifier: mkisofs I 18:07:32 Source File File System(s): ISO9660, UDF (1.02) I 18:07:32 Destination Device: [1:0:0] _NEC DVD+-RW ND-6650A 103C (D:) (ATA) I 18:07:32 Destination Media Type: DVD+R DL (Disc ID: RITEK-D01-01) (Speeds: 2.4x) I 18:07:32 Destination Media Sectors: 4,173,824 I 18:07:32 Write Mode: DVD I 18:07:32 Write Type: DAO I 18:07:32 Write Speed: 2.4x I 18:07:32 Link Size: Auto I 18:07:32 Test Mode: No I 18:07:32 BURN-Proof: Enabled I 18:07:33 User Specified L0 Data Zone Capacity: 1,889,328 I 18:08:06 Filling Buffer... I 18:08:07 Writing LeadIn... I 18:08:10 Writing Image... I 18:08:10 Writing Layer 0... (LBA: 0 - 1889327) I 18:27:08 Writing Layer 1... (LBA: 1889328 - 3430665) I 18:43:12 Synchronising Cache... I 18:43:13 Closing Track... I 18:43:32 Finalising Disc... W 18:46:00 Potential 'WaitImmediateIO' Deferred Error - (0/2) - Write Error - Retrying successfully closes the disc but will not play in the standalone player. Edited October 27, 2006 by Peppero01 Link to comment Share on other sites More sharing options...
spinningwheel Posted October 28, 2006 Share Posted October 28, 2006 RITEK-D01-01 Your choice of media is part of the problem Peppero01, Verbatims are the only ones we have had consistent success with here. Ritek was good media, but they changed about 18 months ago and now are very problematic. Link to comment Share on other sites More sharing options...
polopony Posted October 28, 2006 Share Posted October 28, 2006 before you make yourself nuts trying to see if its a software problem get Verbatims because like its been said Ritek has ben going down the tubes Link to comment Share on other sites More sharing options...
blutach Posted October 28, 2006 Share Posted October 28, 2006 Sorry to take a while to respond. The LU is simply a designator that there may be additional LUs on the DVD. There is no issue in breaking at, or in the middle of, any LU. For mine, however, I would always try to break at the start of a title - this is the natural place because there is always an STC discont and a non-seamless joint (in your case, you have title 4, 5 or 6 to pick from). Although, some would also say that it's a good thing to have a whole VTS on a single layer (so there's no swapping back and forwards across the LB when a menu call is made). So, 6 of one .... But, don't be afraid of breaking at the start of any LU (you can use PgcEdit to eliminate unwanted LUs if you like - Menu --> Remove LU). Regards Link to comment Share on other sites More sharing options...
Recommended Posts