close snippet is not in any way different from what growisofs does at the end. It's simply executed after some time, when unit most likely has cooled down. So that yes, it can as well be environmental problem... In other words I don't think it's application software problem, but rather hardware. A.it would be good explanation if not the fact that it started _exactly_ when i upgraded from 5.17 and that close works _every time_.
There were no changes in code path executed at the end of recording between 5.17 and 5.21... Well, there were minor changes to accomodate DVD+R DL, but they're not taken in your case.
i'll downgrade to 5.17 and run few more tests both with LITE-ON and ASUS to see if the problem still exists or disappears.
Please do.
what do u mean by 'environmental problem'? system environment (installed software, other hardware and so on) or things such as air temperature (don't laugh at this - i'm asking because u said that session closing procedure is started with delay to let drive get cooler :) )
The latter, but rather temperature in the unit itself, then one outside computer. Unlike CLOSE TRACK/SESSION executed by growisofs instantly after last data block is recorded without spinning down, close is executed even after media reload, right? A.