A few new apps for launchbox users UCR-Next & LED-Next

[QuincyR]

Hi Everyone, I wasn't sure if it was ok to post this here, mods please let me know and I can move or remove as required.

I started two small personal projects that are now live. With help from Claude and building off what a few other apps have started in the market, I built a virtual controller program (which builds on what UCR started, consider it a spiritual successor called UCR-Next) with a bunch of new features. It imports profiles from UCR v090 (or builds profiles from scratch) and can act as a stand in replacement (at the user's discretion) if you install it to a folder with the same name.UCR-Next github

The second item is LED-Next, a modern Windows replacement for LED Blinky. It drives arcade button led and animations. It has better performance, switching between games in LaunchBox displays the LED buttons as fast as 3 milliseconds. It's stable and won't leave lights on if the app encounters a problem. It runs in the background and can import your LED Blinky data, building on it with a new database. You can find it here: LED-Next github

Pics are on the github links above

Both are based on my current arcade setup, launchbox frontend, and ultimarc led Pac64 controller boards. LED-Next comes with a launchbox plugin so when using either Launchbox or Bigbox the switching works as you would expect. The two apps can also share some data. Both apps are free and have many new features; please see their respective GitHub pages. I will continue developing both, adding new features and support for different frontend software, etc. So far I’m using both with my setup and they are working well. I hope others find them useful and suggest some new features you may want to see.

Thanks!

Edited 9 hours ago by QuincyR

[rexryan]

Does LED-Next speak what the buttons do?

 

[QuincyR]

it doesn't at the moment, though it does have button naming included. I was debating if I should include that feature. i had it enabled for LED blinky and sorta liked it for a while before I started skipping the audio.

My next focus is to get output from all the different emulators working to animate the lamps. The current build works with mame lamp output if you have it enabled.  

[QuincyR]

If i do include the buttons being read out, I want to improve on it in some way. any ideas what would make it better?

[QuincyR]

version 0.1.1 is up. Changes:
- It can speak your game name and button names ( some extra controls under the speech tab)
- improved the output lamp handling ( 1st step towards allowing the end user to create custom lamp animations & triggers)