Nero takes longer to recode than usual

[proboller86]

So when i start to burn it says that it will take 13 minutes and 50 seconds. Throughout the burn it keeps upping the time and finally finished at 24 minutes. I have also noticed that just transfering files between hard drives will pause and not do anything for a while, then resume and continue working until they pause again. I have check and made sure that the harddrives are in DMA mode and NOT in PIO mode. Here's the log from nero. Any help is appreciated.


1K22-0867-0795-66M4-5391-6465-****
Windows XP 6.0
IA32
WinAspi: -
NT-SPTI used
Nero Version: 8.0.3.0
Internal Version: 8, 0, 3, 0
(Nero Express)
Recorder: <HP DVD Writer 640c> Version: JS04 - HA 1 TA 1 - 8.0.3.0
Adapter driver: <USB 2.0> HA 1
Drive buffer : 2048kB
Bus Type : set to ATAPI
CD-ROM: <MAT****A BD-RE UJ-225S >Version: Q111 - HA 1 TA 0 - 8.0.3.0
Adapter driver: <IDE> HA 1
=== Scsi-Device-Map ===
DiskPeripheral : WDC WD2500BEVS-75UST0 iaStorV Port 0 ID 0 DMA: On
=== CDRom-Device-Map ===
MAT****A BD-RE UJ-225S E: CdRom0
HP DVD Writer 640c J: CdRom1
=======================
AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
BUFE : 0
Physical memory : 2047MB (2097151kB)
Free physical memory: 1863MB (1908512kB)
Memory in use : 43 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
19.11.2008
UDF/ISO compilation
5:02:46 PM #1 Text 0 File SCSIPTICommands.cpp, Line 424
LockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL

5:02:46 PM #2 Phase 112 File dlgbrnst.cpp, Line 1762
DVD-Video files reallocation started

5:02:46 PM #3 Phase 114 File dlgbrnst.cpp, Line 1762
DVD-Video files reallocation completed (no file modified)

5:02:46 PM #4 Text 0 File Isodoc.cpp, Line 6668
UDF document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
UDF Mode : UDF/ISO bridge
UDF Options : automatic
UDF Revision : 1.02
UDF Partition Type : physical
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : FALSE
Allow pathdepth more than 8 directories : FALSE
Allow more than 255 characters in path : FALSE
Write ISO9660 ;1 file extensions : TRUE

5:02:46 PM #5 Phase 111 File dlgbrnst.cpp, Line 1762
DVD-Video files sorted

5:02:46 PM #6 ISO9660GEN -11 File Geniso.cpp, Line 3345
First writeable address = 0 (0x00000000)

5:02:46 PM #7 ISO9660GEN -11 File Geniso.cpp, Line 3345
First writeable address = 0 (0x00000000)

5:02:46 PM #8 Text 0 File Burncd.cpp, Line 3520
Turn on Disc-At-Once, using DVD media

5:02:51 PM #9 Text 0 File DlgWaitCD.cpp, Line 307
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 2286111 (508:01.36, 4465MB)

5:02:51 PM #10 Text 0 File DlgWaitCD.cpp, Line 319
Write in overburning mode: NO (enabled: CD)

5:02:51 PM #11 Text 0 File DlgWaitCD.cpp, Line 2972
Recorder: HP DVD Writer 640c, Media type: DVD+RW
Disc Manufacturer ID: MKM, Media Type ID: A02, Product revision number: 0
Disc Application Code: 0, Extended Information Indicators: 0

5:02:51 PM #12 Text 0 File DlgWaitCD.cpp, Line 493
>>> Protocol of DlgWaitCD activities: <<<
=========================================
Insert empty disc to write to.
(Medium in drive: DVD+RW. Medium required by compilation: DVD R/RW, DVD+R DL.)
This disc is not empty.
(Medium in drive: DVD+RW. Medium required by compilation: DVD R/RW, DVD+R DL.)
Accessing disc...
(Medium in drive: DVD+RW. Medium required by compilation: DVD R/RW, DVD+R DL.)

5:02:51 PM #13 Text 0 File ThreadedTransferInterface.cpp, Line 795
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 2286112 (2286112) = #2286112/508:1.37
relocatable, disc pos for caching/writing not required/ required
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286112 blocks [J: HP DVD Writer 640c]
--------------------------------------------------------------

5:02:51 PM #14 Text 0 File ThreadedTransferInterface.cpp, Line 997
Prepare [J: HP DVD Writer 640c] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1: Idx 0 Idx 1 Next Trk
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4681957376, ISRC ""
DAO layout:
===========
___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|__ ____NWA_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 0 | 0x41 | 0 | 0 | 0x00
0 | 1 | 1 | 0x41 | 2286112 | 0 | 0x00
2286112 | lead-out | 1 | 0x41 | 0 | 0 | 0x00

5:02:51 PM #15 Text 0 File SCSIPTICommands.cpp, Line 215
SPTILockVolume - completed successfully for FSCTL_LOCK_VOLUME

5:02:51 PM #16 Text 0 File Burncd.cpp, Line 4306
Caching options: cache CDRom or Network-Yes, small files-No (<64KB)

5:02:51 PM #17 Phase 24 File dlgbrnst.cpp, Line 1762
Caching of files started

5:02:51 PM #18 Text 0 File Burncd.cpp, Line 4425
Cache writing successful.

5:02:51 PM #19 Phase 25 File dlgbrnst.cpp, Line 1762
Caching of files completed

5:02:51 PM #20 Phase 36 File dlgbrnst.cpp, Line 1762
Burn process started at 4x (5,540 KB/s)

5:02:51 PM #21 Text 0 File ThreadedTransferInterface.cpp, Line 2723
Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

5:02:51 PM #22 Text 0 File Cdrdrv.cpp, Line 9918
---- Disc Structure: Physical Format Information (00h) ----
Media Type: 0, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-ROM (0), Part Version: 1.0x (1)
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: re-writable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Sector Number in Layer 0: 0 h (LBN: FFFD0000 h, 4193920 MB)
Data in Burst Cutting Area (BCA) does not exist
Media Specific [16..63]:
00 00 00 4D 4B 4D 00 00 - 00 00 00 41 30 32 00 39 ...MKM.....A02.9
23 00 94 79 64 02 20 00 - 9C 7A 6C 02 20 00 9A 7B #..yd....zl....{
68 02 20 12 12 10 E0 00 - F0 00 00 00 00 00 00 00 h...............

5:02:51 PM #23 Text 0 File DVDPlusRW.cpp, Line 675
Start write address at LBA 0
DVD high compatibility mode: Yes

5:02:51 PM #24 Text 0 File ThreadedTransfer.cpp, Line 269
Pipe memory size 83836800

5:27:49 PM #25 Text 0 File WriterStatus.cpp, Line 113
<J: HP DVD Writer 640c> start writing Lead-Out at LBA 2286112 (22E220h), length 0 blocks

5:27:50 PM #26 Text 0 File DVDPlusRW.cpp, Line 935
EndDAO: Last written address 2286112

5:27:50 PM #27 Text 0 File DVDR.cpp, Line 7374
Drive: HP DVD Writer 640c
Book Type request [gen]: DVD-ROM, direct update disc
Changing the Book Type was finished successfully, return code 0

5:27:50 PM #28 CDR -1207 File DVDR.cpp, Line 6449
Book Type automatically set to: DVD-ROM

5:27:50 PM #29 Phase 37 File dlgbrnst.cpp, Line 1762
Burn process completed successfully at 4x (5,540 KB/s)

5:27:51 PM #30 Text 0 File SCSIPTICommands.cpp, Line 261
SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME

5:27:54 PM #31 Text 0 File Cdrdrv.cpp, Line 11159
DriveLocker: UnLockVolume completed

5:27:54 PM #32 Text 0 File SCSIPTICommands.cpp, Line 424
UnLockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL

Existing drivers:
Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon

[Chewy]

If I had to guess, your hard drive(s) are fragmented

Burning with an internal burner and hard drives I notice some slowing when I allow my data drive to start to fill, when I author a dvd compilation, it gets spread out trying to find large enough chunks to write to.

You aren't trying to use an external usb drive as the source when burning to an external usb dvd burner?

Expect drastic stalls as usb is a huge resource hog, the cpu has to handle all the work

[proboller86]

But thats how i have been doing this all along. Never really had this problem before. I have actually had better luck burning from external hdd to external burner.

[proboller86]

I also have defrag set to run every night on all harddrives.

[gonwk]

Hi proboller,

Have U changed your Burner lately by any chance!?!?

G!

[Chewy]

post a screenshot of the defrag analysis of the drive you used to burn that dvd from

[proboller86]

I am using vista ultimate so the defrag app is a little different from xp. (if you didnt know). I am not sure how to get to the screen but i do know how to take a picture of the analysis as you can see its nothing like xp.

[gonwk]

Hi guys,

I don't think VISTA Defrag shows the Analysis Screen ...

G!

[doctorhardware]

I have diskeeper, I have always used Norton's and Windows. Diskeeper indacated the fragmented at 10%, where as norton's level was at 2%. So which one is correct. Windows also indacted the same level as Norton's.

[proboller86]

So waht else can wee do abbout this since we can't see the analysis screen

[Chewy]

Free up some hard drive space, burn off the fragmented data, then create a new file set that's not fragmented

Test with a new dvd + or - R not an rw

[proboller86]

why not an rw. thats the best type that works for me. thats what i have always used and have never had problems with the discs themselves. Most of the time it has just been DMA problems but now this happened.

[MilesAhead]

@proboller86 can you give some more details about the Vista you are using? Does it have SP1? 64 or 32 bit etc..

One of the troubles with Vista is you never know when one of those stupid file indexing services is going to kick on.. pegging your HD when you're trying to do something else.
Also any info on type of PC may be useful(for instance, Media Center PCs may do even yet another redundant layer of media file cataloging etc..)

edit: Oh yeah another possibility depending on your model of PC(as in HP) could
be "HD slowdown syndrome" but if you're not running an HP PC that can be eliminated.

[proboller86]

attached

[MilesAhead]

afaik HP machines are the only ones with "hard drive slowdown" due to errors from
heat from the power supply, so being a Dell rules that out.

Although with Nero I suppose an uninstall/registry clean/reinstall is usually worth a try.
(If you haven't already)

There's so much stuff on that machine tho' that I think Chewy prolly has the best shot at figuring this one out. My experience is not on fully loaded configurations (unfortunately.)