fordman
-
Posts
184 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by fordman
-
-
Ah hah... found the problem
Whilst calculating the position to seek to within the file, the number must have been defaulting to using a 32bit integer rather than a 64bit one - which the result was being stored in.
A large number would have overflowed a 32bit integer variable - as is the case for a BUP file because it's normally much later on in the disc. (large LBA value * sector size is > max value a 32bit int can hold)
That would indeed be why you were finding random data changes in your vob. The new BUP would have been written to whatever (incorrect) file position the program had calculated, overwriting what was there originally.
Thanks, this has now been fixed.
OK, just checking back in after being away for awhile. I understand what you say here, and it appears that it both explains why my VOB was changed, and why the BUP was NOT changed - correct? The BUP was not changed because the changed version was buried in the VOB file that was altered? Meanwhile the original ISO file had the unaltered BUP file contents past the address space for the VOBs?
So, it appears there is no reason to use the grab5m program now?
I guess I need to do some more research about the multiple of 16 sectors for the layer break flag issue. I can point out various places where originally mastered DVDs do not comply with this, and as I said RecordNow Deluxe 7.3 does not pick flag positions that correspond to this, yet it changes layers flawlessly, even on older players which would have a problem with the lack of a layer break flag....
Sorry I left you hanging on this. I got busy with other things, and when I didn't see your usual quick reply, I figured it might take some time to work it out. As you can see, I am a bit obsessive about verifying my data backups before erasing the original files...
fordman
-
I used the ISO tool to see what were acceptable layer break points and ImgBurn only indicated that cell 25 was acceptable, though the previous cell would have been preferable for me, as that was the beginning of a scene change with fade out. Cell 25 was during a scene. Judging from the final burned disc which put 57.72% of the sectors in layer 0 (42.28%) and the short time between chapters (avg 5 minutes) it should have been possible to put the flag on cell 24.
OK, I saw LIGHTNING UK!'s post regarding the placement of layer breaks in his post here:
http://forum.imgburn.com/index.php?s=&show...findpost&p=8192
and looking at VTS_C_ADT in IfoEdit, I see that the start sector (+1) of cell 25 is evenly divisible by 16. How important is this, though? I burned the files from the original image with RecordNow Max Deluxe 7.3, and it chose cell 23, whose starting address (+1) is NOT evenly divisible by 16. Is this important because sectors are only allocated in a layer by groups of 16? I've never had an issue with layer breaks created by RecordNow Deluxe... In addition, I've noticed that pressed DVDs don't necessarily have the break on a cell which begins on an address that is a multiple of 16 sectors.
By the way, beside modifiying the VTS_01_0.IFO and VTS_01_0.BUP on the recorded disc to include the layerbreak flag, RecordNow left the rest of the files identical to the originals, as has been my experience in the past. What really amazes me about this program is that it does this on the fly without even having to modify the original files on your hard disk. Those remain without the flag information.
Perhaps Imgburn would be best served by following this approach, i.e. don't modify the actual ISO file itself, but rather make the layer break flag changes "on the fly" like RecordNow Max does. Of course that would make any image verification fail afterward...
-
I finally burned my first dual layer ISO file that didn't have a .MDS file associated. The image was created by CloneDVD.
I used the ISO tool to see what were acceptable layer break points and ImgBurn only indicated that cell 25 was acceptable, though the previous cell would have been preferable for me, as that was the beginning of a scene change with fade out. Cell 25 was during a scene. Judging from the final burned disc which put 57.72% of the sectors in layer 0 (42.28%) and the short time between chapters (avg 5 minutes) it should have been possible to put the flag on cell 24.
However, ImgBurn modified the ISO file to insert the flag in the VTS_01_0.IFO and burned fine, and compared fine, so that is not the bug.
The bug is that ImgBurn did not make the same change in VTS_01_0.BUP, which is supposed to be indentical to VTS_01_0.IFO and used in case VTS_01_0.IFO cannot be read for some reason. I recommend that this change be implemented in future releases.
I was alerted to this difference by creating CRCs of the files on the original image mounted as a drive and also for the modified image mounted as a drive. By doing this, I found that the CRCs of TWO files differed between the original and modified images:
VTS_01_0.IFO (as desired with the flag inserted, but VTS_01_0.BUP remained the same as original)
AND
VTS_01_3.VOB
Now, why did ImgBurn modify the VTS_01_3.VOB file? The video where the layer break flag corresponds to is actually contained within VTS_01_4.VOB, but even then there is no need to modify a VOB at all when setting a layer break flag - correct?
Here is the file compare log between the .SFV CRC files for both images:
***** Files_Image_Orig.sfv
VTS_01_0.BUP 2A4C6EE0
VTS_01_0.IFO 2A4C6EE0
VTS_01_0.VOB C7EBDAE0
***** FILES_IMAGE.SFV
VTS_01_0.BUP 2A4C6EE0
VTS_01_0.IFO B7667004
VTS_01_0.VOB C7EBDAE0
*****
***** Files_Image_Orig.sfv
VTS_01_2.VOB 145425D8
VTS_01_3.VOB 0EB4222A
VTS_01_4.VOB ABF4D22F
***** FILES_IMAGE.SFV
VTS_01_2.VOB 145425D8
VTS_01_3.VOB C62DF9EB
VTS_01_4.VOB ABF4D22F
*****
So, is ImgBurn actually corrupting my video files when it modifies the .ISO image?
I've attached zip files with the IFO and BUP files from both the original and modified images. However I cannot of course include the VOB file, though I would be curious to find out what change was made to it...
Thanks,
fordman
EDIT: I did some more research and found the the ImgBurn modified ISO had changed the VTS_01_3.VOB quite dramatically! Beginning at address 08E15000 the VTS_01_03.VOB had large sequences of bytes changed - mostly from actually values to 00 (null)! This is not good, so I will likely extract the ISO files and burn with a program like RecordNow Deluxe 7.3 to ensure I have an uncorrupted copy. For example, here is an example of one such range, and I even truncated this one for brevity's sake (The first column is the hex address, the second is the byte value in the original VOB at the address, and the third column is the ImgBurn modified value):
08E16814: 81 00
08E16815: 00 01
08E16817: 0B 2D
08E16818: 30 00
08E16819: E0 01
08E1681A: 33 00
08E1681B: 8C 2E
08E1681C: 1F 00
08E1681D: 20 01
08E1681E: 69 00
08E1681F: 2B 2F
08E16820: 23 00
08E16821: 16 00
08E16822: DC 00
08E16823: 09 00
08E16824: 27 00
08E16825: EC 00
08E16826: AE 00
08E16827: 07 00
08E16828: 55 00
08E16829: 62 00
08E1682A: 33 00
08E1682B: 37 00
08E1682C: 56 00
08E1682D: 4E 00
08E1682E: 51 00
08E1682F: FC 00
08E16830: 3C 00
08E16831: 79 00
08E16832: CD 00
08E16833: 06 00
08E16834: E6 00
08E16835: 0D 00
08E16836: 42 00
08E16837: 5F 00
08E16838: 67 00
08E16839: 5A 00
08E1683A: BE 00
08E1683B: 55 00
08E1683C: 9F 00
08E1683D: 5D 00
08E1683E: 41 00
-
No, you don't need to make an MDS file at all - and in any case, it still doesn't add layerbreak information to it.
You'd just load the ISO in ImgBurn, it'll parse the IFO files at then time of burning.
Thanks - I read somewhere on the forum a recommendation to create a .MDS from the DL ISO, so I thought it must parse the ISO and create a .MDS with the LB info in it. Thanks for confirming that the MDS creation utility functions as it did in DVDD.
By the way, I confirmed that those discs were indeed parallel track path, thus the selection of the VOBU/ECC boundary for the LB!
-
The two apps are standalone, nothing gets deleted, uninstalled or overwritten.
The bit you declined during the install of ImgBurn was nothing to do with the removal of DVD Decrypter, it was just to clean up your context menus so you didn't end up with 'Burn using DVD Decrypter' AND 'Burn using ImgBurn' when you right click an ISO image.
Having both is pointless and as waste of space - hence why ImgBurn offers to clean it up for you.
If the MDS file you have hasn't just been made by the 'Create DVD MDS File' option in the tools menu, the problem you're having with DL burns is that the images you're burning are from PTP DVDROM discs. You can't always burn such images onto an OTP disc because for OTP, Layer 0 must be bigger than (or the same size as) Layer 1.
That is not true for PTP, where Layer 1 can be bigger than Layer 0.
If the layerbreak position read from the MDS file is such that it cannot go on an OTP disc, the program has to attempt to move it.
How well that works out is anyones guess!
You should always use ImgBurn for DL burning now, it has other neat tricks that DVD Dec doesn't.
Thanks for the quick reply - I realized the ambiguity in my statement and edited my post to confirm that the .MDS was created automatically when I read the disc (4 total - 3 from one set, 1 separate) to ISO image.
So, it appears this was a coincidence then that I ran into my first 4 (2 if you count that 3 were from the same set) discs with PTP authoring after installing ImgBurn.
On another, but related subject: If I understand it correctly, if I have an DL ISO file without a .MDS file, I should use ImgBurn's option to parse and create a .MDS file, and burn with that .MDS? The .MDS should function as if it was made along with the image in DVDD?
Thanks again,
fordman
-
Hello,
I was using DVDD 3.5.4.0 and saw ImgBurn 1.1.0.0, which I installed. I declined to uninstall DVDD when it asked, however.
Does the "engine" for ImgBurn in any way affect the choice of a layer break in DVDD when I burn with DVDD and open the .MDS file which I created with DVDD? (EDIT - note that the .MDS was created when reading the disc to an ISO image - I did not use the separate option to create a .MDS file, which I realize does NOT parse ISO files to find the original LB position)
I ask because, despite installing ImgBurn, I decided to continue using DVDD to burn some dual layer images I had read to my HD with DVDD. As usual I opened the .MDS file and in the LOG it showed that it was using the VOBU/ECC method of finding the optimal layer break position, instead of "copied from original image" like it always used to.
So, is there a .DLL file that ImgBurn installed that overwrote what DVDD was using and is not affecting the choice of layer break position in DVDD?
This happened for a total of 4 images now.....did DVDD just burn them in the dumb ISO mode and ignore the .MDS information?
Thanks,
Ford Man
Bug with Layer Break Flag setting on ISO burns
in ImgBurn Bugs
Posted
OK, I was just looking at one back when I wrote the original message in this thread. I'll see if I can find it again, or look for others.
For the .IFO files I posted in the zips attached to the original message, I looked and saw that ImgBurn chose cell 25 as the layer break flag point (a integer multiple of 16 sectors), while RecordNow Deluxe chose cell 23 (not an integer multiple). Meanwhile my preference would have been cell 24 because of a scene change between cell 23 and 24. Anyway, can you confirm my math that RecordNow Deluxe chose a cell that does not conform to DVD-VIDEO specifications? Also, do you have a handy link to this rule? I'm only asking because I may pursue this with Sonic so that they can fix their program to make it compliant. Though I haven't had trouble with layer changes written by RecordNow up through this point, it would be nice to be confident in it's results!
Thanks for your excellent detective work! I'll give you feedback if you release a new version that overcomes this issue.