Feat. req. ARP Sync timings

[oeai]

we can change arpeggio period only in time (ms) right now
i propose to sync it with current tempo, so it was like 1\64 1\16 1\2 and so on
i thought that sync mode (Sort, Sync) can do that, but it's not, sync time is still in ms that is very hard to handle with current beat.

[softrabbit]

Right-click the time knob and there should be a tempo sync submenu in the context menu.

[curlymorphic]

This is already implemented.

If you right click on the time knob, Tempo Sync, choose timing. This could be handled in a better way though

[tresf]

Just a guess, but he may be observing the failure to ever round-robin sync from start to finish in conjunction with a major chord and a standard 4/4 measure. (try it out)

I can draw a picture if you'd like.

[curlymorphic]

@tresf you mean that a major chord is played in 3/4 time ish? maybe pics would help please.

Oh, now ive sat here for a bit,I can here it drifting.

[tresf]

It behaves as described. It's just math. Count the number of notes in a major chord up and then back down, versus the number of slots... The alignment never works out on a standard measure because the C note only gets played once. :)

[curlymorphic]

I agree that is incorrect, but changing that would break backwards compatibility.

[tresf]

It is technically correct. What we could possibly do is increase the chord progression by the appropriate notes to match, but make it an ARP checkbox setting perhaps?

[curlymorphic]

It is technically correct. What we could possibly do is increase the chord progression by the appropriate notes to match, but make it an ARP checkbox setting perhaps?

Yes thats a good idea. we would need to work out how to handle this for various note counts and time signatures.

[oeai]

if we take abstract note and divide it into shares (quantitze) without counting current tempo, then this case can be solved with quantization (1-128).
the other way is in recalculating ms timings with tempo \ period change

[zonkmachine]

@oeai I think it really sounds like you're describing the sync function we already have as described in the two first answers in this thread.

[zonkmachine]

I can draw a picture if you'd like

I would like that plz , but if I understand you right you want the chord to progress up fully to the base note one octave above and then back? It's just a matter to change (code here):
const int range = (int)( cur_chord_size * m_arpRangeModel.value();
to
const int range = (int)( cur_chord_size * m_arpRangeModel.value() + ( bool m_addOneForFunk );

Also, as Vesa commented here, we could implement this with a knob to more fine grained set the range.
I'll try both these option out. I'm currently just testing the arpeggiator with const int range = (int)( cur_chord_size * m_arpRangeModel.value() + 1; and it sounds totally worthwile it imho.