AmpliTube Version 3.7.1 Now Available! Optimized: 30% to 40% less CPU & RAM

[ObiWonder]

Why on earth does the new version introduce latency?

The new AmpliTube update does not introduce latency. If you are having issues with latency please contact our support for some 1 on 1 help figuring it out.

[Peter - IK Multimedia]

Edit - I see Obi was on it and correct.

[Amon1973]

if it's not a bug on my side - yes!
I worked on a project before downloading the new version... 0 latency.
After installing 3.7.1 I get 256 samples latency(depending on my audio device I guess).

Just installed the uppdate, I still read 0 latency.

[paterpeter]

I don't know what the delay was before the update, but now it reports 256 samples (Reaper) or 0.2ms (Studio One v2) respectively, tested on two different systems.

[Amon1973]

That is odd. Especially considering that 256 samples should introduce a way higher latency than 0.2 ms. I checked in Cubase 6, but didn't try in Reaper, will test tomorrow.

[Dr.Gunjah]

Latency is also reported in Reaper 4

[Peter - IK Multimedia]

I was told no latency should have been introduced (obviously not on purpose) but of course we have developers looking into it. Thanks!

[Funkybot's Evil Twin]

This appears to be host specific. Testing in Sonar 8.5 I got 0 samples latency. Here was my testing method (in case I did something wrong):

1. Loaded a mono kick drum track with a nice defined transient
2. Loaded Amplitube 3.7.1 on that track
3. EDIT: Unchecked the "Enable Delay Compensation" checkbox in the VST Plugin Properties for AT 3.7.1
4. Bypassed amp and cabs
5. Bounced the audio to a new mono track
6. Reduced the volume of the new track by 3db (to compensate for a Sonar bug where gain increases with certain pan laws when doing mono bounces)
7. Flipped the phase on the new track

Result: it nulled completely. If there was latency getting introduced, the two tracks wouldn't null.

Now when I checked in Reaper, AT 3.7.1 was always reporting 128 samples latency regardless of whether or not amps/cabs were on.

[A.M. Gold]

Confirmed, 256 samples effectively added in Reaper 4.

[kbaccki]

Result: it nulled completely. If there was latency getting introduced, the two tracks wouldn't null.

Don't think so... the whole purpose of PDC is to compensate for latency buffers across all plugs tapping into the audio engine... so if SONAR is doing what it's supposed to be doing, effected and uneffected tracks should always null out, because the uneffected tracks will be shifted around to compensate for latency on the effected tracks... right?

Your test would work if you could disable PDC globablly in SONAR. I think that was introduced in recent versions.

[Echoes in the Attic]

Seeing 0.2 ms latency reported in Studio One 2. Hope it gets fixed.

[Funkybot's Evil Twin]

Result: it nulled completely. If there was latency getting introduced, the two tracks wouldn't null.

Don't think so... the whole purpose of PDC is to compensate for latency buffers across all plugs tapping into the audio engine... so if SONAR is doing what it's supposed to be doing, effected and uneffected tracks should always null out, because the uneffected tracks will be shifted around to compensate for latency on the effected tracks... right?

Your test would work if you could disable PDC globablly in SONAR. I think that was introduced in recent versions.

I forgot to mention, I had disaled "Enable Delay Compensation" in the plugin's VST Properties.

[hibidy]

btw, the singles introduced "latency" into reaper (3 or 4) as well (64)

This was supposed to be resolved but never was. I have an i7 and tons of ram, I'm not touching this update

[A.M. Gold]

Well now it's gone through the roof with 256 samples. Guys, please deal with this ASAP. You've fixed this this version and broken it at the same time.

[shanecgriffo]

i'm getting a '403 forbidden' when i try download it from my user area, maybe they took it down , can anyone verify? thanks