Page 1 of 1
Loop Timing Problem
Posted: Tue Nov 16, 2010 3:19 pm
by Gig
I just bought the Kaossillator Pro and i can't get a clean loop recorded!
First i thought i played it off beat, but i figured out this is not the case.
Here is what i did:
Turn the Arpeggiator function on and set it to 1 (Time Mode), so it would record exactly four beats a bar.
Now i record eight beats (2 Bars) with a base drum or snare and it seems that the loop time is slightly to long!
Every time the loop comes around there is a tiny space to much time between the loops. I have tried it with sync on and off - no difference.
Am I doing anything wrong here or do i have a faulty device?
Any suggestions!?
Thanks
Posted: Tue Nov 16, 2010 4:19 pm
by Mr36
My first reaction is to suggest something that most people don't like. The most likely cause for this is that, put simply, you're just not playing it right.
To elaborate, your finger is touching the pad later than it should be and therefore causing the problem.
You said you considered the possibility that you just played it off beat and that you "figured out this is not the case". How exactly did you do that? How did you figure this out?
Anyway, try this:
From scratch, set the gate arp as you have done (1), set the bank length to whatever you want, hold down the bank you want to record to and, while still holding it down, press and hold your finger on the touchpad (wherever the bass drum or whatever you want recorded is) and keep it there until the end of your designated loop. Once your finger touches the pad in this technique, recording will begin automatically.
Remember, of course, that you must release your touchpad finger before the first beat comes round again, otherwise you will get a phasing effect (if your finger is still in the same place) and it is good practice to allow your bank finger to remain holding the bank down until a few beats into the first repetition (this allows the natural decay to be recorded and not be cut off).
If this works and the loop loops correctly, the machine is working as it should.
Posted: Tue Nov 16, 2010 5:00 pm
by Gig
@ Mr36 thank you for the quick response, but I think I have a lemon here!
I did exactly like you described (start with holding the recorder bank button) - no difference. Even the internal drum loops don't sound smooth when recorded.
One more thing i have noticed is, that each recorder bank A,B,C,D has a slightly different length when recorded separately (same bpm)! Which in my case D is the best but still slightly off.

Posted: Tue Nov 16, 2010 5:22 pm
by Gig
Ok I just tried the following which confirms my findings.
I kept recording a drum kick (arpeggiator at 1) to get a phrase effect, but the second time the loop came around the kick was slightly off the first one.
Posted: Tue Nov 16, 2010 8:53 pm
by Mr36
Hmm... This is very strange.
When you did this last test, did you keep your finger held down for the entire time? No breaks at all?
I can't even conceive how the loop banks could be all different lengths. What makes you think this?
Posted: Tue Nov 16, 2010 9:57 pm
by Gig
Alright I flushed the ROM despite that i had the newest firmware already.
This fixed most of the timing issue
The internal drum loops are perfect now! I still think arpeggiator is not air tight, but it got a lot better! I guess its ok for live performance.
I talked to to korg customer support, they said there was some timing issues when they first came out. They told me they fixed it with 1.02.
Well I wished it had quantize function. Anyway this works for me now and I'm happy with it.
Thanks for the help!
Posted: Tue Nov 16, 2010 11:15 pm
by Mr36
I think it's a lot to ask for £300 device to have audio quantizing. Unless you mean the kind of quantizing that the Boss RC-50 has. And then, I'd say, the KPro has got that.
But I think you mean like how you can quantize MIDI. And I agree, this would have been so much more powerful if its internal sound engine recorded MIDI and not audio. Oh well.
Glad you got it sorted though. When I had mine, I never updated it with that little update and mine didn't have these timing issues. However, never mind. It's just good that it's fixed.