Repository navigation
Anymote
Anymote, any remote, a remote from anywhere: the player's meters in any browser, a phone, a tablet, a laptop, a spare screen with a browser on it. Nothing is installed on the device. The page draws the meters itself with the display's own engine, compiled for the browser, from the theme the player shows and the same frames the player's screen and the remote displays receive, so what it shows is what the player shows, and a tap on the theme's controls acts on the player.
The page is served by the player's manager:
http://<player>.local:5582/anymote
5582 is the manager's port, the settings page sets another. On a network where .local names do not resolve, the player's address serves instead; the Manager's Status tab shows both forms once "Reveal addresses" is pressed. The Manager's Face tab is the same face inside the manager, with an "Open Anymote" button.
The theme on show and the meter the player's own display shows, following both as they change; the levels as they play; the title, artist and album, the time, the format's icon, the volume and the play state, the album art, the artist fanart and the pictures a theme takes from the track's folder, as the theme draws them. The pictures come through the player's manager as the track changes; the theme's own files are kept in the browser, the track's pictures are fetched each time. The theme's pictures and the fonts come from the player the first time and are kept in the browser by checksum, so a second visit fetches only what changed; the built-in fonts are the bulk of it, about 60 MB, brought once.
A tap or a drag on a theme's controls acts on the player as on its own screen: play, pause, stop, next, previous, mute, shuffle, repeat, the volume bar, the progress bar, and the buttons a theme draws of its own. Whether the controls act follows the player's own setting, "Interactive controls" on the settings page and the Manager's System tab; the Meters-Reference has the theme's keys. A tap elsewhere does nothing.
Anymote is Glass's picture, not a copy of the player's screen: what a kiosk shows on that screen, Volumio's interface or the Now Playing plugin's screen, does not appear here. From 0.8.87 with glass-evo 0.1.52, when nothing plays and the look names a picture of your own, Anymote shows it behind the clock as the player's screen does, fetched from the player once and kept while the page is open.
With glass-evo on the player (0.1.14 or later, Glass 0.8.10 or later) Anymote and the Face tab can show more than the theme: glass-evo's face over it, as the player's own screen has it once the screen is handed to glass-evo. While the player stands still the clock and the date stand, with the bar of controls under them; while it plays a touch brings the bar, which leaves again by itself, and More opens its sheet with repeat, random and mute. The look and the sizes are the ones chosen for the player, a touch on a button acts on the player, and the clock tells the time of the device the browser runs on. It is drawn by glass-evo's own code, compiled for the browser, so the page and the screen cannot differ.
Whether the pages carry the face is a setting on the Manager's Screen tab, The Face tab and Anymote show:
| Choice | While glass-evo owns the player's screen | While the kiosk owns it |
|---|---|---|
| the Glass interface while glass-evo holds the player's screen (as it comes) | the theme with the face over it | the theme alone |
| the Glass interface, always | the theme with the face over it | the theme with the face over it |
| the theme alone | the theme alone | the theme alone |
On a player whose screen stays with the kiosk, the first and the third choice show the same thing, the theme alone; "the Glass interface, always" is the one that makes a tablet on Anymote a Glass interface by itself. Without glass-evo, or with one older than 0.1.14, the setting is not shown and Anymote shows the theme alone. The Screen page has the setting in full.
A browser only takes the whole screen on a touch or a click: no page can open full screen by itself. Three ways, by how well they fit:
-
On a phone or a tablet, keep it as an app. "Add to Home screen" in the browser's menu (Android Chrome offers "Install"). The icon then opens Anymote full screen, without the browser's bars, every time.
-
On a computer, a kiosk launch. Chrome, Chromium and Edge start full screen with
--kiosk, Firefox with-kiosk; a shortcut with the line is a one-click display:chromium --kiosk http://<player>.local:5582/anymote msedge --kiosk http://<player>.local:5582/anymote --edge-kiosk-type=fullscreen firefox -kiosk http://<player>.local:5582/anymote -
On the page, a tap. The first tap anywhere on the meters takes the screen (from 0.7.44), as does the "Full screen" button at the top right; Escape gives it back, and the page then leaves it to you until it is opened again.
The page fills the window whatever its size, the theme's shape kept, black around it.
The page speaks to the player over plain HTTP, and browsers allow a page to keep the screen awake only over HTTPS; the phone's own screen timeout therefore still applies. Set it longer in the phone's display settings while Anymote is the display. Anymote costs the phone what the theme costs: the frame rate on the settings page and the theme's size decide; a large turntable theme at 60 frames a second is the most a phone will be asked, a bar meter at 30 the least.
A remote display (Remotes) is Glass itself running on the machine: full screen from its own start, its own settings page, a theme of its own if wanted, a service that starts with the machine, and the Windows and Android builds. Anymote is the face in a browser: nothing to install, any device, the player's theme only, and a tap on the page or a kiosk launch for the full screen. A machine that will live as a display wants the remote; anything that happens to be at hand wants Anymote. The Glass interface is on both: in Anymote by the setting above, on a remote as the bundle from glass-evo's releases, which the Remotes page describes.
The Contracts page has the module's contract under "The browser face": what the page fetches, what the module reads, the event stream that carries the frames and the player's state, and what a pointer event asks for. The Manager-API page has the routes: the stream, the module and the page's script, the command, the picture and the fanart set, the page and its manifest. A picture the page cannot fetch is asked for again after ten seconds; a fanart set it cannot fetch shows nothing in the slot.