Posts made by evroom

evroom

@evroom
…
Sorry for the delay in replying, I don’t get e-mail notices when someone replies to my posts.

No problem.

I discovered the reason why it happens and am busy with a new version.
Hope to release it soon (first need to solve an issue with recalculating the window position).
Those that are interested can have a look at the README of the dev branch.

evroom

To answer myself:

I cleaned the array using:

    const mplayerArgumentsArrayFilter = mplayerArgumentsArray.filter(discardEmptyArgument);
    function discardEmptyArgument(value, index, array) {
      return value != '';
    }

Then spawned using that array:

    // Spawn a new mplayer process
    const env = { ...process.env, DISPLAY: ':0' };
    const mplayerProcess = spawn(`mplayer`, mplayerArgumentsArrayFilter, {env: env});

Now it is working correct.

evroom

I found out following:

When using

    // Spawn a new mplayer process
    const env = { ...process.env, DISPLAY: ':0' };
    const mplayerProcess = spawn(`mplayer`,
       ['-rtsp-stream-over-tcp',
        '-noborder',
        '-monitoraspect', '0',
        '-vf', 'rotate=-1',
        '-geometry', '5:225',
        '-x', '640',
        '-y', '360',
        'rtsp://axisviewer:password@192.168.178.55/axis-media/media.amp?streamprofile=ACC_Low'],
        {env: env});

The stream is correct on the monitor.

When using

    // Spawn a new mplayer process
    const env = { ...process.env, DISPLAY: ':0' };
    const mplayerProcess = spawn(`mplayer`,
       ['',
        '', '',
        '-rtsp-stream-over-tcp',
        '',
        '', '',
        '-noborder',
        '-monitoraspect', '0',
        '-vf', 'rotate=-1',
        '-geometry', '5:225',
        '-x', '640',
        '-y', '360',
        'rtsp://axisviewer:password@192.168.178.55/axis-media/media.amp?streamprofile=ACC_Low'],
        {env: env});

The stream is NOT correct on the monitor (MPlayer window in the center).

So the problem is spawning with empty parameters.
When running it from the command line, this is not an issue, as the shell takes care of the empty places between the arguments.

I tried with undefined and null iso ''but that does not work.

Only idea how to solve this ?
Cleaning the array somehow ?

evroom

There is a main branch now that contains the original code.
And a dev branch that contains the new code.
The new code needs a different entry in the config.js.

evroom

@clakkentt said in MMM-MPlayer:

@hrmax23
I don’t know why but the MPlayer header show up in the latest MMM-MPlayer update, at least in my setup, it does not show up in the previous version. I upgraded and then downgraded.

Hi, could you please sent me the output of

$ ps -eaf | grep mplayer | grep -v grep

for the version that is working?

I am currently busy with a new version, but I messed up a bit by not using a development branch.
Hope to have sorted that out soon.
The new version will have a bit different configuration setting than the old one.

Also refer to
https://forum.magicmirror.builders/topic/19539/mmm-mplayer-display-issue
for the issue I am facing (related to what you are seeing with the new version).

evroom

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 ?

evroom

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.

evroom

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.

evroom

@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?

evroom

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.