Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Exquse

Members
  • Posts

    2
  • Joined

  • Last visited

Exquse's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Thank you for youre reply. Its solved. It seems there is a snapshot function in Realearn. With that I control the blocks in Helix and the leds on the floorboard
  2. Hi everyone, I’m testing Helix Native inside Reaper 7 (Windows 11) together with a Nektar PACER and ReaLearn. The sound is amazing, but I’m stuck on one important thing: LED sync. Here’s what works: Block ON/OFF is assigned to automation (“Controller Assign → Bypass → Switch 01–16”). ReaLearn maps Helix automation → PACER LEDs. Clicking blocks with the mouse updates PACER LEDs correctly. Clicking presets with the mouse also updates the LEDs. Tapping Pacer toggles blocks on and off Here’s what does not work: Selecting snapshots via MIDI CC69 (or mouse) changes the snapshot inside Helix Native, but no automation update is sent, so PACER LEDs don’t update. Selecting presets via MIDI Program Change loads the preset, but again no automation change is sent. (selecting presets by double click DO update the PAcer Leds) So I,m lost and the core issue is: Helix Native doesn’t seem to send any automation updates to the host when snapshots or presets are changed via MIDI. My question: Is it possible to keep a hardware controller (like the PACER) in sync when changing Helix Native presets/snapshots via MIDI? Does Helix Native send any automation to the host when doing this? If anyone has a working setup or a known workaround, I’d really appreciate it. Thanks en best regards, Quirien
×
×
  • Create New...