| Author |
Message |
Hoi Polloi
Guest
|
Posted:
Sun Oct 31, 2004 8:39 pm Post subject:
NeroVision Express 3 - What HAVE They Done? |
|
|
I've been using NeroVision Express 2 for a while now and have been very
happy with it.
A couple of days ago, I downloaded the components of the new Nero "Reloaded"
suite, including NeroVision Express 3.0.1.4.
There are some weird things happening with this program! My source files are
MPEG-2 encoded, and when I use "Add Video Files" to load files to a project:
a. one file (MPEG-2, 1.6 GiB, approx 1 hour) shows as over 13 hours
requiring 18 GiB DVD disc space!
b. Another file (MPEG-2, 2.4 GiB, also about 90 min) shows the correct
timing, but suddenly becomes 4.2 GiB on DVD. (On NVE 2, with "Automatic"
there was very little change is size.) Time to process this file is shown as
2 hr 38 min. Reverting to NVE 2 shows the correct length and a processing
time of 38 min.
c. Adding a fade at the end of the movie (crossfade) gives a default time
for the fade on NVE 2 of 3s, which can be changed with the properties
control. On NVE 3, the fade showed 23 minutes plus a strange number of
seconds!
Even removing all the Nero components, using the Nero Clean utilities and
then re-installing from scratch did nothing to change this strange
behaviour.
Is anyone else finding these kinds of things with NVE 3?
|
|
| Back to top |
|
 |
luminos
Guest
|
Posted:
Mon Nov 01, 2004 1:44 am Post subject:
Re: NeroVision Express 3 - What HAVE They Done? |
|
|
"Hoi Polloi" <nomail.thanks@nospam.com> wrote in message
news:418506a1$0$33620$ed2619ec@ptn-nntp-reader02.plus.net...
| Quote: | I've been using NeroVision Express 2 for a while now and have been very
happy with it.
A couple of days ago, I downloaded the components of the new Nero
"Reloaded" suite, including NeroVision Express 3.0.1.4.
There are some weird things happening with this program! My source files
are MPEG-2 encoded, and when I use "Add Video Files" to load files to a
project:
a. one file (MPEG-2, 1.6 GiB, approx 1 hour) shows as over 13 hours
requiring 18 GiB DVD disc space!
b. Another file (MPEG-2, 2.4 GiB, also about 90 min) shows the correct
timing, but suddenly becomes 4.2 GiB on DVD. (On NVE 2, with "Automatic"
there was very little change is size.) Time to process this file is shown
as 2 hr 38 min. Reverting to NVE 2 shows the correct length and a
processing time of 38 min.
c. Adding a fade at the end of the movie (crossfade) gives a default time
for the fade on NVE 2 of 3s, which can be changed with the properties
control. On NVE 3, the fade showed 23 minutes plus a strange number of
seconds!
Even removing all the Nero components, using the Nero Clean utilities and
then re-installing from scratch did nothing to change this strange
behaviour.
Is anyone else finding these kinds of things with NVE 3?
|
Yes, it is a mess. And now the transcoding process is 35% slower than
before. I completely uninstalled and went back to Express 2 (last
revision). |
|
| Back to top |
|
 |
Chuck Forsberg
Guest
|
Posted:
Tue Nov 02, 2004 5:08 am Post subject:
Re: NeroVision Express 3 - What HAVE They Done? |
|
|
Definitely a work in progress.
One mpg file which worked with NVE 2 causes NVE 3 to hang,
doing no i/o and consuming no processor time. Apparently
some sort of deadlock.
Mpg files that used to whiz past at disk copy speeds now
now transcode slowly.
NVE 2 did all the authoring before touching the recorder.
NVE 3 now starts the recorder, resulting in a ruined disk
if a problem arises in transcoding. I would suggest authoring
to a disk directory, then burn from that directory.
NVE 3 may be more tolerant of chapter stops than the previous
version.
Time for 3.01 already.
--
Chuck Forsberg caf@omen.com www.omen.com 503-614-0430
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 FAX 629-0665 |
|
| Back to top |
|
 |
Wiley
Guest
|
Posted:
Wed Nov 03, 2004 10:20 am Post subject:
Re: NeroVision Express 3 - What HAVE They Done? |
|
|
If the recorder starts burning when you begin transcoding, you need to
uncheck "Use Burn-at-once" under "Recording Settings" in the "Burn
Options" window. For some inexplicable reason, that toggle is set by
default in the new version.
I'm still trying to figure out what happened to the transcoding speed
that I was enjoying in Express 2. I've sent mail to Ahead (Nero
support), specifically asking that question. I wonder if I'll get
anything useful back.
Wiley
Oregon, USA
Chuck Forsberg <caf@localhost.localdomain> wrote in message news:<pan.2004.11.02.00.08.38.778340@localhost.localdomain>...
| Quote: | Definitely a work in progress.
One mpg file which worked with NVE 2 causes NVE 3 to hang,
doing no i/o and consuming no processor time. Apparently
some sort of deadlock.
Mpg files that used to whiz past at disk copy speeds now
now transcode slowly.
NVE 2 did all the authoring before touching the recorder.
NVE 3 now starts the recorder, resulting in a ruined disk
if a problem arises in transcoding. I would suggest authoring
to a disk directory, then burn from that directory.
NVE 3 may be more tolerant of chapter stops than the previous
version.
Time for 3.01 already. |
|
|
| Back to top |
|
 |
luminos
Guest
|
Posted:
Wed Nov 03, 2004 12:46 pm Post subject:
Re: NeroVision Express 3 - What HAVE They Done? |
|
|
"Wiley" <0eyf-0opr@xemaps.com> wrote in message
news:1ad3bceb.0411022120.2ae30121@posting.google.com...
| Quote: | If the recorder starts burning when you begin transcoding, you need to
uncheck "Use Burn-at-once" under "Recording Settings" in the "Burn
Options" window. For some inexplicable reason, that toggle is set by
default in the new version.
I'm still trying to figure out what happened to the transcoding speed
that I was enjoying in Express 2. I've sent mail to Ahead (Nero
support), specifically asking that question. I wonder if I'll get
anything useful back.
|
It's not only the speed, which is now much slower. I did some initial
tests, and I suspect even the quality has decreased when a recode is done.
I need to confirm this though...it might just be my frustration over the
longer encoding speed. |
|
| Back to top |
|
 |
|
|
|
|