Anyone using LEDBlinky?

[FlightRisk]

I know LEDBlinky works directly with some sofware or has a standalone version that may be able to tie in somehow. Is there LED Blinky support, now or planned?  Is there support for RGB LED control in some other way.

[DOS76]

There is LEDBlinky support if you look up post by Arzoo he is the author of the software and he comments on the forums to try and help people out with it also there are settings in LB under Tools>Options>LedBlinky where you can enable it in the program.

[DerHof2007]

Yeah Arzoo is great for tech support.

Also make sure you download the PDF manual. I've downloaded countless pieces of software over the years and he has one of best, easiest to follow, up to date manuals I've ever seen.

Also check out this guys 5 part series on setup for it. Very informative. Wish it existed 6-7 years ago when I first used it!

https://youtu.be/opu6NofnyWg

 

[FlightRisk]

Amazing. Thanks. This is going to take a while. Hope my wife will understand why I will be locked in the bonus room for hours for the next few years

[SteveB69]

Hi, can I jump in & ask, I'm new to LB & Ledblinky, when LB launches it flashes all my buttons via ledblinky but after the loading animation it stops & then leaves 5 buttons lit. I don't know why it's keeping these 5 lit? I'd ideally like it to have lit the buttons I'm likely to use ie Play, Page Up & Page Down. Where do I go to configure what buttons Ledblinky lights up please?

[Headrush69]

On 10/14/2019 at 11:22 AM, SteveB69 said:

Hi, can I jump in & ask, I'm new to LB & Ledblinky, when LB launches it flashes all my buttons via ledblinky but after the loading animation it stops & then leaves 5 buttons lit. I don't know why it's keeping these 5 lit? I'd ideally like it to have lit the buttons I'm likely to use ie Play, Page Up & Page Down. Where do I go to configure what buttons Ledblinky lights up please?

Set up your keys in BigBox and it follows that.

[Hifihedgehog]

On 12/30/2019 at 8:56 PM, Headrush69 said:

Set up your keys in BigBox and it follows that.

 

 

Digging into this now, I set up my controllers in Big Box but how do I set up the light to button mappings? I have a new RGB setup (PACLED64) and LEDBlinky needs to know which RGB LED trio goes with which controller and button. How do I set up the buttons in BigBox to know which XInput button goes with which LEDs? I have two virtual XInput controllers created via XOutput since I am having to combine two standalone analog joystick (Ultimarc Ultrastik 360) with a button encoder (Xin-Mo Co XM-10) to get two functional controllers across my repertoire of games. Maybe @arzoo can point me in the right direction? (I have full paid licenses to both LEDBlinky and Launchbox.)

Edited December 15, 2020 by Hifihedgehog

[arzoo]

8 hours ago, Hifihedgehog said:

Digging into this now, I set up my controllers in Big Box but how do I set up the light to button mappings? I have a new RGB setup (PACLED64) and LEDBlinky needs to know which RGB LED trio goes with which controller and button. How do I set up the buttons in BigBox to know which XInput button goes with which LEDs? I have two virtual XInput controllers created via XOutput since I am having to combine two standalone analog joystick (Ultimarc Ultrastik 360) with a button encoder (Xin-Mo Co XM-10) to get two functional controllers across my repertoire of games. Maybe @arzoo can point me in the right direction? (I am full paid licenses to both LEDBlinky and Launchbox.)

Hey, the virtual XInput controllers may make this a bit tricky because LEDBlinky uses the mame .cfg files to determine how the inputs map to the buttons and I'm guessing the virtual controller alters the mapping. I guess let's start by emailing me a debug.log so I can see what's going on.

[Hifihedgehog]

11 hours ago, arzoo said:

Hey, the virtual XInput controllers may make this a bit tricky because LEDBlinky uses the mame .cfg files to determine how the inputs map to the buttons and I'm guessing the virtual controller alters the mapping. I guess let's start by emailing me a debug.log so I can see what's going on.

Will do!

[Hifihedgehog]

On 12/14/2020 at 12:04 PM, arzoo said:

Hey, the virtual XInput controllers may make this a bit tricky because LEDBlinky uses the mame .cfg files to determine how the inputs map to the buttons and I'm guessing the virtual controller alters the mapping. I guess let's start by emailing me a debug.log so I can see what's going on.

Will do! EDIT: So what I am grappling at is even initial setup and this is after having gone through the video tutorials online and reading the manual. I will email you because I am bit at loss at how to do it.

[Hifihedgehog]

Given the uniqueness of my configuration, I am running into some unique roadblocks in getting the buttons and LEDs to tie together, so I am responding to your kind offer for help. As I had touched on, my setup is using two virtualized Xinput controllers that are meshed together my bartop cabinet's control interface. Hardware-wise, there are two Ultimarc Ultrastik 360 joysticks, one Xin-Mo Co XM-10 dual game controller interface and one PacLED64 controller.

 

On the software front, I am using XOutput along with ViGEm and HidGuardian to resolve the four detected physical controllers into two virtual XBox 360 controllers (each controller is composed of one of Ultrastik 360 and one of the two controller on the Xin-Mo) and hide (with HidGuardian) the physical controllers from the rest of the system. I currently have the following completed in LEDBlinky. The first player 1 virtualized Xbox 360 controller was detected as JOYCODE_4 (using Quick Code) but the second is not detected by LEDBlinky. I can provide more button documentation as required.

 

LED Ports | Physical Button | Detected button by LEDBlinky

 

Player 1

1-3 Button X = JOYCODE_4_BUTTON1

4-6 Button A = JOYCODE_4_BUTTON3

7-9 Button B = JOYCODE_4_BUTTON2

10-12 Button Y = JOYCODE_4_BUTTON4

13-15 Button LB= JOYCODE_4_BUTTON5

16-18 Button RB = JOYCODE_4_BUTTON6

19-21 Button LT = JOYCODE_4_BUTTON9

22-24 Button RT= JOYCODE_4_BUTTON10

25-27 Button Select / Coin = JOYCODE_4_BUTTON7

28-30 Button Start = JOYCODE_4_BUTTON8

31-33 Button Guide / Home / Pause = none

 

Player 2 (not detected)

34-36 Button X

37-39 Button A

40-42 Button B

43-45 Button Y

46-48 Button LB

49-51 Button RB

52-54 Button LT

55-57 Button RT

58-60 Button Select / Coin

61-63 Button Start
 

 

Top:

 

Front:

 

Left side:

 

Right side:

Perspective:

 

[Hifihedgehog]

Thanks to @arzoo's tremendous help, I got it working! After adding the mame.xml and mame cfg file and folder, I did one simple swap from JOYCODE_4 to JOYCODE_1 for player 1 and then made the controls for player 2 identical except for JOYCODE_2 and the LEDS came up perfectly! So it would seem that the JOYCODE_4 quick code mappings were a good starting point. They mostly followed the expected button numbering for a player 1 and 2 Xbox controller. For anyone wanting to replicate an Xinput controller experience on their cabinet, this is a great starting point. The debug log also proved helpful since I noticed the mappings expect JOYCODE_1 and JOYCODE_2 and the start/select button numbering matched what I expected for the Xbox controller setup. All in all, all's well that ends well.

 

Amending what I sent along:

 

 

Player 1

1-3 Button X = JOYCODE_1_BUTTON1

4-6 Button A = JOYCODE_1_BUTTON3

7-9 Button B = JOYCODE_1_BUTTON2

10-12 Button Y = JOYCODE_1_BUTTON4

13-15 Button LB= JOYCODE_1_BUTTON5

16-18 Button RB = JOYCODE_1_BUTTON6

19-21 Button LT = JOYCODE_1_BUTTON9

22-24 Button RT= JOYCODE_1_BUTTON10

25-27 Button Select / Coin = JOYCODE_1_SELECT

28-30 Button Start = JOYCODE_1_START

31-33 Button Guide / Home / Pause = JOYCODE_1_BUTTON11

 

Player 2

34-36 Button X = JOYCODE_2_BUTTON1

37-39 Button A = JOYCODE_2_BUTTON3

40-42 Button B = JOYCODE_2_BUTTON2

43-45 Button Y = JOYCODE_2_BUTTON4

46-48 Button LB = JOYCODE_2_BUTTON5

49-51 Button RB = JOYCODE_2_BUTTON6

52-54 Button LT = JOYCODE_2_BUTTON9

55-57 Button RT = JOYCODE_2_BUTTON10

58-60 Button Select / Coin = JOYCODE_2_ SELECT

61-63 Button Start = JOYCODE_2_ START

Edited December 17, 2020 by Hifihedgehog