Graph data not written automatically

[mumdigau]

Hi,

 

When using 'Write files/folders to disk' the graph data file isn't written automatically even though the option 'Capture Graph Data' is checked. DVDInfoPro is selected as Default Viewer with location 'Documents and Settings\...\Application Data\ImgBurn, but I have to export the ibg-file manually under File | Export Graph Data to get it written to disk. It's the actual version of ImgBurn. I remember that in earlier versions this has been done automatically.

 

Additional remark: It takes more than 3 min(!) before ImgBurn starts building and writing the image. The status line shows 'Creating Graph Data Thread...'. Is this normal behaviour?

 

Best regards

 

mumdigau

Edited January 29, 2010 by mumdigau

[LIGHTNING UK!]

Look in the log file, what does it say? Normally it will say it's exporting it at the end of the operation.

 

No it's not normal for it to take that long to make the thread, it should take a fraction of a second.

 

You need the 'Auto 'Export Graph Data'' option enabled under the Write tab (in the Settings) for it to automatically export the data to a file - and that is normally checked by default.

[mumdigau]

Thanks for your quick reply.

 

 

You need the 'Auto 'Export Graph Data'' option enabled under the Write tab (in the Settings) for it to automatically export the data to a file - and that is normally checked by default.

 

This option was disabled. When checked the ibg-file is written automatically. Thanks.

 

Concerning the long time for 'Creating Data Graph Thread...' please have a look at the logfile:

 

I 13:55:29 Operation Started!
I 13:55:29 Source File: -==/\/[bUILD IMAGE]\/\==-
I 13:55:29 Source File Sectors: 2.129.984 (MODE1/2048)
I 13:55:29 Source File Size: 4.362.207.232 bytes
I 13:55:29 Source File Volume Identifier: 0097DVDV
I 13:55:29 Source File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER!
I 13:55:29 Source File Implementation Identifier: ImgBurn
I 13:55:29 Source File File System(s): ISO9660; UDF (1.02)
I 13:55:29 Destination Device: [4:0:0] BENQ DVD LS DW1655 BCGB (D:) (RAID)
I 13:55:29 Destination Media Type: DVD+RW (Disc ID: RITEK-004-48) (Speeds: 2,4x; 4x)
I 13:55:29 Destination Media Sectors: 2.295.104
I 13:55:29 Write Mode: DVD
I 13:55:29 Write Type: DAO
I 13:55:29 Write Speed: MAX
I 13:55:29 Link Size: Auto
I 13:55:29 Lock Volume: Yes
I 13:55:29 Test Mode: No
I 13:55:29 OPC: No
I 13:55:29 BURN-Proof: Enabled
I 13:55:29 Book Type Setting: DVD-ROM
I 13:55:29 Advanced Settings - OverSpeed: No, Solid Burn (K/U): Yes / Yes, WOPC: Yes
I 13:58:36 Filling Buffer... (40 MB)
I 13:58:38 Writing LeadIn...
[/Code]

 

Same happens when I try to write an image file to disc. Any idea?

 

Best regards

 

mumdigau

[mmalves]

(unrelated to your delay problem)

I 13:55:29 Destination Device: [4:0:0] BENQ DVD LS DW1655 BCGB (D:) (RAID)

There's newer firmware available for your burner (remove any disc and close the tray before updating then reboot after it's finished).

[Cynthia]

but I have to export the ibg-file manually under File | Export Graph Data to get it written to disk.

When you did this, did it also take a very long time for the file to be written to the hard disk?

[LIGHTNING UK!]

There is actually some debugging code in the program that could help work out exactly which bit of that 'Creating Graph Data Thread' function your machine it taking ages to process.

[mumdigau]

(unrelated to your delay problem)

There's newer firmware available for your burner (remove any disc and close the tray before updating then reboot after it's finished).

I know, but I get better burning results with BCGB than with BCHB or BCIB.

 

mumdigau

[mumdigau]

but I have to export the ibg-file manually under File | Export Graph Data to get it written to disk.

When you did this, did it also take a very long time for the file to be written to the hard disk?

No, immediately.

 

mumdigau

[mumdigau]

There is actually some debugging code in the program that could help work out exactly which bit of that 'Creating Graph Data Thread' function your machine it taking ages to process.

 

How do I activate this debugging code?

 

mumdigau

[Cynthia]

Beats me how it's activated. Can't see any extra rows in the log. Unless it shows up in the program info area.

 

The path you save it to in the settings - does it exist? I know some other programs can hang for some minutes if the path is not existing any longer.

[LIGHTNING UK!]

The debugging stuff is actually only visible when the program has to get a 'localised' name for the performance counter.

 

Otherwise, it should all be very straight forward.

 

Does the data you eventually end up with include everything it's supposed to?

 

I assume you're using XP yeah? Is it SP3?

[Cynthia]

The debugging stuff is actually only visible when the program has to get a 'localised' name for the performance counter.

Aha. It's this:

 

D 17:23:58 GetLocalisedPdhName(Processor) - RegQueryValueEx BufferSize: 131 072

D 17:23:58 GetLocalisedPdhName(Processor) - CounterIndex: 238

D 17:23:58 GetLocalisedPdhName(Processor) - PdhLookupPerfNameByIndex BufferSize: 2 048

D 17:23:58 GetLocalisedPdhName(Processor) - LocalisedName: Processor

D 17:23:58 GetLocalisedPdhName(% Processor Time) - RegQueryValueEx BufferSize: 131 072

D 17:23:58 GetLocalisedPdhName(% Processor Time) - CounterIndex: 6

D 17:23:58 GetLocalisedPdhName(% Processor Time) - PdhLookupPerfNameByIndex BufferSize: 2 048

D 17:23:58 GetLocalisedPdhName(% Processor Time) - LocalisedName: % processortid

[LIGHTNING UK!]

Aye, that be the stuff

 

You really just have to take note of the times and perhaps one bit will appear to be taking ages.

 

As all yours are '17:23:58', you clearly don't have any issue there.

[mumdigau]

Here a debug log of writing files/folders to disc:

 

I 18:06:37 ImgBurn Version 2.5.0.0 started!
I 18:06:37 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)
I 18:06:37 Total Physical Memory: 3.406.820 KB  -  Available: 2.298.112 KB
W 18:06:37 Drive C:\ (FAT32) does not support single files > 4 GB in size.
W 18:06:37 SPTD can have a detrimental effect on drive performance.
I 18:06:37 Initialising SPTI...
I 18:06:37 Searching for SCSI / ATAPI devices...
I 18:06:37 Found 1 DVD±RW and 1 BD-ROM/HD DVD-ROM!
I 18:07:51 Project Loaded Successfully!
I 18:07:51 File Name: X:\Software\TMPGEncXpress\Alpha Centauri\0098DVDV\ImgBurn\AphaCentauri.ibb
W 18:08:35 Program 'Debug Mode' has been Enabled!
I 18:08:41 Operation Started!
I 18:08:41 Building Image Tree...
I 18:08:41 Checking Directory Depth...
I 18:08:41 Calculating Totals...
I 18:08:41 Preparing Image...
D 18:08:41 GenerateFileLBA_DVDVideo - Image size < DVD+R size
I 18:08:41 Checking Path Length...
I 18:08:41 Contents: 44 Files, 10 Folders
I 18:08:41 Content Type: DVD Video
I 18:08:41 Data Type: MODE1/2048
I 18:08:41 File System(s): ISO9660, UDF (1.02)
I 18:08:41 Volume Label: 0098DVDV
I 18:08:41 IFO/BUP 32K Padding: Enabled
I 18:08:41 Region Code: 1; 2; 3; 4; 5; 6
I 18:08:41 TV System: PAL
I 18:08:41 Size: 4.346.186.926 bytes
I 18:08:41 Sectors: 2.122.175
I 18:08:41 Image Size: 4.346.937.344 bytes
I 18:08:41 Image Sectors: 2.122.528
I 18:08:43 Operation Successfully Completed! - Duration: 00:00:02
I 18:08:43 Operation Started!
I 18:08:43 Source File: -==/\/[bUILD IMAGE]\/\==-
I 18:08:43 Source File Sectors: 2.122.528 (MODE1/2048)
I 18:08:43 Source File Size: 4.346.937.344 bytes
I 18:08:43 Source File Volume Identifier: 0098DVDV
I 18:08:43 Source File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER!
I 18:08:43 Source File Implementation Identifier: ImgBurn
I 18:08:43 Source File File System(s): ISO9660; UDF (1.02)
I 18:08:43 Destination Device: [4:0:0] BENQ DVD LS DW1655 BCGB (D:) (RAID)
I 18:08:43 Destination Media Type: DVD+RW (Disc ID: RITEK-004-48) (Speeds: 2,4x; 4x)
I 18:08:43 Destination Media Sectors: 2.295.104
I 18:08:43 Write Mode: DVD
I 18:08:43 Write Type: DAO
I 18:08:43 Write Speed: MAX
I 18:08:43 Link Size: Auto
I 18:08:43 Lock Volume: Yes
I 18:08:43 Test Mode: No
I 18:08:43 OPC: No
I 18:08:43 BURN-Proof: Enabled
D 18:08:43 DeviceIoControl(IOCTL_CDROM_EXCLUSIVE_ACCESS, Unlock) Failed! - Reason: Unzulässige Funktion.
D 18:08:43 DeviceIoControl(IOCTL_CDROM_EXCLUSIVE_ACCESS, Lock, 1) Succeeded!
I 18:08:43 Book Type Setting: DVD-ROM
I 18:08:43 Advanced Settings - OverSpeed: No, Solid Burn (K/U): Yes / Yes, WOPC: Yes
D 18:11:28 GetLocalisedPdhName(Processor) - RegQueryValueEx BufferSize: 65.536
D 18:11:28 GetLocalisedPdhName(Processor) - CounterIndex: 238
D 18:11:28 GetLocalisedPdhName(Processor) - PdhLookupPerfNameByIndex BufferSize: 2.048
D 18:11:28 GetLocalisedPdhName(Processor) - LocalisedName: Prozessor
D 18:11:28 GetLocalisedPdhName(% Processor Time) - RegQueryValueEx BufferSize: 65.536
D 18:11:28 GetLocalisedPdhName(% Processor Time) - CounterIndex: 6
D 18:11:28 GetLocalisedPdhName(% Processor Time) - PdhLookupPerfNameByIndex BufferSize: 2.048
D 18:11:28 GetLocalisedPdhName(% Processor Time) - LocalisedName: Prozessorzeit (%)
D 18:11:28 Device Buffer Size: 983.040 bytes.
D 18:11:28 Device Buffer Available: 163.840 bytes.
I 18:11:28 Filling Buffer... (40 MB)
I 18:11:31 Writing LeadIn...
I 18:11:39 Writing Session 1 of 1... (1 Track, LBA: 0 - 2122527)
I 18:11:39 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2122527)
I 18:24:58 Synchronising Cache...
I 18:24:59 Closing Session...
I 18:25:00 Exporting Graph Data...
I 18:25:00 Graph Data File: E:\Dokumente und Einstellungen\Eckhardt Newger\Anwendungsdaten\ImgBurn\BENQ_DVD_LS_DW1655_BCGB_FREITAG-29-JANUAR-2010_18-08_RITEK-004-48_MAX.ibg
I 18:25:00 Export Successfully Completed!
I 18:25:00 Operation Successfully Completed! - Duration: 00:16:16
I 18:25:00 Average Write Rate: 5.319 KB/s (3.8x) - Maximum Write Rate: 5.671 KB/s (4.1x)
I 18:25:00 Cycling Tray before Verify...
W 18:25:08 Waiting for device to become ready...
I 18:25:14 Device Ready!
I 18:25:15 Operation Started!
I 18:25:15 Source Device: [4:0:0] BENQ DVD LS DW1655 BCGB (D:) (RAID)
I 18:25:15 Source Media Type: DVD+RW (Book Type: DVD-ROM) (Disc ID: RITEK-004-48) (Speeds: 2,4x; 4x)
I 18:25:15 Image File: -==/\/[bUILD IMAGE]\/\==-
I 18:25:15 Image File Sectors: 2.122.528 (MODE1/2048)
I 18:25:15 Image File Size: 4.346.937.344 bytes
I 18:25:15 Image File Volume Identifier: 0098DVDV
I 18:25:15 Image File Application Identifier: IMGBURN V2.5.0.0 - THE ULTIMATE IMAGE BURNER!
I 18:25:15 Image File Implementation Identifier: ImgBurn
I 18:25:15 Image File File System(s): ISO9660; UDF (1.02)
I 18:25:15 Read Speed (Data/Audio): MAX / MAX
D 18:25:15 GetLocalisedPdhName(Processor) - RegQueryValueEx BufferSize: 65.536
D 18:25:15 GetLocalisedPdhName(Processor) - CounterIndex: 238
D 18:25:15 GetLocalisedPdhName(Processor) - PdhLookupPerfNameByIndex BufferSize: 2.048
D 18:25:15 GetLocalisedPdhName(Processor) - LocalisedName: Prozessor
D 18:25:15 GetLocalisedPdhName(% Processor Time) - RegQueryValueEx BufferSize: 65.536
D 18:25:15 GetLocalisedPdhName(% Processor Time) - CounterIndex: 6
D 18:25:15 GetLocalisedPdhName(% Processor Time) - PdhLookupPerfNameByIndex BufferSize: 2.048
D 18:25:15 GetLocalisedPdhName(% Processor Time) - LocalisedName: Prozessorzeit (%)
I 18:25:15 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2122527)
I 18:25:15 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2122527)
D 18:30:02 DeviceIoControl(IOCTL_CDROM_EXCLUSIVE_ACCESS, Unlock) Succeeded!
I 18:30:02 Exporting Graph Data...
I 18:30:02 Graph Data File: C:\Documents and Settings\eln\Application Data\ImgBurn\BENQ_DVD_LS_DW1655_BCGB_FREITAG-29-JANUAR-2010_18-08_RITEK-004-48_MAX.ibg
I 18:30:02 Export Successfully Completed!
I 18:30:02 Operation Successfully Completed! - Duration: 00:04:47
I 18:30:02 Average Verify Rate: 14.791 KB/s (10.7x) - Maximum Verify Rate: 21.705 KB/s (15.7x)
[/Code]

 

Hope this helps.

 

mumdigau

[LIGHTNING UK!]

Hmm, I think the delay must be coming from the initial API call that 'opens' the performance data stuff.

 

What's odd is that it takes 3 mins the first time when Write starts and is then instant when Verify starts.

 

Sorry, I'm not really sure what to do now.

 

Try looking in EventViewer to see if anything is logged during those 3 minutes that might provide us with clues.

[LIGHTNING UK!]

Does the hang happen every single time you burn? Even if you burn and verify (where verify happens quickly remember) and then burn again (with or without closing down the program) ?

 

I can send a version that logs the actual calls to the openquery and addcounter functions that are used for the performance data stuff if you fancy giving that a go and getting a more useful debug log?

[mumdigau]

Does the hang happen every single time you burn? Even if you burn and verify (where verify happens quickly remember) and then burn again (with or without closing down the program) ?

 

I can send a version that logs the actual calls to the openquery and addcounter functions that are used for the performance data stuff if you fancy giving that a go and getting a more useful debug log?

Yeah, please do that. BTW, Event Viewer doesn't help. There is just one entry with more or less identical time stamp, i.e. the start of WMI Performance Adapter. This service is stopped 5 min later. I can't see any relationship to the problem here.

 

mumdigau

Edited January 29, 2010 by mumdigau

[Cynthia]

Curios.

 

While it's waiting for the graph data thread to be created, does your computer hang or can you use it during those three minutes?

[mumdigau]

Curios.

 

While it's waiting for the graph data thread to be created, does your computer hang or can you use it during those three minutes?

 

No, PC is fully functional during those 3 min. If I remember right, this behaviour was there from the very beginning after I installed ImgBurn on this PC (Intel E8400, 4GB RAM, motherboard ASUS P5Q, Win Pro XP SP3).

 

mumdigau

Edited January 30, 2010 by mumdigau