Amplitube 3 - screenshot (from NAMM)

[Hink]

I ran, all in Samp 11 pro at once

AT3 2 Marshalls>2 4x12s
GR4 2 Marshalls>2 4x12s
GTR3.5 2 Marshalls>2 4x12s
Vandal Lead> 4x12
xt live Marshall>4x12

od stomp on each but no other fx, no eq

Samp had the multiband enhancer on with the maximizer at about 75% (the three bands were bass mono, mids slightly expanded and the highs full expanded), plus the new delay from essential fx in Samp at about 380ms, very little feedback (ping pong) and the mix very low. My buffers were at 256, core 2 duo e6700.

There was a little latency but not enough to stop my fun (wouldn't want to record at that setting though), no issues at all. I had everything panned a little different from wide to Vandal being in the center. Of course this is unrealistic for practical use but was a great way to have fun.

I did solo different models, spent about an hour and a half on it and tbh none were my favorite and none were disappointing, little tweaks here and there when soloing amp sims always gave me something interesting. That's just using all Marshalls, imagine all the models I have and the endless possibilities, not to mention my amps.

Bottom line, I can see AT3 being my go to for re-amping but not exclusive. I do think it does bring the most to the table, but each has it's strengths. Vandal is very cool but a much different concept, tbh it could be my go to as well and I suspect I'll use them all a lot (including changing sims on one track many times)

If I had to give them all up but one I would surely choose AT3 because it offers so much in one package.

[badmotorfinger74]

I'm not sure if this has been answered yet, but in order to use the StealthBoard and StealthPedal together, you would just connect them both via USB. You wouldn't need to connect the StealthBoard to the external switch input on the StealthPedal, correct? Also, are there any plans to offer the StealthPedal without Amplitube software for people that already have it? I've been considering getting the Apogee Gio for controlling Mainstage (with Amplitube as a plugin, but may go the StealthPedal/Board route instead.

[dimitar]

Speaking of strings, I love Elixir Nanoweb strings. I change them in 5-6 months. Of course I'm cleaning them with Fast-Fret.

[Peter - IK Multimedia]

I'm not sure if this has been answered yet, but in order to use the StealthBoard and StealthPedal together, you would just connect them both via USB. You wouldn't need to connect the StealthBoard to the external switch input on the StealthPedal, correct? Also, are there any plans to offer the StealthPedal without Amplitube software for people that already have it? I've been considering getting the Apogee Gio for controlling Mainstage (with Amplitube as a plugin, but may go the StealthPedal/Board route instead.

I will need to get more information as we approach release but as an example we were working with doing BOTH of those things at NAMM. For best programming and control functions, you'd hang the StealthPedal off the StealthBoard as a controller AND have both hooked up via USB though in the StealthPedal's case you'd only do that for the audio interface functions.

Again, this is not final spec and I will have more information as we approach release.

[Hink]

Speaking of strings, I love Elixir Nanoweb strings. I change them in 5-6 months. Of course I'm cleaning them with Fast-Fret.

clean them? What an interesting idea

Seriously, I've tried that fast fret (but I think that was at least 25 years ago) and I found it made the strings too slipery and caused me to slide past where I wanted to be.

It's an interesting comparison because I don't think either one of us is known for being sluggish guitarists. I do a thing I call rolls or spider hopping (for lack of a better term) open>1>4>open>1>3 (sometimes picking sometimes not) repeated a lot and moving different intervals along the neck and across strings (depending on the tuning that can be across two strings open>1>3 on one and open>1>4 on the other altenating, use to be an exercise for me).

When I start taking off (spider hopping) where I stop for each change in interval is critical and fast fret caused me to slide by my stopping point. In open tunings I often use a back pick from my highest string to end it by dropping the base of whichever finger I'm ending on as a bar. Again this is really an exercise for warming up or, just plain fun or testing a tone.

But I just could never get use to fast fret, I don't care for gorilla snot either

[Oscat01]

Hi all
I relented and got it even though not 64 bit, -- deal was to good and sound to wonderful.
I am using it with Cubase 5.1.1 64 bit with jbridge + TC electronic 24D.
In my case it does use slightly more than X-Gear, but not so much as to worry about. Running 9 active tracks with plenty of headroom. About 15% higher usage then with X-Gear. Jbridge also runs in optimised mode as it did with X-gear.
I did however have a problem getting two channels of input into the vst.

1. Set up interface so guitar is on a mono input channel
2. Create a New Project in Cubase 64
3. Add an audio track choosing mono
4. Add Amplitube 3 as an insert and bring up interface.

Now the problem for me is that in 64 bit cubase when i look at the input meter (bottom left) on the Amplitube 3 interface I only have one channel of sound. Not two as expected ? and volume is reduced.

If I do the same in 32 bit cubase there are two channels of sound.All works as expected --- Mono input, mono track with AT3 showing two channels as it does in stand alone mode as well

Work around for 64 bit is in step 3 pick stereo instead of mono when adding an audio track even though in cubase Vst connections inputs still shows two mono ins and a stereo out and the inspector shows mono in.

Once I got it working Wow fantastic, though the idea of just replacing X-Gear
instances with AT3, well tweaking will be necessary especially with two or more inter-playing guitars and having replaced X-Gear if I record using AT3 I have to reduce gain by 8 db to have same volume as recorded X-Gear.
Some folks in the past have said they do not like X-Gear for distorted sounds due to "rice on tinfoil artifacts", and even though overstated I knew what they meant, this does not happen in AT3, it is far better now.

The Vst and stand alone now sound very similar (remembering to set input gain to 0 in standalone) this was never the case for me with X-Gear or any of the Amplitube 2 serise.

So far my feature request for the first update for AT3 standalone would be
1. An option to load a project at start up rather than the default. Having to reload a preset every time I open it just seems long winded.

2. That presets for Amps, pedals etc have say AH, AM, AT2, SVX, AF next to them, so idiots like me know what's what.

3. Not important but some Skins or alternative Gui buttons, I am not a fan of the way it looks, especially the recorder section, it somehow needs better definition. Amps Cabs etc all look great, but the surrounding control section could be better. All this is minor when I listen to how it sounds.

Only my take on it and it's a very short list but 1. and 2. would make it more user friendly.

Tc electronic really dampens single coil pickup feedback from the SD Texas Hot Antiquities in my self built strat, Had to replace Emu because it increased it, now with AT3 I am one very happy man. Now all I want is Native 64 bit.

If anybody else notices one channel sound issue, I have emailed Joao (jbridge), please post because I don't imagine so many people will be using it Jbridged in Cubase 64 and I always wonder if it just a problem I have

There's a marketing opportunity for week old bedded in strings with temporary brightness removed,

[Restless]

If anybody else notices one channel sound issue, I have emailed Joao (jbridge), please post because I don't imagine so many people will be using it Jbridged in Cubase 64 and I always wonder if it just a problem I have

what do you mean with a one channel issue? Is that the input? Unless you have a stereo guitar there will always only be one channel going into amplitube. Doesn't the same thing happen with any stereo amp sim?

[Oscat01]

If I do the same in 32 bit cubase there are two channels of sound.All works as expected --- Mono input, mono track with AT3 showing two channels as it does in stand alone mode as well

So no it is not correct, M speaker for mono is equally split down left and right channels normally.

[Undercoverman]

I am disappointed by the lack of automation available for stereo routing (as in, cannot assign more than one variable to a parameter). This makes tweaking stomp FX in stereo a little more difficult than it needs to be. I would very much like this to be a feature available in the future. Any chance, Peter?

Ran into that, too.
Simple task : bypass two stomps (OD and delay) and switch both on for the solo - you need two automation lanes for that.
I could imagine a matrix would be ideal, simple as it gets, quick and quite effective. Just click the dots ...
Ymmv,
susiwong

I use the automation function with the remote control aspect of Cubase - the adjustment of automation lanes (clicking dots) just don't cut it for practical, real-time control when coupled with a hardware controller (like the BCR2000, which I use). And that's assuming that I use them only for solos - the beauty of automation is that you can use it to record what would ordinarily be a completely impractical style of performance. Slowly adjusting an ambient soundscape, for example, is incredibly difficult without hands on control. It's not as though I arrive at my preferred settings, then just turn them on or off. I record the sound as it evolves - I need to record the tweaking.

Again, it's difficult to do this in stereo. Not impossible - but it requires me to map twice as many variables to my control surface, and if I'm to affect the stereo image evenly, I have to be very delicate in adjusting the variable on L and R at the same time.

Peter, any chance that this feature could be added at some point?

[deanx]

So far my feature request for the first update for AT3 standalone would be
1. An option to load a project at start up rather than the default. Having to reload a preset every time I open it just seems long winded.

2. That presets for Amps, pedals etc have say AH, AM, AT2, SVX, AF next to them, so idiots like me know what's what.

3. Not important but some Skins or alternative Gui buttons, I am not a fan of the way it looks, especially the recorder section, it somehow needs better definition. Amps Cabs etc all look great, but the surrounding control section could be better. All this is minor when I listen to how it sounds.

Only my take on it and it's a very short list but 1. and 2. would make it more user friendly.

And the ability to use WMA'a in the speed trainer like is says in the manual. I've had it confirmed from tech support that although it says the speed trainer play MP3, WAV, AIFF and WMA it doesn't actually do WMA.

I'm hoping this will be included in the first update patch. It's availble in X-gear so hopefull it can be done.

[Oscat01]

It should play WMA files if it says it does, though I imagine this will be a bug fix and should be dealt with asap. PITA but obviously conversion is the workaround.

Also to add to my feature request
That Input Gain remains where we put it, though this may tie into loading a personal project rather than the default.

Input Gain and where it is set has always puzzled me slightly, when presets are developed where should it be set and if it's above 0 then are these presets going to sound as they should when used in a DAW at 0db.
It is all very subjective, when you consider Pickup type, audio interface and the rest. I would always have expected it to default to 0db but for me it's +6db.
If anybody knows why it is set +6 db it would be intresting to know, there must be a reason ?

[Peter - IK Multimedia]

I am disappointed by the lack of automation available for stereo routing (as in, cannot assign more than one variable to a parameter). This makes tweaking stomp FX in stereo a little more difficult than it needs to be. I would very much like this to be a feature available in the future. Any chance, Peter?

Ran into that, too.
Simple task : bypass two stomps (OD and delay) and switch both on for the solo - you need two automation lanes for that.
I could imagine a matrix would be ideal, simple as it gets, quick and quite effective. Just click the dots ...
Ymmv,
susiwong

I use the automation function with the remote control aspect of Cubase - the adjustment of automation lanes (clicking dots) just don't cut it for practical, real-time control when coupled with a hardware controller (like the BCR2000, which I use). And that's assuming that I use them only for solos - the beauty of automation is that you can use it to record what would ordinarily be a completely impractical style of performance. Slowly adjusting an ambient soundscape, for example, is incredibly difficult without hands on control. It's not as though I arrive at my preferred settings, then just turn them on or off. I record the sound as it evolves - I need to record the tweaking.

Again, it's difficult to do this in stereo. Not impossible - but it requires me to map twice as many variables to my control surface, and if I'm to affect the stereo image evenly, I have to be very delicate in adjusting the variable on L and R at the same time.

Peter, any chance that this feature could be added at some point?

I know this has taken a little while... I'm wondering if you are using a controller that can send MIDI, and I do recall someone else being able to do this, that you can't use the right-click MIDI learn to assign multiple tasks to one control? I can do that to do exactly what is mentioned - bypass two stomps at the same time. Would that not suffice? You could definitely assign a neat set of changes to one control and do some really interesting things this way. I think the other example where it was successfully used was a more "practical" guitar use like two volume pedals with the same control so that both sides of a dual rig were able to have volume controlled from the same pedal.

[Undercoverman]

Hi Peter,

Thanks for getting back. One of the advantages of using the automation functions that are inbuilt into a DAW compared to MIDI is that the DAW will always send automation information back to the controller. This comes in particularly handy with a BCR2000. What do I mean by this? Well, take a look at this video on youtube:



This is a BCF2000 rather than a BCR2000, but the principle remains the same. The controllers are responding to automation data returning to the controller through the 'remote control' section in Cubase's device setup menu. The advantages of this are three fold:

1) Because Amplitube (the VST) does not output MIDI data, when a change of patch occurs, all of the parameters to which I have assigned a knob or button on the BCR2000 will not update (LEDs in the correct position) if I use pure MIDI. They will remain where they are for the previous preset. If you assign controllers to respond to automation, they will automatically grab the relevant data and update automatically - allowing you to always see, at a glance, what your controllers are doing and it eliminates the possibility of a controller 'jumping' when you move the knob. Automation is always preferable over MIDI for this very reason - without it, your controller will not update.

2) If properly adjusted in Cubase, you can set your controller to grab the data for the selected track - allowing you to simply choose a track and the controller will grab all of the automation information automatically. This is a massive time saver, as all of your adjustments will appear on your controller immediately, removing the need for you to sit and get everything in line before you start tweaking.

3) Because everything corresponds between the VST and the controller, any adjustments made with the mouse in the VST are reflected in the controller. Tweaking, say, a phaser's depth with the mouse will move the LED around the knob assigned to that paramter on the controller. If you play your project, which includes automation, you will see the LEDs (or faders, as in the example video above) moving according to the changes you made as you went along. This is particularly useful to see where you made changes, and you can always dive in and change something as you go along. Of course, the pratical applications of this are not just limited to VSTs - you can do effective mixing this way without the need for a Mackie control by assigning the faders to your tracks' volume controls etc. Anything you want, really.

Sorry for the long winded explanation Peter, but this is the reason as to why automation is so important to me and (I should imagine) anyone else who uses a controller with LED feedback like the BCR. Lots of MIDI controllers nowadays are using motorized faders or LED rings around their encoders purely for this reason.

Unfortunately, you cannot assign more than one automation parameter to one MIDI input in the device automation setup of Cubase - that was the first thing I tried! At the moment MIDI is the only way to control two parameters at once, but you lose all of the advantages of automation which I outlined above. Some VSTs DO output MIDI, but not Amplitube.

[Peter - IK Multimedia]

Ah yes, I understand that. I had misunderstood thinking you DIDN'T want to use automation, when in all you just didn't want to draw lines and plot dots

[Undercoverman]

Haha, yeah. I find that when you're making music with a computer, it helps as much as possible to try and find the closest approximation of using the hardware which your software is modelled on. When you combine that with the sorts of advantages available to you through the computer, namely automation, you get the best of both worlds.