Need help with simple sequencer setup (model:cycles)

[House de Kris]

Cool! Glad I could help out a bit.

I tried some stuff out here. I don't have a Model:Cycles, so I just used an ordinary sequencer instead, therefore what I say may not apply to your use case.

With the clock coming from the NDLR and going to the sequencer, this implies the NDLR is set to Internal clock, and the sequencer must be set to Slave mode. As such, in my setup, the Start command MUST come from the NDLR. Pushing the Start button on the sequencer does nothing, as it's in Slave mode and must listen to instructions coming over MIDI to it. So if you're good with that constraint, then no problem! I didn't take it farther by having the sequencer Pause/Continue parts as you appear to be doing.

Also, you mentioned, "Clock going out of NDLR to M:C and (supposedly back into the NDLR at the same tempo, yes?)" If the clock goes back to the NDLR, it is of no consequence. The NDLR is in Internal clock mode, therefore it ignores whatever clocks are sent to it via MIDI. But, yes, it should be coming back to the NDLR at the same tempo, nonetheless.

At any rate, it's really great what you want to do is now working. Give a shout out if you get stuck again, someone will help.

Thanks for checking it out. Sooo... actually there is an issue, which is that, either way I set it, with M:C as master clock or NDLR, there is a delay. When I have Pad quantize set to 1/4 or 1/8 its basically a beat or an 1/8 behind. If I have it set to none, then it is just a touch late. Still, the motifs stay off by one beat. Everything changes exactly when the M:C hits the 1/8 or 1/4.  Very strange!

If I set it to have my M:C as master clock, it's all wonky. Like if I have it at 100 on the M:C, it'll be 100.8 on the NDLR. I think I read someone else say that M:C's clock acted weird with NDLR. 
But I don't understand the whole delay thing. Changing the PPQ or clkout div doesn't change anything. 

And actually all I'm trying to do is have one track on the M:C change chords. No pause/continue or anything. 

The mystery continues. I have a TR-06 coming next week. Hoping that syncs with less headaches.

OK, looks like two issues here, clock speeds and quantization. 

1-clock speed. Although it may appear they are going at different speeds, the machines are indeed working in lockstep. Has to, as MIDI forces them to. It all comes down to how things are measured and displayed. Let's say you've got two 2-1/2 digit display DVMs. You plug probes from both of them into the same wall outlet. They may both report 120V. All cool. But, one might say 120V while the other displays 122V. Which is correct, what's the actual voltage? They can't both be right. Next, use two 3-1/2 digit meters. One says 120.1V and the other claims 120.4V. In fact, the more digits of precision displayed, the less likely you'll get two meters to agree. For example, use two 6-1/2 digit meters, and no measurement will agree. Same here with one machined slaved to the other. They are in synch with each other, it's just that the way they measure the BPM and display it doesn't agree.

Actually, my tablet is having huge lags right now in displaying what I type, so I have to reboot before I continue. 

HdK

---

I'm back, but unfortunately I must go to work now. I'll share my thoughts on quantization with you later, unless someone else steps in first.

HdK