I was using Nero Vision Express version 3 and a two hour DVD took about three and a half hours to transcode from the MPEG source file to the .nrg image. I then upgraded my CPU (and motherboard) from an AMD Sempron 2400 to a dual core AMD Athlon 64 X2 3600. I was astounded at the speed increase! I could transcode a two hour DVD in about 15 minutes! At first I thought something was wrong, but the resulting DVDs were perfectly fine. Then I "upgraded" from Nero 6 to Nero 8, which comes with Nero Vision 5. Now a two hour DVD takes about two and a half hours to transcode. What's up with that? I've tried experimenting with settings like 1-pass versus 2-pass, and they make a noticeable difference in the encoding time, but nothing like the performance I got when I used NVE3 on my new hardware. The format of the source files hasn't changed. Any ideas as to what is going on? Can I get the screaming performance that I had with NVE3 on NV5? If not, why not?
Thanks for the link. I checked and the devices are using the "DMA if available" option, but I'm not sure that would make a difference in my case because I'm burning to the "image recorder", not to my burner. That is, I'm creating a disk image from files on the hard drive. The burner is not even involved in this step, so I would think that the settings on the burner device shouldn't make a difference. Any other ideas?
as a rule of thumb the longer the process the better the results, perhaps the encode engine is better than before? i use TFM/CCE for avi to dvd which should be longer than mpeg to dvd and it takes about 1 hour for a 700meg file to dvd iso, on a 4400 dual core does seem abit wierd are you useing mpeg and mpeg2 formats?
The source file is in MPEG-2 format. The outboard WinTV-PVR-USB2 unit converts the signal to this format using hardware encoders before sending it to the hard drive via a USB 2.0 cable. The hardware encoders cannot be bypassed, so AVI is not an option.
i wonder? mpeg2 can be dvd compliant, check your mpeg2 with gspot for more info re: resolution of pal or ntsc whatever yours is... i wonder if nv5 re encodes mpeg2 to mpeg2, where nv3 didnt do it if it didnt need it. just a thought...
According to GSpot, the source file is MPEG-2. The container Sys Bitrate is 10125 kb/s VBR. Resolution is 720x480. 29.97 frames per second. Aspect ratio is 4:3. The audio is MPEG-1 Layer 2 CBR at 48,000 Hz, stereo, 384 kb/s tot. The appropriate codecs are installed for both the video and the audio. Under "Resizing" it says "None, already DVD format." Does that clear anything up? I was wondering if maybe NVE 3 took better advantage of the dual core processor.
well it lets us know its a dvd compliant mpeg2... im wondering if the mpeg2 that took 15 mins was smaller than the mpeg2 that took 2 hours? dvd structure has to make mpeg2 into vob chucks of not more than 1 gig, and maybe the 15 min project only had to make ifo/bup to match the changed mpeg2 to vob, i say "changed" vob, NOT converted/re-encoded. as mpeg2 is a vob you could just rename the ext from blar.mpeg2 to blar.vob under one gig and ading the ifo/bup may work ok, over 1gig it needs to be converted to 1 gig parts + ifo/bup... hmm......
I created at least 3 or 4 different DVDs with NVE3 and the new hardware before switching to the newer version of Nero Vision. They were definitely over 1GB. Come to think of it, though, I was having another problem at that time, which was why I ended up upgrading in the first place. Changing the quality settings didn't change the calculated disk space. I would have, for example, 100 minutes of video and it would tell me that it wouldn't fit on a DVD. (It reported needing about 5GB.) That was at the standard playback quality that should have allowed for 120 minutes. I tried changing to long play and even extra long play, but it always said it wouldn't fit. I recently posted about an issue I found (using the new version of NV) with the SmartEncode feature. Using the SmartEncode feature cut the encoding time from 2 1/2 hours down to 1 1/2 hours, but the encoding failed after the first few minutes. Turning the SmartEncode feature of added an hour to the encoding time, but at least it completed successfully. The post, along with details on the actual error, can be found at this link: http://forums.afterdawn.com/thread_view.cfm/636751
