Tap Tempo activates Stomp A ??‍♂️??‍♂️

Quote from petezoom

Hi I just update my Kemper,

BUT my Tap Tempo activates the Stomp A of the unit ?

Any ideas of what can I do ?

Thanks for your time ???

I’ve seen a few people on Facebook having this issue. You should open a support ticket to make sure Kemper is aware of it. This will likely be a very quick fix.

It looks a Release bug to me.

In System Settings, Remote Buttons, select Button Assignment.

You can restore the “Tap” function to the button on that screen.

In case no one else has yet, I have reported this to Support.

You're welcome

And, Welcome to the Forum!

Fixed in OS 7.2.2.

I’m running 7.2.2 and the problem still exists but I manually switched it off and now it seems OK.

someone else explained this nicely in another thread yesterday. As the bug in 7.2.1 left profilers with the Tap wrongly assigned, the KPA would have no way of knowing what state your KPA was in prior to 7.2.1 when you installed 7.2.2. Therefore, it would just leave it in the state it encountered rather than changing everyone’s to Tap tempo as some may have been set to Stomp A on/off deliberately. That explanation was a lightbulb moment for me ?

If you experience that issue, just enter System Settings page Remote Settings sub-page Button Assignments and reassign TAP to TAP button.

Quote from Burkhard

Fixed in OS 7.2.2.

Burkhard, any idea when the “E” glitch will be fixed? I’m using the most current release 7.2.2.16146, and for the last 3-4 firmware releases, the “E” that indicates that the rig has been edited, shows up on EVERY rig, even if it hasn’t been edited. I’ve tried everything (restarting, saving a rig, saving performances, etc.) and the E shows up all the time. I’ve submitted a support ticket and it was acknowledged last week, but still no resolution.

An "E" glitch is not common.

The "E" is normal, if a Rig is stored in old file format and gets automatically migrated when it gets loaded. This can be permanently "fixed" by a simple Store/Replace, which stores the Rig in current file format. I just have user data on a PROFILER in front of me, where that works like a charm.

"E" is also normal in current OS, if Modules or Sections of the signal chain are locked. The "E" indicates, that the signal chain you see and hear is not identical to the Rig you loaded and as it is stored. It is practically edited. If you Store/Replace the Rig in this situation, it will be changed. This behavior has changed compared to earlier revisions, but you could argue the "E" is appropriate in this scenario.

Burkhard

if the Input Section is locked, the E will appear for every Rig?

No, the Input Section does not indicate the ‚E‘ (at least in OS 7)

What I wrote applies to Module A-REV.

Thanx for this, it is doing the same thing on mine. Will change it via the system settings today.

Quote from Burkhard

An "E" glitch is not common.

The "E" is normal, if a Rig is stored in old file format and gets automatically migrated when it gets loaded. This can be permanently "fixed" by a simple Store/Replace, which stores the Rig in current file format. I just have user data on a PROFILER in front of me, where that works like a charm.

Thank you Burkhard. I think this must be what happened to mine because it was never a problem before - and then around 3 firmware releases ago it started and has been the same ever since. Can you further explain what you mean by a store/replace fix? Is this something I'd do in Performance mode? Thank you.

Quote from OhG

Thank you Burkhard. I think this must be what happened to mine because it was never a problem before - and then around 3 firmware releases ago it started and has been the same ever since. Can you further explain what you mean by a store/replace fix? Is this something I'd do in Performance mode? Thank you.

i think he means, once you have changed it in the settings, hit the “store” button, then select replace. ?

Tried it and confirmed - works. Thanx!

Quote from barryhugo33

I don't think that's it Barry. I never changed anything in my settings to begin with. This began happening to me 3 firmwares ago and I've never touched the tap/tempo settings. The way I read Burhard's comments is that this is something that has to be done by replacing a rig through a save feature, but I'm not what he meant.