ScreenSplice setup: live video with a USB HDMI capture card
Use this setup when you want an external HDMI source in the main picture with side advertisements and optional full-screen ad breaks.
Hardware checklist
Item
What to choose
Pi player
Raspberry Pi 4 or 5 with at least 2 GB RAM and suitable cooling. A 1 GB Pi 4 and Pi 3 are not supported for capture. Use the official 15 W supply for Pi 4 or 27 W supply for Pi 5.
Capture card
Standard-driver USB 3 HDMI input/UVC capture device. The project’s observed Pi 4 tests include Guermok USB ID 345f:2130 and XIIXMASK USB ID 345f:2131. Branding or a listing’s “4K” text alone does not guarantee the same hardware.
Tested product references
Guermok ASIN B08Z3XDYQ7: https://www.amazon.com/dp/B08Z3XDYQ7 ; XIIXMASK ASIN B0CP659ZSV: https://www.amazon.com/dp/B0CP659ZSV . Verify the current listing, connector type and exact unit before purchasing. No current price or universal compatibility is claimed.
Video source
Your camera, media player, computer, Fire TV or other source with a supported, unprotected HDMI output. Supply its own power.
Display and cables
HDMI TV/monitor; micro-HDMI-to-HDMI cable from Pi 4/5 to the display; HDMI connection/extender from the source to the capture card’s HDMI IN. A Fire TV Stick’s male HDMI plug may connect directly or through a suitable extender.
Storage and setup
32 GB microSD card recommended (16 GB minimum), card reader, computer with 8 GB+ free space, venue network and a phone for setup.
Start with a simple video source
Begin at 1080p30; try 720p if playback is unstable. Test the exact source, audio and display before using it at your venue.
The capture card transfers video/audio from the source into the Pi. It does not by itself send remote-control button presses back to the source.
Before you begin
Your first two screens are free. Sign in and create your workspace, then open Downloads for the current ScreenSplice OS. Hardware is separate.
Download the current ScreenSplice OS image and its SHA-256 checksum. Compare the downloaded checksum with the published checksum before flashing.
Keep the download compressed. Its filename should end .img.xz. If the browser saved a name ending img.xz without the dot before img, rename the completed download to ScreenSplice.img.xz. In Windows, enable View → Show → File name extensions first.
No extraction is needed. If you already extracted this ScreenSplice download and the resulting file has no .img extension, rename that extracted file to ScreenSplice.img. Do not rename the compressed archive to .img.
Open Raspberry Pi Imager. Choose your actual Pi model, then Use custom and select the downloaded .img.xz file (or your already extracted .img).
Choose the correct microSD card. Writing the image erases that card.
Skip Imager OS customization: do not add a separate username, Wi-Fi or SSH configuration. ScreenSplice handles setup from your phone.
Write the card and wait for verification to finish. Safely eject it. If Windows offers to format a Linux partition afterward, choose Cancel.
Connect the venue network and pair the screen
Insert the written card, connect the display to the Pi’s HDMI output, select that HDMI input on the display, then power the Pi with its own suitable supply.
Wait for the setup screen. On your phone, join the setup Wi-Fi name shown on that screen. Use the displayed password; do not use your ScreenSplice account password as the Wi-Fi password.
If the setup page does not open, browse to http://10.42.0.1 while still connected to that setup Wi-Fi. If your phone says the network has no internet, stay connected for setup.
Scan for venue Wi-Fi, select it and enter the venue password with the correct uppercase/lowercase letters. Avoid guest networks that require a browser sign-in/captive portal.
If setup asks for the website address, use https://screensplice.com. Select Ads only for a slideshow or menu, or USB/UVC capture for live video.
Connect. Your phone leaving the setup Wi-Fi during handoff is expected. Let the Pi restart and join the venue network.
Read the one-time SS-… pairing code on the display. Older images may show an FS-… code; both formats are accepted.
Sign in to ScreenSplice from your phone/computer, open Devices → Add device, enter that full code, name the screen and save.
The screen normally checks in about once a minute. Leave it online until pairing, content download and any required signed player update are complete.
Wire the video path — before choosing live mode
Power off the Pi while making the initial connections.
Connect the external source’s HDMI output to the capture card’s HDMI IN. A Fire TV Stick connects here, not to one of the Pi’s HDMI sockets.
Plug the capture card’s USB connection into a blue USB 3 port on the Pi. Begin without an unpowered hub.
Connect the Pi’s HDMI output to the TV/monitor and select that input on the TV.
Power the source with its own appropriate supply, then power the Pi with the correct Pi supply.
Video path:
Source HDMI OUT → capture card HDMI IN → capture card USB → Pi USB 3 → Pi HDMI OUT → display
Complete phone setup and choose the source
Follow the shared card-writing, Wi-Fi and pairing steps above.
In phone setup select the USB/UVC capture source rather than Ads only. Keep the source powered and connected.
In the device’s Display settings choose Live feed with side advertisement.
With one card, begin with Capture device 1. With multiple devices, verify the selected physical input rather than assuming USB numbering is permanent.
Save settings and wait for the next check-in. You should see the external picture.
Add side artwork in Ad library. The side-rail artwork target is 480 × 864; use full-screen artwork near 1920 × 1080 for full-screen breaks.
Build and deploy the side-ad playlist. Check that the live source remains visible while side advertisements rotate.
If wanted, build a separate full-screen playlist, select it under full-screen ad breaks, and choose interval/duration. This independent campaign feature requires the updated player.
Test a full break and return to live video. Check any desired source audio at venue volume; do not assume audio behavior from the video test alone.
Fire TV and protected sources
A source home screen can be visible while a protected movie/show appears black. HDCP/DRM can prevent capture even when all cabling is correct. ScreenSplice does not bypass protection or supply viewing/broadcast rights. Test the exact app and authorized content you intend to use before buying or rolling out capture hardware.
To control a compatible Fire TV device from the dashboard, use the separate Fire TV control guide. Video capture and network control are independent connections.
Two displays / two sources
Independent dual output is experimental. Two separate live feeds require two compatible capture cards and different capture indexes. Begin performance tests at 720p per capture; the second output starts muted. The two outputs count as two screens. Do not promise a dual-capture deployment until your exact Pi, power, cooling, cards, display modes and audio have been tested.
Quick troubleshooting
No signal at all: check source power, capture-card HDMI IN, the blue USB 3 connection and the Pi-to-display HDMI cable.
Source menus appear but a show is black: test an unprotected camera/computer source; the app may require a protected HDMI path that a capture card cannot provide.
Intermittent video: start with a lower source resolution/frame rate, correct power/cooling and a direct USB connection.
Wrong feed: confirm the selected capture device and use separate indexes for independent feeds.
Source sound or video continues during an ad break: verify the matching player update and test again; report it before wider rollout.