Add Optional Windows Output Hooking Method

[djGLiTCH]

Firstly, thanks so much for rebuilding this tool in the modern era. It is shaping up amazingly, and I can't wait to have a verified set of configs up and running for modern lightguns with this community! :) I really appreciate your detailed changelogs and video updates too.

Something I wanted to flag as a potential optional feature, if it is possible to even do this, is to have the ability to swap between hooking "network" or "windows" output in MAME. I understand this goes against some of the core principles behind this tool (cross compatibility between OS), but there are instances where it would be quite beneficial to have this at least as an optional feature.

For example, in my case I will eventually run into a dead end, as I need to utilise the "windows" output hook in MAME for RGB LED control on my arcade cabinet, which is also where I am adding my lightguns (just finalising the arcade control config before doing the lightgun config). The RGB LED lighting control is powered by a really great tool called LEDBlinky. This kind of thing is useful for flashing "player start" buttons after inserting coins/credits, etc.

I have not spoken with the developer of LEDBlinky to see if they could add an optional "network" output hook for MAME. If you feel "network" is easier than "windows" to work with, then I can try contacting Arzoo (developer of LEDBlinky) to see if this is something they could perhaps introduce for longevity reasons.

I am also assuming that there is no way to output to both "windows" and "network" simultaneously in MAME - if there is, then that could actually be quite useful. Or perhaps a separate tool that can forward the notifications from "network" to "windows" or vice versa, essentially maintaining parity in game logic status without worrying about which hooking method each tool needs to use?

I'll leave it there for now as I've already rambled enough, but just thought I'd put this out there and see if there was any interest from the community and also check if it was even feasible to begin with. Thanks!

Edit 1:
Found the following thread to be quite insightful. Will need to test this, as it seems like having two "windows" hooks may not be feasible in any case. So perhaps "network" output is required for both instead. Does anyone know if "network" output has this same issue/limitation as "windows" output?
LaunchBox: Blick LEDBlinky for starting when launching a specific title

Edit 2:
LEDBlinky can have static controls lit up like you'd expect while Mamehooker is running, will test for "reactive" button lights shortly.

[6Bolt]

There are some problems with adding the Windows 2 Windows communication. As you mentioned above, it goes against my cross platform goal. I guess you could say you could have both on the Windows side. I think that people use the WINE stuff on Linux to get it working.

The second problem with it, is that Qt has no support for it. This is not surprising, as they promote cross-platform a lot. I have gone outside of Qt, for example the serial port code is based on Windows and not Qt. Why, that is a whole different story, which I point to Release v1.1.1 for more info. A lot of the times that I see the Windows communication done, is with Microsoft tools. Usually in Visual Basic or C# (C Sharp), which are both own by Microsoft. I know MAMEHooker is based in Visual Basic. However, MAME is written in C or C++, if I remember correctly.

If I did do this, it would be in Advance Features, which is months out right now. Right now, I am finalizing the commands for HOTR. Once finalized, I can then work on the game files, and game file data base. I didn't want to add anymore game files, until the commands were finalized. As I would have more work adding stuff to them, once commands are put in, like the display stuff. Then I plan on converting MameOutputSender.exe from Windows to Network. Then work on LED controller support, which the Ultrimarc products will be first added. As they have sent me hardware to test with already. Then do the wiki, here on GitHub. Take a break from HOTR, to get some other projects completed. Then come back and do advance features.

To answer you question on having multiple connections. You can only have one connection to a TCP socket, however, you can have multiple TCP sockets. Right now, HOTR only has one TCP socket. But I can easily add more, but it is hardware intensive when looking for a connection. As it polls for the connection, and why I have it multi-threading. But again, can add another thread with the socket. Also, some people have saw this problem already, and made an UDP Broadcast on port 8001. But I think a UDP Broadcast is one source with multiple listeners. So it would fix this situation, as you want to listen to MAME and another source. In the end, yes, you can have multiple connections, but I don't think anyone supports right now.

Also, what would be easier? Me adding the Windows communication, or LEDBlinky adding Network support. I would say LEDBlinky adding Network support. As Network support is widely supported, and easy to set-up. Where the Windows communication is not well known or supported.

[djGLiTCH]

Thanks for the detailed response and consideration of this request, I really appreciate it.

I've reached out to the developer of LEDBlinky, and they have said they will look at HOTR and potentially work on network output as a future enhancement for their tool. There is no guarantee of them adding this, but to have it on their radar is a good start, as network output does seem like the only path forward for longevity.

Ultimarc products are generally used with LEDBlinky to take advantage of LED outputs too, so hopefully this partnership comes in handy for future enhancements.

On another note, speaking of Qt, just in case you haven't heard of a similar project I thought I'd share it with you. Might have a few synergies that could help.
QMamehook

[eckers569]

Definitely a friendly +1 for this request.

Another converted arcade cab here and looking to hook those 'network' lamp outputs.

For me it's Flycast >>> F355 Challenge >>> Ultimarc I-PAC device. I've salvaged an F355 cab hence my disproportionate affiliation to getting this game as authentic(...ish) as possible .

As dgGLiTCH highlighted above, there's a gap in the various tools available at the moment for this functionality - albeit probably quite a niche user case.

Using HOTR I can at least see the output signals now.

Honestly though, great work. It's unbelievable how HOTR has progressed in such a short space of time - quicker that I've been able to move my light gun setup over from Mamehooker.