4 Likes
Or just take a little summer break themselves, or am I saying a really weird thing now 
2 Likes
Transfer was updated quite recently though it’s just a mac thing , likely didn’t make any major difference.
It’s done this since day one !
It’s a good thing …
r u sure?
so with 1.55 it did it normally stopping at -64/+63 and so do all other knobs (obviously with 1.55 it wasn‘t functioning as it should)
with 1.55b it’s decoupled but it can spin full clockwise which is a one timer for Elektron, no?
It has always been like a watch … the seconds(fine) and the minutes(coarse)
I nagged this fix because since day one if the coarse dial was pushed too far either way it would break a clumsy algorithm which supported this watch analogy
Essentially I’d you had gone too far it would max out the fin to a max or min at which point the watch had run out of road … i.e the whole pitch was either 0 or 16383 (akin to Pitchbend in resolution) … so the fin could move no more
This was wack for osc turning as it’s half a semitones out and this issue was tripping me up from day one as I used push encoder acceleration and func acceleration to get octaves … so now the algorithm for pushing and funcing is maxed out at plus/minus 5 octaves
Also it used to only allow a reset of the pair irrespective of which you aimed to reset, so you always went back to 0 0 (half the 14bit range)
Now you can reset either independently and it’s less prone to this annoying overshoot … all the issues were predicated on this watch analogy, it’s good they kept it you can scroll your osc tuning down without interruption … a manual falling pitch can be interesting in a few ways … plus there’d have been uproar if it was removed
Overall it’s a friendlier ux regarding all the workflow things we are used to
The ‘decoupling’ is affecting the extremities and the ‘pair’ resetting … those were the three areas where the ‘watch’ coupling was extremely irritating… sadly the acceleration on FUNC twisting wasn’t sorted despite asking, it’s painfully slow, slower than non func!
So yeah, It’s definitely been this way since day one, as it’s one of the most annoying things I have moaned about for over a decade … it wasn’t planned for this bugfix, but I made a noise about it and thankfully they obliged
2 Likes
Perhaps they could figure out their devices aren’t bricked and play music
1 Like
I think we’re also decoupled but iam talking about the fact that the fine tune knob can be turned endless in either direction, you can spin it from - to + and + to - with breaking points at the top and bottom.
It’s always been that way… as I said I unclearly evidently
It still is
But there’s been some decoupling from UX events at either end of the whole range and in the middle of the range especially wrt zeroing
Fine isn’t decoupled … it’s just that the extent of coupling has been tamed to prevent issues
alright, I’ve been so confused after 1.55 and now after it‘s been fixed it’s confusing to see it spinning around, interesting of course 
1 Like
Here’s an old post referencing one of the decouplings which has been added
This recent post points to the extremity issue perfectly …
Just adding for completeness… plus Elektron can see these issues were bothering many others
2 Likes
OS 1.1 / 2013 
Just upgraded, went straight to 1.55B
What’s up with the Mk2 color codings? Didn’t parameter pages use to have distinct red or green highlights on the corresponding LED when active?
I can maybe see a hint of green if I go to OSC2, ENV2 or LFO2 but it’s still more like a dimmed version of the base white. This makes it harder to see the UI state at glance. And it’s even worse if you turn down the LED brightness.
The Track button LEDs also look washed out when green.
1 Like
The link to the A4 Mk1 1.55B update on the website is still broken …
Just checked and it now seems to work OK
1 Like
I contacted support and there is a confirmed bug with the LED color palette in OS 1.55B affecting the grey Mk2 units. A fix is in the works.
8 Likes
How do I access the slewing of the stepped random lfo setting?
3 Likes
I’m hoping I’m just being dumb, but I’m having issues with track mutes since updating. I used to hold func + track and I could mute the track parts in and out, but they don’t respond anymore. Also in perf mode I could hit tracks/trigs 1-6 to bring parts in and out too. They’re, the UI updates, but the sound doesn’t.
I’m I missing a setting or preference or mode that I’ve previously overlooked by any chance?
I’m not by my A4 to test it. The obvious gotcha to me is that muting track mutes the sequencer not the sound… so if you have for example a trig with infinite length with the arp running, muting the track would not stop the sound once that trig had been triggered.
1 Like