Jump to content


  • Posts

  • Joined

  • Last visited

quantumred's Achievements

ISF Newbie

ISF Newbie (1/5)

  1. Actually I was originally referring to: Tools->Settings->Write->Verify Against Image File I see that you think I was referring to: Mode->Verify->Verify Against Image File But I was not. Now that we have that cleared up :-) Tools->Settings->Write->Verify Against Image File Does not seem to have any effect. Checked or unchecked, it always compares against the original data. I'm thinking unchecked should do a simple "disk is readable" verification.
  2. Unless I don't understand the point of the "Verify Against Image File" check box, it doesn't work for me in It always reads against the original data when verifying after build mode. I'm trying to do a simple "disk is readable" verify after a build and write, so I have the box unchecked, but Imgburn still accesses the original data during verify, which happens to reside on a remote PC on my LAN.
  3. I second this request, regardless of where the option is activated. I drag and drop to the ImgBurn window and have to shuffle things around to make it work. "Always on Top" would help.
  4. Way back in the old days when I first started burning DVD's, I put MD5's in the root of the DVD: Video_ts\ Audio_ts\ checksum.md5 I could then verify the entire Video_ts directory from the checksum file. Creating the MD5 was a time consuming process so I quickly abandoned it. Additionally, DVD's have their own error correction built in. If you are can copy the files from the burned disk, then they should, in theory, be guaranteed to be free of errors. If there are errors, the copy should fail. If LUK could add the md5 file as shown above without taking additional time, then it might be an interesting feature.
  5. By the time you see that dialog, if the label has not been set, you have to click cancel, click back to the labels tab, type it in, click start, answer the dual layer break again, click past the info dialog to begin. From the standpoint that less clicks to get the job done is better, this is not as efficient as it could be. Another option would be to include the volume label on the main build screen where it's always visible, and maybe have a button to auto generate the name from the directory name It would also be nice to have the write speed for the device (if applicable) on the main screen perhaps right near the "destination". Of course it's your program so do what you think is best. Being an old school programmer and UI designer myself, I can't help but notice when I'm making clicks that I think are "extra". Then I have to bring it up here which is your fault for making a "suggestions" forum
  6. This could be reasonable if used in a specific context. A folder, call it "matrix_root" is added to the compilation that contains a video_ts subfolder. The fact ImgBurn handles this and creates a valid DVD structure complete with audio_ts folder is actually a cool feature. If it's the first folder in the compilation and the volume label is not already set, then set the volume label to the name of the root folder (the one immediately above video_ts). This could be a time saver and prevent accidentally not setting the volume label. I've already burned some disks where the label was not set because it's on a different tab and I forgot to update it.
  7. My tests show if you select a different layer break when prompted by ImgBurn, it will replace the existing one. I don't know if you can tell from ImgBurn's popup which of the layer break choices was originally in the IFO.
  8. Thought I'd start another thread separate from the announcement thread to thank LUK for his fine work. Burning files is an important step for ImgBurn. It will save time and steps for burning single and double layer disks without having to first create an image or use commercial software. Additionally, if you need to overburn a DVD+R, you can do that in a single step from files instead of making an image first. I'm not aware of any other software, commercial or otherwise, that can claim that capability. A fine piece of work all around.
  9. This time I really will answer my own question. I borrowed this from a DVD rebuilder change log: ...Also note IFOEDIT will incorrectly see the changes to the IFO for padding as offset errors. Do NOT perform an IFOEDIT "Get VTS Sectors" against a VIDEO_TS folder that has been built for ISO unless you are planning to use some other burning package to create the disc... I notice jdobbs turned off padding as the default.
  10. I'm clear on what's happening, but I don't understand the reasons. I'm not an ifo and dvd structure expert, so my question is, why does ifoedit think the sector addresses are wrong when using the 32k padding? Will my standalone be similarly confused?
  11. I reburned the same disk (I should have just made an image, but...) Ifoedit did not complain about sector addresses on the burned files when I turned off IFO/BUP 32k Padding.
  12. After burning two DVD's using build mode, I ran Ifoedit and "Get VTS Sectors" on the burned files. The disks are single layer. Ifoedit complained about sector addresses in the IFO's. I'm wondering if this is due to the ImgBurn default 32k padding? I'm going to reburn with the padding option disabled and see what happens.
  13. How many hours ago was this posted? By my watch, it appears to be about 26 hours ago?
  14. That looks like some of it. Maybe some screens will help: The first screen shows the CD-DVD Speed Disc Info tab for a DVD-R disc. Notice the "Recorder information" field is populated. The second screen shows and example of a disc quality scan and you can see the recorder information on the screen. The third screen shows a DVD+R. Notice there is no "Recorder information" field and it does not appear on the following scan. DVD+R recorders do not normally save this information while DVD-R recorders do. The point is, the CD-DVD Speed author has developed a way to somehow store the recorder information on a DVD+R, even though normally it is not stored by the recorder, when burning disks with CD-DVD Speed. If Lightning UK can duplicate this when we burn +r with imgburn, then we can have recorder information on +r when we scan with CD-DVD Speed.
  15. Even more ideal would be: Recorder - Firmware - Burn Speed - Date Example: BenQ DW1650 - BCHC - 8x - 07-30-06 I realize the date is stored when you originally burn the disc, however if you do a disc copy, the original date is retained and not the newly burned date. So recording the date it was actually burned would help.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.