Model:Cycles OS 1.11 & 1.12: bug reports

Elektron Gear Model:Cycles
#91

Do you have multiple devices in your MIDI chain?

1 Like
#92

Not at the moment.

EDIT: but I should try syncing Elektron w/ Elektron, just the two of them. Although I would like to all my gear to play in sync :slight_smile:

#93

Your Master is a DAW or a piece of Hardware?

#94

This I noticed while slaving M:C with a Five12 Vector sequencer.

#95

It regularly happens when using only two Elektrons. Eg, OT to M:C, or OT to DN. Nothing else chained, no DAW involved. Just straight midi cable from OT (master) to either M:C or DN (slave) :frowning:

#97

Does it happen when you Double-press Stop on both units?

#98

It’s confusing as hell. Sometimes doing that makes the M:C Play and Stop button light up, other times just the Stop button. It shouldn’t be this difficult to work out. It should just work every time. Hence why I think it’s definitely a bug or slow passing of Midi

#99

Couldn’t agree more! I’ll test my M:C later on.

1 Like
#100

Thanks! It’s almost as if triggers are very late in the priority list, so transport commands work perfectly everytime, but if there’s some kind of latency then transport starts but first trigs of the pattern don’t fire. I’m not sure why as I’m using internally sequenced triggers. Nothing being sent midi note-wise from OT. Just transport and PC, so this should be the optimal setup. Nothing complicated! No weird microtiming on those first triggers either. Just bang on the grid. To get around this on DN in the past I pushed first step triggers the smallest amount allowed by microtiming and that worked but still, you know the rest haha

#101

For me, this didn’t work on the M:C :-/ not reliably.

1 Like
#102

I’ve done some intensive tests with the M:C.

The MIDI chain is : DT > M:C

I can confirm that the first Step is sometimes skipped. And when the first Step is skipped, I can say that this behavior is repeated 3 or 4 times in a row (if I press Stop, then Play). I didn’t notice that before because, for now, I always use the M:C by itself.

2 Likes
#103

Thanks for confirming. Yeah, it’s odd behaviour for sure and hard to replicate exactly every single time. Happened to me the other day recording a live set. We just pretended it was part of the song haha.

1 Like
#104

Have same issue with MonoMachine to M:S

#105

Need to try switching midi sync to the midi ports, but trying to do midi clock sync (w. M:C as slave) + usb audio with Bitwig gets me many of the problems described in this thread. Sometimes audio dropout, sometimes extreme distortion, etc. Powering on and off sometimes helps, sometimes doesn’t.

Any clue on how high a priority Elektron is putting on fixing this?

#106

I’ve no idea about its priority. You should send them a support ticket and ask them if they have an estimate time I guess. I had no issues when I switched to using the midi ports but I was slaving Reason to the M:C, so not quite the same setup as you describe.

2 Likes
#107

If history is anything to go by (Overbridge …cough… cough…) we’ll prob. have to wait 2 years before it actually works as advertised…

#108

I’ve been in touch with customer support. They are really responsive! :heart: Elektron folks!

So far they say they can’t replicate my issue, so I’m trying to help them with more specific pointers. Were they able to replicate yours?

#109

AFAIK Overbridge is a monster project that required them to restructure their entire org, so I wouldn’t draw conclusions here from that case.

Customer support has been super responsive despite the pandemic. So far the bigger bottleneck seems to be that they can’t replicate the issue from my pointers. Trying to figure out how to better document the problem.

#110

That’s good I’ve always had a great response from support! Ehh, so I never quite got around to that after I decided to sell mine.

#111

I tried to record all 6+2 midi channels (all sequencer tracks plus the two extra tracks) to Ableton via USB. It seems like I can’t always record parameter changes. Sometimes it seems to work, sometimes not. If I use Control All to record e.g. myself tweaking Reverb Send, it doesn’t seem to record, at least not every time.

Moreover, when I play back the recorded MIDI tracks and control Cycles with them, and have e.g. recorded myself tweaking the Decay, the initial decay value is at 0 which is not what the track had originally. Only the movement of me tweaking the Decay knob is recorded accurately.

Model:Cycles also hangs completely quite often with this setup, so that it becomes unresponsive, and the only way to turn it off is to unplug the power.

Does anyone else have these issues?