v0.62.0: andTunes 0.4.0 — speakers (AirPlay, Chromecast), a list for a menu, icon pills, full-screen art
Now Playing: tap the art for it full screen, the title or artist line for its album; shuffle, repeat and a new speakers button are icon pills. The main menu is a list (Now Playing on top, Settings at the bottom, six rows to a screen). The speakers button lists this Rabbit plus every AirPlay speaker and Chromecast on the Wi-Fi: AirPlayRemote is the desktop's RAOP sender in Java (verified from the R1 against shairport-sync), CastRemote speaks the Cast protocol directly to the Default Media Receiver and serves the file over HTTP (not yet tried on a real Chromecast).
This commit is contained in:
@@ -671,6 +671,15 @@ persistence) → GUI (Qt widgets that read the manager and connect to its signal
|
||||
`lintunes/android/andTunes.apk` with its version in `andTunes.json`;
|
||||
**re-run `--ship` whenever the app changes**, since the committed APK is
|
||||
what the self-updater carries and what `install.py` installs.
|
||||
**App v0.4.0** (Round 92): the menu is a list, Now Playing has icon
|
||||
pills and a full-screen art / album link, and a speakers pill plays the
|
||||
queue on AirPlay (`AirPlayRemote`, raop.py in Java) or Chromecast
|
||||
(`CastRemote`, the Cast protocol by hand) — see andtunes/README.md.
|
||||
Test speakers only against shairport-sync in Docker published on this
|
||||
machine's LAN address (its avahi stays on the Docker bridge, so it is
|
||||
never advertised), listed in the device's `Music/andTunes/speakers.txt`
|
||||
— **never** connect the Rabbit to a speaker that isn't trav's, and read
|
||||
a screencap before every `input tap`: the picker lists the neighbours'.
|
||||
`andtunes/andtunes.keystore` is committed on purpose (both machines must
|
||||
sign identically or `adb install -r` refuses the update). `install.py` is
|
||||
Connections → Install andTunes on Rabbit…: adb as a runtime tool, then the
|
||||
|
||||
Reference in New Issue
Block a user