Jump to content
Sign in to follow this  
gottogo99

Write speed miscompare bug?

Recommended Posts

Hello,

 

I have recently updated to version 2.5.0.0 of this fine program. I frequently use it to burn CDRWs, which are Verbatims rated for 16x-24x. Using 2.4.4.0 I was able to burn at 24x but 2.5.0.0 only burns at 16x. I have 24x set as the AWS. Logs follow in case I'm doing something wrong.

 

This log shows 24x can't be used (write speed miscompare), although 24x is one of the speed choices.

; //****************************************\\

; ImgBurn Version 2.5.0.0 - Log

; Saturday, 01 August 2009, 22:24:24

; \\****************************************//

;

;

I 22:11:48 ImgBurn Version 2.5.0.0 started!

I 22:11:48 Microsoft Windows 7 Ultimate Edition (6.1, Build 7100)

I 22:11:48 Total Physical Memory: 1,020,280 KB - Available: 496,860 KB

I 22:11:48 Initialising SPTI...

I 22:11:48 Searching for SCSI / ATAPI devices...

I 22:11:49 Found 1 DVD

Share this post


Link to post
Share on other sites

Saw a similar thread yesterday - also with CDRW discs (another burner and O/S). If you use a regular CD disc - same issue?

 

(ATAPI)

How is your burner attached? Directly to a SATA on the mother board?

Share this post


Link to post
Share on other sites

Thanks for the reply. I missed the other thread.

 

I've only made a few burns with 2.5.0.0; no CDRs or DVDRs yet.

 

I have an Intel motherboard and the SATA burner is plugged in directly. It's been that way for 20 months; never had an issue in XP or Win7 until now.

Share this post


Link to post
Share on other sites

Same problem here. Tried to burn a DVD (supported up to 16x) at 16x speed but ImgBurn only burned at 4x!?

Edited by Dstruct

Share this post


Link to post
Share on other sites

The problem also exists using Verbatim/Mitsubishi CDRs. Write speed is one level lower than desired. In this case, I wanted to burn at 32x and the program gave me 24x, even though 32x is one of the options.

 

; //****************************************\\

; ImgBurn Version 2.5.0.0 - Log

; Sunday, 02 August 2009, 21:07:03

; \\****************************************//

;

;

I 21:00:06 ImgBurn Version 2.5.0.0 started!

I 21:00:06 Microsoft Windows 7 Ultimate Edition (6.1, Build 7100)

I 21:00:06 Total Physical Memory: 1,020,280 KB - Available: 522,860 KB

I 21:00:06 Initialising SPTI...

I 21:00:06 Searching for SCSI / ATAPI devices...

I 21:00:07 Found 1 DVD

Share this post


Link to post
Share on other sites

I tested 2.5.0.0 with a DVD+R. No issues: requested 16x burn and it burned at 16x.

 

For me, the problem is only with CDRs and CDRWs.

 

Any suggestions?

Share this post


Link to post
Share on other sites

burn one in discovery mode, set the speed as required and before you click the 'Write' button, press the F8 key so it produces a Debug enabled log file. Then save the log to a file and include it with your post.

 

The disc info from the panel on the right would be useful too.

Share this post


Link to post
Share on other sites

Ok, Discovery Mode log file is attached. This is for a CDRW, wanted 24x, got 16x due to write speed miscompare.

 

Here's the disc info on the completed 16x burn.

 

TSSTcorp CD/DVDW SH-S183L SB03 (ATAPI)

Current Profile: CD-RW

 

Disc Information:

Status: Complete

Erasable: Yes

Sessions: 1

Sectors: 182,944

Size: 374,669,312 bytes

Time: 40:41:19 (MM:SS:FF)

Supported Write Speeds: 16x, 24x

 

TOC Information:

Session 1... (LBA: 0 - 182943)

-> Track 01 (Mode 1, LBA: 0 - 182943)

-> LeadOut (LBA: 182944)

 

ATIP Information:

Disc ID: 97m34s24f

Manufacturer: Mitsubishi Chemical Corp.

Start Time of LeadIn: 97m34s24f

Last Possible Start Time of LeadOut: 74m43s00f

 

Format Capacities:

DT: 0x02 - NB: 182944 (0x0002CAA0) - TDP: 2048

FT: 0x00 - NB: 275744 (0x00043520) - TDP: 2048

FT: 0x10 - NB: 275744 (0x00043520) - TDP: 32

FT: 0x24 - NB: 259360 (0x0003F520) - TDP: 0

 

Performance (Write Speed):

Descriptor 1...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 336118 (0x000520F6)

-> RS: 5,632 KB/s (32x) - WS: 2,816 KB/s (16x)

Descriptor 2...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 336118 (0x000520F6)

-> RS: 5,632 KB/s (32x) - WS: 2,816 KB/s (16x)

Descriptor 3...

-> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00

-> EL: 336118 (0x000520F6)

-> RS: 5,632 KB/s (32x) - WS: 4,224 KB/s (24x)

CDRWtest.log

Share this post


Link to post
Share on other sites

Ok so I've looked into this a little more now and to me it seems like a bug in the drives firmware.

 

Here's why....

 

First you query the drive to get the list of supported write speeds - these are what get written at the bottom of the disc info in the panel on the right.

 

I 22:29:42 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:42 CDB: AC 00 00 00 00 00 00 00 00 32 03 00

I 22:29:42 CDB Interpretation: Get Performance

I 22:29:42 BUFFER: 00 00 00 34 00 00 00 00 00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 10 80 00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 0B 00 00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 0B 00 00 00 00 00 00 00 00 00

 

Breaking that down, this is what we get:

 

00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 10 80

00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 0B 00

00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 0B 00

 

The top one is the 24x descriptor (0x00001080), the other 2 are the 16x ones (0x00000B00) - there shouldn't even be 2 identical 16x ones.

 

The 3 values from the 24x descriptor are then fed into the command that sets the speed.

 

That's: 0x000520F6 for the End LBA, 0x00001B80 for the read speed and 0x00001080 for the write speed.

 

I 22:29:43 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:43 CDB: B6 00 00 00 00 00 00 00 00 00 1C 00

I 22:29:43 CDB Interpretation: Set Streaming

I 22:29:43 BUFFER: 00 00 00 00 00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 03 E8 00 00 10 80 00 00 03 E8

 

...and then we query the drive to see what it actually set it to.

 

I 22:29:43 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:43 CDB: AC 14 00 00 00 00 00 00 00 01 00 00

I 22:29:43 CDB Interpretation: Get Performance

I 22:29:43 BUFFER: 00 00 00 14 02 00 00 00 00 00 00 00 00 00 0B 06 00 05 20 F6 00 00 0B 07

 

Notice that although I've told it 0x00001080, it's decided to change to 0x00000B07 which is the 16x ones... all be it slightly higher than the one the drive originally told me to use (0x00000B00).

 

So it would appear that the drive is reporting speed values slightly lower that it should do in the original query and they don't actually allow us to achieve the desired result - i.e. setting the speed to 24x.

 

For the real 24x is seems to want/work with 0x0000108A but not the reported 0x00001080

 

Not working:

 

I 22:29:43 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:43 CDB: B6 00 00 00 00 00 00 00 00 00 1C 00

I 22:29:43 CDB Interpretation: Set Streaming

I 22:29:43 BUFFER: 00 00 00 00 00 00 00 00 00 05 20 F6 00 00 1B 80 00 00 03 E8 00 00 10 80 00 00 03 E8

I 22:29:43 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:43 CDB: AC 14 00 00 00 00 00 00 00 01 00 00

I 22:29:43 CDB Interpretation: Get Performance

I 22:29:43 BUFFER: 00 00 00 14 02 00 00 00 00 00 00 00 00 00 0B 06 00 05 20 F6 00 00 0B 07

 

Working:

 

I 22:29:42 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:42 CDB: B6 00 00 00 00 00 00 00 00 00 1C 00

I 22:29:42 CDB Interpretation: Set Streaming

I 22:29:42 BUFFER: 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF 00 00 03 E8 00 00 10 8A 00 00 03 E8

I 22:29:42 [0:2:0] TSSTcorp CD/DVDW SH-S183L SB03 (Z:) (ATAPI)

I 22:29:42 CDB: AC 14 00 00 00 00 00 00 00 01 00 00

I 22:29:42 CDB Interpretation: Get Performance

I 22:29:42 BUFFER: 00 00 00 14 02 00 00 00 00 00 00 00 00 00 10 89 00 05 20 F6 00 00 10 8A

Share this post


Link to post
Share on other sites

Thanks for looking into this.

 

I must admit that your explanation is somewhat beyond me.

 

I'm wondering why I got the desired speed in the old 2.4.4.0 but not now. And wondering why no problems with DVDR, only CDR and CDRW.

 

Did 2.5.0.0 expose flaws in the firmware which were previously not detected? If so, can they somehow be bypassed? Firmware is the latest available.

Share this post


Link to post
Share on other sites

Yes, 2.5 exposes a firmware bug in the way it (the drive) handles setting the write speed for CD media using the 'SET STREAMING' command.

 

I'm actually away on holiday at the moment and so can't test with a physical drive for a few weeks... when I can I'll see what I can do.

Share this post


Link to post
Share on other sites
Same problem here. Tried to burn a DVD (supported up to 16x) at 16x speed but ImgBurn only burned at 4x!?

 

 

Ok, I did another burn using the same DVD-R media. This time it was burning faster than 4x. But I'm not sure if it burned at selected 16x this time!?

 

 

The logs:

 

PHILIPS DVDR1648P1 P2.4 (ATA)
Current Profile: DVD-R

Disc Information:
Status: Empty
Erasable: No
Free Sectors: 2.298.496
Free Space: 4.707.319.808 bytes
Free Time: 510:48:46 (MM:SS:FF)
Supported Write Speeds: 2,4x; 4x; 8x; 12x; 16x

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Physical Format Information (Last Recorded):
Book Type: DVD-R
Part Version: 5
Disc Size: 120mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196.608
Last Physical Sector of Data Area: 0
Last Physical Sector in Layer 0: 0

Performance (Write Speeds):
Descriptor 1...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2298495 (0x0023127F)
-> RS: 7.181 KB/s (5,3x) - WS: 3.324 KB/s (2,4x)
Descriptor 2...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2298495 (0x0023127F)
-> RS: 7.181 KB/s (5,3x) - WS: 5.540 KB/s (4x)
Descriptor 3...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2298495 (0x0023127F)
-> RS: 7.181 KB/s (5,3x) - WS: 11.080 KB/s (8x)
Descriptor 4...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2298495 (0x0023127F)
-> RS: 7.181 KB/s (5,3x) - WS: 16.620 KB/s (12x)
Descriptor 5...
-> B0: 0x00; B1: 0x00; B2: 0x00; B3: 0x00
-> EL: 2298495 (0x0023127F)
-> RS: 7.181 KB/s (5,3x) - WS: 22.160 KB/s (16x)

 

I 22:55:34 ImgBurn Version 2.5.0.0 started!

I 22:55:34 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)

I 22:55:34 Total Physical Memory: 1.570.540 KB - Available: 1.245.056 KB

I 22:55:34 Initialising SPTI...

I 22:55:34 Searching for SCSI / ATAPI devices...

I 22:55:34 Found 1 DVD-ROM and 1 DVD

Share this post


Link to post
Share on other sites
I 22:57:08 Operation Started!

I 22:57:08 Source File: -==/\/[bUILD IMAGE]\/\==-

I 22:57:08 Source File Sectors: 664.512 (MODE1/2048)

I 22:57:08 Source File Size: 1.360.920.576 bytes

I 22:57:08 Source File Volume Identifier: Test

I 22:57:08 Source File Application Identifier: ImgBurn v2.5.0.0 - The Ultimate Image Burner!

I 22:57:08 Source File Implementation Identifier: ImgBurn

I 22:57:08 Source File File System(s): ISO9660; Joliet; UDF (1.02)

I 22:57:08 Destination Device: [0:1:0] PHILIPS DVDR1648P1 P2.4 (E:) (ATA)

I 22:57:08 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 2,4x; 4x; 8x; 12x; 16x)

I 22:57:08 Destination Media Sectors: 2.298.496

I 22:57:08 Write Mode: DVD

I 22:57:08 Write Type: DAO

I 22:57:08 Write Speed: 16x

I 22:57:08 Link Size: Auto

I 22:57:08 Lock Volume: Yes

I 22:57:08 Test Mode: No

I 22:57:08 OPC: No

I 22:57:08 BURN-Proof: Enabled

I 23:00:13 Average Write Rate: 10.302 KB/s (7.4x) - Maximum Write Rate: 14.015 KB/s (10.1x)

You did select 16x and it was burning at 16x but didn't reach that speed because you were burning too little data.

Share this post


Link to post
Share on other sites
Same problem here. Tried to burn a DVD (supported up to 16x) at 16x speed but ImgBurn only burned at 4x!?

Ok, I did another burn using the same DVD-R media. This time it was burning faster than 4x. But I'm not sure if it burned at selected 16x this time!?

 

 

IMHO your problem in this burn is another one.

 

I 22:57:08 Source File Sectors: 664.512 (MODE1/2048)

I 22:57:08 Destination Media Sectors: 2.298.496

I 22:57:08 Write Speed: 16x

I 23:00:13 Operation Successfully Completed! - Duration: 00:03:04

I 23:00:13 Average Write Rate: 10.302 KB/s (7.4x) - Maximum Write Rate: 14.015 KB/s (10.1x)

Your source material is to tiny to make the burner go up to the max speed (16x). Normally it's only the last 20% of the burn of a full disc that reaches those speeds.

 

Do this test to find out if you can get up to 16x:

 

Use the Discovery mode

Select 'All Sectors'

The the burn speed to 'MAX' or 16x (should be equal results)

 

If you enable 'Auto export Graph Data' in the settings Write tab - you could look how the burn speed is over the total burn time - you can use BurnPlot (It's on the www.imgburn.com download page) to show it.

 

Edit: mmalves did the short version...

Share this post


Link to post
Share on other sites

I 22:57:08 Destination Device: [0:1:0] PHILIPS DVDR1648P1 P2.4 (E:) (ATA)

I 22:57:08 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 2,4x; 4x; 8x; 12x; 16x)

I 22:57:08 Destination Media Sectors: 2.298.496

I 22:57:08 Write Mode: DVD

I 22:57:08 Write Type: DAO

I 22:57:08 Write Speed: 16x

Ok, this is looking good I think. Last time ImgBurn said "Write Speed: 4x" even when 16x was selected. Strange ...

 

 

 

 

Do this test to find out if you can get up to 16x:

 

Use the Discovery mode

Select 'All Sectors'

The the burn speed to 'MAX' or 16x (should be equal results)

 

Not needed anymore. As written above: Last time ImgBurn said "Write Speed: 4x" even when 16x was selected. Strange ...

Edited by Dstruct

Share this post


Link to post
Share on other sites
Yes, 2.5 exposes a firmware bug in the way it (the drive) handles setting the write speed for CD media using the 'SET STREAMING' command.

 

I'm actually away on holiday at the moment and so can't test with a physical drive for a few weeks... when I can I'll see what I can do.

Thanks. Get around to it when you can. It's an issue, but not a huge one. Maybe you'd rather not work around a "bug" that's not your fault.

Share this post


Link to post
Share on other sites

Any progress on this issue for the next release?

 

In case anyone is interested, my workaround is to set the write speed one setting higher than what I actually want for burning CDRs. For example, if I want to burn at 48x, set the write speed to 52x. Obviously, the highest speed is not possible.

 

Anyone know if this issue has been fixed for newer Samsung drives? Does it affect other brands as well?

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.