Kronos1 output suddenly silent in sequencer mode
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Kronos1 output suddenly silent in sequencer mode
Hi!
I managed to run my Kronos1 from the Reaper DAW.
When doing some music I noticed that if I move around the top
joystick to adjust filters etc the Kronos can suddenly become silent (quite randomly!) and then start to make sound when I touch the joystick again.
When this happens the channel volumes goes down to zero but in the processor usage tab it seem to continue on processing just like before (approx 70% CPU usage, still in the green but with quite abit of voice stealing).
Anyone knows what might be happening? Some kind of overload protection?
I managed to run my Kronos1 from the Reaper DAW.
When doing some music I noticed that if I move around the top
joystick to adjust filters etc the Kronos can suddenly become silent (quite randomly!) and then start to make sound when I touch the joystick again.
When this happens the channel volumes goes down to zero but in the processor usage tab it seem to continue on processing just like before (approx 70% CPU usage, still in the green but with quite abit of voice stealing).
Anyone knows what might be happening? Some kind of overload protection?
-
- Platinum Member
- Posts: 1046
- Joined: Fri Nov 14, 2014 11:57 am
- Location: Orlando, Florida USA
Thanks! Yes, I found the volume fading of the vector joystick not that usable.
I have done some more research:
1. Vector Joystick produces correct values when spying on it with a MIDI watcher.
2. Kronos can become silent also when moving the pitchbend-joystick.
What happens when audio stops is: All sequencer volume bars goes to zero. Kronos becomes silent. But it is is still receiving MIDI input from the DAW since CPU/voice usage just continues on as previously (it follows the music).
I found several ways to break out of this:
Move either joystick, or go into Global/MIDI settings and change local echo on/off (or whatever it is called). Other knobs like PAN etc does not affect anything, nor pressing note keys.
Its almost like some kind of overheat protection? But why then is the CPU usage still up. I use lots of drums and a heavy patch called "dobuled screamer" which eats voices like hell (lots of voice stealing happening).
A short test this morning seem to indicate that if I mute that particular patch the Kronos does not become silent.
As a software engineer I would say this points to it being some kind of bug actually.
I have done some more research:
1. Vector Joystick produces correct values when spying on it with a MIDI watcher.
2. Kronos can become silent also when moving the pitchbend-joystick.
What happens when audio stops is: All sequencer volume bars goes to zero. Kronos becomes silent. But it is is still receiving MIDI input from the DAW since CPU/voice usage just continues on as previously (it follows the music).
I found several ways to break out of this:
Move either joystick, or go into Global/MIDI settings and change local echo on/off (or whatever it is called). Other knobs like PAN etc does not affect anything, nor pressing note keys.
Its almost like some kind of overheat protection? But why then is the CPU usage still up. I use lots of drums and a heavy patch called "dobuled screamer" which eats voices like hell (lots of voice stealing happening).
A short test this morning seem to indicate that if I mute that particular patch the Kronos does not become silent.
As a software engineer I would say this points to it being some kind of bug actually.
-
- Platinum Member
- Posts: 1046
- Joined: Fri Nov 14, 2014 11:57 am
- Location: Orlando, Florida USA
These are indications of a MIDI loop. In your DAW, turn off MIDI echo. Changing your Kronos to MIDI Local Off also breaks the loop.Nihoteph wrote:What happens when audio stops is: All sequencer volume bars go to zero. Kronos becomes silent. But it is is still receiving MIDI input from the DAW since CPU/voice usage just continues on as previously (it follows the music).
I found several ways to break out of this.
(lots of voice stealing happening).
Thanks psionic311
It WAS a MIDI-loop it seems , because now the issue does no longer appear.
I had forgot to turn off "Record Monitoring" for one of the channels in REAPER (I am rather new to this). In addition I set all channels on the Kronos to be "INT" under "Track Parameter / MIDI" to avoid any additional data bouncing back into REAPER.
Now I also turned off the joystick-to-volume (thanks for the tip!)
I think this MIDI-loop caused some internal MIDI buffer inside the Kronos to fill up and sound stopped. Wish Korg could put an alert somewhere (like the performance monitor) when things like this happens.
Happy Camper! Now back to work on the old-school techno tune.

It WAS a MIDI-loop it seems , because now the issue does no longer appear.
I had forgot to turn off "Record Monitoring" for one of the channels in REAPER (I am rather new to this). In addition I set all channels on the Kronos to be "INT" under "Track Parameter / MIDI" to avoid any additional data bouncing back into REAPER.
Now I also turned off the joystick-to-volume (thanks for the tip!)
I think this MIDI-loop caused some internal MIDI buffer inside the Kronos to fill up and sound stopped. Wish Korg could put an alert somewhere (like the performance monitor) when things like this happens.
Happy Camper! Now back to work on the old-school techno tune.


yeskeys: The ribbon controller is innocent in this case.
However, I feel I sacrifice alot of skin to make the thing happy.
I have to hold down annoyingly hard onto the surface to get consistent values. A MIDI dump explains a lot of the glitching I heard when I used it before, the controller believes I release my finger and spits out some random "64" values in the middle of the sweep.
I disabled the jumping-to-middle by SW2 using EQ/Vector/Controller and then Controllers and SW2, selecting "ribbon" in the combobox.
Nevertheless this is a bit annoying.
However, I feel I sacrifice alot of skin to make the thing happy.
I have to hold down annoyingly hard onto the surface to get consistent values. A MIDI dump explains a lot of the glitching I heard when I used it before, the controller believes I release my finger and spits out some random "64" values in the middle of the sweep.
I disabled the jumping-to-middle by SW2 using EQ/Vector/Controller and then Controllers and SW2, selecting "ribbon" in the combobox.
Nevertheless this is a bit annoying.