Atomic Transient
-
- KVRAF
- 2575 posts since 25 Apr, 2009 from gone
32 milliseconds in Cubase 8.5 Pro (don't know if it would be exactly the same in any DAW). Not measured using tools, simply by duplicating a track to another one, setting the second to inverted phase and inserting Atomic Transient, then adjusting the pre-delay of the second track until the two waves disappear nearly completely.
-
- KVRer
- 2 posts since 20 Dec, 2011
Hi DJErmac,
Latency-correction should be correct handled by plugins that need some preprocessing and every DAW should compensate different latencies if using different insert-effects in a project.
AtomicTransient uses this latency correction of the DAW (also Cubase) and this works fine.
I have done some investigation about your problem using Cubase. To check that, I use a simple mono drum-rhythm sample in the first track, copied it to a second and added AtomicTransient as an insert plugin. Then I set the first track (original) to be on the left channel and the second to be on the right one. In this case there is no difference between the first original and the second track with Atomic Transient. I also exported the mixdown and checked it in a wave editor. Both samples are absolute synchronous and there is no latency using AtomicTransient.
But there seems to be a problem if AtomicTransient is BYPASSED (switched off): Because Cubase does not read the latency time for bypassed plugins anymore and AtomicTransient returns the
untouched signal immediately, the output comes earlier than on the other channels.
We will correct this behavior with the next update.
As a workaround for AtomicTransient to be bypassed you should move the dry/wet knob to 0% (full dry).
best regards,
André
Latency-correction should be correct handled by plugins that need some preprocessing and every DAW should compensate different latencies if using different insert-effects in a project.
AtomicTransient uses this latency correction of the DAW (also Cubase) and this works fine.
I have done some investigation about your problem using Cubase. To check that, I use a simple mono drum-rhythm sample in the first track, copied it to a second and added AtomicTransient as an insert plugin. Then I set the first track (original) to be on the left channel and the second to be on the right one. In this case there is no difference between the first original and the second track with Atomic Transient. I also exported the mixdown and checked it in a wave editor. Both samples are absolute synchronous and there is no latency using AtomicTransient.
But there seems to be a problem if AtomicTransient is BYPASSED (switched off): Because Cubase does not read the latency time for bypassed plugins anymore and AtomicTransient returns the
untouched signal immediately, the output comes earlier than on the other channels.
We will correct this behavior with the next update.
As a workaround for AtomicTransient to be bypassed you should move the dry/wet knob to 0% (full dry).
best regards,
André