Amplitube 3 - screenshot (from NAMM)

[nix808]

I like the tone of the big pig or Big Muff pi emu. I'm loving at3 and my tele Did you get my mail about the X shaped guitar body Peter?
http://www.bcrich.com/stealth.html

[Peter - IK Multimedia]

Ah yes, I did get that thank you! And I too enjoy the Big Pig quite a bit. That and the Fender Blender get a lot of play around here.

[hibidy]

The only turn off with the pie is it's set so high gain wise (the rat emu is like this too) that you have to jump out of your chair when selecting it at first.

[redshift factor]

The only turn off with the pie is it's set so high gain wise (the rat emu is like this too) that you have to jump out of your chair when selecting it at first.

This reminds me of a feature request I'd like to make: that instead of always defaulting to the same factory settings when a model is loaded, that it defaults to the last setting you had it on. I mean, when I turn on my amp, or plug into one of my Boss pedals, they're always set to where I last left them. So shouldn't the stomps and and amps in AmpliTube 3 be too?

Either that, or the new model should retain the same settings as the one you're replacing when you switch amps, at least with the AT2 style amps.

[Agreed]

The only turn off with the pie is it's set so high gain wise (the rat emu is like this too) that you have to jump out of your chair when selecting it at first.

This reminds me of a feature request I'd like to make: that instead of always defaulting to the same factory settings when a model is loaded, that it defaults to the last setting you had it on. I mean, when I turn on my amp, or plug into one of my Boss pedals, they're always set to where I last left them. So shouldn't the stomps and and amps in AmpliTube 3 be too?

Either that, or the new model should retain the same settings as the one you're replacing when you switch amps, at least with the AT2 style amps.

Man, this seems like it would be a severe pain in the ass. They'd have to store data for every effect to reference its "last state," seems like it would be a headache and frankly not a big deal. Especially since they implemented preset saving.

Give an inch I just use projects for this, I have a few projects that are my default settings for different kinds of sounds and then I roll from there. May or may not be of use to you.

[redshift factor]

They'd have to store data for every effect to reference its "last state,"

What's so hard about that, really?
Most models only have a few parameters each.
AmpliTube could have a simple file for that, not unlike an .ini.

[Agreed]

Nothing is ever as easy as it seems like it would be to the end user, though. Otherwise I'm sure Drag and Drop would have been patched in long, long before AT3's release. If Peter has a comment though I'd love to hear it... But I personally have no problem with the current functionality, and the preset manager makes it kind of a moot point imo. A few short clicks and you're at wherever you want, no big deal...

And, as I said before, when working on a project your settings are saved and loaded back up anyway. I can't think of many situations when I would want exactly the same settings on an overdrive pedal or a tape delay to pop up while everything else in the signal chain is different. It would be not unlike how it is now - requiring immediate adjustment to turn it to a setting appropriate for the new patch, whether by hand or by loading a more appropriate preset.

Physical pedals stay at the same settings a lot of the time because physical rigs stay at the same settings a lot of the time. It's not really the same concept as a modeler; unless you do want to just recreate the same path, in which case the preset manager (individual module, or a whole signal chain preset) covers you.

[poonna]

What's so hard about that, really?
Most models only have a few parameters each.
AmpliTube could have a simple file for that, not unlike an .ini.

It certainly is not that simple. Consider a situation when you have more than 1 instance of AT3 in a project, each of which using same amps and pedals, but different settings. Now, which one of them should be used for as a default when you start another instance?

[Hink]

I'm just guessing here, but I'm thinking redshift factor is talking about while in stand alone mode. Looking at it that way I can easily see both points, though opening a preset is not that big of a deal.

However, I can say that I myself do not always remember to save everything to presest. I also can see myself wanting just to pick the guitar up and jam, opening to the last state can be good in this case. The important thing to remember is that we all have our own work habits and redshift has a valid feature request. It might not happen but I surely understand his point and I do agree it probably wouldn't be that hard to give the user the choice.


In the case of opening more than one instance what is the difference between it going to default instead of your last settings? You're going to change things either way, unless of course you want to open the same thing again then make slight variations to it. Then you're back to a preset, which isn't bad but some may find that an albeit small annoyance, but still an annoyance none the less.

I guess we could go in circles all day

[Agreed]

The important thing to remember is that we all have our own work habits and redshift has a valid feature request. It might not happen but I surely understand his point and I do agree it probably wouldn't be that hard to give the user the choice.

I guess the only thing for me then, apart from the often hidden difficulty of putting in what might ostensibly seem straightforward features, is that I would basically be a dissenter to the feature request, as it would complicate things more for me, so if they do implement it I certainly hope they make it optional and easily bypassed.

[redshift factor]

How is substituting the AmpliTube factory default setting with your own last setting possibly detrimental to you?

But anyways, I thought of an even better way to do it: when you click on a model and get the menu to save or load a preset for that specific model, how about an option for "save as default" and also "restore factory default"?
Lots of guitarists just keep their amps and pedals set to their own settings, and don't really change them. That's what makes their "sound."

[Hink]

The important thing to remember is that we all have our own work habits and redshift has a valid feature request. It might not happen but I surely understand his point and I do agree it probably wouldn't be that hard to give the user the choice.

I guess the only thing for me then, apart from the often hidden difficulty of putting in what might ostensibly seem straightforward features, is that I would basically be a dissenter to the feature request, as it would complicate things more for me, so if they do implement it I certainly hope they make it optional and easily bypassed.

I'm reasonably sure that's what I meant by "give the user the choice"

[Agreed]

Lots of guitarists just keep their amps and pedals set to their own settings, and don't really change them. That's what makes their "sound."

That's what a preset is for, it seems to me I have pedals, used to have over 40 of them, now down to a little over 20 (I'm getting better ), I'm no stranger to how using them works or anything... I just don't see the point of recalling the last settings used for the pedal in AT3. Maybe because I don't think of it the same way as a physical chain - it's a work station for getting the sound for the job. If a previously used sound would work well, great, I'll load the preset. But at best it'd be the same as it is now, for me.

I hope they've got bigger fish to fry, like getting around to all the suggestions we've made in the thread But maybe they will do something like what you're asking (though, again, it's not as simple as just having an .ini, since there are so many possible usage scenarios of AT3 - for example if I have two pedals of the same kind in a row, a trick I quite like for getting smooth crunchy sounds out of overdrives, and they're set differently, what will it pick for the next time it's loaded? Or if there are multiple instances?)

Not trying to shoot you down here, just offering my dissenting opinion. Take it for that and nothing more.

[redshift factor]

Agreed, this revised method I mentioned last post would solve all of the issues you brought up.

But anyways, I thought of an even better way to do it: when you click on a model and get the menu to save or load a preset for that specific model, how about an option for "save as default" and also "restore factory default"?

[Agreed]

Yeah, that'd be a good way to do it if they decide to - wouldn't step on anyone's toes but it would help people who use the same pedal in the same way each time do their thing without loading presets.