Jump to content

Synchronising Cache


tvride

Recommended Posts

What is "Synchronising Cache" and why is it needed? It takes a long time to complete this function, and added to the other functions, including "verify", it makes the whole "Write Disk" operation take a seemingly very long time. If I UN-check "verify" it STILL goes through the "Synchronising Cache" function. What is "Synchronising Cache" doing?

Link to comment
Share on other sites

It's a required part of the burn.

 

Read the MMC specs if you really want to get into the technical stuff.

 

What exactly do you mean by 'a long time' anyway? 10 seconds? 1 minute? 1 hour?

 

Post a typical burn log for us to look at. Maybe we'll spot a problem.

Link to comment
Share on other sites

It's a required part of the burn.

 

Read the MMC specs if you really want to get into the technical stuff.

 

What exactly do you mean by 'a long time' anyway? 10 seconds? 1 minute? 1 hour?

 

Post a typical burn log for us to look at. Maybe we'll spot a problem.

 

Below is the log file of a typical burn with verify.

Yes, I am trying to use up some ignorantly purchased DVD-R DL disks by burning them using only the first layer (which works just fine BTW), instead of throwing them away. It does eventually work.

Although I have not actually sat down in front of my comuter while it happened and timed it, it appears to add approx 15 minutes to the whole process. In all, it takes over 50 minutes to burn a single layer disk at 4x speed. That is execcive by my experience with other burning software.

 

Tvride

 

 

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

; ImgBurn Version 2.5.5.0 - Log

; Thursday, 05 May 2011, 12:54:52

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

;

;

I 12:01:31 ImgBurn Version 2.5.5.0 started!

I 12:01:31 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)

I 12:01:31 Total Physical Memory: 16,768,096 KB - Available: 13,119,260 KB

I 12:01:31 Initialising SPTI...

I 12:01:31 Searching for SCSI / ATAPI devices...

I 12:01:31 -> Drive 1 - Info: hp BD-RE BH30L B633 (F:) (ATAPI)

I 12:01:31 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (M:) (SCSI)

I 12:01:31 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE!

W 12:01:46 User accepted disc space warning and is attempting to underburn!

I 12:01:46 Operation Started!

I 12:01:46 Source File: E:\Health\KILLER_AT_LARGE - Obesity 2008 .iso

I 12:01:46 Source File Sectors: 2,289,775 (MODE1/2048)

I 12:01:46 Source File Size: 4,689,459,200 bytes

I 12:01:46 Source File Volume Identifier: KILLER_AT_LARGE

I 12:01:46 Source File Volume Set Identifier: 4DA75CDB________KILLER_AT_LARGE

I 12:01:46 Source File Application Identifier: ELBY CLONEDVD

I 12:01:46 Source File Implementation Identifier: ELABORATE BYTES

I 12:01:46 Source File File System(s): ISO9660, UDF (1.02)

I 12:01:47 Destination Device: [0:2:0] hp BD-RE BH30L B633 (F:) (ATAPI)

I 12:01:47 Destination Media Type: DVD-R DL (Disc ID: RITEKP01) (Speeds: 2x, 4x)

I 12:01:47 Destination Media Sectors: 4,172,816

I 12:01:47 Write Mode: DVD

I 12:01:47 Write Type: DAO

I 12:01:47 Write Speed: 4x

I 12:01:47 Link Size: Auto

I 12:01:47 Lock Volume: Yes

I 12:01:47 Test Mode: No

I 12:01:47 OPC: No

I 12:01:47 BURN-Proof: Enabled

I 12:01:47 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)

W 12:01:48 Optimal L1 Data Zone Start LBA: None Found! (VTS_15)

I 12:01:48 Optimal L0 Data Zone Capacity: 2,092,896

I 12:01:48 Optimal L0 Data Zone Method: Fixed LBA

I 12:01:48 Filling Buffer... (40 MB)

I 12:01:49 Writing LeadIn...

I 12:02:21 Writing Session 1 of 1... (1 Track, LBA: 0 - 2289774)

I 12:02:21 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2289774)

I 12:02:21 Writing Layer 0... (LBA: 0 - 2092895)

I 12:15:27 Writing Layer 1... (LBA: 2092896 - 2289774)

I 12:16:54 Synchronising Cache...

I 12:29:14 Exporting Graph Data...

I 12:29:15 Graph Data File: C:\Users\Terry\AppData\Roaming\ImgBurn\Graph Data Files\hp_BD-RE_BH30L_B633_THURSDAY-MAY-05-2011_12-01_PM_RITEKP01_4x.ibg

I 12:29:15 Export Successfully Completed!

I 12:29:15 Operation Successfully Completed! - Duration: 00:27:28

I 12:29:15 Average Write Rate: 5,245 KB/s (3.8x) - Maximum Write Rate: 5,590 KB/s (4.0x)

I 12:29:15 Cycling Tray before Verify...

W 12:29:24 Waiting for device to become ready...

I 12:29:38 Device Ready!

I 12:29:40 Operation Started!

I 12:29:40 Source Device: [0:2:0] hp BD-RE BH30L B633 (F:) (ATAPI)

I 12:29:40 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: RITEKP01) (Speeds: 2x, 4x)

I 12:29:40 Image File: E:\Health\KILLER_AT_LARGE - Obesity 2008 .iso

I 12:29:40 Image File Sectors: 2,289,775 (MODE1/2048)

I 12:29:40 Image File Size: 4,689,459,200 bytes

I 12:29:40 Image File Volume Identifier: KILLER_AT_LARGE

I 12:29:40 Image File Volume Set Identifier: 4DA75CDB________KILLER_AT_LARGE

I 12:29:40 Image File Application Identifier: ELBY CLONEDVD

I 12:29:40 Image File Implementation Identifier: ELABORATE BYTES

I 12:29:40 Image File File System(s): ISO9660, UDF (1.02)

I 12:29:40 Read Speed (Data/Audio): MAX / MAX

I 12:29:40 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2289774)

I 12:29:40 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2289774)

I 12:29:40 Verifying Layer 0... (LBA: 0 - 2092895)

I 12:38:34 Verifying Layer 1... (LBA: 2092896 - 2289774)

I 12:39:10 Exporting Graph Data...

I 12:39:10 Graph Data File: C:\Users\Terry\AppData\Roaming\ImgBurn\Graph Data Files\hp_BD-RE_BH30L_B633_THURSDAY-MAY-05-2011_12-01_PM_RITEKP01_4x.ibg

I 12:39:10 Export Successfully Completed!

I 12:39:10 Operation Successfully Completed! - Duration: 00:09:30

I 12:39:10 Average Verify Rate: 8,048 KB/s (5.8x) - Maximum Verify Rate: 11,456 KB/s (8.3x)

I 12:54:52 Close Request Acknowledged

I 12:54:52 Closing Down...

I 12:54:52 Shutting down SPTI...

I 12:54:52 ImgBurn closed!

Link to comment
Share on other sites

Burn

I 12:01:47 Destination Media Type: DVD-R DL (Disc ID: RITEKP01) (Speeds: 2x, 4x)

I 12:01:47 Write Speed: 4x

I 12:29:15 Operation Successfully Completed! - Duration: 00:27:28

I 12:29:15 Average Write Rate: 5,245 KB/s (3.8x) - Maximum Write Rate: 5,590 KB/s (4.0x)

 

Verify

I 12:39:10 Operation Successfully Completed! - Duration: 00:09:30

I 12:39:10 Average Verify Rate: 8,048 KB/s (5.8x) - Maximum Verify Rate: 11,456 KB/s (8.3x)

Link to comment
Share on other sites

Yes, and around twelve minutes of "Synchronizing Cache" was included in the "Write" process. At 4x Write speed (which I always Write at}, that amounts to about fifteen minutes of actual Writing (which is normal), and about twelve minutes of "Synchronising Cache".

 

That seems absurd to me.

Again I ask: why is this needed?

 

tvride

Link to comment
Share on other sites

This looks like your issue.

 

W 12:01:46 User accepted disc space warning and is attempting to underburn!

I 12:01:46 Operation Started!

I 12:01:46 Source File: E:\Health\KILLER_AT_LARGE - Obesity 2008 .iso

I 12:01:46 Source File Sectors: 2,289,775 (MODE1/2048)

That image could have been burned on a single layer disc. Now when you have forced it onto a DL disc, there is a lot of "empty" space that needs padding at the end of the burn (so the image is laid out properly on the two layers), and that is what's taking the time.

 

by burning them using only the first layer

As in the log, the image is burnt on both layers.

 

I 12:02:21 Writing Layer 0... (LBA: 0 - 2092895)

I 12:15:27 Writing Layer 1... (LBA: 2092896 - 2289774)

Link to comment
Share on other sites

Yup, what Cynthia said is correct.

 

The 'Sync Cache' command is always sent to the drive at the end of a burn, it's what tells it that you're done sending data and that it should finish writing anything it has in its buffer.

 

Depending on the format of the media being used, the drive will also then take the opportunity to do other things it needs to do in order to complete the burn - in this case, finish writing the unused portion of the 2nd layer.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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