git pull says everything up to date and didn’t do anything. No image size info available.
I tried reverting TO the fake driver as I was not using it (real one instead) and that hasn’t made any difference. I also tried editing the startup file to remove the rotate setting, also didn’t help.
“do a get pull”… To date, I’ve done little with repositories - can you elaborate on how I do this to make sure I do it correctly?
Also… Some updates.
CTRL - does not affect image size in any way. It DOES affect the sizing of the text for the other modules, though.
I believe that I have determined that the desktop / browser “believes” that it is in portrait mode. The images seem to be getting constrained properly, but because the browser is configured to be as tall as it is, I’m losing all kinds of content off the bottom of the screen. If I do a CTRL-SHIFT-I and then turn on the device toolbar, I see a full vertical representation of the browser and I can see the entire image. As I increase the zoom, it becomes apparent where the image is getting clipped vertically.
Thoughts?
I’ll definitely give it a try. But… If it were a browser zoom issue, wouldn’t that prevent the other module from displaying them properly as well?
I tried with the config you provided:
{
module: "MMM-ImagesPhotos",
position: "fullscreen",
config: {
opacity: 0.9,
animationSpeed: 0,
updateInterval: 30000, // how often to change pic
backgroundColor: "#808080", // color around pic (if u want something other than black)
},
},
This results in the photos running off the edges of the screen and not being able to view the entire image. I have also tried using the config on the project page, and adding the maxHeight and maxWidth variables as well.
Just for the heck of it, I even tried using the “fullscreen_below” positioning area that the other module uses.
The photos always run off the edge of the screen. And by a lot.
As of right now, these are all photos that were shot on a 24MP DSLR and they are being displayed on a 1080 TV. There is definitely more pixels in the photo and the device needs to ‘resize’ them down to fit the screen (which it does not appear to be doing).
While you don’t ‘contain’ the images, I do recall that was an option being used in the other module that would ensure they did not overrun the screen edges. Is there a config option for yours that would enable it?
Quoting the values corrected the issues I was having with them. I think I’m good with this now and appreciate the help.
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 100 lines:
PM2 | 2019-12-12T14:19:37: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:19:37: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:41:26: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=process killed
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:43:33: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:43:33: PM2 log: pid=4543 msg=process killed
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:46:33: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:46:33: PM2 log: pid=4667 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:46:33: PM2 log: pid=4667 msg=process killed
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:47:42: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:47:43: PM2 log: pid=4822 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:47:43: PM2 log: pid=4822 msg=process killed
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] online
PM2 | 2019-12-12T15:00:40: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=process killed
/home/pi/.pm2/logs/mm-error.log last 100 lines:
0|mm | [5004:1212/145553.006275:FATAL:memory.cc(22)] Out of memory. size=96641024
/home/pi/.pm2/logs/mm-out.log last 100 lines:
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm | Shutting down server...
0|mm | Stopping module helper: MMM-ImagesPhotos
0|mm | Stopping module helper: updatenotification
0|mm | Stopping module helper: calendar
I will try quoting them.
It hadn’t occurred to me that “words” need to be quoted since true and false do not.
Why do some of the more general config options throw errors stating that they are undefined? For example, I can’t set tableClass or timeFormat as the values I chose (xmall and absolute, respectively) throw errors and prohibit MM from starting. I have these defined in the general config section.
Thanks for the reply. While adjusting as you’ve mentioned does give me the expected result, I have to say that it seems counter-intuitive.
Placing those settings OUTSIDE of the calendar definition seems to make them overrides for the defaults and would make them be the settings used for all calendars. Shouldn’t setting them per-calendar need to be done within the definition of the calendar itself?
At a minimum, the apt-get update / upgrade seems to have at least helped. After installing the updates and restarting, I’ve been running this module with clock, calendar, current weather, and weather forecast all enabled and it hasn’t crashed in about an hour.
I stopped everything and reverted to the BackgroundSlideshow module to see if it would also run clean, but it died pretty quickly. I’ve flushed the logs again (although I did capture their contents from the other module’s crash) and once again changed over to ImagesPhotos to see what happens after another run.
While I’m waiting to see if it will crash, I have some questions about the rendering configuration.
I’ve tried both the “fullscreen” and “middle_center” settings and the photos are not constrained to the screen (in terms of the actual image, not where it’s shown). I can change the details so that I use less than full height and/or width, and there is a black border. However, the image itself is getting cropped - badly.
How can I get this to display the entire image on the screen like I can with the other module?