Amblitube and MIDI controll - how?

[Fever]

Just to add to this thread, I've been having issues myself with Amplitube, but it in a slightly different way.
I am using a standard midi controller, which works well with X-Gear and the integrated "Learn" function for anything within the normal Midi CTL parameter list provided:

• Preset Next
  Preset Previous
  Stomp A slot 1 through 6
  Stomp B slot 1 through 6
  Volume
  Wah
  Wharmonater

It seems all we can do is toggle pedals or adjust volumes.
How do I control other Amplitube parameters through Midi? Like:

• Amp knobs (gain, bass, treble...)
  Pedal knobs (for compressor level, overdrive gain, etc...)
  Cab Mic Models?
  Rack effects?

Any ideas? That would be greatly appreciated...

[ajw31]

Harry_HH, please PM the email address you used for your support request so I can get this sorted. Thanks!

This is a message (and a Christmas present) for all the Live + X-Gear -users.
As you can read in this thread, about a month ago I posted question concerning the MIDI automation of the Amplitube X-Gear inside the
the Ableton Live (Live8 ). I also tried to get help from the IK support -
first thy told me that my official request (request #413089) was lost in their system, then about two weeks ago I got a message where they regretted not having time for my problem but promised to start working with it soon. So far I haven't got any answer from the IK support. Because any of the KVR Forum member hasn't had any solution either, I presume no one has known how to use the external MIDI controller to move any Amplitube, e.g. the wah pedal with the MIDI expression pedal inside the Live. (!?) And I think this is quite a relevat feature, don't you?

Now - here's the solution! Thanks to the great Ableton tech support's Michael Duehr:

1. Load Amplitube XGear
2. Load Wah FX into STOMP
3. Open AUTOMATION window in the Plugin GUI
4. Select the WAH Parameter of the Wah FX and press ADD to activate the Host automation
5. In Live, activate the MIDI Learn function and and select the Plugin Parameter in Live6. Move the MIDI Pedal, then deactivate Live's MIDI Learn READY!

(As you can see, this is not what the X-Gear manual offers as a solution).

Be my guests, I want to share this information with the KVR memebers, that's why these Forum are. This information may be useful for the IK support,too.
(IK may even sell a couple more products when the potential clients find out how versatile the X-Gear is). BTW, I think that Amplitube/X-Gear is great product.
Michal even sent me attached screenshot pictures of the procedure,
those who have the same dilemma which I had and can't solve it according to the information above, send me a pm and I incude Michal's screenshots to you.
I'm sure Michael don't have anything against this.

Happy Xmas and Great New Year, for everybody.

Harry

It's a few years further on but this post has just helped me sort out the same issue of automating Amplitube within Live 8. Thank you for your patience trying to sort it out the first time and then posting a detailed solution. I agreed with everything you said about the difficulty of getting good support. Not just IK Multimedia, all of those big companies are just as difficult to get quick responses and solutions from. And they always start by treating you like an idiot.

ajw

[wasi]

In Live, to get midi learn to work within an audio effect, you have to first create a separate midi track, choose your external footpedal as midi in device on that track and route the 'midi to' to the audio track with the effect you want to 'midi learn'.

Live's audio tracks can't reiceive midi directly. You have to route it into them from a dedicated midi track. It's a limitation of Live, or rather, a manner of implementation. I usually afterwards group the audio and the controller's midi track.

[ajw31]

In Live, to get midi learn to work within an audio effect, you have to first create a separate midi track, choose your external footpedal as midi in device on that track and route the 'midi to' to the audio track with the effect you want to 'midi learn'.

Live's audio tracks can't reiceive midi directly. You have to route it into them from a dedicated midi track. It's a limitation of Live, or rather, a manner of implementation. I usually afterwards group the audio and the controller's midi track.

wasi, thanks for your suggestion, I tried it but without success. The track I have the effect on is a MIDI track, not audio, not sure if that makes a difference. I understand the concept you describe, I've used it to route MIDI before with other plugins (one of my recent favourites Cthulhu for instance). Others have had issues with Amplitube and MIDI learning, so maybe it is something to do with this particular plugin?

[jancivil]

wow, age-old thread but I'll use it rather than make a new one.

at ca. 4:19 here, the MIDI implementation is shown. However, this is idiotic. This will, supposedly, assign one physical controller to *a slot*. Typically what I load has several parameters in a *slot*. Which one is it? You've got to be kidding us.
As it happens, I have the exact controller displayed here. This does nothing at all to the intended slot.

I use the automation parameters and draw values in a project window lane usually; additionally the Stealth Pedal seems to work. Beyond that I can't recall anything else working with it MIDI-wise. I am not at all new to midi control. I'm not one to dwell on shit that doesn't work, I got on with it via the other ways.

It should be noted that not every parameter I have automated actually responds to it. Almost always it does but I think some of the FX have features that are broken. I would have to go back to the template and test it and I'm not gonna. For these and a number of serious problems I encounter with it in Vienna Ensemble Pro (and that is the way I host plugins, full stop)*, my confidence in this line is too low for me to spend anything more on it. NB: I have every single piece of AT2.

*: I took out a ticket to tell youse that AT3 will immediately crash VE Pro using the menu browser. This has been reproduced on other people's systems, it is not unique to me. It works in no version and never has. The other issue is XGear fails to process what it's given, around half the time, causing me to reinstantiate. I have automation assigned and evidently XGear does not recall anything in a save so I'm reinstantiating the project and when that fails quitting and reinstantiating the larger frame, when that fails I'm rebooting. After a couple of the other fails I'm liable to have to reboot if I'm using a lot of memory, OSX holds out to memory. I have actually run out of 24GB of physical memory forced to reload frames with XGear in it due strictly to it repeatedly failing to work. An alarmingly high % of the time it fails from the outset. It fails during renders. (I'm a pretty serious user so do not tell me it's my management of my machines.)

I'm not going to follow the AT3 problem, I don't have it installed any more, and frankly I expect to have to work around the other shit unto perpetuity. But these issues should be known to you and known here.