Here are some actual posts from the Nuendo Forums site,
after hearing so much about rock solid sync, no bugs, No
latency with ASIO drivers plus VST support......let's here
what the users have to say with their recent posts.
Post 1
I'm experiencing some strange behavior:
I have a project with not too many tracks but a fair number
of waves and native plugins being used.With the performance
panel showing, when running I see almost no disk usage and
about 75% cpu usage. However... when I stop playback, cpu
goes all the way up and the little indicator on the cpu
meter lights up. The behavior is that if I click something,
it takes about 10 seconds for nuendo to respond, but it does
eventually respond. I discovered that to do things quickly,
I have to start playback, then everything is responsive and
fine while playback is going.
Weird! What in the world is nuendo doing?
Answer: Trying to compete with Veges and Failing.
Post 2:
This wave construction error enigma is a real dilly. The new
version 1.02 upgrade does not solve the problem on my
machine so I am still using the first version. By the way I
find that if I use the REM Hammerfall highest buffer
default setting I get wave construction errors anyway after
my tracks build up. I have 32 mono tracks running right now
and I have to use a lower buffer setting on the card to take
care of the Wave construction errors. I tried using the
lowest settings possible with the new upgrade but makes no
difference....so I guess there is a problem with the
software in regards how it sits in windows...and my God
there are a shit load of systems and configerations out
there !!!!! I Wonder if the next Upgrade will take care
ofthese various bugs FOR GOOD....or am I cursed to be stuck
with Version 1 forever ???????
Answer: You cursed yourself. Visit www.sonicfoundry.com to
relinquish the demonds.
Post 3:
Topic: Latency between audio tracks
Hi all,
I have a question for regarding audio latency in Nuendo:
I have seen Nuendo working on a Midiman Delta 1010 and there
seems to be a problem with the latency between audio
tracks.If you record an audio track on another track ( a
loop back test )there is a delay between them ( with the
lowest latency on Delta card 8ms using ASIO drivers this
latency is about 10 ms ).When you increase the latency
setting on the ASIO driver the latency between the tracks is
increasing too.Don't tell me that the ASIO driver is to
blame and stuff like that, on Vegas the same test with the
MME driveres give a 1ms latency.
Answer: ASIO Drivers have 10 times the lantency of a MME
driver in Vegas? That's because it's developed by Stankberg
who specialize in reverse engineering.
Post 4:
Topic: NUENDO REBOOTING
PROBLEM
georgek
Junior Member
posted 09-25-2000 05:30 PM
Hi all,
Have encountered a maddening problem using nuendo, other
apps on the same system seem to work fine. When I start a
project and enable inputs to record, system reboots. This
seems to happen consistently when I'm preparing to record
(arming tracks, enabling sync etc.). Samplitude and other
apps seem to record fine using the same RME 96/52 card and
celeron II overclocked to 850MHZ. Any insights greatly
appreciated.
Answer: Your system is trying to tell you something,
Unistall Nuendo and upgrade to Vegas.
Thanks for the insight Victor!!!!
after hearing so much about rock solid sync, no bugs, No
latency with ASIO drivers plus VST support......let's here
what the users have to say with their recent posts.
Post 1
I'm experiencing some strange behavior:
I have a project with not too many tracks but a fair number
of waves and native plugins being used.With the performance
panel showing, when running I see almost no disk usage and
about 75% cpu usage. However... when I stop playback, cpu
goes all the way up and the little indicator on the cpu
meter lights up. The behavior is that if I click something,
it takes about 10 seconds for nuendo to respond, but it does
eventually respond. I discovered that to do things quickly,
I have to start playback, then everything is responsive and
fine while playback is going.
Weird! What in the world is nuendo doing?
Answer: Trying to compete with Veges and Failing.
Post 2:
This wave construction error enigma is a real dilly. The new
version 1.02 upgrade does not solve the problem on my
machine so I am still using the first version. By the way I
find that if I use the REM Hammerfall highest buffer
default setting I get wave construction errors anyway after
my tracks build up. I have 32 mono tracks running right now
and I have to use a lower buffer setting on the card to take
care of the Wave construction errors. I tried using the
lowest settings possible with the new upgrade but makes no
difference....so I guess there is a problem with the
software in regards how it sits in windows...and my God
there are a shit load of systems and configerations out
there !!!!! I Wonder if the next Upgrade will take care
ofthese various bugs FOR GOOD....or am I cursed to be stuck
with Version 1 forever ???????
Answer: You cursed yourself. Visit www.sonicfoundry.com to
relinquish the demonds.
Post 3:
Topic: Latency between audio tracks
Hi all,
I have a question for regarding audio latency in Nuendo:
I have seen Nuendo working on a Midiman Delta 1010 and there
seems to be a problem with the latency between audio
tracks.If you record an audio track on another track ( a
loop back test )there is a delay between them ( with the
lowest latency on Delta card 8ms using ASIO drivers this
latency is about 10 ms ).When you increase the latency
setting on the ASIO driver the latency between the tracks is
increasing too.Don't tell me that the ASIO driver is to
blame and stuff like that, on Vegas the same test with the
MME driveres give a 1ms latency.
Answer: ASIO Drivers have 10 times the lantency of a MME
driver in Vegas? That's because it's developed by Stankberg
who specialize in reverse engineering.
Post 4:
Topic: NUENDO REBOOTING
PROBLEM
georgek
Junior Member
posted 09-25-2000 05:30 PM
Hi all,
Have encountered a maddening problem using nuendo, other
apps on the same system seem to work fine. When I start a
project and enable inputs to record, system reboots. This
seems to happen consistently when I'm preparing to record
(arming tracks, enabling sync etc.). Samplitude and other
apps seem to record fine using the same RME 96/52 card and
celeron II overclocked to 850MHZ. Any insights greatly
appreciated.
Answer: Your system is trying to tell you something,
Unistall Nuendo and upgrade to Vegas.
Thanks for the insight Victor!!!!