I just tested this, not having the same behaviour, very odd. This was an old 1.25h project though.
Edit: Actually have not tried any new projects since the update. 
1 Like
Maybe you can test with a new project ?
I use Thru for pattern 1 part 1 track 1 and a Flex playing the recording on pattern 2 part 2 track 1.
For what it’s worth, I have about 3 hours of time in on 1.3b and haven’t hit any bugs so far, but that has all been using template projects I made in 1.25h, I haven’t started a new project since the update. I haven’t done any recording yet, either, mostly MIDI sequencing and playing back flex samples I already had in the project from before.
edit : this was another problem above, solved.
Rec setup problems are not solved.
I found out why I had a Thru on a Static track :
After part change, you need a trig to make a new machine effective. In previous patter/part, Thru had trig with INF hold/release, so Thru was still active.
As @Open_Mike remind me, Silence Track parameters can help.
I also found out why I had midi notes without midi channels nor notes : in previous pattern/part, notes were set to INF, with arp.
2 Likes
I think you need to specify the exact minimum steps to recreate
I read you said parts were forgetting the recording settings, so I just tested that in a new proj
It works fine for me if I switch parts whether they are saved or not, I tried two saved parts and one unsaved and the relevant settings were kept fine when switching between all parts
Can you be very specific about minimal steps to reproduce
edit:you just posted - are you okay, found the issue ?
1 Like
One bar patterns.
Pattern 1, Part 1, Track 1 :
A trig with Thru
Rec INAB, Rec trig, Rec Len 16
Pattern 2, Part 2, Track 2 :
A trig with Flex, Recording 1
Tweaking Rec Setup INCD, LEN
Go to pattern 1, listen recording in pattern 2.
Tweak Rec settings again, go to pattern 1, etc…
Pattern 1 part 1 keeps pattern 2 part 2 rec setup tweaked values.
I reproduced it in 4 new projects.
At the first few attempts it seemed to be playing the recording1 buffer captured from AB fine when going into pattern 2, but messing with those recording settings in part 2 did eventually result in the recording1buffer being full of CD content although there is no recording trig in the second pattern - so I guess you’re seeing this ? - I do think you absolutely need to detail the minimum steps to replicate 100% so that there’s no hit and miss - it does look like something’s wrong on the face of it, but I haven’t thought it all through - write out your detailed step by step so someone else can try and then send to support if it’s still not right
1 Like
I didn’t mess with the rec settings too long but I haven’t been able to replicate it yet.
1 Like
Hi everyone,
I updated the OS to 1.30B and now, when I’m switching on the OT, I have an error message : “UI NOT TESTED”. The current project is loading fine but the UI is frozen and I can’t do anything. It doesn’t respond at all.
I have to switch the machine on and off 3 times to be able to use it again.
Any clue on this ? Anyone has had that bug too ?
Thanx a lot !
1 Like
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