ypares / arpligner Goto Github PK

Re-mapping poly aftertouch events should be just as simple as remapping the note offs (after all those two MIDI messages differ by only 1 bit), however on my aftertouch branch this is not working correctly (at least in Bitwig). Aftertouch events are transmitted only when they are mapped to a note that actually was received by Arpligner. So if you are hitting C3 (in a pattern) and sending aftertouch events on that note, these aftertouch events will be mapped and transmitted only if the current chord does contain a C3.

JUCE code does not seem fishy, so maybe that's a Bitwig problem. I'll check with another DAW.

In Multi-instance mode the pattern seems to be continually sent as MIDI note-off commands and there are not any MIDI note-on commands.

• Add instance of arplinger to chain with MIDI channel 1
• Configure as [Multi-instance] Global chord instance
• Add instance of arplinger to chain with MIDI channel 2
• Configure as [Multi-instance] Pattern instance
• Add sequence driving MIDI channel 2
• Monitor output of pattern instance

Expect to see nothing but actually see MIDI Note Off messages on MIDI channel 2.

• Play a chord on MIDI channel 1
  Expect to hear and see MIDI Note On/Off to match sequence but actually continue to see MIDI Note Off messages only.

Noticed this behaviour on Bitwig 4.4.6 on Windows:

After reloading a project with Arpligner instances, or deactivating/reactivating an Arpligner instance, only the int parameter (Global chord track lookahead) is properly reloaded at its latest value. All the other parameters (choices) are reset to defaut.

On Ubuntu I do not have this behaviour.

The artifacts in the latest builds (4 months ago) are expired so we can't download it, e.g. https://github.com/YPares/arpligner/actions/runs/4098641585 .

win32 build for win32 veterans.

May be a JUCE bug

https://github.com/YPares/arpligner/actions/runs/4090909288/jobs/7054650202

The goal is to get Arpligner to build as standalone exe for usual raspberry pi OSs, and as LV2 for the Zynthian platform.

See https://discourse.zynthian.org/t/gui-less-polyphonic-arp-plugin-buildable-to-lv2/7711/1 for context

Currently, playing chords live doesn't play super great with the default "latch & transpose" behaviour (for management of 0-note and 1-note situations on the chord channel)

The user has to release the keys of the chord at the exact same time, or for a fraction of a second Arpligner will register a 2 or 1-note input (the 1 or 2 notes released last).