google home assistant screen saver photo alumb

fps Whether to show a frames-per-second display at the bottom of the screen. titles Whether to print the file name of the current image in the upper left corner. The idea here is that if your machine can't maintain a decent frame rate, then it must not have fast 3D hardware, so we might as well behave in a simpler cutoff number If the frame rate drops below this number of frames per second, then certain features will be turned off automatically (first zooming, then, if the low delay number Per-frame delay, in microseconds. 2 means twice as fast 0.5 means half as fast. Images will still smoothly fade from one to another, however, assuming -fade is non-zero. If set to 100%, then the images willĪlways fill the screen, and no panning or zooming will occur. Default: 75, meaning that 75% or more of each image will always be visible. zoom number Amount to zoom and pan as a percentage.

Note that fades are included in the pan, so -pan should always be longer than -fade (it is auto-corrected if not.) If set to 0, then no cross-fading will be done (all transitions will be jump-cuts.) fade seconds How long each fade (in and out) should last. pan seconds How long each pan should last. duration seconds How long each image will be displayed before loading a new one.

Legal values are the name of a visual class, or the id number (decimal or hex) of a specific visual. Options -visual visual Specify which visual to use. To specify the directory that images are loaded from, run xscreensaver-demo(1) and click on the 'Advanced' tab. This program requires a good video card capable of supporting large textures. Loads a random sequence of images and smoothly scans and zooms around in each, fading from pan

Google home assistant screen saver photo alumb