Significant Bug

[GregC]

Thanks but I don't use karma at all. I'm sure everyone wants me to go through the common steps of things that novices might overlook but I've had the kronos a couple years now. This is a system wide bug, apparently, that happened randomly while I was doing very common shallow tasks in sequencer mode with kronos unattached to any other gear or inputs. I appreciate any thoughts anyone has on this. I'll explore further but I didn't want to do too much without seeing if anyone has experienced any similar bugs as mine. So far my conclusions are that the entire board needs to be initialized and my fear is the bug is within the song files themselves rather than the system which means all my songs are useless and a loss. Here's to hope.

You didn't say what OS you are on. If you are on a ver from 4-5 yrs ago, it might be related to a bug going way back.

If your Kronos is current and you are 100% convinced its a bug.
You could wait a few days and maybe Dan @ Korg will have suggestions above/beyond what we have suggested.

You are hearing from folks that use the SEQ for some years. 99% ( or 98%) of what we read on the forum is worthy of trouble shooting.

[etnate]

On further inspection this bug has apparently affected the entire system. In program mode the tempo doesn't change to program tempo and remains at whatever I set it at even after changing from one program to another. Any organ sounds' leslie effect works improperly being a weird combination of both slow and fast at the same time and this is just what I've noticed in a few brief minutes. At this point I think this is beyond the scope of correcting without initializing and reinstalling everything. I've been ill and unable to really dig in but it's becoming apparent that this is a very significant sort of bug. Perhaps I just pushed the board too hard in a weird specific way and it faulted under the pressure.

[etnate]

FYI: Kronos 2, OS is whatever was the most recent one right before the newest one.

[NormC]

Looks like a corruption rather than a bug. Reload factory load.

[SeedyLee]

I'm really interested to try and understand what's going on here.

Any chance you can post a video of the behaviour?

[StephenKay]

On further inspection this bug has apparently affected the entire system. In program mode the tempo doesn't change to program tempo and remains at whatever I set it at even after changing from one program to another.

Did you by any chance set the "Load KARMA settings when changing Programs/Combis" checkboxes in Global to Off? This would definitely affect the tempo as you are describing (Tempo is stored as part of the KARMA settings). So with this off, every program or combi will keep the same tempo as the KARMA settings when this was first turned off (or the current tempo).

Even if you don't use KARMA for anything, you should leave these checkboxes on. However, I don't know how this could affect some of the other things you have reported.

But if this is what you did, it's important to understand what a feature does or doesn't do when activated. These checkboxes do not mean "Disable KARMA". Rather, they mean "keep the current KARMA settings when changing Programs or Combis" (if turned off). Load the KARMA settings (including tempo) that are stored with the program/combi (when turned on).

[etnate]

Stephen, I personally did not turn those karma settings off but the bug I have did so thanks for pointing me in the right direction. Regardless, the bug I have seems to be very specific to me and not a common one as no one seems to have experienced anything like it. The bug has affected the entire OS, changing settings and parameters in ways I can't understand, and unless someone from Korg specifically wants to discuss it further I'm not going to bother discussing it here any more. I'm going to back everything up and initialize the board.