Jump to content
Sign in to follow this  
BlizzardUK

Problem with other software causing premature results

Recommended Posts

I use IMGBurn version 2.5.7.0 on a Windows 7 64bit PC.

 

My problem is that when trying to multi-task by using certain other software it will cause IMGBurn to finish a disc early but it makes out is has burnt correctly, when it hasn't. The culprits seem to be TMPGenc software, not just one of theirs, but any of theirs you can burn discs with. I often burn dual layers while making the next one in the TMPGenc software, to save on time. However if I am burning a disc in IMGBurn then get to the write page in TMPGEnc then the IMGBurn write will stop and say it has completed. Quite often I will have 20 dual layer discs to burn in a row, so if I don't multi-task then it can be 10 hours before I can use the PC again.

 

Any ideas ? The log of the last incident it happened is below. The usual time for a burn of this type is 27 minutes, 15 minutes was far too quick and I remember it happening when it wasn't near the end in percentage.

 

I 05:31:58 Operation Started!
I 05:31:58 Source File: H:\ISO Images\DLfile.iso
I 05:31:58 Source File Sectors: 3,773,168 (MODE1/2048)
I 05:31:58 Source File Size: 7,727,448,064 bytes
I 05:31:58 Source File Volume Identifier: DVDLabel
I 05:31:58 Source File Volume Set Identifier: 3CEC2239RDUS0004
I 05:31:58 Source File Implementation Identifier: Ulead Systems USA Inc.
I 05:31:58 Source File File System(s): ISO9660, Joliet, UDF (1.02)
I 05:31:58 Destination Device: [0:0:0] ATAPI eHBU312   2 VL12 (J:) (USB)
I 05:31:58 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 05:31:58 Destination Media Supported Write Speeds: 4x, 6x, 8x
I 05:31:58 Destination Media Sectors: 4,173,824
I 05:31:58 Write Mode: DVD
I 05:31:58 Write Type: DAO
I 05:31:58 Write Speed: 4x
I 05:31:58 DVD+R DL Reserve Track: No
I 05:31:58 Link Size: Auto
I 05:31:58 Lock Volume: Yes
I 05:31:58 Test Mode: No
I 05:31:58 OPC: No
I 05:31:58 BURN-Proof: Enabled
I 05:32:00 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x)
I 05:32:03 Optimal L1 Data Zone Start LBA: 1973216 (VTS_02, PGC: 13, Cell: 1, Vob/Cell ID: 13/1, Time: 00:00:00, SPLIP: No -> Yes)
I 05:32:03 Optimal L0 Data Zone Capacity: 1,973,216
I 05:32:03 Optimal L0 Data Zone Method: IFO Cell Boundary, 'SPLIP' Flag Not Set
I 05:32:39 Set L0 Data Zone Capacity Succeeded!
I 05:32:39 Filling Buffer... (253 MB)
I 05:32:40 Writing LeadIn...
I 05:32:41 Writing Session 1 of 1... (1 Track, LBA: 0 - 3773167)
I 05:32:41 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3773167)
I 05:32:41 Writing Layer 0... (LBA: 0 - 1973215)
I 05:44:49 Writing Layer 1... (LBA: 1973216 - 3773167)
I 05:47:09 Synchronising Cache...
I 05:47:10 Closing Track...
I 05:47:11 Finalising Disc...
I 05:47:12 Exporting Graph Data...
I 05:47:12 Graph Data File: C:\Users\My Name\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_eHBU312_2_VL12_26-JULY-2013_05-31_MKM-003-00_4x.ibg
I 05:47:12 Export Successfully Completed!
I 05:47:12 Operation Successfully Completed! - Duration: 00:15:14
I 05:47:12 Average Write Rate: 8,703 KB/s (6.3x) - Maximum Write Rate: 348,964 KB/s (252.0x)
I 05:47:26 Close Request Acknowledged
I 05:47:26 Closing Down...
I 05:47:26 Shutting down SPTI...
I 05:47:26 ImgBurn closed!
Edited by BlizzardUK

Share this post


Link to post
Share on other sites

It must have a weird filter driver installed or something similar and it's making out that the commands I'm issuing to burn the disc are completing successfully when they aren't. It's out of my hands I'm afraid.

Share this post


Link to post
Share on other sites

It must have a weird filter driver installed or something similar and it's making out that the commands I'm issuing to burn the disc are completing successfully when they aren't. It's out of my hands I'm afraid.

 

Thanks. Does this mean it is managing to unlock the drive even though IMGBurn has locked it ? 

 

If you are ever bored and want to experiment, then they do trials of their software (Mastering Works 5, Authoring Works 5, and Smart Renderer 4), all three of those cause it.  

Edited by BlizzardUK

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.