LFO trigger from CC Table ignored if same id as LFO?

Midihub Support
1

Hey @Giedrius - thought I’d mention this in case it’s an issue.

scenario & preset

I’ve got a compact solution which selects 8 different channel “modes” from 4 footswitches by distinguishing between short vs long presses.
It does this by using the ON value to both trigger a 1-shot Sq LFO and set it’s depth.
The OFF value stops the LFO either before or after it’s output its second value

Short-Long Press Mode Selector.mhp

The CC used for Manual Trigger mapping is Virtual H Ch.9 CC#1.
It works fine when the LFO is say CC#2:

LFO1shotCC2
LFO1shotCC21644×1568 394 KB

(so the High|Low LFO values will always give Ch.9 ± i for switch i )

but when the LFO is CC#1 (same CC# as trigger even tho different channel)…

LFO1shotCC1
LFO1shotCC11644×864 127 KB

…no LFO triggered.

Just did a quick test with a version mapped direct to MIDI A: issue seems to be related to CC Tables

1 Like
2

Nope, not CC Table; it’s a virtual mapping thing:

LFO1shotCC1vm
LFO1shotCC1vm1644×988 143 KB

1 Like
3

Good catch - the LFO pipe absorbed the matching CC id event without checking for it to be on Ch. 1 on which all LFOs work. If it was started & output enabled, it would transform the CC value according to its settings, but in case it’s not started, it silently updates its internal memory of the last seen CC value and drops it.

I’ll get this fixed.

1 Like
4

Aah and so, because in my scenario, it’s the mapping event “bouncing back off” the virtual output that triggers the LFO, the LFO never gets started!