[request] 2nd q-link (arp) in chord mode should work in real

Being able to modify the arpeggiator speed as the arpeggiator is playing would allow for smoother control of the chord speed.

It would also be cool if there was a way to set maximum and minimum arpeggio time. After a certain length it isn't so useful, and if you go down to 0 it stops playing. It's awkward to try to limit this manually.

What are you talking about. it does work in realtime!!
well i can anyways, so maybe try in grid edit mode instead. I find the values good by the way,

It updates the speed per-"strum", but not per-note. I haven't tried it in grid mode, maybe it works there.

I just tried it in grid move. The behavior is the same: speed updated per-chord/strum, not per-note.

In modular synth terms, it's like a sample & hold module grabs Q-link value when a chord is hit, applies this to the strum speed & keeps it the same until the chord is done, and doesn't grab a new Q-link value until the chord triggers again (thus repeating the process).

Maybe this will be a little clearer.

Requested behavior:
(Pad hit, Q-link sliding down) Pluck-Pluc-Plu-Pluck (Pad, Q-link sliding down more) Plu-Pl-P-Pluck (Pad hit, Q-link sliding back up) P-Pl-Plu-Pluck


Current behavior (exactly the same pad/Q-link activity):
(Pad hit, Q-link sliding down) Pluck-Pluck-Pluck-Pluck (Pad, Q-link sliding down more) Plu-Plu-Plu-Pluck (Pad hit, Q-link sliding back up) P-P-P-Pluck

yeah i can see what ya mean. I do not think this is anyway a real deal breaker. THere is a work around, just do multiple passes or edit in grid edit mode. It is not something i would consider a big deal myself. In other words I think its just how it is and do not thing it would be a great improvement, but do understand that you would be frustrated by this but really in the greater scheme of things you can see that is good and works just not perfect

It's not a big deal at all. It just seems like an easy thing to fix, a low-hanging fruit.

The messed up chord timing when you first hit the pad, however, is a problem.

license wrote:It's not a big deal at all. It just seems like an easy thing to fix, a low-hanging fruit.

The messed up chord timing when you first hit the pad, however, is a problem.

yeah but that is in ARP mode though not CHORD mode?? I think you will find the ARP function works better in the CHORD mode instead of the ARP mode for chords. Which of course makes sense, like your not using correct mode. Not that there is any such thing but you know what i mean, you are kinda doing it another way. I did notice it though in ARP mode, but i do not use ARP much, but do use CHORD mode a lot, and use the arp function in chord mode, and write in step edit mode. Not the same I know just giving you my view.

I haven't used either much at all but CHORD mode has attracted my interest. I like the ability the CHORD mode has to change to timings that don't line up perfectly with the grid, so your resolution is the pulse/tick rather than standard 1/8th, 1/16th, triplet, etc. As far as I know that's not available in ARP mode. The real-time option would just be icing on the cake.

I was using the arpeggiator on my Shruthi-1 to do this kind of thing before and it has many more options, so I will probably use that when the MPC isn't meeting my needs.

yeah the chord mode is awesome, and under rated if you ask me
lol, all good. Yeah ARP mode to me is not as useful as CHORD mode, and I to use external synths if i really need an ARP.