Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Yesterday
  3. dbminter

    Four 50gb BD-Rs down the drain with LG BU40N

    I wasted about half of my first stack of BD-R DL's testing them out. The most common issue was failure to Verify at the layer change, although I also got random failures like burning before the layer change in Layer 0 and a random lockup at near completion of a Verify. What I did learn was never to use the VanTec Gen 1 or OWC USB enclosures, e.g use the VanTec Gen 2 USB enclsoure, to burn at 2x, and use the WH16NS60 as opposed to the ASUS BH-16.
  4. AbsoluteMan

    Four 50gb BD-Rs down the drain with LG BU40N

    I will try that, thank you. After 7 discs that all crashed out early on in their burns, I've just spent the last four hours hoping and praying. BurnAware, after changing the cache to 2048mb, seemingly burnt through an entire disc. Unfortunately, it failed the verification process and does not play in my Xbox One S. Here's the log: Disc #1 of 1 [19:34:10] Preparing compilation [19:34:10] Anti-sleep mode activated [19:34:10] OPC activated [19:34:49] 41.33 GB [19:34:49] Burn process started [23:41:37] Closing track [23:42:59] Burn process completed successfully [23:43:00] Verify process started [23:43:00] Verify process failed Total time: 04:08:47 Average write speed: 0.7x (2938 KB/s) So looks like the drive is capable of writing onto both layers, but yeah sadly not a legible disc. I will try the hardware error fix you outlined above and get back to you
  5. zurst

    Blu-ray burners are disappearing

    We live in dark times, and the faint light that remains grows dimmer with each passing day. People have lost interest in preserving information, sacrificing it for the convenience of streaming services and cloud storage. For quite some time now, I have watched with dismay as PC cases have stopped being designed to accommodate optical drives. What concerns me even more is that there are now very few Blu-ray burners available. The options are scarce, of poor quality, and expensive. To me, this is a symptom of society's decline. People no longer value information and knowledge the way they once did, and it also represents a loss of freedom. Respected technology brands such as ASUS, LG, Pioneer, and others, which once produced outstanding optical drives and Blu-ray burners, have all but disappeared from the market. What worries me most is this growing indifference, and especially the prospect of losing access to my collection simply because the optical drives needed to read those discs are disappearing. It is both sad and absurd. Yet that seems to be the direction things are heading. Blu-ray always felt like such an established format that I never imagined its future could be called into question. I should also add that I do not trust hard drives, SSDs, USB flash drives, or memory cards to the same extent. If there is a storage medium that has proven to be truly durable, it is the optical disc—especially high-quality Blu-ray discs. Sadly, they are now on the verge of extinction because almost nobody values them anymore.
  6. dbminter

    Four 50gb BD-Rs down the drain with LG BU40N

    You could try using the Hardware error correction and formatting with spare areas if you wish. See this thread here for more details:
  7. dbminter

    Four 50gb BD-Rs down the drain with LG BU40N

    As you pointed out, it's probably an incompatibility in the firmware with your LG burner and those Ritek DID's. The only thing I can recommend at this point is that you try Verbatim DataLife Plus BD-R DL. However, they're about twice the price of the Riteks, but if they're the only thing that work in that LG, at least it's an option. I've never used that particular LG BD burner, just the WH14NS40, WH16NS40, and the WH16NS60. The 16 NS40 is not recommended unless you don't mind the fact that it can't properly read CD's in ImgBurn. And, well, both the 16 NS40 and NS60 aren't manufactured anymore. In fact, the only BD drive I know that is still manufactured by a major company is ASUS's USB BH-16 model. I've tried the internal BH-16, but ImgBurn didn't produce regular positive results with that in my testing, even at 2x.
  8. AbsoluteMan

    Four 50gb BD-Rs down the drain with LG BU40N

    Tried Burnaware. Actually did a pretty good job writing the first half of the disc, but then crashed when it went to the next layer. At my wits end.
  9. dbminter

    Four 50gb BD-Rs down the drain with LG BU40N

    That error code is Windows's infamous "I don't know what the Hell went wrong" return code. It's "Unspecified Error."
  10. AbsoluteMan

    Four 50gb BD-Rs down the drain with LG BU40N

    Tried the isoburn.exe route and it spat the disc out. Gave me error code 0x80004005. Tried it a second time and it ran really quickly considering its a 40+gb ISO, then jumped to finalizing disc. Then it threw error up again saying: 'The disc image didn't burn successfully because an error occurred. Same error. 0x80004005 I'm not sure what the matter is with this drive. It can rip blu-rays but can't seem to write. It can't even erase a rewriteable from a company called BRTech.
  11. dbminter

    Four 50gb BD-Rs down the drain with LG BU40N

    You might want to invest in trying one more BD-R DL test. It involves using Windows's built in disc image burner. It may work where ImgBurn keeps failing. See this thread:
  12. Forrker

    burning

    waoo, I know that
  13. Having a very sad start to the weekend. Not managing to write an ISO to a 50gb BD-R. They are RITEK-DR3-000 BD-R DL 50GB (Inkjet Printable, 1-6x rated) Drive: HL-DT-ST BD-RE BU40N Firmwares Tested: 1.03 (stock), 1.00 (downgraded) Software: ImgBurn 2.5.8.0 Settings Tested: Write Speeds: 1x (rejected), 2x, 4x, 6x OPC: On/Off BURN-Proof: Enabled Lock Volume: On/Off Link Size: 0 (default) Write Type: DAO/SAO Best Result: Firmware 1.00 with OPC enabled at 2x reached 54% before layer break failure. Conclusion: RITEK-DR3-000 is incompatible with LG BU40N at firmware level. Drive cannot calculate correct sector addressing for layer transition on this media. Anyone have any advice for me?
  14. Last week
  15. How do you enable Verify? This thing only works via the command line. The option to Burn disc image is not available on my system on Windows 11, even under Show more options. The entire command line is ISOBURN.EXE /Q "D:" "C:\Image.iso" without the quotes around D:. They are only present here because without the quotes, it becomes 😧 on these forums. Never mind. I figured it out. The /Q option opens the window, but automatically starts the burn apparently. If you just run ISOBURN.EXE E: "C:\Image.iso" it opens the main interface where you can select Verify image.
  16. Try this with dummy data at the layer break. Devloped by teaching-droid. I was the beta tester und found some bugs. Now it works just fine and stable. https://mega.nz/folder/7IR2kZhD#S8_Ld_MXOZFbRZbewdYHOw
  17. My isoburner.exe has a selection for the drive and a check box for verification, this is what pops up after run: I think I can chalk this up to some weird dual layer burning quirk with imgburn- I may try another utility too to see what happens because for certain images Windows rejects the burn if they are extremely close to the full BD-R DL capacity, even though ImgBurn says they technically fit... Luckily whatever error I am running into with the disks I burned using imgburn that I saw during verification, doesnt seem to affect playback. This weekend I'll watch one entirely through to double check.
  18. This reminded me of another issue with double layer BD burning. Some years ago, it was determined that ImgBurn would fail more often than not writing BD-RE DL on the LG WH16NS40, yet when you used Roxio's burning engine, it would succeed all the time. At least, that's my memory of the situation. It was odd results back then, too, but I played around with it and it did seem to bear out that it worked with Roxio's burning software but not as well with ImgBurn.
  19. I found isoburn.exe on my Windows partition. It is apparently a command line driven utility. I can also try the context menu to see if that works. Does it have settings where you can set the write speed or does it just use the maximum speed allowed by the drive? And I guess it automatically verifies because the only command line switch I see is /q which apparently opens the isoburn program window. Which may have settings available there. Anyway, it's something I can play around with later.
  20. I launch Windows Disc image burner with: Press Win + R. Run: isoburn.exe "C:\path\to\image.iso" I think you can also right-click the ISO and select 'burn disc image' I should clarify though that the ISO I burned with Windows was not created by imgburn- It was an existing Blu-ray ISO from another source. Though I did originally create an ISO from a blu ray disc I already had in order to test the drives full dual layer read functionality to make sure it wasnt broken, I did use makemkv and imgburn for that.
  21. How exactly can one burn an ISO image file created by ImgBurn with the Windows burning engine you used? It's something I could maybe play around with, too.
  22. Thanks. I agree the result is strange, but it now looks very consistent. I also completed another controlled ImgBurn burn at 2x. It failed verification again at the same point: Verifying Layer 1... Failed to Read Sectors 12219424 - 12219455 Reason: L-EC Uncorrectable Error So both 2x and 4x ImgBurn burns fail immediately after the layer change. The Windows-burned disc: completed Windows verification successfully then passed a manual ImgBurn verification against the original ISO crossed the layer transition with no read errors I’ll still play the entire Windows-burned disc in a standalone player to rule out playback freezes that verification may not reveal. I have not watched an entire full-length film fully through, so Ill make sure to do that ... Appreciate the help 👍
  23. It does seem that Windows built in burning engine is different that ImgBurn's. Of course, ImgBurn is just sending standard operational commands to drives. So, WHY it should make a difference is a bit odd. However, you can't really argue with results. Of course, there's no sure fire result until you play the entire contents of the Windows burned BD-R DL in a standalone Blu-Ray player. Some of my 4x tests passed Write and Verify, but they apparently weren't written correctly, causing freezes on playback at certain points. Reburning those discs at 2x played fine.
  24. Thank you for the reply! I manually verified the Windows-burned disc in ImgBurn against the original ISO, and it completed successfully: Verifying Layer 0... LBA: 0 - 12219391 Verifying Layer 1... LBA: 12219392 - 16002559 Operation Successfully Completed I’ll run another controlled ImgBurn burn at exactly 2x and report the full log. I previously selected 3x on one attempt, but the drive fell back to 2x and that disc still failed at the layer transition. I’ll repeat it deliberately at 2x with the current Vantec enclosure and no other disc software running.
  25. I am curious to follow up on your suggestion that it could be ImgBurn's writing process that is faulty, and it's always possible. Since the built in Windows burning and verifying engine seems successful, I would be interested to see a manual Verify operation performed on one of these Windows burned BD-R DL's. See if it fails around the layer change. If it does, then the issue isn't the ImgBurn writing engine, since ImgBurn didn't write the disc, Windows did, but apparently ImgBurn's reading engine. As for known issues with ImgBurn and the layer change with BD-R DL, it's a known issue that many users report with BD-R DL's, regarding the circumstances. It seems that for the most part BD-R DL just isn't very reliable, regardless of hardware. See my other testing thread for possible enabling Hardware error correction and other settings. For instance, my best experience has been with Verbatim DataLife Plus BD-R DL and Ritek's in an LG WH16NS60 in the same VanTec enclosure you're using with ImgBurn burning at 2x only.
  26. Hello, I’m having a repeatable problem burning Verbatim BD-R DL discs with ImgBurn. The burn completes successfully, but verification fails immediately after the layer transition. Hardware and media Pioneer BDR-206DBK Firmware: 1.56 Drive label says manufactured March 2024 Vantec NexStar DX2 USB 3.0 optical-drive enclosure Verbatim 50 GB BD-R DL, rated 8x Media ID: VERBAT-IMf-000 Windows 11 ImgBurn failure I have tried: Multiple brand-new discs from the same spindle Multiple unrelated Blu-ray 3D ISOs 2x and 4x write speeds A generic powered SATA-to-USB adapter The Vantec enclosure specifically designed for 5.25-inch optical drives Different USB ports The burn itself completes and finalizes normally. Verification consistently fails at or just after the start of layer 1: Verifying Layer 0... LBA: 0 - 12219391 Verifying Layer 1... LBA: 12219392 - ... Failed to Read Sectors 12219424 - 12219455 Reason: L-EC Uncorrectable Error Other attempts failed around: LBA 12219456 So the failure is always within the first few sectors of the second layer. Some of the failed-verification discs appear to play through the entire movie normally, although one separate PowerISO attempt failed during writing and produced an unusable second layer. Important new result I burned another BD-R DL ISO using the built-in Windows Disc Image Burner, with: The same Pioneer drive The same Vantec enclosure The same Verbatim spindle The same computer and USB setup Windows completed both the burn and its full verification successfully. That suggests the drive, enclosure, and media can produce a valid BD-R DL, but ImgBurn’s write process consistently creates unreadable sectors at the layer transition. The Pioneer also successfully backed up an entire pressed dual-layer Blu-ray using MakeMKV without any read errors. Questions Is there any known ImgBurn-specific issue involving: Pioneer BDR-206 drives VERBAT-IMf-000 media BD-R DL layer transitions SPTI versus Windows IMAPI OPC or another advanced ImgBurn setting USB optical-drive enclosures I understand ImgBurn should theoretically be sending standard commands and that there should not be a major difference between burning an ISO with ImgBurn and Windows. However, the result is currently repeatable: ImgBurn fails at the layer break, while Windows burns and verifies successfully. What logs or settings would be most useful to post for comparing the successful Windows burn against the failed ImgBurn burns?
  27. dbminter

    Setting Write speeds by MID

    Is the database of DID's and Write Speeds associated with them stored in the Registry or locally?
  28. Earlier
  1. Load more activity
×
×
  • Create New...

Important Information

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