Remote Tunes
Hand a Pixel Brite queue to a phone, computer, or Raspberry Pi connected to your speakers. Keep your phone as the remote; the receiver owns playback.
Your phone becomes the remote
Choose a receiver from the Pixel Brite player screen. The phone sends the full queue and current position, then that same screen controls the receiver’s queue, pause state, position, and volume.
The queue and position transfer before local playback stops. Only the receiver’s acceptance completes the handoff. If it cannot take over, the phone keeps playing; selecting a destination alone does not interrupt the song.
Receiver hardware
The receiver can be another phone running Pixel Brite, the full app on a computer, or a lightweight background player with no interface. Connect that phone, an old computer, a Raspberry Pi, or another device with audio output to speakers and leave it running.
The background player starts automatically, remembers its volume, and waits for music without a screen. An old device can stay by the amplifier while the phone supplies the interface.
Receiver-owned playback
After the handoff, the receiver runs the full queue and gets media directly from its source. The phone no longer carries the audio, and no controlling app needs to remain open.
The receiver is the source of truth for queue, position, pause state, and volume. Connecting a second phone reads that state instead of applying its own volume or queue. Several people can control the same receiver and see each other’s changes.
Local network control
Bonjour finds receivers on the local network. Each Pixel Brite app connects directly over TCP and versioned NDJSON to send commands and receive live playback state, with no cloud service in the path. Pixel Prism handles the media.
Control is shared within the LAN: devices can discover the receiver and join without an account. Reconnecting a controller retrieves the receiver’s current state, while playback continues independently.