rpi-vidlooper
A video looper for the Raspberry Pi, controlled by GPIO pins. Designed to run an unattended video display, where users can select the active video by switch.
MIT licensed.
Features
- Play videos using OMXplayer, a hardware- assisted video player for smooth playback.
- Switch between 2 or more videos using hardware switches wired to the Raspberry Pi's GPIO pins.
- Optionally, indicate the active video by LED. This can be used with arcade-style switches which have built-in LEDs, or separate ones.
- Callback-based, rather than polling-based. This means that button presses should always be acted upon.
- Thread locking, to avoid issues when buttons are pressed rapidly and the video hasn't finished loading yet.
Usage
I've published a two part tutorial on my blog:
- In part 1, I cover the hardware parts list and build instructions, including a 3D-printed case
- In part 2,
I describe this
rpi-vidloopersoftware tool and how to get it set up and configured
On the hardware side, you'll need a Raspberry PI with several switches, one for each video. Each switch should be connected to a GPIO pin, and to ground. Optionally, you can set up an indicator LED for each video, connected to a GPIO pin.
Install dependencies:
sudo apt-get update
sudo apt-get install python3-pip omxplayer fbi
Install rpi-vidlooper:
pip3 install rpi-vidlooper
This creates the vidlooper command. For usage help, see:
vidlooper --help
Troubleshooting
RuntimeError: No access to /dev/mem. Try running as root!
By default, you'll need to run sudo vidlooper, to gain access to the GPIO
pins and the graphics card (GPU) for omxplayer. Generally, this is not
recommended.
To avoid this, the user you want to run the vidlooper as will need to be
in the gpio group. For example, for the pi user, you'd need to do this:
sudo usermod -a -G gpio pi
See further information on this issue.
No rights to /dev/vchiq
See the OMXplayer troubleshooting to fix
this issue. It's also possible to avoid by running sudo vidlooper, but
as above, this is not recommended.
Further reading
Metadata
Release files for rpi-vidlooper 0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rpi_vidlooper-0.6.tar.gz | 23.1 kB | Without provenance | Details for rpi_vidlooper-0.6.tar.gz |
Release files / rpi_vidlooper-0.6.tar.gz
| Download URL | rpi_vidlooper-0.6.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e778a11126ffeb260125dfaa1b3fe5d2ae32415de60990550f9cb35f6138ce7
|
|
BLAKE2b-256 checksum How to use checksums |
c25a2b83e7110ee3c3e0ae402b27bce80ff0ac63734687b7bbc8bd97daca1827
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for rpi-vidlooper 0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.