Octatrack OS Bug Reports

Elektron Gear Octatrack
#77

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.

#78

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
#79

Recording on record buffer 5,switch to other pattern - recording continues with no rec trig.
Yesterday OT Didn’t react on rec trigs, ignoring “RLen” parameter.
Freeze after switching on.

#80

Sounds very logical.

#81

OS 1.30B, OT mkI.

I wanted to make a long recording so I went to the Memory menu, set dynamic recorders on and reserves off. None of the sounds in my Static slots played after this. Preview from the sample list did nothing. Previewing each sample in the sample editor brought them back one by one. I luckily only had about 15 slots so it didn’t take too long…

#82

Known bug, if you change Memory Config.
Reload project may works, not sure.
Edit :

4 Likes
#83

Jap, but it do not work really… Have same Problem again:(

1 Like
#84

I contacted support re the UI NOT TESTED problem, which now appears at every boot up and then freezes, and they mentioned they don’t know what has caused the problem, and sent me 1.25H to put on the OT, but it won’t let me backdate the OS, I says MK1 OS NOT ALLOWED so now I essentially have a bricked OT. Any ideas ?

1 Like
#85

Following…

1 Like
#86

Try test mode before downgrade.
Try downgrade with midi sysex.

#87

I had the same issue a few days ago, don’t know what combi caused this, as of now it seems to work normal…

#88

In Rec Setup 1, if you hold the Rec Trig, INAB, INCD and SRC3 are highlighted. You can disable/enable that sources, pressing the corresponding buttons : REC 1/2/3, REC AB/CD/MIDI for MKI.

#89

I know I’m aware of that, i was using a flex slot setup as a looper and it worked a few times at some point it stopped…

1 Like
#90

Whilst in CHROMATIC mode : When I enter the ARP sub page (scale correction bit) on the MIDI side and then re-select the ARP main page (with or without editing e.g. scale) - I get a solid row of 16 yellow trigs instead of the faux ebonies/ivories - pressing the page button or other UI elements will fix it - but this is clearly a bug at my end

Can anyone confirm ?

#91

Hi guys, I’m having an hard time trying to get pickup machines working since the update.
After recording the first loop, the recorder stops recording, and makes impossible to overdub. Also i get picth flutter.

First thing i did was trying without any midi in to the OT (even if i have clock and transport receive NOT flagged), but nothing changes.
The OT behaves like having some midi input wich varies the tempo, but JUST with the pickup machine, not anything else!

Tried with a new project and old project (working perfectly fine before the update!), with midi input connected and without anything connected to midi in… the bug is identical

#92

I’ve come across this numerous times but just glossed over it as I didn’t know what was triggering it. I’ve always assumed its an incorrect display from another trig mode.

1 Like
#93

Works just fine for me - sounds like you have something modulating playback speed somehow (or MIDI clock incoming), but this makes no sense if you have a new project

You cannot run PUM in slave mode reliably - so completely disconnect MIDI IN for the meantime to determine if it’s clock or a stray cc and double check LFOs etc

#94

Thanks, I did, but then it said MK1 OS NOT ALLOWED. It did work OK once after the test on 1.30B, then back to same behaviour

#95

On a MKI ?!
Not very reassuring for downgrade… :sketchy:

#96

Is this issue related only to MKII OS, or both? Been holding off updating my MK1 OS because of things like this.