ImgBurn is no exception to that rule when burning double-layer medias.
When the program needs to change from the 1st layer to the 2nd layer WHILE being in the process of burning a peculiar file, often a LARGE FILE, then, either the burning program will CRASH during the burning process and right at that exact moment, OR that peculiar file, which has actually been SPLIT between the 1st layer and the 2nd layer of the media during the burning process, will become unusable, like, for instance, it will become impossible to COPY that peculiar file from the media BACK on the hard disk drive of the computer (copying that peculiar file will always "fail" exactly at the moment when the process of reading that peculiar file on the media reaches the end of the 1st layer of the media), or for instance, if it's a video file, the reading of that peculiar file will stop and freeze.
The developers of "burner programs" all fail at managing that very issue.
The solution to that issue is simple though, you need to actually determine in advance WHAT IS GOING TO BE BURNED ON THE 1ST LAYER and WHAT IS GOING TO BE BURNED ON THE 2ND LAYER, EITHER by creating and using an algorithm which can automatically generate "2 SUBDIVISIONS" of a specific "COLLECTION OF FILES", each of these "2 SUBDIVISIONS" being able to be entirely contained on ONE SINGLE LAYER of a specific media, OR by leaving the manual management of these "2 SUBDIVISIONS" to the user of the program, and eventually include in the "burner program" a series of WARNINGS to prevent the user from PREPARING a SUBDIVISION which exceeds the capacity of ONE SINGLE LAYER of the double-layer media which is going to be burned.
That's all what needs to be done to finally solve that double-layer issue.
