Resend identical automation event?

Hapax
1

Hi,
I’ve looked around the forum and scratched my head on that issue for some hours now: is there a possibility to just resend the same automation value for a CC twice in a row?

If I’m not mistaken, Hapax mostly works like a “toggle” logic: it sends something only if that exact something was not the last event sent. “Fire and forget” logic, such as sending 5 times “CC#27 value 5” in a row, is not possible to my knowledge. Don’t get me wrong, I think this is great design for optimization.

When it sends an automation event, it’s CCnumber+value. Upon pattern change, this is followed by CCnumber+defaultValue (only if a default value is setup of course).
If there are no default value in that lane however, and if there are no changes in this specific CC’s value itself, one can write as many automation event, Hapax won’t send them (I verified this in the awesome Midi Out screen).

My problem is, I would like to control my looper remotely (Microcosm), and for some reason its CC are designed like “fire and forget” CCs. For example:

  • CC#28, any value (0-127) will trigger Looper Record
  • CC#29, any value (0-127) will trigger Looper Play
  • CC#31, any value (0-127) will trigger Looper Stop
  • CC#34, any value (0-127) will trigger Looper Erase
    etc.
    I would like a way to launch and stop the looper without triggering double events. If I put a “default” value, it will double trigger any event (send a value, then send default value, thus sending a “Play” command twice for example). If I don’t put a default value, it will only shoot “once”, which is nice, but regardless of Pattern changes, it will never send that value again (so I can’t proceed to a second try). Even Stopx3/Start won’t resend that value :).

I’m going to try moving forward with double triggered events, hoping not to get into trouble as the workflow gets more complex.

I’ve also looked into applying randomization or effects (filter, matrix, lfos etc.) on that poor Automation event so the value is somehow always different (and thus sent), but I really think there must be an easier way…
PS: I don’t want to do the configuration on the microcosm side (it can quantize, but it’s not setup to the Hapax clock).

Ultimately, I do not know if the Microcosm’s design is standard practice or not (had they chosen to have a single CC value, like “0”, actually do “nothing”, one could easily leverage “toggle” logic to do anything really). If it’s a standard design practice, then I hope it won’t mind a double trigger here and there :smiley:

Any chance someone has an idea to resend an identical automation event?

2

another track… at least you have 1 more chance to send another identical event. i could be wrong of course.

3

Just tried. It does work like another “one shot”. Switching between tracks / muting etc. won’t retrigger. Thanks for offering.

1 Like
4

you can do it 32 times if youre clever!

or more with something like this

https://www.perfectcircuit.com/midi-solutions-event-processor.html

turn a note into a cc value then youll have full control no matter what you use! complete with resend as many times as you need. and compensate for any ‘latency’ with hapax

5

Found a workaround costing 4patterns in a single track:

  • set a pattern to CC#28 (Looper Record), value (e.g. 10) followed immediately by another value (e.g. 50), Follow#1 to STOP
  • set a pattern to CC#29 (Looper Play), value (e.g. 10) followed immediately by another value (e.g. 50), Follow#1 to STOP
  • set a pattern to CC#31 (Looper Stop), value (e.g. 10) followed immediately by another value (e.g. 50), Follow#1 to STOP
  • set a pattern to CC#34 (Looper Erase), value (e.g. 10) followed immediately by another value (e.g. 50), Follow#1 to STOP

Bonus: RGB all the way each of those patterns so they are red, green, blue etc. like a nice looper :slight_smile:

It’s not perfect (it still double triggers for each action), but at least it is very compact and does not send an endless loop of cycles (which would make the microcosm LEDs look like they are having a festival of their own).

Note: I have not run checks on the Microcosm to see if it’s affected by double commands.

PS: your idea had inspired another one, where I tried to have several tracks with different values. Yet switching from, say Track 1 (with CC27 value 50) to Track 2 (with CC27 value 60) also only works once: I assume the Hapax learns and remembers, on a per track basis, if a command was sent already before deciding to send again or not.

1 Like
6

cool! btw that midi solutions in line device is powered from midi cable so no extra cables

1 Like