Korg Forums

Hello everybody,

I've got a problem on my KP3 (firmware 2.0), which seems to be tiny, but at times disturbs the workflow and the results.

In the new version 2.0 there are four different sample trigger modes to start and stop a sample. The first two modes are working all right on my unit.

When sample trigger mode is set to 3 or 4, there's a little crackle or glottal stop when stopping the sample by pressing the sample-knob again (on mode 3) respectively stopping the sample by releasing the knob (on mode 4).

That crackle isn't very loud or noticeable, but audible, especially using headphones. Usually I'm not nitpicking things like that, but in this case it sometimes destroys a clean transition from one part to another.

Has anybody experienced this and maybe got an idea how to fix it?
Could anybody confirm, that usually it doesn't occur, therefore being a fault on my unit only?

If you have any idea on this, please share it. Thank you very much.

Pirx

I noticed this on my unit, only after resampling a few times. I assumed it was noise from abruptly cutting the sample in an uneven section. I'm not familiar with samplers though.

I know in software if I just cut a loop off mid-sound there can be a click, because of the abrupt change from some volume level to 0. So I sometimes have to set a quick fade on the end of a loop. I can't do this with a kp3, so perhaps this is something they should have included. Some sort of rapid fade, instead of an abrupt end.

Thank you, Zedius, I also think that this is something I have to live with. It's a bit disturbing sometimes, and some kind of quick fading would do the trick, as you said. Apart from that the KP3 is an amazing tool, not perfect, but really inspiring.
Pirx

I can add it to the bug section of the wish list if more peepz got the same problem..

Should be pretty simple to recreate this one. Try sampling any sound source, and then resample it a bunch of times adding different effects. Record samples into a few different banks, though I'm not sure it matters. Then see if you can hear a click. I've had it happen a couple times, I think it's a bug and worth fixing in an update.

I'll give it a try on my unit when I get back home tonight.
Unwanted clicks suck Danish balls..

I've noticed the same thing...just thought it was the nature of the unit. I've either come up with simple work-arounds (time slice) or just let it be apart of the sound...made it work. But yes if there is a fix for this. that would be helpful.

Now I've verified, that the clicks (when stopping samples) are captured when the sample is resampled, they are louder depending on the effects that are used during resampling process. On the resample the clicks are really noticeable now and a bit bothering - in this context it's definitely a bug.

Pirx

Bug 7 added to wish list.
Is it only on sample trigger 3 and 4?

Yes, it's only 3 and 4, because in these modes the samples are actually stopped, while in modes 1 and 2 the samples, when 'stopped', are going on in the background with the level just turned to zero.

Pirx

We are talking about sample banks, right?
So 1, 2, 3, 4 is actually A, B, C, D, correct?

I think he means sample trigger modes

Thats right, theres a problem with the sample trigger modes 3 and 4. The sample banks are working all right, no problem here.

Ahh..
I can't recreate any crack, snapple or pops. No matter how I mess with them new trigger modes (3-4).
I guess I'm just lucky. But it's still added as a bug since it is verified on some units.

Hi maako, what kind of samples are you using? Maybe it depends on what kind of sound is interrupted when stopping the sample. I have a noticeable click or a kind of very short distortion sound just in the moment I stop it (on mode 3 and 4)- that's on nearly every sample I create. With all kinds of synth-sounds it's more noticeable then on drum- and percussion-sounds, but it is there most of the time.

Could be, that you are just lucky, but that would mean, that it isn't any software problem, because if it would depend on software only, each and every unit would have it. If some units have it and some not, it's probably a hardware issue, which couldn't be fixed by a firmware update.

Pirx