#1 Burning Software

Hello Support,

1) I am using ImageBurner to burn an ISO image to disc.
2) While burn process is in going on we are getting OnProgress(...,...) event.
3) Many times this event reports same percent. Example, 3 times I am getting percent burned 41. Which is of no use to me. As I cannot update burn progress from 41 to anything else.
4) This unwanted event raising I think may affect overall time required for burn.
5) This can be avoided, by using one normal int32 variable. New progress has to be compared with previously reported progress stored in in32 variable.
6) Can this be implemented? I think this will help you.

Hello,

Already done ... many thanx!!

Dmitry

Hello Sir,

I checked this in dlls I have. Not updated in these dlls.
Will you please kindly check with those.

Thank you in advance.

Hello,

We have fixed this problem in sources We plan to upload new build of StarBurnX on Wednesday!

Regards,

Dmitry

Any New?
Will you please kindly provide me help for newly added functions so that I can use those in my applications and update all the newly added functionality in my application. Due to lack of help topics available to me I cannot use newly added changes in DiscInfo Class.

Thank you in advance.

Hello,

No:( the build is not ready

We apologize for delay

Dmitry

Hello Dima Sir,

I am using latest build. This problem is not solved.
Thank you.

Hello,

It's strange! Be aware that version of StarBurnX was changed ... so you should change reference on StarBurnX for your application from RocketDisivion.StarBurnX.10 to RocketDisivion.StarBurnX.12!!!

Perhaps you are testing old version of StarBurnX?

P.s. in any case we will test it today.

Regards,

Dmitry

Hello Dima Sir,

1) First of all thank you for your attention. I observed that the reported problem is solved but only for burn progress value.
2) Still the problem is there for used buffer value.
3) Even while verifying data repeated progress values are reported.
4) One more thing, for burning a ISO image of data around 3.5 GB it took 14 minutes & for verification of the data it took 15 minutes.
I think for verification of data it should take less time.
5) Problem can be simulated in normal case for any image burning with verification.

I have readings from studio for image file burning in Samples provided with SDK V12 as follows,
14 min were required for burning & 15 min for verification.

Release mode custom log:
DoBurn Started : 18:20:40
DoBurn Completed : 18:34:56
DoVerifyData Started : 18:34:56
DoVerifyData Completed : 18:49:05


Thank you Sir.

Hello,

Thank you very much!! We will fix it ASAP!!

Regards,

Dmitry!!