The last couple of burn attempts seemed to have frozen the MF4SE at (one ) 7% and (the other) at 11% (when actually burning onto the disk ). Note that I did re-boot before each succeeding burn failure.
As MF froze up and nothing short of hard booting would close it, expecting to lose the .dwz (project files) and sure enough even the TS files, before I booted, I copied the TS files, so I was able to save the capture by burning the files to DVD (using Shrink to convert the TS's to .MDA files, then got DVDDecrypter to write the file to DVD).
As for my Windows Event Log, all I see related to each freeze are event ID's of 490 w/a source of ESENT and the described event says svchost (1032) An attempt to open the file "C:\WINDOWS\system32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}\catdb" for read / write access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ". The open file operation will fail with error -1032 (0xfffffbf8).
Of course MS has no answer for the event.
As for MF in general, for me, even simple MF burns (6 to 10 chapters) are taking 6 to 10 hours to accomplish (for 120 to 180 min movies), maybe it's just 'my' OS/MF that seems to be really slow (better than 3 times what I'm assuming a burn straight to disc might take?).
Does everyone's burn process taking this long (once "burn" is clicked)?
Burn process failing & MF not flagging any error.
-
FRance
Hi
that burning process of yours is too long.. I think you should try a clean re-installation:
http://www.explorecommerce.com/members/ ... 31&ID=9826
Also if you installed any burning softwares recently, please disable or uninstall it temporarily and make a test burn. Other burning softwares, especially ones with packet-writing capabilities that load into your system tray, can cause compatibility problems with the Ulead burning engine. Examples of such softwares are Nero InCD and Roxio EZCD Creator.
Hope this would help. =)
that burning process of yours is too long.. I think you should try a clean re-installation:
http://www.explorecommerce.com/members/ ... 31&ID=9826
Also if you installed any burning softwares recently, please disable or uninstall it temporarily and make a test burn. Other burning softwares, especially ones with packet-writing capabilities that load into your system tray, can cause compatibility problems with the Ulead burning engine. Examples of such softwares are Nero InCD and Roxio EZCD Creator.
Hope this would help. =)
Seems like it's the multiplexing that troublesome
No nothing else running either in tray or even processes that task mgr lists, even though my only other burn programs are Shrink-Decrypter and the KWorld PVR/TVR software.
I just had some quicker results in burning a DVD though. What I've been doing was capturing from VHS (using the KWorld dongle) and those vids are being formatted to mpeg2. Then I was using MF's "add files" to do the burning to DVD.
This time I used MF to capture and the burn time was considerably faster.
I did notice one oddity. The entire MF DVD processing (aside from the capture) took some 50 mins for the 90 min movie and I did tick the TS and ISO tick boxes (for backups). But the actual burn time took 11 mins despite one of the last things I did was set the advanced burn option to 2X burn speed.
Note, I also had "test burn" and "buffer underrun protection" tick boxes ticked, but my burner's 'run' light didn't light up until the test burn and actual burn, each of those steps taking 14 and then 11 mins.
But it seems that the actual burn took 11 mins which is something like 13X as opposed to the 2X I set MF for.
The only other potential cause for way I'm seeing as a high burn speed is that for my burner's properties, I've not ticked the 'enable cd burning' and below that the ghosted box is set for "fastest".
I suppose I can try enabling and setting it to 2X there, but I don;t think that setting should affect DVD burns.
I've avoided enabling my burners for cd recording as I have so much trouble getting the onboard (laptop's) burner to play DVD's as it plays nothing but a very few of the one's with the logo of DVD Video (w/"video" insode a saucer like outline just below the word DVD. All other DVD's I have, that also have that logo as well as added DVD logo's, the onboard optical drive fails to even see the DVD discs. But that's a problem I gave up on (assuredly Sony's OEM bunkware, not the drive itself).
Again, many thanks for the rpelies.
I just had some quicker results in burning a DVD though. What I've been doing was capturing from VHS (using the KWorld dongle) and those vids are being formatted to mpeg2. Then I was using MF's "add files" to do the burning to DVD.
This time I used MF to capture and the burn time was considerably faster.
I did notice one oddity. The entire MF DVD processing (aside from the capture) took some 50 mins for the 90 min movie and I did tick the TS and ISO tick boxes (for backups). But the actual burn time took 11 mins despite one of the last things I did was set the advanced burn option to 2X burn speed.
Note, I also had "test burn" and "buffer underrun protection" tick boxes ticked, but my burner's 'run' light didn't light up until the test burn and actual burn, each of those steps taking 14 and then 11 mins.
But it seems that the actual burn took 11 mins which is something like 13X as opposed to the 2X I set MF for.
The only other potential cause for way I'm seeing as a high burn speed is that for my burner's properties, I've not ticked the 'enable cd burning' and below that the ghosted box is set for "fastest".
I suppose I can try enabling and setting it to 2X there, but I don;t think that setting should affect DVD burns.
I've avoided enabling my burners for cd recording as I have so much trouble getting the onboard (laptop's) burner to play DVD's as it plays nothing but a very few of the one's with the logo of DVD Video (w/"video" insode a saucer like outline just below the word DVD. All other DVD's I have, that also have that logo as well as added DVD logo's, the onboard optical drive fails to even see the DVD discs. But that's a problem I gave up on (assuredly Sony's OEM bunkware, not the drive itself).
Again, many thanks for the rpelies.