Full ACK, the encoder bahaviour is pure shit on my Analog Rytm MK2.
It’s nearly impossible to change the values from 1 to 0 or from 66 to 67.
The acceleration does not work properly.
2 Likes
Indeed
Depends on what parameter you adjust with it
For some ot works, for others it is an always returning issue
It will be better soon, I think
Even on older MK1 machines, Analog Rytm for example, the encoder settings are translated too sensitive on certain menu pages.
In his initial post, Petur already listed the problematic settings.
While some menu pages are perfectly fine and just feel right, on others, it’s completely oversensitive, like when selecting the filter type, than what we were used to from the silver machines.
It’s just a little change that has to be made to the firmware, it can be easily fixed via software. Same thing happened to the Ableton Push 2 when it was new and was later changed via firmware, when enough people were complaining and asking for it.
When opening up a ticket, please refer to this thread, guys.
On A4 mk2 there used to be similar difficulties with encoders. They were addressed with later OS.
I am know used to these new encoders, and never push a knob anymore. It feels great, and mk1 feels pretty slow to me now.
1 Like
I just took some time and went through my Rytm MK1 menus to check which menu locations seem to be a bit problematic.
In the following list, I’ll only mention the menus that, in my opinion, need revision. The other settings to me are totally fine. Also, values that only offer two choices (i. e. Delay PingPong: Yes/No) won’t be listed. In these cases, the encoders being too sensitive is no usability issue, since turning an encoder into the opposite direction chooses the opposite value (yes -> no), which follows the intention of the user.
Trig Page:
- Note: Too sensitive
- Trig Condition: A bit too sensitive
Synth Page:
(see engine pages below)
Sample Page:
- Tune: Since movement here happens in semitones, this could be a bit less sensitive
- Sample List: Too sensitive
- Start: Totally Fine (I know that people were asking for more precision, but that is another issue)
- End: Totally Fine (I know that people were asking for more precision, but that is another issue)
Filter Page:
- Filter Type: Too sensitive
LFO Page (both):
- Multiplier: Too sensitive
- Destination: Too sensitive
- Waveform: Too sensitive
- Trig Mode: Too sensitive
Compressor Page:
- Attack (ms): Too sensitive
- Release (s): Too sensitive
- Comp. Ratio: Too sensitive!
- Sidechain EQ: Too sensitive!!
BD Hard:
- Tune: Since movement here happens in semitones, this could be a bit less sensitive
- Waveform: Super Sensitive, please fix! There are only 3 values to choose from, touching the knob slightly already results in reaching the maximum and minimum value.
BD Classic:
- Waveform: Super Sensitive, please fix! There are only 3 values to choose from, touching the knob slightly already results in reaching the maximum and minimum value.
- Transient: Too sensitive!
BD Sharp:
- Waveform: too sensitive
Dual VCO:
- Tune: Since movement here happens in semitones, this could be a bit less sensitive
- Osc Config: Too sensitive!
CY Ride:
- Cymbal Type: Too sensitive
BT Classic:
- Snap: Too sensitive
Maybe someone with a Mk2 can go through these and see if it’s an issue, too?
3 Likes
Reply from Elektron support is that it will be tuned in a future OS.
8 Likes
I also got an answer from support (Christian). He said he forwarded the issue to the developers and that I also could mail a feature request to a specific feature request adress… I will do so…
3 Likes
I think the encoders on the MkII are too loose to begin with, that’s not fixable. I noticed it as soon as I got mine because I was used to the tension on the Heat’s encoders. I think if they were more firm it would be easier to slowly go thru the menu of whatever setting you’re adjusting. Hopefully they do fix it with an update though, I guess i’ll just deal with the super light encoders.
Hmm, still no update … quite disappointing.
2 Likes
Yup indeed…
There’s other more pressing issues on the rytm firmware that will be addressed first. Knobs Flicking values too fast is gonna be behind stability and crash fixes
Must be extremely pressing… There are issues unresolved since release especially the freezing… But hey, we got a model s instead, wow 
I’m sure the bean counters who saw 10x more digitakt and digitone sales have a little bit of say on which box gets priority dev hours as well. Problems of being held by private equity.
I love my AR2, but it has some glaring flaws considering it is Elektron’s flagship drum machine.
I’m Finding the A4 mk2 has a much smoother parameter travel and far easier to get the setting you want where as the Rytm mk2 jumps really fast on some pages and parameters… eg retrig
I’ve seen it mentioned but not as a new topic
Really hope this gets addressed in future os update
3 Likes
I just want to post here, since I also had some issues with the encoders. They felt really loose and sometimes despite turning them slowly, nothing happend. Then turnung faster made the value jump, etc. It was also terribly hard to set some values precisely, since it was always over or undreshooting while turning.
I mainly had to use the performance encoder to record modifications, since that was not possible good enough with pots A-H.
I had many many bugs and issues wiht my device, so I have read about this here, but did not give it high priority.
So I swapped my device for other reasons and I have to say, it is WAY BETTER. The encoders have some resistance and the values follow way more exact. Alltogether I could feel the difference immediately. So the good news is, not all devices have got that loose/unprecise encodr issue.
If you got this issue maybe insist on a repair or swapping, if still possible.
Okay, just installed the 1.50 update on my MK1 and it seems like nothing has changed.
In the release notes, encoder values are mentioned, but only for Rytm MK2.
[MKII] Some encoders were set to change their parameters at the wrong speed.
Well, that’s disillusioning …
It was not working correctly on the mk2 with the high resolution encoders
with wrong speed settings on some pages Moving too fast,
It seems to be fixed but haven’t tried all the parameters yet.
As far as I know there was no issues with mk1
1 Like