Skip to content

Beat sync / output set (loopjefe support) - #10

Open
sastraxi wants to merge 11 commits into
mainfrom
ur/loopjefe
Open

Beat sync / output set (loopjefe support)#10
sastraxi wants to merge 11 commits into
mainfrom
ur/loopjefe

Conversation

@sastraxi

@sastraxisastraxi commented Aug 24, 2026

Copy link
Copy Markdown
Collaborator
  • allow OutputSet (does not appear to increase CPU usage as I feared; pi-stomp drops most of them quickly)
  • Forward on a beat_sync message from mod-host (see Beat sync mod-host#3)
  • notes from discovery about how MOD input ports + echoes work (each port is unidirectional)

sastraxiand others added 9 commits July 4, 2026 22:30
pi-stomp renders plugin state from output_set: loopjefe's looper state
drives its footswitch LED, LCD slot, and loop-progress border. Suppressing
it left that state permanently stale.
The suppression existed to keep meter traffic off the local socket, but
that fear was unfounded: a live gareus meter measures ~30 msg/s, not the
375/s per-cycle ceiling, because plugins update monitored outputs at about
UI refresh rate and mod-host discards the rest. pi-stomp drops the ports
it hasn't subscribed to anyway.
data_ready stays suppressed. pi-stomp echoes it from the socket read loop
before queueing, so acking would provide no real backpressure -- it is
functionally identical to the existing any_non_local_received self-ack
while putting pi-stomp's 10ms loop inside mod-host's feedback path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pi-stomp renders plugin state from output_set: loopjefe's looper state
drives its footswitch LED, LCD slot, and loop-progress border. Suppressing
it left that state permanently stale.
The suppression existed to keep meter traffic off the local socket, but
that fear was unfounded: a live gareus meter measures ~30 msg/s, not the
375/s per-cycle ceiling, because plugins update monitored outputs at about
UI refresh rate and mod-host discards the rest. pi-stomp drops the ports
it hasn't subscribed to anyway.
data_ready stays suppressed. pi-stomp echoes it from the socket read loop
before queueing, so acking would provide no real backpressure -- it is
functionally identical to the existing any_non_local_received self-ack
while putting pi-stomp's 10ms loop inside mod-host's feedback path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sastraxisastraxi changed the title Ur/loopjefeBeat sync / output set (loopjefe support)Aug 24, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@sastraxi