#163
  • Created on
    2011-06-11 15:59
  • Reported by
    thijz
  • Status
    New
  • Priority
    Normal (3)
  • Assigned to
    -
  • Milestone
    1.0
  • Plan Level
    -
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug

midi : add new option to SELECT_NEXT_PATTERN (feature req)

option to combine how the next pattern is selected in stacked mode (next pattern is activated at the loop point) with the select_next in non-stacked mode (only 1 pattern is active at once)
requested by Berry (see http://hydrogen.popez.org/hcms/node/1843#comment-57347)
User picture
  on 2011-07-23 08:40 *
By thijz
this basically means that SELECT_NEXT_PATTERN in stacked and non-stacked mode behave differently

the current SELECT_NEXT_PATTERN should be replaced with this :
- SELECT_NEXT_PATTERN_NOW this is the current default behavior when working in non-stacked mode (i believe that Wolke has an improved version 'select_next_pattern_instantly')
- SELECT_NEXT_PATTERN_ON_LOOP (or something like that) : this is the current default behavior when working in stacked mode
User picture
  on 2011-07-24 16:11 *
By thijz
Summary changed from add new option to SELECT_NEXT_PATTERN (feature req) to midi : add new option to SELECT_NEXT_PATTERN (feature req)