Weird Sustain Pedal Bug

xtatty · Post by **xtatty** » Tue Apr 17, 2012 10:15 pm

danatkorg wrote:If it's an intermittent short in the cable, then it will work exactly as you describe, popping up once in a while. Very slight changes in the relative positions of the pedal, cable, and keyboard may affect whether or not it happens. Last year, I had exactly this issue with a sustain pedal.

Thank you for the answer Dan. Really appreciate the help.

When the problem occurs one key (note) stucks and keeps sounding ceaselessly.
While this is happening i am able to play other notes and use the sustain pedal normally.
I tried playing many keys together in order to overrun the polyphony and make it stop.
The older keys i played mute due to the polyphony but that particular stuck key never stops!
So i think it is more than an intermittent short in the cable.

Also i used the same pedals with M3 and the Triton Extreme for many years and i never had this problem.

danatkorg · Post by **danatkorg** » Tue Apr 17, 2012 10:40 pm

xtatty wrote:
danatkorg wrote:If it's an intermittent short in the cable, then it will work exactly as you describe, popping up once in a while. Very slight changes in the relative positions of the pedal, cable, and keyboard may affect whether or not it happens. Last year, I had exactly this issue with a sustain pedal.
Thank you for the answer Dan. Really appreciate the help.

When the problem occurs one key (note) stucks and keeps sounding ceaselessly.
While this is happening i am able to play other notes and use the sustain pedal normally.
I tried playing many keys together in order to overrun the polyphony and make it stop.
The older keys i played mute due to the polyphony but that particular stuck key never stops!
So i think it is more than an intermittent short in the cable.

In that case, this has nothing to do with the hardware sustain pedal or any software related to processing the sustain pedal. (Earlier you write that you've only noticed this when the sustain pedal is connected, but I expect that will turn out to be a red herring.)

If other notes are stolen while the stuck note remains, that means that the system thinks that the key is being held down. This might happen with a MIDI loop, for instance, if MIDI (including USB) happens to be connected. There might be other causes as well.

My recommendation is to contact your Korg Distributor's tech support department; they should be able to help you get to the bottom of the issue.

- Dan

.Jens · Post by **.Jens** » Sun Apr 22, 2012 4:23 pm

Confirmed here, this never happened before 1.6 to me. Nothing else connected than a sustain pedal - there are single stuck notes from time to time, especially (seems so, at least) with CPU-consuming combis (many voices).

@Korg: This really looks like a bug in the new OS. It happens to different keys, and at least with one orchestral combi (brass + strings) I had only one of the voices (woodwind) that would sustain, while all other voices on the same key went silent as supposed on key release. That can definitely be no hardware issue.

Jens

danatkorg · Post by **danatkorg** » Sun Apr 22, 2012 6:47 pm

.Jens wrote:Confirmed here, this never happened before 1.6 to me. Nothing else connected than a sustain pedal - there are single stuck notes from time to time, especially (seems so, at least) with CPU-consuming combis (many voices).

@Korg: This really looks like a bug in the new OS. It happens to different keys, and at least with one orchestral combi (brass + strings) I had only one of the voices (woodwind) that would sustain, while all other voices on the same key went silent as supposed on key release. That can definitely be no hardware issue.

Jens

Possible, but I use the Kronos daily and haven't seen the problem.

Name a specific sound or two, and we can look into it. Note that this is not an official Korg support forum; if you need to communicate directly with Korg for any reason, please contact your Korg distributor as usual.

.Jens · Post by **.Jens** » Sun Apr 22, 2012 7:00 pm

Thanks for the quick reply, Dan.

This happened a few times today (but not always reproducible) with Combi U-G 000 Orchestra & Timpani EXs3 (from the "EXs_Extras/EXs3 Brass Woodwinds.PCG" - EXs3-samples are completely loaded).

But the same happened to a single AL1-Patch I created on my own (hanging single notes).

The behaviour is almost exactly like a lost MIDI note-off command, like in ancient times when you had to press the PANIC button often in a performance because of stuck notes

SPAB · Post by **SPAB** » Sat Aug 24, 2013 1:10 am

Hello everyone,
(first post in the Korg Forums !)

I recently bought a Kronos X88, and I am really happy with it, there is one thing bothering me quite much though :

Pretty randomly (and rarely) a single note sustains itself, often when using a lead sound.
Well, in a nutshell, pretty much the exact same thing as what xtatty explained it in his first post of this topic :

Once it occurs, it stops only by changing the patch 2 times or switching to a different sound and switch back.
And it continues doing that with several other patches. The only way to stop it completely is by rebooting.

I can bring you more informations if you want, but is there any fix or update I can make to solve this problem ? (I received the Kronos already updated to the 2.0.6 OS)

Thank you !

P.S. : sorry for bringing back this problem again, but I've made many researches around the internet and it seems that this problem is no longer topical, and since I haven't found anything that can help me ...

amosdef · Post by **amosdef** » Sun Aug 25, 2013 3:28 pm

I can confirm this intermittent problem as well. When can get back to my Kronos later this week, I'll post the sounds that get stuck. It seems to happen in certain combis, so it could be related to just a few sounds (mostly leads)

I was thinking possible midi loop as I have a 2nd controller hooked up to it, but it mostly happens while playing on the Kronos' keyboard. Hitting the midi panic button on the external midi controller doesn't stop the sound either. I have to cycle through 2 other combis in setlist mode before the note shuts off. A power cycle seems to help when it does happen, but it's hard to troubleshoot while performing a gig and usually doesn't show up again for weeks if not months. Very inconsistent and frustrating issue.

SPAB · Post by **SPAB** » Fri Aug 30, 2013 1:56 pm

Thanks for replying.

Ok so I played a lot out of my kronos last week and the problem remains.
I did some tests when the problem happened, here are what I found :

- The combination "I-C066 Dyna Slow/Fast Orch" once triggered the sustain on the middle E. When this happened, the sustain remained on most of the lead sounds I was using like "I-A109 Simple Saw Lead" and even some E. Piano "I-B039 Layered E.Piano pad".

- The only way I found to stop the sustain (besides switching the program/combination twice) is simply to enter the "Global/Wave Seq" menu. Don't know why, but most of the time, the problem dissapeared after getting in that menu. Sometimes it triggered again while playing the "corrupted" program though *sigh*.

- The randomness of this "bug" is pretty incredible. Once, the note got stuck, I switched the Wave seq menu, got back, problem no longer here. I played a bit, problem here again on the same key. Oh, yesterday, the sustain jumped from a E to a A.

- Some sounds seem to be "victim" of the sustain and other "trigger" (and also victim) of the sustain (see above, the orchestral patch triggered it, and the lead sounds were stuck ; after resetting using Wave Seq menu, no problem with leads until I played the orchestral patch)

- Hard (impossible ?) to replicate. Right now I'm doing my fanciest orchestral clusters with sustain, no problem.

Two last things :

- My kronos is pretty new and for the moment I didn't make my own sounds from scratch (only splits/layers out of the existing programs).

- I'm 99% sure this is not a "hardware" related issue, I'm using kronos sustain and switch pedals (sustain pedal from the PA588 -can be an issue ? i doubt it- and the PS3), nothing else plugged in beside headphones/audio output.

Thank you for anyone who read all of the above, and sorry for all the spelling/grammatical mistakes.

Maybe I'm missing something, doing something wrong, should I reinstall the O.S. (already in 2.0.6), I don't know... Everything's fine apart from that...

Rosen Sound · Post by **Rosen Sound** » Sun Sep 01, 2013 4:45 am

I have had the same issues and was able to re create it. I have posted a few threads about it and I have been in contact with korg about it in the past. Instead of resetting he kronos every time it happens: go to sequencer mode, pull the drop down menu down and click initialize song and then "ok". this is similar to a panic button on the kronos for some reason.

heres my thread

http://www.korgforums.com/forum/phpBB2/ ... 067aeae0db

since this all started, if i do a lot of heavy editing on my kronos (programming my bands new songs and adding to set list etc) i will eventually come out with a stuck note and have to "initialize song"

I do wish that in the next update, this bug is fixed because it basically renders using sequences in my setlist useless.

db1 · Post by **db1** » Sun Sep 01, 2013 3:49 pm

It happens to me also. Most of the time when i'm playing a bass or lead program in combi mode. The way for me to make it stop is to switch to another program, then back again. If it keeps happening, I have to robot then it goes away.

Really sucks when you are working on a project & you have to wait for the Kronos to reboot again. It messes with my creative flow.

Nightale · Post by **Nightale** » Sun Sep 01, 2013 4:17 pm

Got the same issue, randomly appears, but tends to appear more with orchestral combi and lead sounds....

amosdef · Post by **amosdef** » Thu Sep 26, 2013 5:34 pm

Just had this happen again at my gig last night on a lead sound in a combi (didn't remember to look it up) It's the first time I remember it happening on this particular combi, but I will see if it's the same sound as some of the other combis that I've seen this bug happen on. I hope this is something that can be fixed as it is tough to deal with when it happens.

rickster1 · Post by **rickster1** » Fri Sep 27, 2013 2:23 pm

I have also had this happen, but lucky for me it's happened at home and not on a gig. To have it happen on a gig and have to reboot for two and a half minutes would not be fun. Re-booting seems to be the only way to stop it.

amosdef · Post by **amosdef** » Fri Sep 27, 2013 2:43 pm

One thing I am noticing is that it seems to trigger when I play at or above the C above middle on the 61 key keyboard. I'm pretty sure it's the actual C note that gets stuck almost all of the time. I may switch up my problematic combis to avoid this range for the lead sounds and see if that helps. I have some time off soon and should be able to troubleshoot it better soon, but with it happening so sporadically, it's a tough one to track down.

xtatty · Post by **xtatty** » Mon Sep 30, 2013 7:11 pm

Back again after my first posts!

After a long time of absence the problem appeared again. I really thought it was gone with OS v1.6, but i was wrong!

This time i took the time and made a video in order to help Korg members solve the problem. I noticed that not all keys get stuck. See the video at the link below:

https://www.youtube.com/watch?v=KflH8YlYBy0