Octatrack OS 1.40: bug reports

Elektron Gear Octatrack
#64

MAP/TRACK:

  1. Make sure you’re not in MIDI mode
  2. Select an audio track
  3. Hit MIDI+UP - Do you see the “MIDI MAP [TRACK NUMBER]” box pop up?
  4. Select CHROMATIC or another mode, hit YES or NO (they both exit the dialog)
  5. Do you see the tiny icon in the bottom-right corner, next to the scene number indicators?

Also, remember that the different MIDI MAPs have their own ranges. Are you pressing a key that’s out of range (for instance, C#3 in CHROMATIC mode?)

Finally (or maybe firstly?), check your MIDI controller device with something like MIDI-OX to see that you are, in fact, sending the appropriate MIDI data.

2 Likes
#65

Yes, im aware of that. However I have to wiggle the src input volume encoder for the gate to open, even though I’ve already sent a trig to it… that, I did not have to do before.

1 Like
#66

I’m not having that issue with thru machines. :thinking: sounds like it could be the project. Can you repeat the behavior in several projects?

#67

I’ve only tried with new banks, not with new projects, I will try that… I’ll get back to you…

#68

Cool see if you can find a pattern and I’ll try to reproduce

#69

The problem persists from project to project, here’s another video showing it happen again. It seems to happen only if you press stop and play really rapidly to switch from pattern to pattern.

2 Likes
#70

No, the patterns autosave the setting given to them when they are adjusted.

#71

When I try to save a selection as sample from the pickup machine, the sample will result in a zero length file (that’s what it says, when you want to load it into a flex machine: error zero-len).

Workaround: save sample and assign to self. Then it works also from within the pickup machine.

#72

Sorry for my assumption :slight_smile:

No problems with any of my THRU tracks on existing projects, or when using a fresh project…

What happens if you p-lock your volume on the activation trig?

#73

Yeah guys you are right. I was pushing function+up instead of MIDI+UP.
All good, sorry for the fuss!!!

2 Likes
#74

8 posts were merged into an existing topic: OT Feature Requests Thread (active)

#75

Can confirm! Replicated on MKI:

  • New project
  • Tempo per pattern: A01 = 120 bpm, A02 = 60 bpm
  • Sequencer running on A01, switch to A02
  • Before the sequencer reaches the end of A01, press stop to immediately switch pattern
  • Press play on A02, sequencer runs at 120 bpm

ticketed!

4 Likes
#81

The strange thing is that I only have to move change the volume once, then it works like normal, but when I make a new pattern (either from new bank or part) I have to jiggle that volume just to get any sound on the thru tracks less strange really

#82

I’m finding that in MIDI CHORMATIC mode , trigs 1 , 5 , 7 , 8 will not trigger any sounds to my sound module. Anybody else finding this ?

#83

4 posts were merged into an existing topic: OT TRig Conditions (TRC) thread

#86

3 posts were merged into an existing topic: Noob Q:Blinking track LED?

#87

So has anyone found that removing the bin file from the card after update solves their glitches? Does it need to be there? Seems like a simple solution, anyway.

#88

No, it doesn’t need to be there, but it shouldn’t hurt either. It’s just a file on the CF card and until you trigger an OS upgrade manually it shouldn’t be touched by the device (unless there is some hidden and undocumented mechanism).

2 Likes
#89

Well, I’m not an extensive or deeply versed user of the OT at this point. So far I have only had a minor issue with triggering my external synth via the trig keys over midi. Notes seem to be hanging and then pressing or tapping the same key twice really quick seems to resolve it, but I never had it happen like it seems to be now more frequent.

#90

EDIT: I get it now and can reproduce it.

The tempo indicator changes, but the next pattern will retain the previous one’s BPM.