Wile_E Posted August 13, 2006 Share Posted August 13, 2006 (edited) I am curious if Imgburn writes the VIDEO_TS files in the correct order on a DVD-R? There is a specific order that these files have to be written on the disc, to be fully DVD compliant. I believe the order should be IFO -> VOB -> BUP, physically like that on the disc. What about ROM folder for a DVD? If I add this folder, will it still burn compliant? There is some discussion over at the VideoHelp.com forums, whether ImgBurn burns fully compliant DVD's. http://forum.videohelp.com/viewtopic.php?t...c&start=360 Edited August 13, 2006 by Wile_E Link to comment Share on other sites More sharing options...
blutach Posted August 13, 2006 Share Posted August 13, 2006 Yes. The order of files is perfect. Yes, you can add DVD ROM files to the parent directory of VIDEO_TS. If anyone is at all unsure, make an ISO with ImgBurn and use ISOBuster to examine it. Here's a simple example: Regards Link to comment Share on other sites More sharing options...
volvofl10 Posted August 13, 2006 Share Posted August 13, 2006 Welcome to the forum Wile_E 10/10 for coming in here and asking the question , why no one else did off that forum i dont know Link to comment Share on other sites More sharing options...
blutach Posted August 14, 2006 Share Posted August 14, 2006 I got totally lost in all the BS in that thread volvo. My eyes just glazed over, particualr one bloke who wrote War and Peace every time sat down at the keyboard. Maybe they are RecordNow's answer to the AnyDVD forum at CD Freaks? Regards Link to comment Share on other sites More sharing options...
volvofl10 Posted August 14, 2006 Share Posted August 14, 2006 Blu - i started reading it, then skipped thru it at 16X Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 14, 2006 Share Posted August 14, 2006 Spend all that time doing the layerbreak stuff and then miss the basic ordering of VIDEO_TS files..... that would be pretty silly wouldn't it! It builds the images as 'fully compliant' as I know how to make them. Link to comment Share on other sites More sharing options...
Wile_E Posted August 14, 2006 Author Share Posted August 14, 2006 Thanks for clearing this up. A couple of people were saying how RecordNOW is very compliant. Now I can tell them that ImgBurn is just as compliant. Thanks again! Link to comment Share on other sites More sharing options...
blutach Posted August 14, 2006 Share Posted August 14, 2006 RecordNow is very compliant, AFAIK and respects the authoring, unlike Ner0. Regards Link to comment Share on other sites More sharing options...
jack Posted August 15, 2006 Share Posted August 15, 2006 (edited) Nice to see that RecordNow is compliant now, it used to be a bag of crap and "not fit to burn rags"(?jack1998-2006 ) Had a few horrible experiences with it when I first started burning DVD's, but then I found LUK's burning engine and havent had a coaster since. Edited August 15, 2006 by jack Link to comment Share on other sites More sharing options...
fordman Posted August 28, 2006 Share Posted August 28, 2006 Thanks for clearing this up. A couple of people were saying how RecordNOW is very compliant. Now I can tell them that ImgBurn is just as compliant. Thanks again! Actually, I thought RecordNow Deluxe 7.3+ was the way to go to burn dual layer DVDs directly from VIDEO_TS files, but I then ran into an instance where it failed. In the instance where it failed, I had over 3 hours of video in a title, and found the RecordNow did NOT insert the layer break flag as expected! Upon further examination, I discovered the reason. The cell (identical VOB/Cell ID) where the layer break flag should have been inserted was also used in another title, and RecordNow chose to flag the cell ONLY in that title! The end result was that the DVD would insert the necessary wait when playing that secondary title, but NOT when playing the main title - essentially the main title played as though it had a seamless layer break! I asked on the ImgBurn support forum whether the PGCEDIT/mkisofs combination would recognize and flag all instances of that vob/cell, and the answer was that it would, and I've since verified that in practice. I have not yet verified that the ImgBurn build mode will do the same as PGCEDIT/mkisofs in this instance, but if LUK has followed the logic of PGCEdit, then I assume it does. So, you can tell those people that ImgBurn is MORE COMPATIBLE than RecordNow! After that failure, I began using PGCEdit exclusively to make my dual layer images, even though it required an extra step compared to RecordNow, and I've since switched to ImgBurn's build mode, though I do avoid using it if the image I'm writing needs the 32K padding.... Link to comment Share on other sites More sharing options...
Recommended Posts