|
MAME and Outputs
#391908 - 09/26/21 04:09 PM
|
|
|
Been a while since I last messed with MAME and the output system.
Previously I used to use MAME Hooker to connect devices to MAME but it seems that with the current version (0.234) this no longer works. I'm looking at the documentation and it's saying that the output options are "auto, none, console, network".
So if I need to output data to the Serial port, would I use the console option? Is there no interprocess communication any more?
Thanks
|
|
|
|
Re: MAME and Outputs
[Re: NaokiS]
#391947 - 09/29/21 05:52 AM
|
|
|
There’s an additional for the output provider on Windows that isn’t listed. I think it’s because we’re trying to encourage people not to write software that depends on it, so it can be removed at some point. It looks like MAME Hooker hasn’t been updated in half a decade or however long it is. Anyway, try setting the output provider to "windows" to use Windows named pipe communication and see if MAME Hooker is happier.
|
|
|
|
Re: MAME and Outputs
[Re: Vas Crabb]
#391967 - 09/29/21 05:22 PM
|
|
|
> There’s an additional for the output provider on Windows that isn’t listed. I think
> it’s because we’re trying to encourage people not to write software that depends on
> it, so it can be removed at some point. It looks like MAME Hooker hasn’t been updated
> in half a decade or however long it is. Anyway, try setting the output provider to
> "windows" to use Windows named pipe communication and see if MAME Hooker is happier.
Thanks Vas, will do.
EDIT: Yes so the windows option works.. somewhat. MAME Hooker detects the output now however it's clear it's not so happy with windows 10 anymore. If it's going to be deprecated then is there going to be a os-independant option that would allow an external program to do the same as name hooker?
Edited by NaokiS (09/29/21 05:28 PM)
|
|
|
|
Re: MAME and Outputs
[Re: NaokiS]
#391974 - 09/29/21 09:21 PM
|
|
|
> Thanks Vas, will do.
>
> EDIT: Yes so the windows option works.. somewhat. MAME Hooker detects the output now
> however it's clear it's not so happy with windows 10 anymore. If it's going to be
> deprecated then is there going to be a os-independant option that would allow an
> external program to do the same as name hooker?
The "network" option is the current preferred output module, and it works on Windows, Linux and macOS. However, MAME Hooker has never been updated to support it.
The current "network" output option isn’t very scalable – it can’t deal with things like fruit machines that have huge numbers of LEDs/lamps, or machines that update blinkenlights very fast. Eventually we’ll have to rework it again to perform better in more extreme use cases.
|
|
|
|
Re: MAME and Outputs
[Re: Vas Crabb]
#391975 - 09/29/21 10:24 PM
|
|
|
> > Thanks Vas, will do.
> >
> > EDIT: Yes so the windows option works.. somewhat. MAME Hooker detects the output
> now
> > however it's clear it's not so happy with windows 10 anymore. If it's going to be
> > deprecated then is there going to be a os-independant option that would allow an
> > external program to do the same as name hooker?
>
> The "network" option is the current preferred output module, and it works on Windows,
> Linux and macOS. However, MAME Hooker has never been updated to support it.
>
> The current "network" output option isn’t very scalable – it can’t deal with things
> like fruit machines that have huge numbers of LEDs/lamps, or machines that update
> blinkenlights very fast. Eventually we’ll have to rework it again to perform better
> in more extreme use cases.
I'm just going to assume its a network packet with the light data on it. Where would i find resources to look at the technical side of it? I did look at the source code but it wasn't easy for me to figure out
|
|
|
|
Re: MAME and Outputs
[Re: NaokiS]
#391978 - 09/30/21 05:19 AM
|
|
|
> > > Thanks Vas, will do.
> > >
> > > EDIT: Yes so the windows option works.. somewhat. MAME Hooker detects the output
> > now
> > > however it's clear it's not so happy with windows 10 anymore. If it's going to be
> > > deprecated then is there going to be a os-independant option that would allow an
> > > external program to do the same as name hooker?
> >
> > The "network" option is the current preferred output module, and it works on
> Windows,
> > Linux and macOS. However, MAME Hooker has never been updated to support it.
> >
> > The current "network" output option isn’t very scalable – it can’t deal with things
> > like fruit machines that have huge numbers of LEDs/lamps, or machines that update
> > blinkenlights very fast. Eventually we’ll have to rework it again to perform better
> > in more extreme use cases.
>
> I'm just going to assume its a network packet with the light data on it. Where would
> i find resources to look at the technical side of it? I did look at the source code
> but it wasn't easy for me to figure out
Right now, “the source is the documentation”, but the protocol is really simple. It’s basically human-readable text. You can connect to localhost:8000 and watch it.
|
|
|
|
Re: MAME and Outputs
[Re: Vas Crabb]
#392020 - 10/02/21 11:39 AM
|
|
|
im just trying to test something, pls what protocol is MAME network sending the output? when i try http:// in chrome, i get webpage with just "error" in window.
ive added the "web" folder, and enabled the "http = 1" in mame.ini
thanks in advance,
D.
|
|
|
|
Re: MAME and Outputs
[Re: Dam0]
#392033 - 10/03/21 12:09 PM
|
|
|
The output protocol is a simple test-based protocol on port 8000 - you can connect to it with a plain socket client. The web server is different - it serves HTTP on port 8080 by default (can be changed with the http_port option).
|
|
|
Index 
Threaded 
MAME and Outputs
Reply
[Re: 