MMM-GooglePhotos

krishnatnl

@Sean
Maybe i did not explain properly. I need a layout for the portrait oriented pictures to fit in the screen without disturbing the aspect Ratio.

MODE:COVER

Works perfectly for the landscape oriented pictures since it is fitting the picture perfectly in the screen. There is no stretch or crop.

Portrait oriented pictures are cropped to landscape orientation (technically).

MODE:CONTAIN

Works fine for the portrait oriented pictures i.e: The full image is visible in the screen, no crop, no stretch

Landscape pictures are also displayed without crop, but there are borders.

Need something like this:
If the pic is a Landscape oriented one, Mode should be COVER, else should be CONTAIN.
In Other words, need an AUTO-SCALING option.

From a programming perspective, is this feasible? If not, I will try the COVER mode but not liking black borders for all the images.

A Former User

@krishnatnl
In my MMM-DropboxWallpaper, I applied already that feature(automatically changing mode by ratio). I have been doubting whether it has really usefulness in real usage. Anyway I’ll consider this feature in this module too.

A Former User

@krishnatnl
I’ve updated. mode:hybrid is available for changing mode:cover or mode:contain automatically by aspect ratio.

krishnatnl

This working fine and solved my issue @Sean . Happy Holidays :)

krouton

Hi Sean,

I keep getting the “[GPHOTO] Scan finished : 0/There is no scanned photo currently.” error however there are 3000 photos in the folder. Sometimes it will successfully scan and display the photos fine but more and more recently it fails.

{
		module: "MMM-GooglePhotos",
		position: "fullscreen_below",
		disabled: false,
	config: {
		albumId: "xxxxx", // your album id from result of `auth_and_test.js`
		refreshInterval: 1000*60*5,  
		scanInterval: 1000*60*10, // too many scans might cause API quota limit also.
			//note(2018-07-29). It is some weird. API documents said temporal image url would live for 1 hour, but it might be broken shorter. So, per 10 min scanning could prevent dead url.

		sort: "random", //'time', 'reverse', 'random'
		showWidth: "1380px", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
		showHeight: "1060px",
		originalWidthPx: 1380, // original size of loaded image. (related with image quality)
		originalHeightPx: 1060, // Bigger size gives you better quality, but can give you network burden.
		mode: "contain", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)
  }
},

Connecting socket for: MMM-GooglePhotos
MMM-GooglePhotos started
Connecting socket for: MMM-MyCalendar
Starting node helper for: MMM-MyCalendar
Sockets connected & modules started …
Ready to go! Please point your browser to: http://0.0.0.0:8080
MMM-ModuleScheduler is removing all scheduled jobs
MMM-ModuleScheduler received CREATE_GLOBAL_SCHEDULE
MMM-ModuleScheduler is creating a global schedule for all modules using “30 6 * * *” and “00 18 * * *” with dim level 40
MMM-GooglePhotos initialized after loading.
[RCREPO] Repository scanning…
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.
[RCREPO] Repository scanning…
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.

Inspector shows it loads the module but not an actual photo.

Any help would be greatly appreciated.

A Former User

@krouton
Move to some smaller folder than try again. 3000 would be so many photos, and ther could be more in your subdirectories.

A Former User

@krouton
By the way, sorry for out of topic, but…
RCREPO seems too many times working. Scanning should be executed at start of MM once. Why did the log say so many times?
Would you try again after removing MMM-Remote-Control-Repository from config.js??

yupwho

@Sean , thanks a ton for this great module. My wife would have never been ok with a Smart display in our family room without having family pictures on it.
I have MMM-Google photos on full screen mode (monitor is in portrait mode). It works perfectly as expected - although the pictures come up as pixelated or not as sharp in lower resolution. All photos in my configured album are uploaded in full resolution. Is there any way to display it in high(est/er) resolution?

My configuration is as below:-

		{
		  module: "MMM-GooglePhotos",
		  position: "fullscreen_below",
		  config: {
		    albumId: "XXXXX", // your album id from result of `auth_and_test.js`
		    refreshInterval: 1000*60,  
		    scanInterval: 1000*60*10, // too many scans might cause API quota limit also.
		    //note(2018-07-29). It is some weird. API documents said temporal image url would live for 1 hour, but it might be broken shorter. So, per 10 min scanning could prevent dead url.
		
		    sort: "random", //'time', 'reverse', 'random'
		    showWidth: "100%", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
		    showHeight: "100%",
		    originalWidthPx: 1920, // original size of loaded image. (related with image quality)
		    originalHeightPx: 1080, // Bigger size gives you better quality, but can give you network burden.
		    mode: "hybrid", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)
		    //ADDED. "hybrid" : if you set as "hybrid" it will change "cover" and "contain" automatically by aspect ratio.
		  }
		},

bhepler

@yupwho - Hmm. If you uploaded at full resolution, they are probably higher than 1920x1080. Specifying those parameters may be causing some weird resizing artifacts.

As an experiment, trying taking out the orginalWidthPix and originalHeightPx parameters and see what you get.

yupwho

@bhepler Thanks! Removing it seemed to worsen the quality. I think I am going to experiment with different values here - https://en.wikipedia.org/wiki/Display_resolution#Common_display_resolutions.
I have tried the 2560*1440 and it looks little bit better.

Still looking if there is a more definite solution.

Thanks!