|
5 years ago | |
---|---|---|
cfg | 5 years ago | |
src | 5 years ago | |
.gitignore | 5 years ago | |
Doxyfile | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 5 years ago | |
dbuscontrol.sh | 5 years ago | |
fltk_exists.py | 5 years ago | |
setup.sh | 5 years ago |
README.md
PiPlayer
PiPlayer is a very simple GUI around the OMXPlayer on the Raspberry Pi.
OMXPlayer is a quite basic player using the hardware decoding features of the Raspberry Pi for decoding HD videos. This GUI is intended to be used with other tools like smtube, which do not give you the opportunity to open a terminal for controlling OMXPlayer. You can now use PiPlayer for controlling OMXPlayer.
The file dbuscontrol.sh
is not written by me! I take no authorship in that bash-skript. I copied it from popcornmix's repository
Setup
You will need the following packages installed on your system:
- FLTK (fltk1.3)
PiPlayer uses (pyFLTK)[http://pyfltk.sourceforge.net/] as a binding to FLTK for Python. At least under Arch Linux ARM there is no package for pyFLTK. Therefore you will need to install pyFLTK. This can be done using the setup.sh
file in this directory. Try (without root-priviliges):
bash setup.sh prepare
Then you can try PiPlayer without "installing", or install it with the command:
bash setup.sh install
This will need root-privileges. By default it will copy the files to /opt/piplayer/
. Try setting PiPlayer as default player for HD-files in your file manager.
Usage
You should be able to call it via a CPython3-interpreter (as far as I know the pypy-interpreter does not support pyFLTK):
python piplayer.py filename
You can also give parameters which will be directly handed to omxplayer on startup.
Technical mumbo-jumbo
PiPlayer quite litterely calls omxplayer and communicated to it via the DBus-interface. There are some functions not present in the GUI, which could be reached via the dbuscontrol.sh
-bash skript.
The window is placed on the screen and omxplayer is called with the --win
parameter to fit exactly inside the window. On resize of the window a DBus-interface is called to adjust for the new size of the window. That works well for maximizing, resizing or moving the window, but not for restoring it from maximized setting to normal. For that reason the OMXPlayer-output cannot be placed in the background, whereas the player-window can be in the background.