[Libburn] Re: Cancelling an ongoing burn. Is this dangerous ?

[Derek Foreman]

On Thu, 9 Feb 2006, scdbackup at gmx.net wrote:

> Hi,
>
>>>   if(d->cancel)
>>>     return;
>>
>> This looks ok to me.
>>
>> You'll probably want to add one of those ifs to the loop in
>> burn_write_leadout too.  That should cut down on the pause by a bit.
>
> Hm ... no, it didn't.

Ah well.  I figured some of the time was the drive writing lead-out. 
Guess it wasn't getting there after all.

> I inserted  return; or  break; but the abort waiting
> time was still 12, 13, and 13 seconds in three tests.
> Abort was done after the first few MB had been written.
>
> I inserted a fprintf(stderr,) and found out that
> the function is not reached if i abort during
> burn_write_track() .
>
> ... it actually is never reached even if the burn
> is allowed to complete without any disturbance.

Ah, I think you're burning in SAO mode then?

> My burn procedure is still quite the same as in
> test/burniso.c .
> Did i miss a call which enables lead-out ?

Nope, I think only DAO has to explicitly write the lead-out.