Hi,

I have this issue with MMM-MPlayer, that also has been reported by other users of the module.

When using the module, the MPlayer window is seen in the middle of the screen and has a MPlayer title.

This is what is running when using the module:

admin@MagicPi3b:~/MagicMirror/modules/MMM-MPlayer $ ps -eaf | grep mplayer | grep -v grep
admin 38919 38729 18 12:17 ? 00:00:01 mplayer -monitoraspect 0  -noborder -vf rotate=-1 -geometry 10:225 -xy 640 -rtsp-stream-over-tcp -vo xv,gl,gl_nosw,vdpau, -nosound rtsp://axisviewer:password@192.168.178.55/axis-media/media.amp?streamprofile=ACC_Low

The value of DISPLAY is: :0

When I run the same command like this, it is working as expected:

admin@MagicPi3b:~/MagicMirror/modules/MMM-MPlayer $ DISPLAY=:0 mplayer -monitoraspect 0  -noborder -vf rotate=-1 -geometry 10:225 -xy 640 -rtsp-stream-over-tcp -vo xv,gl,gl_nosw,vdpau, -nosound rtsp://axisviewer:password@192.168.178.55/axis-media/media.amp?streamprofile=ACC_Low

The MMM-MPlayer module uses this to start mplayer:

    const env = { ...process.env, DISPLAY: ':0' };
    const mplayerProcess = spawn(`mplayer`,
       [`${mplayerOption}`, `${mplayerOptionValue}`,
        :
        :
        `${stream}`],
        {env: env});

I cannot get my finger behind this and I have no idea why this happens like this.
Any ideas ?

When I tested the module, I used a Pi 3b connected to a 4K monitor and it was working okay.
After reading about the MPlayer window, that appears in the center, I decided to test again.
And to my surprise I have the same issue.

It seems that MPlayer is ignoring the window position defined by the module.

The GUI screen resolution is set to 1920x1080 @60Hz.
Both xrandr and wlr-randr reflect this.

On my Pi 4b, connected to a 1600x900 monitor, I do not have this issue.

I did do an update & upgrade of Debian before looking at the issue, so it can be that something ‘broke’ the module.
But then again I updated both Pis and only one has this issue.

I will try to connect the 1600x900 monitor to the Pi 3b, so see if it is a monitor thing.

All in all very odd.

Hi, I notice some requests and other activities,here and on GitHub.
Due to unforeseen medical issues, I do not have really time, nor the means to respond to everything
Already happy I have some sort of Internet connection here.
But with Sam it is in good hands, just make use of his fork.
Greetings, E.J.

@sdetweil
Short question:

There are 2 versions of MMM-pages:

https://github.com/edward-shen/MMM-pages
https://github.com/sdetweil/MMM-pages

They seem in-sync, but which one would be the preferred one to take?

As a workaround, I will make it a requirement to put the MMM-Player on the first page (page index 0).
When I receive 0, then I will start streaming, otherwise I will stop streaming.
That seems to work.

@sdetweil
Yeah, this module is kind of in my foster care.
I did not come up with the code; only made some tweaks and made it available.
There is not suspend or resume to been seen in the code.

But I will study the stuff you mentioned and will try to implement that.

Thx.

Hi,

I am currently adopting MMM-MPlayer to interact with MMM-pages.
Reason is that suspending the module does not suspend (stop) the stream, as it is an overlay.
As long as MMM-MPlayer is running, it will always display the stream.

From the config I can deduct the page index (3 in this case):

      modules: [
        ["compliments"], // page 1
        ["MMM-YrThen"], // page 2
        ["calendar"], // page 3
        ["MMM-MPlayer"], // page 4
      ],

And I see that reflected in the log:

0|MagicMirror  | [2025-01-18 16:13:55.383] [LOG]   [MMM-MPlayer.js:65:15] Received MMM-pages NEW_PAGE 3
0|MagicMirror  | [2025-01-18 16:13:55.804] [LOG]   [module.js:189:7] compliments is suspended.
0|MagicMirror  | [2025-01-18 16:13:55.835] [LOG]   [module.js:189:7] calendar is suspended.
0|MagicMirror  | [2025-01-18 16:13:55.917] [LOG]   [module.js:189:7] MMM-YrThen is suspended.
0|MagicMirror  | [2025-01-18 16:13:56.395] [LOG]   [module.js:196:7] clock is resumed.
0|MagicMirror  | [2025-01-18 16:13:56.439] [LOG]   [module.js:196:7] MMM-MPlayer is resumed.

But I would need to see my module name in the payload (MMM-MPlayer in this case), to act on the correct page index.

Come to think of it, I also would need the keyword suspended or resumedin the payload, in order to know what to do.

Any thoughts on this ?

Best regards,

E.J.

@plainbroke
Yes, that makes sense.
Keyword: overlay.
I will reply in the MPlayer issue you opened for this, to not hijack this topic.

@blinkybob

I tested this and indeed it does not seem to work (anymore).
For directionI used the station Id for the station adjacent to my station.
I will raise an issue for this.

@KristjanESPERANTO said in MMM-PublicTransportHafas: Service Temporarily Unavailable:

I just released version 3.0.1 to fix this 😀

At this moment I see an entry in the past with +0.5.
Also saw +0.6.
When turning on debug, I only see delay values of 0, 60 and null, so I wonder where the current 0.5 comes from.
The values for when and plannedWhen all have a difference of 0 or 1 minute.

It seems that it only affects the first entry in the list, which in my case is the first unreachable in the past.
And it does not really bother me, but it still is odd.