Arp/seq - round Robin mode on with reset

[Sebastiangarst]

Hi ive posted some topics before about this before but i Will try to make it more precise.

Its about the round Robin mode - on with reset. (Default Settings) ,

What im doing:
Paraphinic 4 + arp/seq running with hold and play buttons on, any Chord of notes playing. (Hands of keyboard)

Are you hearing Sound from osc 2,3 and 4??

I Can only get Sound from osc, 2,3,4
If i chance global Settings to round Robin ON.

But i like the Setting “on with reset”(default) more, but then arp/seq is only using osc 1.

This is Frustration what am i missing, or is it just like this?

[hudri]

Seq works as expected here: Osc1 is used for the primary note in each sequence step, osc2/3/4 are used for additional notes. So you will only hear anything from osc2/3/4 if you have any chords in your sequence.
Arp plays only 1 note at a time (and resets the osc counter on each step), so of course osc2/3/4 are silent.

Or maybe you want to hear each note on all oscs? Then look at parameter 4.3 paraphonic unison.

[Sebastiangarst]

Thanks for anwering!

Yes i totally get your points! it makes sense that way.

BUT.

When im doing the patch books, one you get in original box, and others downloaded from moog website.

I can refer to patch "sparkle motion" from the patch book "dark theme".

There they tell you to set it to robin with reset.
And the patch is all about diffrent osc semitone pitches.
It says USE THE ARP.

Normally you would hit 3 keys like a Cminor,

And then.... Nothing from osc 2,3,4

Its only seq that makes chords. right?

So hole patch is wrong.

There are many more patches with this problem. It seems they can get something out of the round robin "first note reset" (default) setting that i cannot!

So im still confused.

[jerome_n]

I have a similar question - I found your post because i was playing with the "sparkle motion" preset, and once again failed to get the oscs 2, 3, 4 to activate with Round robin on with reset with an ARP with 4 voices paraphony, so decided to google it.

The behaviour does match the documentation, but several patches mention this so i'm very confused.

Have you solved this since then?