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

[filkertom]

I can verify that I was able to get to my user area and download both the Windows and Mac versions. No 403 here.

[asseca]

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

VstHost clearly reports: Initial Delay: 7 samples.

[PeterL]

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

VstHost clearly reports: Initial Delay: 7 samples.

Wow, 7 samples latency. This is 0.0x ms ?!
It's less latency than all soundcards on this planet can handle.
Does anyone notice latency under 1ms when played live (at least not me) ?
And for 'not live' usage we have PDC in our host.

Although 256 samples latency for live usage is another story.

[A.M. Gold]

Reaper 4 shows the same thing, actually. It shows two numbers for each plug-in, one I believe is the reported plug-in latency, and the second is what the final total is for all active plug-ins. For some reason, it shows 7 samples when you activate AT 3.5, but the total jumps up by 256 samples. I have no idea what this means.

[asseca]

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

VstHost clearly reports: Initial Delay: 7 samples.

Wow, 7 samples latency. This is 0.0x ms ?!
It's less latency than all soundcards on this planet can handle.
Does anyone notice latency under 1ms when played live (at least not me) ?
And for 'not live' usage we have PDC in our host.

Although 256 samples latency for live usage is another story.

7 samples is 0.16ms latency at a sample-rate of 44100.

The problem is that Reaper's DPC works in multiples of block-size. While previous versions of Amplitube has 0 Initial Delay, Amplitube now introduces this small amount of 7 samples, which now triggers the PDC to kick in with a delay of one block-size which could be (depending on ASIO settings) anything from 32 to 512 ms, so for some users suddenly this is a major issue !!

[A.M. Gold]

Yea, like a 256 sample sized issue.

If this is really what's happening, I'm not sure what to say. Reaper shouldn't be translating 7 samples into 256 by default, that makes no programming sense whatsoever.

[A.M. Gold]

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.

[bishop666]

shifting tracks by complete blocksizes simplyfies the PDC work for the daw. Think of multiple track/busses with different delays of 3/15/188344/254/... samples.

[A.M. Gold]

Then I guess it's good that most plug-ins report 0 latency. Efficient or not for the DAW, 7 transforming into 256 is extremely inefficient for the end user.

[geroyannis]

So the new version's RAM requirement is about 150MB less than the previous one, but still it's unusable for me. Right now it needs 240 MB when Amplitube2 needs half of it and a typical rack in GuitarRig eats about 100MB or so.

It's a pity because in general I like Amplitube's amps more than GuitarRig but I'm on WinXP 32-bit and can't afford to spend my precious RAM on Amplitube in my mixes.

[kgdrum]

updated last night:
1 thing surprised me with this, downloaded & installed last night& DP7.24 didn't do a AU inspection.Just looks like it overwrote and optimized Amplitude without AU needing to be re-examined.Anyone else get this? strange, never saw this before.
I checked to make sure it was updated and info window says 3.7.1
Thanks

[DarkStar]

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.

And if you add another instance of AT3 to the track you'll get 512. Reaper does indeed work in whole blocks sufficient to handle the pug-in delay announced by each plug-in.

256 samples is about 5.8 milliseconds.

-------------
Edit: I've just added another FX as an Input FX in Reaper and the delay is shown as the actual delay announced by the plug-in, not a multiple of block sizes. Try that for AT3. I've no idea what that does to PDC.

[Dr.Gunjah]

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

[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.

[Dr.Gunjah]

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