Since you cannot get log files when the software doesn't complete a burn successfully I've resorted to screen captures. Here they are:
Of course, the software is not able to successfully close the disc and the infinite grinding loop continues until I reboot the PC.
As far as I can tell there are no errors on the disc itself. I've taken the liberty of writing .sha-1 hash files for all of the biggest files burned so I will check those. While this looks pretty bad and it's no fun having to jump through all the hoops by "attempting" to close the session and actually having to reboot the PC, the burn still seems to be okay.
I left about 1 megabyte of free space on the BD-R in the project editor window. So, I am filling these discs to capacity. I think there may be an issue somewhere in that regard. Maybe the discs I'm using are about 200 sectors shy of meeting the official BD-R requirements?
To fill my discs full, I am burning some small files in the name of redundancy.
How can I control what folders/files would literally be burned near the end of the discs where this type of failure is most likely to occur? I want to engage in this practice.
Okay, I just tested a small video file near the end of the disc. It does appear to be messed up near the end of the video. So, it looks like the files are written to disc in the order of the actual folder/file structure used to master the disc. No worries. 99% good, I'll burn the bad file to another disc. Still, what's causing this?
DVDInfoPro thinks the disc is only half full:
Edited by AlbertEinstein, 21 March 2018 - 09:53 PM.