E2 bug - part doesn't record notes
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
E2 bug - part doesn't record notes
I'm trying to figure out what exactly causes this bug. As the post subject clearly states, there is a bug where you cannot record new notes onto a part.
In my experience it feels random. Maybe there's some obscure combination of factors that lock a part. But I have no idea what the bug's trigger would be, never noticed a pattern.
The only solution is to overwrite the pattern with a working or initialized pattern and start over. Surely someone at Korg actually uses these things, you'd think they would have encountered it.
The only solution is to overwrite the pattern with a working or initialized pattern and start over. Surely someone at Korg actually uses these things, you'd think they would have encountered it.
Definitely some type of combo that creates this. for instance, I have a particular pattern saved, where I'm able to record notes on, say, part 5, if I leave it as an initialized patch (you know, saw, with everything like mod, ifx, amp eg, etc off). Now, as soon as I start tweaking and putting on ifx, mfx, amp eg on, etc, im no longer able to record new notes. So yes, something about that, probably in conjunction with the other parts, is causing it to lock up...Ted3000 wrote:In my experience it feels random. Maybe there's some obscure combination of factors that lock a part. But I have no idea what the bug's trigger would be, never noticed a pattern.
The only solution is to overwrite the pattern with a working or initialized pattern and start over. Surely someone at Korg actually uses these things, you'd think they would have encountered it.
I read this topic yesterday but I never had this problem before... until a couple of hous ago. 
I registered a part in a very busy pattern but the playback was a total mess (like time-shifted, I can't tell exactly what and why). I tried to record it again (maybe after cahnging a couple of parameters) but from that moment I couldn't record notes again on that part.
The sequencer mode still worked so I tried to enable all the steps and record a new line over it without success. Fortunately I had another part empty. I've been able to record the line there and move it to the one not working.
It would be really annoying if you don't have a blank part in the pattern

I registered a part in a very busy pattern but the playback was a total mess (like time-shifted, I can't tell exactly what and why). I tried to record it again (maybe after cahnging a couple of parameters) but from that moment I couldn't record notes again on that part.
The sequencer mode still worked so I tried to enable all the steps and record a new line over it without success. Fortunately I had another part empty. I've been able to record the line there and move it to the one not working.
It would be really annoying if you don't have a blank part in the pattern

The only time I have ever seen something like that for me was when I didn't realize that I had accidentally recorded some motion sequences that lead to the filter closed so I didn't hear anything until I cleared the motion sequence.
I figured it out when I just start turning all the knobs to see what was causing it.
Not sure if it is the same thing, but something to try.
I figured it out when I just start turning all the knobs to see what was causing it.
Not sure if it is the same thing, but something to try.
<b>Korg Gear:</b> Electribe 2, microSAMPLER, Mini Kaoss Pad 2, monotron, nanoKey, nanoKontrol2, nanoPad2
<b>Korg Apps:</b> iMS-20, iElectribe, iKaossilator
<b>Old Korg Gear:</b> Electribe EMX-1SD, monotribe (with MIDI), Kaossilator Pro, KP3, SOS
<b>Korg Apps:</b> iMS-20, iElectribe, iKaossilator
<b>Old Korg Gear:</b> Electribe EMX-1SD, monotribe (with MIDI), Kaossilator Pro, KP3, SOS
I had this problem yesterday. Was in keyboard mode and recording the first part into an initialized pattern. Wouldn't record anything. I put in a bunch of triggers in sequence mode, and it played those, but wouldn't overdub new note data with record enabled. I ended up writing the pattern and the bug cleared up.