OS version? (I’m sure you mentioned it above)
Oh sorry - I did way back, but not here. It’s 1.25H. Thanks in advance!
The whole, “I was in the middle of an awesome jam and now I’m chasing/narrowing down unexpected behaviors/bugs” happens to me a lot, and I consider myself an advanced user, not stumped by solutions you’d find in the manual, etc… My borderline ocd about knowing exactly what’s going on with all my gear so that I’m always in control of what’s happening, usually makes me keep chasing those issues next time I power up as well…
Just saying that that experience happens to me as well, not trying to be negative at all. The OTs the heart of my setup and I love it and that’s why I care…
Edit: The way I make it work is by meticulously defining a saved project state that is taylored to specifically avoid the issues that I run into, while having lots of options for jamming and improvising already set up. As long as I stick to that I can make music for hours without snag…
1 Like
thanks Olle,
I just registered a support ticket for the pickup track non-working scene-locks,
hope this will be useful
Cheers
3 Likes
The comments from Clancy and Open_Mike register with me as well. The nature of what I do during the day (software development on complex systems) plus years spent officially beta testing things for Alesis and Akai means that when I run into an issue, I tend to try and duplicate it and document so it can be reported and fixed.
However, that takes a lot of time. Even as a beta tester where you got to keep the unit as compensation, the time spent doing that meant that was time away from making music, family activities, sleep, and anything else.
Now, with time at such a premium, any time I have to stop and document a bug (whether it was the Modal 002, 008, Octatrack, Prophet 12, Lemur, Parva, or whatever), it just makes me tired and sad. To document a single difficult bug properly could take most of my week’s worth of free time. I want gear to just work and when companies ship gear with half-completed OSes and fairly obvious bugs, it makes me wonder how much testing is really being done. Paying customers should not be the beta test team.
So what happens is real issues get either reported anecdotally on a forum or simply worked around if possible.
Sure, it would be great to have them documented, reported, and addressed, but since we’ve seen a real dearth of actual hard bugs fixed and OS updates that introduce more issues, it’s hard to believe anything will be done about whatever we report. I’m not going to waste my time documenting a real issue only to hear back that it won’t be fixed or even worse “thanks, it’ll go on the queue” and 2 years later not see it addressed.
If Elektron wants to have a real dialog about how much they can fix and whether any of the issues brought up will ever be addressed, that would help.
As of now, I feel that only the easiest, most superficial issues are ever going to be addressed and that harder things will never be looked at.
7 Likes
Brief description of issues:
Older:
-Switching from a pattern/part with a pickup to a pattern/part with a flex on the same track # as the pickup will trigger the pickup loop instead of flex sample if the pickup was not playing before switching, Confirmed…
scene locks from pickup track also may remain on new flex track…
Workaround: make sure pickup loop is running before switching, muted if necessary.
-Switching from a pattern/part to another pattern/part that has recorder trigs, sometimes the recorder source and length from the first part get used, even if I lock the sources.
Workaround has been to set all recorder buffers of same track number across parts to the same settings.
-Under certain conditions with sequencer running and making pickup loops using qrec and qpl, rlen max, slave loops using the x() parameter for length begin playback from the middle of your recorded loop instead of the beginning., confirmed but there’s many more details
Workaround has been to not use the slave loop multiple x() parameter and instead use one2 mode and manually define length for long slave loops.
-Pre sliced recorder buffers no longer remain through power cycles osH, confirmed
Workaround for me is use start points but has been suggested that saving and assigning a sample to the recorder buffer slot and then re recording into it might work…
Current things I need to look into:
-Switching from pattern/part with a pickup to pattern part with a thru on the same track# as pickup, sometimes the thru is at about half volume…
-Using pickups with rlen max, qrec enable but not qpl, in one2 mode with sequencer running, pressing a/b to define a length and go into overdub works but pressing c/d to define a loop and start playing results in the pickup recording changing length to your max mem allocation length…
-Switching from a part/pattern with recorder trigs to a part/pattern with different settings for recorder trigs, sometimes the recording len doesn’t get reset and the new recording gets cut or doesn’t work…
5 Likes
Indeed the idea of Elektron officially stating an official bug-list would be ace from them,
and if possible with definitive answers for each of them (will be fixed, won’t be fixed…)
My support ticket is registered on february 12th 2017, I didn’t receive even an automated answer. I know 2 days is nothing and one of these 2 days is a sunday… but this is the kind of feeling… shouting in the wind?
I hope not 
That’s one working day - give them a chance!
But yes I get the way you’re feeling about it & that’s down to a lack of openness about what is or is not planned. There have been some positive noises (did I recently read mention of getting some developer time for the OT?) but I just hope they aren’t going to spend a lot of time trying to build in some new features, when straight up fixing should be the priority.
But how would I know when we hear so little? Or we hear individually what we need to hear en masse.
2 Likes
I’ll give them time for sure!
I was used to ableton or other companies automated answers, like “your ticket has been submitted, blah blah blah very soon”
I did this support ticket precisely because I also read Simon mentionning work being currently done on a new OS for bugfixes, so I hope “my” bug could be taken into consideration.
Before reading this statement I had literally burried the hope for a new OS!
1 Like
Well, Olle just got back to me with the support ticket. He tried but couldn’t replicate the bug, so I have to get deeper in this process…
I don’t really have spare time but I should really try this if maybe they could fix the damn pickup machines bug-list…
Hope is new here, ah ah!!
1 Like
My apologies for lack of reporting my ‘mem full’ issues. Only had it once since downgrading to 1.25E and it was an easily-spotted recorder trig so not like the others. Haven’t forgotten though, will re-apply 1.25H and see if probs recur.
I have been saying the OT is dead in the water for a few years now. (Other than ol Mr Moonbeams and Bunny Rusty’s efforts.) Elekton wont say so, even tho it is bleedin obvious with all hands on deck for overbrdige. and that debacle means the 3 elektron pieces i have now are the last i will buy. i dont make money from music anymore, so I dont need new gear.
I’m not sure if this is the optimal thread, but here goes. I’ll do the support ticket thing too, of course:
At a gig last Thursday, I noticed that after switching banks (to a new song), the fx on my main pickup machine were not loaded. The new bank and pattern were selected, but even a part reload did not engage the current bank’s track effects for that pickup machine. I had to go into the part menu and save the part and then the PM’s fx were engaged.
2 Likes
I usually work out of just one bank but I have had that happen and it probably was when switching banks… I’ve gotten them to kick in by starting either record or play on the pickup. It might have something to do with how tracks from previous patterns play until a trig, but the logic not smoothed out for pickup use… 
2 Likes
timely bump
2 Likes
Now that the OT firmware is still being used in the new OT some of these old bugs could finally be squashed 
2 Likes
Does anyone want to agree disagree that PUM command ‘Toggle Seq Sync + Start : Note 71’ isn’t working consistent with the description (or is buggy)
There is no toggling (as you get with ‘Toggle Seq Sync : Note 70’ ) … it’ll change once
Perhaps the command should be listed as ‘Set PM Seq Sync + Start : Note 71’
I stay sync to seq anyway so I don’t use it, I even prefer to use Flex.
Wishes : plock ability for CUE level (works with midi), part midi control.
Conditional trigs of course.
1 Like
I’d love to get some working “direct” plays free midi tracks… 
1 Like
FWIW, OT1 with 1.30C
Not even using some of the deeper features yet, first I noticed even though the work is “saved” after power off, some trigs missing from patterns and no sound from individual samples. Okay, save every time. Lesson learned.
Then, with either normal or studio mode, one project saved, half tracks going through cue and other mains. Headphone mix normal. OK, guess I’ll just work all the tracks thru the headphones.
Then, later
Have MIDI sending only clock out to thru and down the chain. Everything good.
Change project- no MIDI coming out whatever. Checked cables, twice, switched to another thru box. Switched cables. Same.
Doesn’t respond to clock going in either, changed settings a few times back and forth, reboot. No MIDI.
Turned off and will try again in the morning.
Could some of this stuff just be a simple problem like overheating? I have read through some of these bug threads, it would be a real shame if heads were banging on software fixes for a hardware problem… kinda reminds me of the early Dell laptop issue, where basically it all came down to an inadequate heat sink.