This involves using Amplitube Leslie as a live substitute for a plug-in’s internal rotary in Mainstage.
What’s happening to me is that in Amplitube 5 standalone I set the Leslie speed to respond to CC1-mod wheel and in the lower left, the midi light blinks yellow. Everything worked great. On the advice of someone in the forum I mapped and saved a preset with the correct CC and parameter settings for midi and automation. When I open it in a DAW (Cubase for recording, Mainstage for live) to use as an insert effect, the midi icon remains gray and doesn’t respond to any midi input whether it’s using a controller or responding to pre-recorded midi data. The issue seems to be limited to DAWs since in the Amplitube mapping area CC 1 is correctly mapped to Leslie speed - and it works in standalone. I can record automation for Leslie speed in Cubase but I can’t use a wheel, pedal, or button to control the virtual lever. I either need to draw it in or use a mouse to toggle speed.
The other thing is, and more importantly, shouldn’t the yellow midi light in AT5 or the red one in AT4 be actively lit in my DAW, the way it is in standalone, to tell me it’s receiving midi info? Just to eliminate Leslie as an issue I tested both ATs out just using the default guitar setup trying to map an amp knob with a mod wheel. Again, it worked perfectly in stand alone using right click midi learn. In any DAW however, when I right click on the same default amp in either AT, the pop up appears but doesn’t sense any midi activity no matter what controller I move and the midi indicator light remains dark.
Any ideas? Has anyone else experienced this with midi only active in standalone but not in an DAW even though the mapping is correct (though I think that the indicator light should still be showing activity). Odd that it happens in every DAW I have (Cubase, MS, and Live). Could it be something squirrelly with my computer? Thanks