Amplitube 3 - screenshot (from NAMM)

[shanecgriffo]

if peter or anyone else from ik is around.. i have a reasonably old laptop 1.8 single core etc.. it runs J.H/x-gear pretty well, standalone at low latency (144samples via novation interface) so that i can use it live no probs.
Just wondering if this new amplitube v3 will be using much more resources than that.. i'll be happy to use single rig setups and dont use millions of fx at once..is it far removed from the J.H edition resource wise?
thanks

[Peter - IK Multimedia]

There will be some changes to the Preset XChange and web site coming but this is not happening right away.

[electro]

There will be some changes to the Preset XChange and web site coming but this is not happening right away.

You should host a raw DI E-Guitar file. put the processed Audiofile next to each preset.

[firepile]

Is today THE day?

[fanfarecircuit]

Is today THE day?

[shanecgriffo]

just to inform IK, you can release it now, i just paid for it

[Peter - IK Multimedia]

if peter or anyone else from ik is around.. i have a reasonably old laptop 1.8 single core etc.. it runs J.H/x-gear pretty well, standalone at low latency (144samples via novation interface) so that i can use it live no probs.
Just wondering if this new amplitube v3 will be using much more resources than that.. i'll be happy to use single rig setups and dont use millions of fx at once..is it far removed from the J.H edition resource wise?
thanks

For me, the final version of AmpliTube 3 is using just about the same resources as X-GEAR (seems to bounce just a hair higher on CPU but nothing to write home about, and RAM is nearly identical) when I load up the same Jimi Hendrix preset. This is in "HI" mode using the new HI-MID-ECO settings and you can quickly knock the resource usage down to MID for live use and I'd bet that people wouldn't know the difference. I use my OLD MacBook Pro (Core Duo not even Core 2 Duo!) to have it loaded on a modest setup, with StealthPedal as interface and a buffer size of 64 (lowest it can go, not bad). The RAM was less than my browser was using.

[fanfarecircuit]

the ik facebook page says not tuesday, but "dangerously close".

[Peter - IK Multimedia]

yes, dangerously. I'd tell you the little stuff (all non-code! whoopie!!!) but then I'd have to kill you. After your transformation to a huge IK fan that would be a shame

[electro]

if peter or anyone else from ik is around.. i have a reasonably old laptop 1.8 single core etc.. it runs J.H/x-gear pretty well, standalone at low latency (144samples via novation interface) so that i can use it live no probs.
Just wondering if this new amplitube v3 will be using much more resources than that.. i'll be happy to use single rig setups and dont use millions of fx at once..is it far removed from the J.H edition resource wise?
thanks

For me, the final version of AmpliTube 3 is using just about the same resources as X-GEAR (seems to bounce just a hair higher on CPU but nothing to write home about, and RAM is nearly identical) when I load up the same Jimi Hendrix preset. This is in "HI" mode using the new HI-MID-ECO settings and you can quickly knock the resource usage down to MID for live use and I'd bet that people wouldn't know the difference. I use my OLD MacBook Pro (Core Duo not even Core 2 Duo!) to have it loaded on a modest setup, with StealthPedal as interface and a buffer size of 64 (lowest it can go, not bad). The RAM was less than my browser was using.

The CPU is expected, but X-Gear puts everything including SVX and Fender into RAM and beats out many Sample Libraries for RAM load. Geez..How many people need 40 AMPS and 50 stomps in memory at one time for automation?

Tell IK the Preferences dialog needs a purge RAM checkbox to get rid of all those unused graphics and whatever else is devouring system RAM. What happened to the days when plugins used to take up a few MB?

[Funkybot's Evil Twin]

The CPU is expected, but X-Gear puts everything including SVX and Fender into RAM and beats out many Sample Libraries for RAM load. Geez..How many people need 40 AMPS and 50 stomps in memory at one time for automation?

Tell IK the Preferences dialog needs a purge RAM checkbox to get rid of all those unused graphics and whatever else is devouring system RAM. What happened to the days when plugins used to take up a few MB?

I agree with this point completely. There are times when I need to start freezing X-Gear tracks because of the RAM usage. Running a few X-Gears in a project with BFD2 and a Kontakt piano library will be enough to bring my 2GB machine to it's knees.

A workaround should definitely be developed to appease both people who need X-Gear to load presets instaneously for live use as well as those who need the RAM freed up for studio use.

[zerocrossing]

The CPU is expected, but X-Gear puts everything including SVX and Fender into RAM and beats out many Sample Libraries for RAM load. Geez..How many people need 40 AMPS and 50 stomps in memory at one time for automation?

Tell IK the Preferences dialog needs a purge RAM checkbox to get rid of all those unused graphics and whatever else is devouring system RAM. What happened to the days when plugins used to take up a few MB?

I agree with this point completely. There are times when I need to start freezing X-Gear tracks because of the RAM usage. Running a few X-Gears in a project with BFD2 and a Kontakt piano library will be enough to bring my 2GB machine to it's knees.

A workaround should definitely be developed to appease both people who need X-Gear to load presets instaneously for live use as well as those who need the RAM freed up for studio use.

BTW, although I work mostly on a PC for music these days, this is one of the non mentioned reasons that the Mac OS is better. I've got 8 gig on an old G5 and it addresses all that memory with no issues.

It's a trade off though... I want and like the way XGEAR responds very quickly and I understand that kind of immediacy takes resources. Maybe you're right, some sort of "I'm not changing gear in this patch anymore" button could be put into the UI which could "freeze" the plug in and let it relinquish resources. If you then needed to add/remove components you could unlock it but suffer the added RAM hit. I personally never use more than 2 instances of XGEAR and I'm not a big sampler guy so I don't experience this problem, but I see the merit in it.

[carltonec]

One thing I am wondering is how 64-bit Windows 7 ready Amplitube 3 will be. I have never had any trouble with Amplitube X-Gear and StompIO under WindowsXP, but after I upgraded the SAME computer to Windows 7 64 bit and installed the latest 64 bit drivers, I am running into all kinds of trouble. I talked with support about one of these issues, and didn't really get help. I had to figured it on my own after giving up on support (no offense Peter). The first issue was that I could create and save presets just fine in x-gear, but when I saved them to a stompIO location, it didn't work. I am talking using the buttons on StompIO to save to a location (for example: 000B) so I can switch between them with the buttons on the board. I asked support and never reeally got help. It seems the problem is with permissions on folders under Windows 7 (I figured this out on my own). I hope this is ironed out in Amplitube 3. I am quite handy with a computer and it STILL took me awhile to set everything right to get it to work. I am still not really sure which setting did it, as I changed it for every folder and file in the IK folder. I also ran into this with 64 bit Vista.

The other problem is much more strange. If I load more than one instance of Amplitube X-Gear (1 for each audio track)in Cakewalk Sonar 8, only one has sound. This boggled the crap out of me because it NEVER happened under Windows XP. I could have a bunch open and switch between them. Is it the 64 bit drivers from IK? I think so. It doesn't happen with other plugins. I found a strange workaround though. If I delete the plugin (x-gear) on the audio track, load Amplitube 2 instead, presto! There is sound on both tracks. Now, this is the weirdest part... if I THEN delete amplitube 2 from that track and re-insert amplitube x-gear, I have sound! On both tracks! Again, I hope this is something I don't have to deal with in Amplitube 3. Although I found workarounds for both, many people may not figure this out. It should be plug and play right from the get go. Normally I would think it was Windows itself, but my other plugins are working fine.

[Peter - IK Multimedia]

Going backwards... did you report that second issue directly to support? I'm sure they can help you. I can get our Support Manager to get the other issue dealt with and lift your disappointment too, I'm sure.

On the 64-bit topic, we're still following the DAW and rest of the industry in general and when that really hits its stride we'll be going along with it. Is Pro Tools 64-bit yet? I'll have to check. But we are definitely following the topic closely and not ignoring it.

[electro]

Going backwards... did you report that second issue directly to support? I'm sure they can help you. I can get our Support Manager to get the other issue dealt with and lift your disappointment too, I'm sure.

On the 64-bit topic, we're still following the DAW and rest of the industry in general and when that really hits its stride we'll be going along with it. Is Pro Tools 64-bit yet? I'll have to check. But we are definitely following the topic closely and not ignoring it.

64bit is a must for those huge Nebula and Orchestral Sample libraries. 32bit WinXP and 4GB RAM can work out if you aren't doing Orchestral or running too many big sample libraries. Amplitube with its current demands changes the equation when you try to run several instances.

I read somewhere Win7 64 isn't even refined enough to get lower latency comparable to XP.