Agreed, the highlighted page is quite indistinct. Have found myself cycling through the pages just to get my bearings properly.
4 Likes
turned it on this morning and let it idle for 10 minutes. it got stuck and the crossfader indicator on the screen was at scene b while the faer was at scene a.
also the input led was lit in yellow .
After a reboot it worked fine with no issue.
It seems like if i get the good boot i dont have any issue.
this happen sometimes only. when happens after a whilethe machine will freeze. but usually it stay in position and work smoothly. hope is non an hw problem and have to send it back…
Sounds like the issue I had. I hope it’ll be confirmed as a software issue.
1 Like
Got my brand new Octa and checked it side by side with the old mk1 one.
So: the red rec light (both AB AND CD) get stuck.
Pretty randomly, when there’s a peak the red light stays on and a couple of times I had a freeze.
More often when I use a balanced cable
MKI didn’t have this issue
Whew! Big cross-talk interference (but the mk1 as well)
1 Like
Just in case you all missed it, freezing has been addressed as a bug, and also input meter activity, both to be fixed with firmware:
2 Likes
thx but I don’t think these issues are regarding my problem
It’s a sort of “pemanent red” light freeze, due to (I think) a gain overload
yes…it is exactly the issue. the led remains lit. it will be addressed in a firmware update
1 Like
Sorry dude it seems my english is crap, I thought “blink” was meaning “flashing”, but it’s the opposite, we’re both talkin about “stayin lite”
Thanks JOB
Is anybody having issues with using the crossfader to fade between scenes that lock the XLV parameter?
It seems that sometimes it works as expected, and other times not.
- Create new project
- Switch T5 to a FLEX machine, load a sample, add a trig on the 1, and hit play (you’ll here the sample trigging)
- Hold Scene B (scene 9) and set XLV to MIN
- Now Track 5 should fade out as you xfade from A -> B
- But it doesn’t !
What’s odd is if I repeat the process but with T1 (or T2, or T3, or T4) instead of (T5, T6, T7 or T8) it always works.
EDIT: If anybody could reproduce this (or consistently NOT reproduce it) let me know as it’s driving me crazy.
1 Like
I also got issues with scenes affecting XLV. But I have this issue with projects that were loaded from the card previously.
Here’s how to reproduce.
Create a new empty project.
Create a pattern, that has:
- Looped static sample on Track 1 with trig on 1st step.
- Looped static sample on Track 4 with trig on 1st step.
- Looped static sample on Track 5 with trig on 1st step.
Let the Scene 1 clear, and create other scene (let’s say 9) which sets XLV MIN on Track 1 and Track 4. Leave Track 5 untouched however.
Now start play and move the slider from Scene 1 to Scene 9. We expect that Track 1 and 4 will be faded out and only Track 5 will be heard. That may happen so.
Now save the project. Then switch to different project then switch back to this project. Turn off the device, turn on. Or somehow ensure that the saved project is reloaded.
Try to play the above pattern and move the slider from Scene 1 to Scene 9 again. Now track 5 will also be faded out. According to my experience this issue depends on Track 4. If that is set to XLV MIN, it will also fade out Track 5 (and Track 6). And the same thing happens, too, when the AMP VOL is set to MIN instead of the track main XLV.
Strange issue.
3 Likes
Now I have a guess why Elektron hasn’t released the new firmware for MKI yet. These issues with scenes would make most of the saved projects unusable 
2 Likes
I have the same issue !
Tried with XDIR too, it doesn’t works.
Im tried on T5 or T6 with Thru and Pickup machine, XLV doesn’t works. With flex machine on T1 to T4 it works.
I will try tonight with Thru and Pickup on T1 to T4 and a flex machine on T5…
I let you know !
1 Like
I’ve got answer from Elektron support on these scene issues with XLV. It’s a known bug and will be fixed, eh, soon
5 Likes
Thanks ! We hope soon… 
I will push a ticket too !
You shouldn’t except that you can add a scenario to this which hasn’t been described already. They’re aware of the bug and are going to fix it. Let them focus on other bugs and issues, there are a bunch of such things to fix and what else can come up which we haven’t met yet
I had a prob where LFO 1 on a track didn’t modulate anything, no matter the target. When I setup LFO 2 with identical settings, everything worked…? Will try to reproduce this one before opening a ticket.
MKII os 1.30
Whats good folks. Is anyone able to save a normalized sample? I’ve tried to save a sample in a flex machine that I normalized by saving the sample settings and/or saving a copy of the sample, repeatedly. I then saved the project as a whole. Once the project is reloaded the sample reverts to an un-normalized state. All other settings are recalled properly slices, effects…
I’m sorry but are you all not pissed that you are effectively beta testers on a $1300 machine? The freezing bug surely was known before release unless they simply assembled it and shoved it out the door. Not to mention all the other bugs on a device that has existed for over 7 years (on the assumption that MK1 and MK2 are the exact same OS like they’ve said).
This just confirms to me that preordering and buying an Elektron product up to 6 months after release is the stupidest thing a working musician can do. Unfortunately, this is the new paradigm for manufacturers across the board and to quote the most powerful and yet most stupid person on the planet…it’s SAD!
I know I’m throwing shade here and I’m sure I’ll be told to flip off by many which is completely fine, but seriously, how many of you bought this device with the expectation to use it at a Gig over the next month? How many are just tinkerers with plenty of money to burn and happy to beta test?
5 Likes
Ahh the Pre-order blues…
Becoming a traditional song for electronic artists…
5 Likes