Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Art-Net / REST Input for MusicBeam

Open
#126 2 comments 0 reactions 1 assignee View on GitHub

@suplstfdo is already working on this.

Since Jul 17, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

Hi,
I have another Idea I might like to Implement. I have a upcomming party and I want to have a autonomous light show playing. I already have a few PARs that will be driven by ledFx and ArtNet. I also plan to run MusicBeam there. I somehow want to be able to sync ledFx with MusicBeam, so their effects correlate and not just randomly flicker next to each other.

Thus I either want to drive MusicBeam from ledFx, or have some kind of Orchestrator script that selects currently fitting effects on both ledFx and MusicBeams side. LedFx already has a REST API that can be used for this.

On the MusicBeam side there is currently no way to control it by an API. I could imagine two possible solutions:

  1. REST API: Having a custom REST API to control the currently active effect and its properties. This would need a custom integration in whichever program it shall be used in (e.g. the orchestrator script or ledFx).
  2. Art-Net: Is the defacto standard protocol for professional show lightning infrastructure. This solution would have the great benefit, that MusicBeam could be easily integrated into typical lightshow infrastructure and be controlled by a big variety of lightshow tools like QLC+. The application would just listen on a UDP port and interpret the DMX frames comming from it. In the first step I would only interpret the first value, which would be the effect selector. A 0 would be no effect / the Blackout effect. The other Effects would each have a index they can be activated with.

I tend to favor solution 2, because it opens up a whole world of usecases for the project.

Before implementing anything I wanted to discuss it here. If such a contribution is welcomed, I might contribute an Implementation. If you do not see this as a fit for the project in its current state, I might just make a sloppy AI implementation for my own usage. 😄

EDIT: I vibed a prototype, just to verify the idea. This would still need some work, so don't consider it a PR just yet.

Code of the concept: https://github.com/suplstfdo/MusicBeam/tree/artnet
Screenshot:

Image
Dominant language
Processing
Stars
294
Forks
53
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codingjoe/MusicBeam

All issues in codingjoe/MusicBeam

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.