Jump to content

LIGHTNING UK!

Admin
  • Posts

    30,521
  • Joined

  • Last visited

Posts posted by LIGHTNING UK!

  1. Nope, the dye used on a disc is not something that software has to deal with or do anything special for.

     

    Do you have any other dyes there at all?

     

    I'm wondering if the drive/firmware doesn't support the 'Verify Not Required' setting (although it's not complaining about it) and is actually verifying the BD-R as it writes - that would certainly explain why it's slow but it doesn't explain the buffer issues or high cpu usage.

     

    What speed was the DVD-RW you burnt to and the BD-RE?

  2. Well if it wasn't the media, it was your drive, take your pick.

     

    Something about your drive/firmware/media (and to an extent, write speed) just didn't place nicely together that time and the drive reported a 'Write Error' during the burn.

     

    If it's just one failure, forget about it and move on. If they're all failing then obviously you need to change something.

  3. The 'FORMAT UNIT' command ImgBurn uses for formatting the BD-RE has 1 parameter changed ('Format Sub-type Field') when you select full cert (or don't).

     

    It's set to '2' when full cert is enabled and '3' when it's not... and that's the ONLY difference.

     

    2 = Full Certification: The entire data area shall be certified. The defect tables shall be initialized

    with defects discovered during the certification process.

     

    3 = Quick Certification: If the media has been previously formatted, the defect tables shall be

    reconstructed by certifying only the Clusters that were previously declared to be defective. If

    the disc is unformatted, the format process shall only initialize the disc structures with no

    certification of the data zone.

     

    That text is copied from the MMC v6 r02c specs, page 302, table 245. The specs are available from www.t10.org

  4. What's the problem now exactly?

     

    DVD Flick should just call up ImgBurn automatically once it's done with the conversion.

     

    If you're calling it up manually and dragging over 15gb mpg files (like in your log posted above), that's where you're going wrong.

     

    The program isn't going to make up these issues. If the OS reports the file is 15gb then that's what ImgBurn reports to the user when it says the file will not fit.

     

    DVD Flick will output a set of IFO/BUP/VOB files in a VIDEO_TS folder. They're what needs to be in the 'Source' box within ImgBurn, nothing else. But again, DVD Flick should call ImgBurn with the appropriate parameters anyway so there's no chance of things going wrong - unless caused by DVD Flick itself.

×
×
  • Create New...

Important Information

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