#1 Burning Software

I've tried DVDVideoTrackAtOnceFromTree sample and was able to burn a DVD Video successfully. Starburn works fine. The burning time was less than 2 mins but "closing session..." took about 2 minutes.

I then tried larger video files and session closing took about 15-20 seconds.

Is it because of 1GB DVD padding? If so, do we have an option to turn it on/off? (I understand some players may need disc padded) I've tried StarBurn_SetDVDPadding() but to no avail.

Yes, it's b/s of the DVD padding. You may use StarBurn_GetDVDPadding and StarBurn_SetDVDPadding API calls (pretty easy ones). However some drives would burn padding in single session mode for DVD-R/-RW in any case - it's unturnable. You may experiment with your hardware.

Can you give an example of using GetDVDPadding and SetDVDPadding. I can guess at setDVDPadding but I don't see the purpose of GetDVDPadding(where is the Padding value stored?).

Nathan

Sure!

BOOLEAN l__BOOLEAN__IsEnabled = StarBurn_GetDVDPadding();

StarBurn_SetDVDPadding( TRUE ); // Enable

StarBurn_SetDVDPadding( FALSE ); // Disable

Internally and globally to whole StarBurn library.

Thanks. I actually found were you answered this early just now as well.

>>Posted: Tue Jun 14, 2005 7:34 pm Post subject:
>>
>>--------------------------------------------------------------------------------
>>
>>This one is not yet documented however both methods (to set and get >>are very easy). Here are prototypes (cut-n-paste from StarBurn.h):
>>
>>BOOLEAN StarBurn_GetDVDPadding( IN VOID );
>>
>>VOID StarBurn_SetDVDPadding( IN BOOLEAN NewDVDPadding );
>>
>>First one just retuns correct state (TRUE - enabled, FALSE - disabled) >>and second one sets it (globally, to all of the StarBurn threads).

Nathan

NP

I think my drive is forcing Padding no matter. I have Plextor 716A. I'm burning DVD+R DL and I've set SetDVDPadding(FALSE) but it still takes over 5 minutes to close the session(DVD video). Also I get no callbacks while the closing session.

Nathan

This could be. And there's are no progress for session close (lead-out write) as we don't know amount of data drive would write for sure.