#1 Burning Software

Hi,

when a CD is inserted into a drive, drive.DriveInfo.SupportedWriteSpeeds returns 1 possible speed (the maximum as it seems), with CD-R it returns 4 possible speeds. How can I determine all 4 possible burning speeds when a CD is inserted? If 48x is known to be the maximum speed, there should be a way to determine the remaining lower speeds, shouldn't it?

Best regards,
Florian

Hello,

We should look into the Log file!

Regards,

Dmitry

There you go.

Hello,

Is the inserted disc writable CD disc?

You will get the valid values of write speed with the writable media only!! Otherwise only the maximum and current values of write speed for current device will be returned.

Regards,

Dmitry

Yeah, that's what I have said before.

So once again my question: Is it possible to determine the remaining speeds *lower* than the maximum speed? Guess? I mean if 48x is the maximum speed, why should it not allow 26x, 16x, 8x and so on?

It should allow lower speed. And does. I mean StarBurn core. So guess Dima had messed something in ActiveX wrapper.

Would be great if you could check that. Thanks

Hello,

Ok, I will check it!

Regards,

Dmitry

Hello Dima Sir,
I agree with flöle Sir. More than 1 speed value should be enumerated for the discs.

It's not blind property or something. Do you realize we need to set/get every possible speed combination and it should take time? Are you OK to replace existing sequence?

Was the last post addressed to me actually? Or what is the progress on this issue?

There's no progress as nobody provided any feedback. It was a question. I'll ask it once again.

There's no way to know supported speed list except trying all the speeds one-by-one. It takes time (set/query/report) so should we:

1) Re-work existing code. Listed speeds should be in sync with what device reports (pretty much actually).

2) Provide extended API as 1) would take time and break some software as it's time consuming operation.

?

Well, it depends. What does the current code do when it lists all speeds? Does it also check every single speed? Then just updating the code would be a proper solution, the code to detect speeds should not behave different just because a CD-ROM and not a CD-R is inserted.
If determining the speeds is more time intensive with a CD-ROM inserted, you could instead provide a method additional to a property for a list of speeds that is complete all the time. So you could have "SupportedWriteSpeeds" and "GetAllSupportedWriteSpeeds()" to provide two methods of getting the available speeds (when looking at the COM API).

Checks maximum and reports all possible thru the whole list down.

So the property SupportedWriteSpeeds already is ? In this case, I see no reason why there should be a different behaviour for CD-R and CD-ROM and no reason to not make the change. Or am I missing something?