where did latency come from? -ACID Product Family - MAGIX Community Forums Archive

Subject:where did latency come from? Posted by: ohmaya Date:5/3/2006 11:39:02 PM I just upgraded to 6.0 from 5.0. When I arm an audio track to record my violin, i have latency for the first time when I also arm the monitor option. I go to audio preferences and adjust the user latency recording offset but it never syncs up. I have the slightest delay that is killer for a violinist. I have a Delta 410 card that has ASIO drivers, the latest drivers and never had this issue in either 4.0 or 5.0. My PC is P4 3.2 Ghz and 1.75 GB GB so I know it cant be my hardware. This is nutty....I upgraded a week ago and still have not been able to complete a task or a project. Between this issue, the constant crashes and the program just closing with no warning, I am beyond frustrated. I love the new MIDI stuff in 6.0, but what good is it if the rest of the new version is so unstable I cant use it???? I will go back to 5.0 and await an update if this keeps up!
Subject:RE: where did latency come from? Reply by: LittleStudios Date:5/4/2006 5:23:47 AM when you're using the input monitor during recording you will hear some latency, unless you have a super top notch machine. latency is totally normal. you're probably hearing it for the first time because Aicd 6.0 has input monitoring which allows you to hear the music as your DAW (& sound card) process it and send it back to your speakers. when you use Acid's "automatically adjust offset for hardware latency" you will still hear latency during recording. but when all is said and done and you play the recording back, it should sound all good.
Subject:RE: where did latency come from? Reply by: Tobias7000 Date:5/4/2006 3:29:29 PM "Between this issue, the constant crashes and the program just closing with no warning, I am beyond frustrated." I have a high end machine (in my opinion) and I still have latency. Sometimes I can get around it. Others I have to monitor via the mixing console. I have a dual core AMD 4600+ machine built by PCAudiolabs.com. Fast rock solid machine with a Dakota/Tango audio interface. Frontier has had a stable ASIO driver since mid last year (no updates). Regarding crashes... understand your frustration. I did the following and now have 80% less crashes. Your mileage may vary ;-) 1. Switched from EMU ASIO driver to Dakota ASIO. (my gut told me EMU driver was being flakey) 2. Turned off "track buffering" in Audio Device tab. (this I'm certain causes many crashes for me) 3. Reinstalled .net 1.1, latest directX drivers, and AP6 (it may have been I had the wrong version of .net before) My gut feel is all of these changes had a favorable impact for me. I am certain Sony engineers will be making a few changes also to correct some of the crashes. Hope this helps.
Subject:RE: where did latency come from? Reply by: ohmaya Date:5/4/2006 4:59:25 PM When you say you monitor from the mixing console to reduce latency, do you mean in the software? Can you explain a little more specifically hwo this would be done vs. using the input monitor?

Subject:where did latency come from?

Posted by: ohmaya

Date:5/3/2006 11:39:02 PM

I just upgraded to 6.0 from 5.0.

When I arm an audio track to record my violin, i have latency for the first time when I also arm the monitor option. I go to audio preferences and adjust the user latency recording offset but it never syncs up. I have the slightest delay that is killer for a violinist.

I have a Delta 410 card that has ASIO drivers, the latest drivers and never had this issue in either 4.0 or 5.0. My PC is P4 3.2 Ghz and 1.75 GB GB so I know it cant be my hardware.
This is nutty....I upgraded a week ago and still have not been able to complete a task or a project. Between this issue, the constant crashes and the program just closing with no warning, I am beyond frustrated.

I love the new MIDI stuff in 6.0, but what good is it if the rest of the new version is so unstable I cant use it????
I will go back to 5.0 and await an update if this keeps up!

Subject:RE: where did latency come from?

Reply by: LittleStudios

Date:5/4/2006 5:23:47 AM

when you're using the input monitor during recording you will hear some latency, unless you have a super top notch machine. latency is totally normal. you're probably hearing it for the first time because Aicd 6.0 has input monitoring which allows you to hear the music as your DAW (& sound card) process it and send it back to your speakers.

when you use Acid's "automatically adjust offset for hardware latency" you will still hear latency during recording. but when all is said and done and you play the recording back, it should sound all good.

Subject:RE: where did latency come from?

Reply by: Tobias7000

Date:5/4/2006 3:29:29 PM

"Between this issue, the constant crashes and the program just closing with no warning, I am beyond frustrated."

I have a high end machine (in my opinion) and I still have latency. Sometimes I can get around it. Others I have to monitor via the mixing console. I have a dual core AMD 4600+ machine built by PCAudiolabs.com. Fast rock solid machine with a Dakota/Tango audio interface. Frontier has had a stable ASIO driver since mid last year (no updates).

Regarding crashes... understand your frustration. I did the following and now have 80% less crashes. Your mileage may vary ;-)

1. Switched from EMU ASIO driver to Dakota ASIO. (my gut told me EMU driver was being flakey)
2. Turned off "track buffering" in Audio Device tab. (this I'm certain causes many crashes for me)
3. Reinstalled .net 1.1, latest directX drivers, and AP6 (it may have been I had the wrong version of .net before)

My gut feel is all of these changes had a favorable impact for me. I am certain Sony engineers will be making a few changes also to correct some of the crashes.

Hope this helps.

Subject:RE: where did latency come from?

Reply by: ohmaya

Date:5/4/2006 4:59:25 PM

When you say you monitor from the mixing console to reduce latency, do you mean in the software? Can you explain a little more specifically hwo this would be done vs. using the input monitor?