If you're using programmed IA buttons to send messages, don't send messages with the same CC number from the presets. That would likely result in a conflict.
Yes, for sure, if you intentionally want that to happen, then it's ok. Just make sure that you don't have multiple buttons sending conflicting messages, that's usually where problems originate from.
Yes, on your button, remove the System / Tuner action and add actions that turn on input 2 and turn off output 1 (also another that turns off output 2 if you're using stereo outputs).
It's hard to say without seeing your settings. However, a very common issue is caused by the settings Send on Preset Change and Update on Preset Change. In short, these allow you to program an IA button to turn on or off automatically when you change presets, causing the button to send its...
It's pretty likely still be some issue with that pedal, because it only happens with that pedal. Do you happen to have a voltmeter? If so, plug a cable into the output of the pedal, set the meter to millivolts, then measure tip to ground on the other side of the cable when the pedal is on. Any...
That's not going to work because switching loop 5 off will turn off the boost pedal and it'll turn off the signal that goes to the amp's loop return. You'll lose your dry signal when the boost pedal is turned off.
You'll need one loop to switch the boost pedal, then another one after that to...
Poll State is kinda tricky because all the Axe-Fx reports to the GT is which preset it's on. The GT then has to look through its presets and try to figure out which GT preset is associated with the Axe-Fx preset. If more than one GT preset is mapped to the same Axe-Fx preset, it's not always...
CC implementations like that make it hard to control things, because you can't specifically tell it to turn on or turn off, you can only tell it to change.
Maybe the PC is also turning the pedal on? If so, just remove the CC action - maybe it'll work?
Set button mode back to Normal (not hold) - you don't need it to be a hold function. (unless you want a delay before the feedbacker triggers)
Then, add the same actions to the button settings. Turn off all checkboxes except Momentary, which should be on. The action should be a CC Toggle, not CC...
If the KPP is receiving in Omni mode, then that's the cause of the problem - it's responding to MIDI messages for every device. That needs to be fixed on the KPP - we can't do anything about it on our side.
You can skip releases, especially in the later releases when the structure of the settings data doesn't change much from version to version. A big jump from 2.0 or 3.0 to 5.0 would be more error prone.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.