multipegiator

[netpipe]

See also #687

more options for existing arpegiator options in samples .press the note x ammount of times before moving onto the next. maybe some delay options for inbetween and after note strikes too.

[tresf]

@tecan, if you can draw a mock-up of this idea, it will allow developers to gauge feasibility.

[diizy]

On 11/14/2014 05:33 PM, Tres Finocchiaro wrote:

@tecan https://github.com/tecan, if you can draw a mock-up of this
idea, it will allow developers to gauge feasibility.

No need really. There was already a patch written for this kind of
functionality, it just never got finished as there was some GUI issues
and things... in any case it's better to postpone it until the 2.0
effort because there will likely be changes to how arpeggios and
stacking are handled - as well as notes in general.

[netpipe]

[tresf]

in any case it's better to postpone it until the 2.0 effort

For filing purposes, shall we start categorizing these 2.0 tasks? I only ask because we don't have a dedicated 2.0 milestone yet. (use 1.3?)

-Tres

[diizy]

On 11/14/2014 06:03 PM, Tres Finocchiaro wrote:

in any case it's better to postpone it until the 2.0 effort

For filing purposes, shall we start categorizing these 2.0 tasks? I
only ask because we don't have a dedicated 2.0 milestone yet.

Hmm, not just yet, I don't think... there's still too many uncertainties
here. Let's wait until we have a solid plan and roadmap in place...

[zonkmachine]

@tecan
You can check out my hacks for the arpeggiator here.
#687
( it currently wont compile though )

[tresf]

Thanks @zonkmachine. Since your pull request is closed, I'll leave this bug report open, but we should probably merge information from the two into this new request to make it easier to read when we revisit this down the road.

[Umcaruje]

Closing in favor of #2080