Amplitube next models? What will they be?

[dbender]

My "really want" top picks --

- Supro cabinet (15" ? or was it 12"?) [to go with the Supro amp added to AmpliTube 3]

- Hiwat Amp and matching cabinet(s)

- Mutron Bi-Phase pedal

- Treble boost pedal

[redshift factor]

yet......for some reason he always sounds about the same. Hmmmmmmmmmmmm

Not on 'Beat It'. Eddie just showed up with his guitar and his Echoplex.
He used the amp provided by Quincy Jones, and not surprisingly, his famous tone is MIA.

however, it's undeniably eddie.

Yeah, but we're talking tone, not style.
And on 'Beat It', the sound was not brown, man.

[hibidy]

yet......for some reason he always sounds about the same. Hmmmmmmmmmmmm

Not on 'Beat It'. Eddie just showed up with his guitar and his Echoplex.
He used the amp provided by Quincy Jones, and not surprisingly, his famous tone is MIA.

however, it's undeniably eddie.

Yeah, but we're talking tone, not style.
And on 'Beat It', the sound was not brown, man.

thats true

[redshift factor]

My "really want" top picks --

- Supro cabinet (15" ? or was it 12"?) [to go with the Supro amp added to AmpliTube 3]

- Hiwat Amp and matching cabinet(s)

- Mutron Bi-Phase pedal

- Treble boost pedal

[metalifuxx]

yet......for some reason he always sounds about the same. Hmmmmmmmmmmmm

Not on 'Beat It'. Eddie just showed up with his guitar and his Echoplex.
He used the amp provided by Quincy Jones, and not surprisingly, his famous tone is MIA.

however, it's undeniably eddie.

Yeah, but we're talking tone, not style.
And on 'Beat It', the sound was not brown, man.

But Michael still was

[declan32001]

No way should an algorithim based plug be demanding more RAM than sample libraries. Its just wrong 32bit or not.

Please forgive me, but that's a presumptuous-as-hell statement. Isn't the reason those algorithims were written in the first place was for sound?

[electro]

No way should an algorithim based plug be demanding more RAM than sample libraries. Its just wrong 32bit or not.

Please forgive me, but that's a presumptuous-as-hell statement. Isn't the reason those algorithims were written in the first place was for sound?

Amplitube is loading all 100+ Amps Cabs and Stomps into RAM at once. That is the problem. If it was coded considerately we could have the exact same sound for only 3MB per instance instead of 250MB.

[Peter - IK Multimedia]

I know that's not meant to be exact math but it is a bit extreme. It isn't a simple change to make, it would affect a lot of people who use it live, but it is not something we are ignoring. At this point that's all I can really share but I'm not hiding anything either.

[bishop666]

C'mun Peter, mor' mettel muscheens! Plees! ( Dzermen Emps , Pleez)

[Funkybot's Evil Twin]

No way should an algorithim based plug be demanding more RAM than sample libraries. Its just wrong 32bit or not.

Please forgive me, but that's a presumptuous-as-hell statement. Isn't the reason those algorithims were written in the first place was for sound?

Sorry dude, the statement is not presumptuous. Algorithms are just straight code. Even if the code were a hundreds of thousands of lines long (which is closer to a DAW then a plugin), we're still talking about it being in the 10s of megabytes. This is why something like Mr. Ray is so much smaller than NI/Scarbee's Rhodes. Hell, even Reaper (a fullblown DAW) has a smaller footprint.

The reason AT3 takes up so much RAM is because, 1) whatever impulse responses (i.e. samples) get used to make the cabs, room, and anything else get loaded into RAM, 2) as do the graphics, and 3) as do the algorithms. As discussed to death already, this is to make patch switching pretty much instantaneous in live use (because RAM is faster than anything else).

So while the original statement isn't accurate because AT3 isn't 100% math, the idea that pure algorithmic plugins shouldn't use more RAM than a large sample library isn't all the presumptuous.

[bishop666]

as devil's advocate i can tell you the number of lines of code has nothing to do with ram use. a single line can eat up your ram

[zerocrossing]

No way should an algorithim based plug be demanding more RAM than sample libraries. Its just wrong 32bit or not.

Well, then why don't you write a plug-in that sounds as good and works as well (no long drop between patches) as Amplitube 3 does and prove your statement?

I have no idea how likely or easy it would be, but I think a good compromise would be a version of AT3 that had another option in the "quality" prefs. One, a "live" option that takes as much memory as it needs to make sure there's seamless changes between presets (basically as it is now) and a second "studio" option more suited for projects where the preset doesn't change at all so only the current gear gets loaded into memory and when you change presets you have to wait for the new models to get loaded.

Of course, I say this having no idea of how hard it would be to implement this, but I also don't have an issue with memory.

[declan32001]

No way should an algorithim based plug be demanding more RAM than sample libraries. Its just wrong 32bit or not.

Please forgive me, but that's a presumptuous-as-hell statement. Isn't the reason those algorithims were written in the first place was for sound?

Sorry dude, the statement is not presumptuous. Algorithms are just straight code. Even if the code were a hundreds of thousands of lines long (which is closer to a DAW then a plugin), we're still talking about it being in the 10s of megabytes. This is why something like Mr. Ray is so much smaller than NI/Scarbee's Rhodes. Hell, even Reaper (a fullblown DAW) has a smaller footprint.

The reason AT3 takes up so much RAM is because, 1) whatever impulse responses (i.e. samples) get used to make the cabs, room, and anything else get loaded into RAM, 2) as do the graphics, and 3) as do the algorithms. As discussed to death already, this is to make patch switching pretty much instantaneous in live use (because RAM is faster than anything else).

So while the original statement isn't accurate because AT3 isn't 100% math, the idea that pure algorithmic plugins shouldn't use more RAM than a large sample library isn't all the presumptuous.

I didn't mean to sound as much like a jerk as I did. I respect your posts as well as electros, and Peter has almost confirmed that AT3 was designed purposely this way. And I'm not naieve enough to think it doesn't/won't affect me. I had my first WTF moment since my upgrade last week (but not with AT3).

Maybe the new ampsim world is geared to live performance from a marketing perspective, and that's insane IMHO. If I record an entire track that stuns me, I always end up chopping it all up anyway (even if I don't Melodynize it -which gets very freaky).

But the elephant in the room remains. People scream when a new version of whatever comes out and it's not 64bit. Some people scream that can't run their 32-bit stuff in a 64bit "environment" (I haven't had that problem). Others have been bloodied by the 32 to 64 bit conversion (count me in).

I simply can't tell IK they screwed up with AT3 or their approach in developing it because it may have been in their own best interests, and not mine.

The only personal criticism I have is a company whose flagship ampsim has a Fender ampsim add-on not included that came out before AT3. We live in a bizarre world.

Anyway, I hope they lessen the ram issue and prosper and stop laughing at me because they know I'll eventually frikkin' Fender thingy.

Someone bless us all. I

[dreibel]

what I'd like to see added:

Rangemaster treble booster

Garnet Herzog (late 60s tube preamp pedal co-designed by Randy Bachman and Gar Gilles - the sound of "American Woman")

Vox Brian May "Deaky" practice amp (which itself was modeled on the John Deacon built transistor amp which, when loaded with a treble booster, was the basis for a lot of May's solos and multitracking textures)

Matchless Clubman (tried one of these recently. amazing with a Strat)

80s Ibanez stomp compressor - great compression without losing high end or getting too mushy.

Gorilla practice amp

[buscemi]

Yes, impulses are surely involved in the RAM usage, too - good thing to point out FET