A modern replacement for LEDBlinky: visual arcade panel layout, node-graph LED wiring, multiple LED boards per PC, and per-game lighting for LaunchBox/BigBox.
Still in development. LED-Next is used and tested on one real cabinet (4 players, two PacLED64 boards, LaunchBox/BigBox), but it is not finished: expect rough edges and changes, and check
TASKS/00_ACTIVE_PRIORITIES.mdfor what is being worked on.
Games: each game's lights are previewed on your panel (and on the real boards), and can be edited.

Panel: a visual designer for your control panel. The panel shows what the boards are lighting right now.

Wiring: drag each button's red, green and blue to board pins, or let the wiring wizard find them.

Boards: the live output of every pin on every board. Click a pin to find its LED.

LED-Next reads LEDBlinky's data, so your existing setup carries over, and then adds:
-
One app for everything. Panel layout, wiring, game lights, testing and live lighting live in one window, not spread across separate configuration tools.
-
See your panel. A visual panel designer (with your panel photo behind it) and a node-graph wiring editor, so you can see which button goes to which pin and colour.
-
A wiring wizard that lights one pin at a time on the real boards: click the button that lit and the colour it showed, and the wiring is built for you.
-
Live preview. Selecting a game lights it on screen and on the real panel at once, and every edit shows live.
-
Edit lights safely. Your colour changes per game or per platform are stored apart from the imported data and are kept when you re-import LEDBlinky. One click reverts a game to its imported lights.
-
Light many games at once. Templates, copy and paste of lights (all of them or one button) to the selected games (a template can go on every match), and saved smart lists (platform, genre, button count, "6-button fighting games"…).
-
Lights follow your real key bindings:
- for every MAME install (each one's
ctrlrfile,default.cfgand per-game cfg), not just one; - for TeknoParrot games, from each game's own profile.
So a racing or flight MAME build that remaps buttons lights the buttons the game really uses.
- for every MAME install (each one's
-
Knows your LaunchBox library. It reads LaunchBox's games and platforms. Games that LEDBlinky has no data for still light from MAME's data or the platform default. You can filter for games recently added to LaunchBox or still needing setup. LaunchBox's control-panel pictures show beside each game.
-
Live BigBox lighting. The plugin sends every selection, platform-wheel move, launch and exit straight to LED-Next. Each change is timed in the log, so slow spots are easy to find.
-
Live emulator lamps. MAME's network output and Windows messages are both supported (for example, Start blinks while a game waits for a coin), and every output a game sends is logged.
-
Several boards, the same order every time. Boards are found by their board id, not USB order, so unplugging one doesn't shuffle your wiring.
-
Works without hardware. Simulator mode lets you set up and test everything away from the cabinet.
-
Stays out of the way. It starts in the system tray with LaunchBox/BigBox, and installs to one exe plus your settings folder.
-
Read-only towards other tools. LED-Next never writes to LEDBlinky's or LaunchBox's files. The only exception is its own plugin folder inside LaunchBox.
Tested on a 4-player cabinet with two Ultimarc PacLED64 boards, LaunchBox/BigBox 14.1 and LEDBlinky's data.
LED controllers
- Ultimarc PacLED64 (RGB), several boards per PC, identified by board id rather than USB order.
- Ultimarc I-PAC Ultimate I/O (96 pins, 32 RGB LEDs): new and untested on a real board. Written from Ultimarc's documentation; if you have one, please try it with docs/TESTING_ULTIMATE_IO.md and report back.
- Add or remove boards in the Boards tab.
- Simulator mode: everything works with no boards attached.
- Not supported yet: other Ultimarc boards (PacDrive, Nano-LED, I-PAC LED), LEDWiz, and other makers' boards.
Panel and wiring
- A visual panel designer: buttons, joysticks, trackball, coin and start, with a photo of your panel as a background.
- A node-graph wiring editor and a wiring wizard, which lights each pin in turn so you can find its button.
- A Boards view with a live grid for every pin, plus test patterns.
Game lighting
- Imports LEDBlinky's data (controls, colours and input map) and lights each game the way LEDBlinky would. It matched LEDBlinky on the real cabinet. It only reads LEDBlinky's files; it never changes them.
- Light inheritance: game → parent → platform → MAME default.
- MAME fallback for arcade platforms. On a platform whose games are MAME rom names (Sega Naomi, Atomiswave, Model 2/3…), a game LEDBlinky didn't set up gets a copy of MAME's lights for the same rom instead of a blank or generic platform default. Games you've edited are left alone.
- Per-game and per-platform colour overrides, templates, bulk copy, and saved smart lists. Besides the colour swatches, a colour picker (the "+" swatch) picks any colour and keeps your added colours for next time.
- Each emulator's own key bindings. When a game's buttons are remapped in the emulator, the lights follow:
- MAME: each install's
ctrlrfile,default.cfgand per-gamecfg(for cabinets with several MAME installs); - TeknoParrot: each game's user profile (DirectInput and RawInput keyboard bindings).
- MAME: each install's
Front ends
- LaunchBox / BigBox:
- LED-Next reads its game library; it only reads it and never changes it.
- A plugin lights the panel as you browse games, platforms and the BigBox wheel, while a game plays, and when you exit.
- The plugin starts LED-Next in the system tray.
- LaunchBox pictures ("Arcade - Control Panel", "Arcade - Controls Information") and button-layout banners in the Games tab.
Light shows (Animations tab, all off by default; tested on the cabinet with BigBox)
- Idle animation: after the controls haven't been touched for a set time (default 5 minutes), the panel plays one of ten animations (rainbow wave, comet, twinkle, player colours, scanner, ripple, fire, rain…) or a random one that changes every so often with a cross-fade, at an adjustable speed. Any key, button, joystick, mouse or trackball ends it and the selected game lights again. It never starts while a game is playing, and by default only while LaunchBox / BigBox runs. BigBox's own attract mode moving the selection doesn't end it.
- Follow the sound: during the idle animation the lights pulse with the music or sound playing on the PC (Windows' default speakers; LED-Next only reads Windows' level meter, nothing is recorded). Two animations react to the sound themselves: a level meter from the middle out (left/right channel) and a colour flash on each beat.
- Start-up and shut-down animations for BigBox (optionally LaunchBox too): e.g. "Sweep on" when BigBox has started, then the selected game; "Fade out" of the game's lights when it closes, then all off.
- "Try" buttons play each one on the panel.
Live lamps from emulators
- MAME, over network output (
output network) or Windows messages (output windows). Lamps are mapped through LEDBlinky'sMameOutputs.ini; for example, the Start lamp blinks while Galaga waits for a coin. - Spoken button labels (Speech tab, off by default): when BigBox launches a game, its button labels are read aloud and each button blinks while its label is said. The game's title comes first (bracketed extras such as "(World 940223)" left out), with an adjustable pause after it; a game without labels just says its name. Again on MAME's pause; a button press or joystick move stops it. Windows' newer voices (Microsoft Mark, David, Zira) are listed first and sound better than the old "Desktop" ones. Can copy LEDBlinky's speech settings.
- Known lamps (Lamps tab): every output a game reports (lamps, LEDs, recoil…) is kept in the game library per emulator and game, with what it lit, its values and when it was last seen. "Not mapped only" lists the ones that light nothing yet. This is the one place future lamp triggers will build on.
- LED-Next's own lamp table (
lamps.mapsincabinet.json): map any emulator's outputs to panel controls, per game or for all games, without editing LEDBlinky's files. For MAME it comes beforeMameOutputs.ini. No editor in the app yet. - Other emulators' lamps, told apart by their process (written from each emulator's source, and tested on the
real cabinet with MAME, Keisho, Odin, Supermodel, TeknoParrot and Flycast):
- Flycast (Naomi/Atomiswave): its "Network Output" setting. Lamps differ per game, so each needs a
lamps.mapsrow. - TeknoParrot, through Output Blaster (OutputBlaster.dll in the game folder, "Enable Outputs" in TeknoParrot).
- Odin (Sega Hikaru):
[outputs] network = onin odin.ini. - Keisho (Sega Model 1/2/3): Windows or network outputs in its System tab. Uses MameOutputs.ini like MAME.
- Supermodel (
-outputs=win) and M2Emulator (with Output Blaster). - Start lamps of TeknoParrot, Odin, Supermodel and Keisho games work without any setup (checked on the cabinet: Operation G.H.O.S.T., Brave Firefighters, Scud Race Plus, Daytona USA); other lamps need rows.
- No lamp outputs at all: pcsx2x6, the Xemu Chihiro fork, Hypseus Singe. Their games keep the front end's lights.
- Flycast (Naomi/Atomiswave): its "Network Output" setting. Lamps differ per game, so each needs a
Not yet: other front ends (only LaunchBox/BigBox), LEDBlinky animations (.lwax), BigBox playlists, and
lighting by front-end section.
Needs: Windows 10 or 11, the .NET 8 Desktop Runtime (or the self-contained build), and, for PacLED64 or Ultimate I/O
boards, Ultimarc's PacDrive64.dll, which you supply yourself.
From a release (no build tools needed): download from the Releases page:
LED-Next-x.y.z-win-x64.zip(small, needs the .NET 8 Desktop Runtime, x64), orLED-Next-x.y.z-win-x64-self-contained.zip(bigger, needs nothing else);- for LaunchBox/BigBox, also
LED-Next-LaunchBox-plugin-x.y.z.zip.
Unzip the LED-Next zip, unzip the plugin zip into the same folder, and close LED-Next, LaunchBox and BigBox.
Then double-click Install LED-Next.cmd.
From the source code: the same Install LED-Next.cmd in the repository builds LED-Next first (needs the
.NET 8 SDK). It builds the plugin against your LaunchBox too (needs the .NET 10 SDK).
Either way, LED-Next is installed to D:\LED-Next (or C:\LED-Next with no D: drive). The installer also
adds a Start menu shortcut and installs the LaunchBox/BigBox plugin, pointed at the installed exe. LaunchBox is
found on any drive: from its Desktop or Start menu shortcuts, else X:\LaunchBox or X:\<folder>\LaunchBox. If it
isn't found, the installer asks for the folder (press Enter to skip the plugin). The installed
folder holds only:
LED-Next.exe the whole app in one file
PacDrive64.dll Ultimarc's SDK DLL (copied from your current setup; not shipped with LED-Next)
config\ cabinet.json, games.db, window.json (your settings; never overwritten)
logs\ led-next.log
Run it again to update: config\ is kept, and leftovers of an older multi-file install are removed. On the
first install, settings are copied from the repo's Debug build folder; that folder is left untouched.
Options (pass them to the .cmd or to tools\install.ps1):
-InstallDir E:\LED-Next,-LaunchBox "F:\Games\LaunchBox"(skips the search)-From <old folder>: where to copy the settings from-NoPlugin,-NoShortcut-SelfContained(source code only): a bigger exe that needs no .NET on that PC-Uninstall: keepsconfig\; add-RemoveSettingsto delete it too.
- Set
<Version>inDirectory.Build.props, commit, then tag and push:git tag v0.2.0andgit push origin main v0.2.0. GitHub Actions (.github/workflows/release.yml) tests, runsbuild\Build-Release.ps1and publishes both LED-Next zips. - On a PC with LaunchBox, at that commit, run
tools\build-plugin-release.ps1. It builds the plugin against LaunchBox's own DLL. Then attachdist\LED-Next-LaunchBox-plugin-x.y.z.zipto the release (Edit release, then drag the zip in). GitHub can't build the plugin, because LaunchBox's DLL isn't ours to upload.
dotnet build LedNext.sln
dotnet run --project src/LedNext.App
dotnet test
The app starts in Simulator mode, so it works without boards attached. Switch to
Hardware mode on the cabinet. See TASKS/00_ACTIVE_PRIORITIES.md for hardware setup.
Config is stored in config/cabinet.json next to the exe; logs in logs/led-next.log.