Loading a disc reads its ID. That proves to the burning software that
the disc will be identified when loaded. Some drives are broken in that
ejecting a disc and inserting another one still shows the old disc in
the drive. Change detection fails. The eject and reinsert validates
change detection is working on the drive; else, you could go to burn
another disc but it still looks like the prior one was still in the
tray. It also forces flushing of buffers (see article below).
It may also be overlapping code for a batch operation: you're copying
the same image to multiple discs. The software has to know when you've
inserted the next [blank] disc.
http://forum.imgburn.com/index.php?/topic/6232-the-imgburn-settings/?hl=%2Beject#entry125884
Search on "Cycle Tray Before Verify". So you could disable the eject
before verify action but that is not recommended. PCs with optical
drives really are not burning stations. You should stick around when
burning a disc on your PC. You can preload a bunch of discs and leave
for unattended operation for a burning station (they're made for
automatic disc change and multiple burn jobs). The PC software will
encounter buffers in the OS and the drive that need to be flushed. The
burning stations probably have buffers but their logic takes care of it.
You have an optical drive that can eject and reinsert the tray. That
won't work on optical drives that have no motor to inject, like the
slimline drives in laptops: the tray ejects but the user ALWAYS has to
push the tray back in. So you must be there to push the tray back in to
do the verify. Not ejecting means there's no guarantee that memory
buffers or even temp files got flushed.