On 1.30B on my Mk1, roughly 50% of the time, I have been getting UI NOT TESTED screen if a card is not inserted, or if it is inserted the screen looks OK, but everything is locked up 
Also, this time, when it has finally booted, all the menus are screwy … i.e. Fn > Mixer (project) turns metronome on and off instead of the project menu
Just saw your post, same problem here
I am 100% behind you that you’ve found a bad bug
I had another play with a slightly more portable/controlled setup
Pattern 1 Part 1 T1 Flex uses muted T5 on SRC3 as its feed to play Recording 1 (rec len=16)
Pattern 2 Part 2 T2 Flex uses recording 1
Both have a muted T6 playing a different sample
If I tweak the record setting for T1 Pattern 2 Part 2 on Recording page e.g. Len=3 or SRC3=T6
and then jump back to Pattern 1 it will load Part1 and show the right previous recorder settings but it will have adopted one or both of the tweaked values - occasionally, it may be OK but mostly it borks it for me, it also can be recovered in pattern one by saving the Part (no changes required !!) or reloading, so it clearly has a different working part from the one which is shown and saved - i.e. bug
To make matters worse, sometimes just changing to pattern 2 it would not even consistently play the correct recording1, it would have somehow erased the recording1 buffer even though it was never tasked to do so (pattern 2 has no rec trigs for any track) (may be due to changing during recording though)… so I think there’s a bad parts bug underlying all of this … saving both parts just before pattern hopping was the best way to make it play ok, but the tweaks on pattern 2 part 2 t1 rec-setup would be fed back to pattern 1 part 1 t1 even though they were not shown !
@sezare56 I’d suggest submitting a Parts bug report ticket with your simple steps (or mine above) to support unless @Ess and the support team know about this already, I think there was something recently on the MKii that may or may not relate to this issue, but it clearly needs attention on the MKi
2 Likes
There was indeed a Parts bug in the initial MKII OS release:
I imagine Elektron’s got the iron still hot with another fix on the way.
3 Likes
I still haven’t been able to replicate this problem exactly, but what HAS been happening (using Sezare’s steps for replicating it) is that when I switch to pattern 2 sometimes instead of track 1 recording stopping after 16 steps like it is set to, it just keeps recording using the pattern 2 track 1 defaults (so no inputs selected, length set to max) so instead of pattern 2 part 2 track 2 playing back what was recorded into the buffer in pattern 1 track 1 part 1, it plays silence because the track 1 buffer has been overwritten. Doesn’t happen every time and I won’t have time today to figure out exactly how to reproduce it but unless I’m making some obvious mistake (totally possible, I haven’t had coffee or breakfast yet) then it seems like it’s probably related.
1 Like
@sezare56, @avantronica
I dug this out of a bug report I made from dec 2014:
So the issue has been around, I did not get a direct response about it from support because it was secondary to the main issue I wrote about and I did not give them steps to reproduce…
5 Likes
Here’s the first part of the report and the response from Elektron, just for info as it may be related:
3 Likes
This happens to me as well. I usually have to restart once, as it boots into a locked UI the first time. Then everything behaves normally.
1 Like
Same thing
That locked UI problem is on MKI and MKII ?
Why some people have it, others not ?
Yesterday I noticed “UI NOT TESTED” message showed up on my OTMK2 screen for two seconds during playing. Nothing more happend, no freeze.
I don’t know what it means but I do really want to know.
1 Like
I had a MIDI-only pattern going on a new bank, and I turned off my MKi expecting it to be saved. I flipped it back on a bit later and not only was my work gone - both channel assignments and pattern data - but it would not let me go back to that bank. When I tried to, it displayed a “bank not available” message which I’ve never seen before. I attempted to repro but could not.
In my case it’s a MK1, but it appears to happen on both. Not sure how to work what the criteria is that causes it
I’ve got maybe 3 hours of use on the MKI (about an hour at a time) so far and will have my first proper practice with it tonight so that will be a few more hours. So far no problems, although I suspect he record parameters some people have been having will show up eventually, it just isn’t the kind of thing that my current workflow leads to, since I don’t change record parameters much at all for this project.
If anything shows up tonight I’ll post about it here.
No problems last night, although I didn’t use any track recorders so the record properties bugs wouldn’t have shown up anyhow. But no freezes or display issues or anything.
1 Like
Want to throw this one back into the collective consciousness … I’m finding this hard to overlook, quite a show-stopper whilst I’ve been exploring CC p-locking with the OT
A workaround is to shove in a trigless lock just before (space permitting) to serve the CC manually earlier than the note on - far from ideal !
anyway … discussed back in the day
“CC late bug” is rather apt - is it intentional/changeable
1 Like
I’m wondering if sacrificing a midi track just for cc’s could be a workaround for now, to have access to all the steps.
If the priority track is microtimed differently than the next track, will the OT fire two events or just one because it’s the same step?
2 Likes
I’d been doing that so that CCs could have different TRCs, but it’s a pain to keep two tracks ‘parallel’ not to mention a waste - let alone a drag to microtime
some params won’t be so noticeable, for me this isn’t about how to get by it to make it as intended, it’s about whether it works nicely on the fly as you’d anticipate, otherwise it’s a buzzkill
2 Likes
I had a bug. Loaded a sample, played it, changed the sample slot, but it was keeping the first one, no sound change. Power off/on. Ok.
A freeze too, but I was experimenting to control a midi track with another one, using autochannel, in order to have many lfo’s for midi track control. The first one was controlling an audio track. Messy, not convinced by the promising experience.
Still really don’t like the midi incoming data plockable behavior.
But…for external gear, you can modulate a Ot’s midi track by its other midi tracks set to auto channel. Not convenient for settings.
I’ll make further tests without auto channel, and without audio vs midi corresponding channels.
I have a solution for the “UI not tested!” problem!!
When you power on your OT press function and than testmode… Thats all. In my case no UI boot problems any more…
Next day… same problem: UI not tested… It is not the solution.
3 Likes