#1 Burning Software

Hi!
We found that SDK allocate quite much memory (175Mb) after calling StarBurn_CdvdBurnerGrabber_Create() function. I think that users of SDK based applications will be surprised by such amount of used memory. Is it a bug or a feature?

Alexander.

I think SDK users just don't read documentation for the SDK

Allocated memory are for providing background caching for CD/DVD media streaming. You can control this amount by yourself (check pointed API call help to see what to pass and what's default value).

You are right, some SDK users sometimes don't read documentation
I should remember saying "If nothing is helping you, finally, read the instruction!"

No problem

In general - more memory you allocate - better results would be. Even if modern hardware would survive after buffer underruns it's:

1) not so safe. There's quite often a counter of maximum allowed underruns. If exceeded - drive would stop burning.

2) created disc quality would be low. Less underruns (even survived) - better disc quality.

3) some combination of drive + media (single session DVD-R in "compatbile" mode for DVD-Video creation) would produce unreadable DVD-Video discs. So either buffer underrun OR correct DVD-Video. ATTENTION! DVD-R (or DVD-RW in single session) only.

So again - more memory you allocate for streaming - better results you'd have. But not more then 50% of the available RAM on the machine.