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

[bishop666]

When using input fx you loose flexibility as you record the processed sound and not the DI sound, don't you?

Yes you do. Try freeze instead. It is a stacked freeze.

OR record to two tracks at the same time.

hm I think then it's easier to just install the old AT3 build that didn't have latency

Or wait for an update/fix if the latency wasn't intended

[ObiWonder]

We are looking into this further, we'll update you as soon as we have more information.

[zerocrossing]

Running Windows Vista 64 inside of the latest version of Live I'm getting no added latency. Seems great to me! Sounds great! Less filling!

Now, get on a version that allows you to not load up any model you're not currently using. That's the trick I want to see. Lean. Also... an amp reverb mode where 1 isn't making your signal swimming in reverb.

[ObiWonder]

Yeah, it is odd that latency is only showing up in certain DAWs and why we are looking into it further.

1 step at a time, we still have some other surprises coming...

[DotNoir]

Yeah, it is odd that latency is only showing up in certain DAWs and why we are looking into it further.

Yes, it is odd that you are looking into it further

But really, thank you for this update (not that I had too much problems before either).

[Tale]

Yeah, it is odd that latency is only showing up in certain DAWs

I don't know if it is related to the mentioned latency issues, but REAPER allows a VST plug-in to change its latency on the fly, something which I believe most other hosts don't support.

[Brian @ IK Multimedia]

Confirmed---all other non-convolution and non-linear phase plug-ins (except UAD) report 0 latency and Reaper doesn't add any. AT 3.5 now reports 7 (why?) and Reaper adds one total block size based on your card latency settings. In my case it's 256.

I'm hoping this is a fluke and there is no processing necessity that introduces the 7 samples, otherwise we have traded one pretty serious problem for another, at least in my host. I'd still take this over serious over-usage of RAM, though.

Few developers report their latency accurately. That's actually the reason why you're seeing them all report zero - not because it's not there, but because they're just not reporting their latency at all!

The new optimized engine in AmpliTube 3.7.1 doesn't add more latency than earlier versions did, it just reports those 7 samples now, so that the host can have sample-accurate sync. This appears to create a problem exclusively with Reaper, because of the odd "one-size-fits-all" way Reaper chooses to handles PDC. A work around for this is to disable PDC in Reaper while recording.

[hibidy]

are you kidding? Disable pdc while recording?

wow. One step forward, 3 steps back. I'll be holding onto my 3.7 thanks.

[Brian @ IK Multimedia]

BTW, in my testing of AmpliTube 3.7.1, I got up to 21 instances of AmpliTube going with no problems at all, using around 70% CPU in Studio One Pro 2. I could have kept going, but by that point I was doubling up instances on tracks!

The latency reported was 0.2ms with one instance per track on all tracks, and 0.3ms with two instances per track.

The 21st instance was when I put one on the Master Buss. That's when I knew it was time to stop!

[zerocrossing]

The 21st instance was when I put one on the Master Buss. That's when I knew it was time to stop!

You kids and your dubstep!

[metamorphosis]

Great news man, will give it a whirl.

[Paulie Phonick]

Is it me or v3.7.1 doesn't sound the same? I just upgraded from v3.0.2 (I know, been a while) and my projects sound f..d up. Boomy low end on high gain presets; harshness and levels screwed up on others (80s Ballad for instance). If this is a side effect of the optimization, how do I get rid of it, besides downgrading?

[Peter - IK Multimedia]

Is it me or v3.7.1 doesn't sound the same? I just upgraded from v3.0.2 (I know, been a while) and my projects sound f..d up. Boomy low end on high gain presets; harshness and levels screwed up on others (80s Ballad for instance). If this is a side effect of the optimization, how do I get rid of it, besides downgrading?

The sound quality was not comprised at all during optimization. You should contact support. Thanks.

[Dr.Gunjah]

Few developers report their latency accurately. That's actually the reason why you're seeing them all report zero - not because it's not there, but because they're just not reporting their latency at all!

sorry, but this is sheer assumption.
In my experience it's the other way around... most (serious) devs do it right and just a few don't.

[hibidy]

Few developers report their latency accurately. That's actually the reason why you're seeing them all report zero - not because it's not there, but because they're just not reporting their latency at all!

sorry, but this is sheer assumption.
In my experience it's the other way around... most (serious) devs do it right and just a few don't.

In fact, my singles are the only ones that do report it (not going anywhere near 3.71) with ONE exception, and that is magnetic.