ckhouston

OK I think I finally get it. 2038860 is not half the data to be written as I thought, it is just the maximum sector where a cell can start and satisfy all requirements for a layer break. The data to be written is what LIGHTNING_UK! shows as image_size which is larger than I thought. Thanks for your patence, I'm better able to help with these problems in the ConvertXtoDVD forum. I will encourage them to ask their questions here for most questions from now on.

Sorry for the delayed reply, had an emergency. The log I presented was posted by a user on the CovertXtoDVD forum. He took some advice from me and was able to get a good burn but had to reconvert his project, so the old one is no longer available. I can ask him to reproduce the old project if you want.

Thanks again, I know your time is limited. I'm still confused though. Even accounting for the data pushed into L1 if the LB is at the start of Cell 10, the amount of data to be written to L1 is 2058274 sectors which is less than the 2058288 on L0, unless I'm missing something.

Thanks for replying. I am the curious sort that likes to understand how things work. And, from what I think I know about setting layer breaks, it looks to me that sector 2058288 would work for that project. Since Cell 10 starts at absolute sector 1423391 + 596055 = 2019446, 2058288 - 2019446 = 38842 padding would be needed. That leaves 2038860 + (2038860 - 2019446) = 2058274 sectors to be written to the second layer which is less than the 2058288 available. I must be missing something, maybe some data overhead that must be on L1, but adding even more padding can provide a little more space on L1. I will keep reading to learn more.

Can someone explain from the following log why a valid layer break point was not found? Based on the available window of sectors 2038860 and 2086912 and the criteria that break points must be at the start of a cell and the start of a ECC block (divisible by 16), why are there not several potential break points between sectors 2038864 and 2086912 with the use of padding? Does ImgBurn use some other critera other than those to determine break points?