AK Permanent track mutes issue - Update on how to fix it!

For reasons I haven’t discovered yet (haven’t been able to replicate the issue) my AK entered an abnormal state in which the seq trigs will always act as track mutes when not in recording mode.
In this state:

  • The bottom left portion of the screen shows the track mutes graphic, even when not in performance mode
  • The first 6 seq trigs (when not in recording mode) effectively act as track mutes, regardless of being in performance mode or not
  • When not in recording mode it is NOT possible to change patterns. If any of the bank buttons is pressed the screen changes to the proper pattern change animation, but upon hitting any of the seq trigs nothing happens. The only way to change patterns is to enter recording mode and then proceed to hit a bank button and then the desired seq trig

HOW TO FIX IT
Since I haven’t been able to replicate the issue I can’t be 100% sure this is the proper way to fix it, but here’s what I did that solved everything:
Save the current project.

That was it. As soon as the current project was saved the problem went away. As a side note, before saving the project I backed up all my kits and patterns, so sysex dump actions can be performed if you ever enter the aforementioned abnormal state

Try the test mode, see manual, to check the state of things

Maybe try loading a new project (once existing one is backed up if possible) in case the current one is borked

Thanks for the reply.
Yup, I’ve just thought of the test mode, will enter that as soon as I get my hands on the AK.

Now, supposing it’s the project that’s broken, can I still get my patterns and kits out of there? This project is my main project as of now, everything I’ve been working on is in there, and I have’t performed a backup…

who knows ? but certainly worth doing first before anything else IMHO - as that’s the most irreplaceable aspect

either way, if you get to the bottom of it (or not) at least you’ll have a backup of your time spent

For future reference I’ve edited my op with a more streamlined description of the issue I ran into and how I fixed it :slight_smile: