Pattern change one bar late issue

Yes. I do this while I’m building the sequences I want in my song. Afterwards, I’ll organize them and arrange into a master “Song Sequence”.

At this point, I insert all the Program/Patch Changes for my Elektrons and whatever else is being used. It takes a bit of planning but it’s not too much hassle when you get the hang of it.

I agree with you that it would be nice to Direct Jump. I think it would probably get pretty choppy with multiple sequencers running.

Just hooked up the rytm to DN for the first time. I had hoped I could utilize song mode on rytm to make a full track with just these 2 boxes and have the patterns change at same time. This doesn’t seem to be the case - DN is changing late.

Is this really “just how it is”?? :frowning:

Do the pattern length settings of the patterns on both machines match (M.LEN / CH.LEN)?

If there is a mismatch they will schedule the change at the same time, but they will not change at the same time.

1 Like

Thanks!!
I had another look at the lengths of the tracks and possibly it’s a bug or possibly I’m misunderstanding something. My intention was to have a pattern that would change after 64 steps, however potentially have infinite loop so that polymetric stuff would never reset.

So I had
RYTM
LEN : INF
CHLEN: 64

DN:
M. LEN: INF
CHLEN: 64.

This didn’t work

However when I change it so that
RYTM
LEN: 64
CHLEN: OFF

DN
M. LEN: 64
CHLEN: OFF

It now seems to work, but of course the polymetric stuff will now reset after 64 steps too. I think I can live with this :slight_smile:
thank you!

I would at least submit a support ticket @ elektron.se to inform them since this behavior is definitely not correct. With the same CH.LEN both devices should switch at the same time, of course.

3 Likes

Still nothing… Very disapointed…
I’ve been changing the midi routing of my machines to get everything working right but I can’t get it right because of this issue and the ‘Live record mod wheel PB data from external keyboard?’ issue… Both issues are very crippling.

The problem is that they developped an internal MIDI processing that is working only for the Elektron gear which is cueing the next pattern. But they absolutely missed all the other possibilities of using MIDI including with their gear.

For example now, I’m using:

  • The Digitakt as MASTER, send program changes
  • MPC as Slave, MIDI IN: Arturia MIDI Keyboard AND Digitakt; MIDI OUT: Digitakt (MPC has 2 MIDI IN, 4 MIDI OUT)
  • Analog four as Slave, MIDI IN: MPC

The Digitakt start and send the clock to all the machines, I can send mod wheel PB data from external keyboard as it pass through the MPC to the Analog Four (and Digitakt). The digitakt can’t send mod wheel PB but the MPC can. This is why I want my Analog Four to be followed by the MPC. Also because I can resample MIDI sequence into the MPC and then mute each A4 individual tracks… but I also want to use the A4 sequencer if needed… in short this is my workflow…

But if I pattern change on the Digitakt, the MPC will follow nicely but not the Analog Four ! Two elektron machines that can’t sync correctly, so frustrating !

Indeed, the MPC will pattern change right on time with the Digitakt because when it receive a Program Change (or Pattern Change in Elektron jargon) it changes immediatly. The MPC also send a Program Change to the Analog Four but the A4 will cue it instead of changing immediatly. And that’s why it change one pattern late.

Why don’t they put a checkbox option like ‘Direct Program change on Program Change receive’ ?
That’s all I’m asking and I know it is absolutely possible to develop this because it receive a Program Change detection as it is shown as ‘cueing’, why not change directly ? Is it because the Elektron gear is made to be working only with other Elektron machines ? Why there isn’t any update about this ?

In short, if the master device can’t send the program change a few ms before the pattern change is supposed to happen, an Elektron device will always change too late

The problem is not the MASTER, it’s the SLAVE !

When a program change message is sent to an Elektron device, the corresponding pattern is cued for change. This means that the program change needs to be received a few ms before the pattern change is supposed to happen.

Make a checkbox in the settings to disable the cued for change and make it change instantly please ! The cue is interesting when it is synced between two Elektron devices, but if I put a device (here the MPC) on the middle of Elektron Master and Elektron Slave or a non-Elektron device as MASTER it will always change one bar late !

This makes me crazy, I’ve spend hours trying to figure it out and make it work just as expected. I’m a developper as full time job and music producer as passion and this makes me want to develop something just to make it work! I will try to investigate as I see Elektron isn’t very responsive sadly…

The Elektron device can not foresee the future.

Indeed, a 1980’s MPC can do what your gear can’t

1 Like

I have finally found a solution using a MIDI merger.

Digitakt MASTER settings: send clock; transport; prog chang
Digitakt OUT -> Kenton Thru IN

MPC SLAVE settings: Sync In: 1; Out On
Out A: Off

MPC IN 1 : Kenton Thru 1
MPC IN 2: Arturia MIDI Keyboard
MPC Out A: MIDI Merger IN 1

MIDI Merger:

  • IN 1 -> MPC OUT A
  • IN 2 -> Kenton Thru 2
  • Out 1 -> Analog Four MK2

This way, the MIDI Merge can merge the MPC pattern change AND the digitakt pattern change (going through the Kenton Thru), as it receive both time the pattern change message, it will change for sure the Analog Four pattern which is connected FROM the MPC :slight_smile:

Kind of abusive they didn’t implement anything about this and for sure won’t as they developed it for Elektron only. It says a lot and I take a big consideration on this for futur purchase.
I’ve found a solution and I’m happy with it. Not to forget that this solution cost me more than one hundred euros.

Somehow, my DN and DT have suddenly gone out of sync. I have master and channel change lengths the same, (256 and 16) but some tracks have different tempo multiplier/divisors. Up until I tried routing everything via usb midi on my iPad, the patterns changed fine with regular midi din. Now they’ve suddenly gone out off sync with the one pattern late issue. Bah.

I just wanted to add that this is still an issue even though I have found a work around.
Why do Elektron is the only company that ‘cue’ a pattern change ?
I mean all the other gear, racks, effects, synths instantly change the pattern an not Elektron ?
Why isn’t there an option for this ?

When for example sending a program change from Ableton, you will need to use a negative track delay for the track/clip in order for the program change to be sent early enough for the Elektron device to have time to cue the pattern.

I call this a bug

When PROGRAM CHANGE SEND is enabled on an Elektron device that acts as master, the program change will always be sent a few ms early so the receiving Elektron device has time to cue the pattern. That’s why it’s working in an Elektron ecosystem.

And this is a shame that it only works between two Elektron devices

1 Like

Yeah, it’s the only thing that really gets me down with Elektron, it’s only in the last few years they’ve implemented both LSB & MSB for bank changes, for years it meant the Octatrack couldn’t send bank changes to gear unless it only used MSB. That used to drive me mad…

Since getting an MPC as my main hub, the pattern change problem has become a lot more significant for me. If using the program change box on an MPC track or automation the Rytm starts 1 step late for some bizarre reason. I think it’s pretty shocking they keep making new devices that inherit this atrocious behaviour. I have a lot of love for these machines but this issue always feels like they’re just taking the piss out of me. It’s such basic midi stuff…

1 Like

Syntakt released but still nothing about this, ew elektron

Isn’t the ongoing issue that other devices send pattern change instructions “on time”, too late to be followed up on when the pattern has already started repeating?

How is this handled better in other pattern-based sequencers if you can’t look ahead?

I’m not saying it hasn’t been handled in other, more controlled ecosystems between devices of the same manufacturer (Elektron obviously sends the change request earlier in the process.)

2 Likes

Don’t plan on hearing anything about it. It’s been an issue for many years with many different types of MIDI controlled sequencers. If you dig you’ll find threads from years ago.

I even made a software solution for Ableton Live to get things to sync.

You absolutely have to send the program change early.

You best bet is to look for an outside solution.

I’ve had thoughts about a master control box. One that could send a set of user defined program changes to multiple boxes at the user’s request.

Only a thought though, I have no plans to make one currently.

Get creative. Maybe you could use something that already exists to send a bunch of program changes when you want?

1 Like

Did spot this one-

Obviously a pricey solution but good to see that there’s been options built into other devices.

I could see an agile team like Squarp working on a feature request.

Still haven’t tested program change with my OXI One yet.

1 Like

MIDIbox Seq V4 also has an option to send program change early.

I bet something like a BOME box could be used to convert a particular MIDI note (for example) to a program change. Then you’d just have to figure out a setup that worked for you.

1 Like

I am using your Ableton Live program when I am at home in the studio and I start my computer only for this… Thank you for this.
But I wish this could be fixed so I can hook my gear and play live what I produced at the studio. Without depending on a computer for that unique function.

I know it does exists some gear but spending over 300€ for this unique feature is not a viable solution for me when I’ve already spent over 1K on Elektron.

2 Likes

Despite the above apparently being a statement from elektron, this is NOT what I’m finding within the elektron system: PCH is not syncing correctly between M:C and M:S when playing, even though PCH works immediately when playing is stopped and making manual changes.

FWIW, this is what I found out when trying to sync M:C and M:S, starting out from the simplest possible case, 2 16-step patterns.

1 Like

Can someone explain to me the significance of the auto-channel here ?

Sounds like, for the simplest possible setup (or for M:S <-> M:C sync, where sending PC independently is not an option) the autochannel needs to be used ? Does this mean the sender needs to send on the receivers auto-channel ? Or something else ?

Elektron devices with the same auto-channel set will automatically sync patterns, as opposed to using some sort of program change trig like on a Digitakt, for example. I made that comment before the Model series came out, and I’m not familiar with them personally, but I imagine they aren’t too different in that respect.

2 Likes