#1 Burning Software

I have tried to burn the entire C:\Windows folder onto a DVD using a version of TrackAtOnceFromTree (release version) having all the unnecessary callback processing removed. ( only the name collision callback is processed).

The ISO9660JolietFileTree_Add function took about 12 minutes. The BuildImage function took another 6 minutes, so there are about 18 minutes of processing before the actual burning begins.

This seems too much compared with Nero which started to burn the same folder about less than 1 minute.

I would like to know if there is any way to speed up the whole process.

Many thanks,

Bern

Buy faster machine. With faster hard disk, more memory and faster CPU.

...and currently we work on new mastering engine. It's MUCH faster then current one. If you're registered StarBurn licenser you'll get it as free update. Soon. Thanks

Hello,

I haven't registered yet, but I will as soon as this problem is fixed.
Thanks for your reply. ( the second one )
bern

We don't consider it to be a big problem and it would not be "fixed" in current codebase. What you can try however - use RELEASE build of the StarBurn (instead of DEBUG) and make sure you don't do anything time consuming in the callback routine (for example - update GUI controls or write log or whatever).

...and I wonder what hardware did you use?

I have used a console application for testing, release DLL's with all the callbacks removed excepting the name collision callback ( which was called for about 10-15 files).

My hardware :
AMD Athlon XP @ 1.39 Ghz ( 1600+)
512 MB DDRAM
Maxtor IDE HDD 7200 RPM

Philips DVDR 1628

Fastest software configuration so far. Hardware could be a bit better but not dog slow in any case. I'll run some comparation tests here and would share results with you. Thanks!

OK. Windows 2003 folder (1GB in size) is completely created in 21 seconds on my machine (all callbacks enabled and progress idication and name collisions are processed). It used only around 4 seconds to drag-n-drop the files in Nero project... The problem is - StarBurn at this step has completely prepared file system and I have no clue when exactly Nero engine does wrapping of file tree it created into ISO9660/Joliet/UDF it would burn... So it's a bit difficult to compare them. At least for me.

Hello,

I have tried again the test, this time on the Windows 2003 folder, and the time was the same as before.( about 20 minutes).
If you have the time, I would like to send you my sources ( a stripped down version of TrackAtOnceFromTree). Maybe there is something I do wrong.

P.S. What is your hardware configuration?

20 minutes it's something unacceptable... How much does it take for other software? Say for Nero or whater you use? Maybe you just have antivirus software enbled? And what this 20 minutes stay for?

Tech machine Athlon64 X2 3800+ with 4GB of RAM.

Sure, send me your sources. I'll send you modified version of BuildImage so we could trace EXACT place where the code spends so much CPU cycles.

I have sent you an email to anton@rocketdivision.com
The function ISO9660JolietFileTree_Add take most of the time ~12-14 minutes. Also the BuildImage fuction takes about 6 minutes.

I am waiting for your sample.

That's *VERY* strange. There should not be *THAT* large different. While I'm busy checking your code and sending you my one would you please ask my question about other software performance on the same machine and using same file set? Thanks!

Hello,

Nero started the actual burn in 50 seconds after dragging the folder. The 50 seconds included my clicking on the burn button

There should not be THAT large difference. Did you check the profiling enabled version of BuildImage I've sent you?