Amalgamated Harmonics - plan for v1



In v1.0.0 a new iteration of Arpeggiator will be released, breaking the functionality of Arpeggiator MKII (which is quite tricksy to use) into 2 modules (Arp3.1 and Arp3.2) which will contain almost all existing functionality in a much simpler format. These two modules can be cross patched to create the complex sequences possible with MKII.

What will be missing is the ‘trigger’ function. Having two clocking inputs was confusing and probably not helping people use the module.

With the V1.0.0 release, Arpeggiator MKII will be deprecated and removed in V2.0.0

Polyphonic cables

Bombe, Galaxy, Progress, D’acchord and Arp3.1 will get polyphonic cabling. Existing modules will get a new mark and the old modules deprecated, to be removed at V2.0.0


I am looking at removing almost all the knobs from Progress and replacing them will dropdown menus (like Blamsoft modules) and inputs which should make the module easier to use (especially finding chords and understanding the current state of the module)

Obsolete modules

There are three obsolete modules, (the first versions of Scale Quantizer, Arpeggiator and Imperfect) that have been marked as deprecated for a long time, since v0.6.0 (April 2018) and have newer versions. Now it is time to clean up and these modules will be removed in v1.0.0

Deprecated means: It will not be maintained (any bugs reported will not be fixed) and will be removed completely at the next major release.




Thanks for the news, John. I’m an avid fan of your modules, and I’ve been building and deploying the new versions as they appear on github. I’m not sure how I like the plan for Arpeggiator MkII, I use it a lot as-is, though I’ve never used the Trigger port. I guess that as long as I lose no functionality I can make the switch, though it will eventually mean reprogramming some patches.

I would love to see some way to delimit the Steps to play a sequence beginning on any step (now the delimitation allows sequences starting only on the 1st step, unless I’m missing something). I’m not at all sure how you’d do that.

Anyway, I’ll continue to follow your development path. Gotta love those Amalgamated Harmonics modules ! :slight_smile:

Best regards,



The idea is to split the ‘chord’ and ‘pattern’ sequences. So this is what they look like right now:


So - for example - ‘Strings and Arpeggio’ should be an easy patch to fix as Arp3.1 is a drop-in replacement.

In any case, ArpMKII will not be going anywhere soon (not for another year at least).

Your idea for starting on any step seems interesting and not too hard to do. I’ll take a look.



All the development work I had planned for V1 is complete. AH modules build cleanly against the Rack V1 branch (at time of writing commit 487c24c). Any problems found are probably problems with AH modules not Rack, so bug me not @Vortico. I will continue to track the V1 Rack branch and work on a UI overhaul.

New modules

  • Arp3.1: Arpeggio over a note sequence
  • Arp3.1: Note patterns
  • Imp: Single channel Imperfect, spits out 16 randomised gates over a poly cable
  • Progress MkII: Updated UI using drop-down menus, with polyphonic cable outs. Root/Mode controllable within module
  • MuxDeMux: Multiplexer/Demultiplexer for polyphonic cables. Multiplexer side has a gate out port for channel presence, with configurable bias
  • PolyProbe: Diagnostic tool for Polyphonic cables

V1 implementation

  • Polyphonic cables (D’acchord, Galaxy, Bombe). Switchable with context menu
  • Tooltip implementation

General improvements

  • More readable text colour
  • Fix order of notes in chord inversions
  • Better chord naming and chord ordering
  • Better default values for P and Noise setting in Generative
  • Fix Dorian mode definition
  • Bombe defaults to CMajor not C4 on all outs

Love your Progress module! I need to check out your other offerings! Thanks so much!

Cool Breeze

Polyphonic outputs should usually copy the number of channels of one of the inputs instead of having a context menu item. The exception is when the module is the “source” of the polyphony, like an arpeggiator.

@johnhoar Any chance getting CV control for Ruckus’s knobs?

The exception is when the module is the “source” of the polyphony, like an arpeggiator.

Bombe and Galaxy are chord generators using a fixed number of channels and the ‘old ports’ and context menu are included for backwards compatibility for patches which use the previous version of these modules.

Any chance getting CV control for Ruckus’s knobs?

It would be through a set of polyphonic inputs, so you’d have to use something like Merge to address the right control.

Hi John ! I’ve been testing your v1 plugin for a while. It’s coming along nicely, not much more to add at this time. My tests are pretty light right now, they’ll get heavier as the v1 release date approaches. Just wanted to shout out some praise for the AH modules in v1. :slight_smile:

1 Like

Some updates:

  • Progress 2 now supports multiple parts - up to 32; with the part selected through a control or via CV. Number of steps, key and mode are still (global) so changes e.g. to the number of steps between parts have to sequenced along with the part change. A part can be copied in order to build up pieces with less effort
  • Progress 2 can shift the octave of a chord up or down by up to 5 octaves. As well as adding flexibility it can help in making chord inversions more useful.

Overall UI and new Part additions:


Chord selection:



  • Remove gate outs and poly/mono options where not needed; Bombe, Galaxy and Progress output 6 channels all the time on poly and mono outs. Simplicity ftw.

V1 has gone through the acceptance progress. The changes for V1 can be found here:


Awesome John!

Missed this before now. Absolutely can’t wait for Progress v1. Parts make it an absolute win.

@johnhoar: I was just thinking about this again, I don’t care how to address 'em, ‘CV Everything’ is a mantra I like :wink: given we are in the modular (albeit virtual) world. Please, pretty please? :wink:

@johnhoar Is it just me or the Galaxy module is not showing text?


Seems the font is not converted at the svg?

Oh yes - well spotted… Thanks!

Done. It’s fixed and will appear in the Library sometime soon.