R3 tempo potentiometer (aka knob) won't hold constant value

[Re-Member]

Mine had this problem when I first got it back in 2007, but it actually stopped after a good year of heavy usage and gigging. This means that the pot getting dirty might have actually fixed it, haha.

When the problem kept occurring, here was my solution:

1. Dail in the tempo you want the patch to be locked in, then save the patch. Turn to another patch, then set the tempo knob all the way *counter-clockwise till it can't turn no more. After that, switch back to the patch you saved earlier and DON'T touch the tempo knob. As long as you don't touch the knob, the tempo you saved previously will load up and stay in place.

*Might actually be clockwise, can't remember exactly.

2. Another alternative is syncing the MIDI clock to external synth, drum machine or sequencer.

[DaniH]

I've had two R3's that both had the same problem

and with you having the same problem makes me think it's a manufacturing defect

Mine does this as well when I move it. If it is set to say 120 it stays there fine. Now if I move mine it jumps around one bpm back and forth. If it is synced via midi/usb in there is no problem.

[mesoboy]

Cheers guys! Interestingly, I left my R3 on for about an hour with doing anything and the 'problem' seems to have stopped! By the sound of things I guess I'll just have to live with the various work arounds!

[rukaav]

I've got the same problem with the FilterKeyTrack knob on my Radias.

[th3brownbunny]

Hey guys... I know Im new to the forum and all but something that nobody seems to be considering is that the Korg r3 is an analogue modeling synth... that is the beaty of it. Even though the unit itself is representing the tempo digitaly on the display as 100 bpm or 99bpm... this number is simply a digital rounding off to the nearest BPM integer... which is not a malfunction. It is to be expected. Depending on the length of the sequnce or note you are playing the reading can change between 99 or 100BPM for example... BUT the true BPM in its analogue form could be say 99.51326485353541433 BPM.

Think of a car with a digital speedo... does the car instantly accelerate in 1M/ph increments just because the digital display goes up by 1m/ph as you accelerate. If you were actually traveling 99.3748684635 m/ph the display would just show 99

Im not an expert but Im pretty sure that is what the R3 is doing. It is attempting to display a digital representation of something that is Analogue and when it comes to fine-tuning BPM It would have been alot easier to do if the knob was 10x bigger. But I dont believe its a flaw... just a design bug that could have been done better (But then there would be other people complaining about a big ugly knob on their unit

Hope this helps guys

[tpantano]

Hey guys... I know Im new to the forum and all but something that nobody seems to be considering is that the Korg r3 is an analogue modeling synth... that is the beaty of it. Even though the unit itself is representing the tempo digitaly on the display as 100 bpm or 99bpm... this number is simply a digital rounding off to the nearest BPM integer... which is not a malfunction. It is to be expected. Depending on the length of the sequnce or note you are playing the reading can change between 99 or 100BPM for example... BUT the true BPM in its analogue form could be say 99.51326485353541433 BPM.

Think of a car with a digital speedo... does the car instantly accelerate in 1M/ph increments just because the digital display goes up by 1m/ph as you accelerate. If you were actually traveling 99.3748684635 m/ph the display would just show 99

Im not an expert but Im pretty sure that is what the R3 is doing. It is attempting to display a digital representation of something that is Analogue and when it comes to fine-tuning BPM It would have been alot easier to do if the knob was 10x bigger. But I dont believe its a flaw... just a design bug that could have been done better (But then there would be other people complaining about a big ugly knob on their unit

Hope this helps guys

A. This thread is four years old
B. You're completely wrong.

The R3's tempo is not in any way, shape or form analogue. All tempo based calculations like the arpeggiators and BPM synced LFOs are coming from a digital tempo number. The R3's tempo is always an integer. It's never a decimal. The R3's tempo is not representing an analogue value. The R3's tempo displayed is the actual tempo (unless you count delay of an electrical signal, which is what... milliseconds? nanoseconds?).

[DaniH]

Hey guys... I know Im new to the forum and all but something that nobody seems to be considering is that the Korg r3 is an analogue modeling synth... that is the beaty of it. Even though the unit itself is representing the tempo digitaly on the display as 100 bpm or 99bpm... this number is simply a digital rounding off to the nearest BPM integer... which is not a malfunction. It is to be expected. Depending on the length of the sequnce or note you are playing the reading can change between 99 or 100BPM for example... BUT the true BPM in its analogue form could be say 99.51326485353541433 BPM.

Think of a car with a digital speedo... does the car instantly accelerate in 1M/ph increments just because the digital display goes up by 1m/ph as you accelerate. If you were actually traveling 99.3748684635 m/ph the display would just show 99

Im not an expert but Im pretty sure that is what the R3 is doing. It is attempting to display a digital representation of something that is Analogue and when it comes to fine-tuning BPM It would have been alot easier to do if the knob was 10x bigger. But I dont believe its a flaw... just a design bug that could have been done better (But then there would be other people complaining about a big ugly knob on their unit

Hope this helps guys

Not true because when turned all the way down or up it still jumps for me. It should not do this as it is set to the lowest or maximum bpm range while still ending in a constant. Its not a real problem for me just some OCD taking over.

[Treezy]

I just bought my R3 used and the 1st thing I noticed when i got home was the Arp fluxuates. Not happy, Im gonna link it to my Kp3 up as slave to see if that fixes it. If not Ill try saving each preset. Making my production difficult here Korg. thnx guys.