Amplitube next models? What will they be?

[electro]

I think the reason for the RAM footprint is that AmpliTube has to load the whole thing in memory, and it is very large with a lot of modules and cab impulses. If it didn't load everything in RAM, then you couldn't have smooth program changes/module switching.

And why wouldn't that kind of huge resource consumption just for patch changing be an option?

I like the post AT2 GUIs. I think the displacement of the up/down arrows is an acceptable trade off to have models that are more accurate to the originals.

The thing I don't like about the GUI is the "ghost knobs" on the old AT2 models.

Shifting up down preset arrows are silly. Ghost knobs are silly too, but those are just inconveniences whereas the 250MB RAM hit has a crippling effect on the 32bit DAW.

[redshift factor]

What do you all think looks better?




--OR--




Personally, I think the ghost knobs are quite distracting.

[hibidy]

I like it w/o

But they don't bother me much

[Agreed]

I don't mind the ghost knobs. Just NBD as far as I'm concerned.

[zerocrossing]

I like it w/o

But they don't bother me much

Me too. The ghost knobs never made much sense to me. In my UI philosophy the only time you'd do that is if you were in a mode where they were disabled to let the person know they were in that mode. Once you get out of that mode they'd become fully visible. I'd love to see a "mod" mode where if you clicked a button the ghosted knobs became operational.

[FuzzyKeys]

If IKM came out with an expansion that was only made up of quality effects that you could use within AT3, I'd buy it if it was reasonably priced.

[johnrrrrrr]

Well your pal can contact support With Agreed showing that on a current machine it is a matter of a few percent more than rivals, I would say that we're a few percent better than those rivals but hey I'm a touch biased

To be fair: he's talking about RAM and you're talking about CPU. I think Amplitube is worth every last CPU cycle, but it's RAM usage is ridiculously high. I mean, it's over 1/4 gigabyte of RAM (approximately 260MB if I'm not mistaken) per instance. With three guitar tracks and a bass all running Amplitube, I've got no RAM leftover for the drum or piano samples.

And its not only that..even if you have 6 gigs of Ram.. most peoples Daws will start to fail somewhere around 1.6gigs because of the memory limit. If you have Win7--most people will be using the 32bit version so all their plugins are compatible--this starts to have problems around 2.4 gigs in most Daws---so its just too big to be useful and stable.

[electro]

Well your pal can contact support With Agreed showing that on a current machine it is a matter of a few percent more than rivals, I would say that we're a few percent better than those rivals but hey I'm a touch biased

To be fair: he's talking about RAM and you're talking about CPU. I think Amplitube is worth every last CPU cycle, but it's RAM usage is ridiculously high. I mean, it's over 1/4 gigabyte of RAM (approximately 260MB if I'm not mistaken) per instance. With three guitar tracks and a bass all running Amplitube, I've got no RAM leftover for the drum or piano samples.

And its not only that..even if you have 6 gigs of Ram.. most peoples Daws will start to fail somewhere around 1.6gigs because of the memory limit. If you have Win7--most people will be using the 32bit version so all their plugins are compatible--this starts to have problems around 2.4 gigs in most Daws---so its just too big to be useful and stable.

It really is a bitch. A mere 2 instances can easily crash a project.

[Brittlestem]

Well your pal can contact support With Agreed showing that on a current machine it is a matter of a few percent more than rivals, I would say that we're a few percent better than those rivals but hey I'm a touch biased

It really is a bitch. A mere 2 instances can easily crash a project.

+1, I'm demoing Waves GTR3 and Vandal atm specifically because having both Omnisphere and Amplitube in a project is just becoming unusable.

Omnisphere's RAM usage is worth it, Amplitube not so much. They seem more concerned with making crappy iphone apps and devaluing their products with 3 for 1 offers/obscene licence transfer fees than sorting out user issues.

[Peter - IK Multimedia]

They seem more concerned with making crappy iphone apps and devaluing their products with 3 for 1 offers/obscene licence transfer fees than sorting out user issues.

Just because we market the newest product and have promotions doesn't mean that's the only thing we're working on. We have more than one developer, and marketing and development are two completely separate functions of our company (as it is or at least should be in most).

Do you have an unresolved user issue that has a ticket assigned to it? Please PM it to me and I'll have someone contact you. If you refer to the RAM usage, we are aware that people consider it heavy. There are options and apparently the development team is aware of those options and they have to weigh them against everything else (in AmpliTube, not the "crappy iPhone apps") when considering a fix. The biggest tradeoff, and I'm grossly oversimplifying here, would be the instant switching (and, notably previewing - you can instantly listen to presets using Preset Browser for example) but there are others too. I will keep you guys posted or you can open a ticket with any issues.

[hibidy]

Still hoping for a bad cat

[Funkybot's Evil Twin]

Do you have an unresolved user issue that has a ticket assigned to it? Please PM it to me and I'll have someone contact you. If you refer to the RAM usage, we are aware that people consider it heavy. There are options and apparently the development team is aware of those options and they have to weigh them against everything else (in AmpliTube, not the "crappy iPhone apps") when considering a fix. The biggest tradeoff, and I'm grossly oversimplifying here, would be the instant switching (and, notably previewing - you can instantly listen to presets using Preset Browser for example) but there are others too. I will keep you guys posted or you can open a ticket with any issues.

It's good to know it's being looked at Peter. If you don't mind some unsolicited advice: I'd really just suggest creating two modes, live and studio. If a preference isn't the best option, then allow me to suggest making a second .dll for live usage (call it Amplitube3Live.dll), and reducing the RAM usage in the existing Amplitube plugin.

Anyway, I hope the powers at be at IKMM know that this is probably largest pressing issue with Amplitube as it currently exists, and I hope they address this in the very near future. It's still an absolutely brilliant plugin, but reducing the RAM usage would make it so much better.

[hibidy]

I don't think I need to worry about such things.....being able to use 8gb (soon to be 16gb) of ram (even though the plug is x86)

[Funkybot's Evil Twin]

I don't think I need to worry about such things.....being able to use 8gb (soon to be 16gb) of ram (even though the plug is x86)

I'm definitely going to have to make the plunge to 64 bit soon.

[hibidy]

I still get goosebumps sometimes using it