-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
suggestion: use pip3 install instead of setuptools/easy install #146
Comments
see https://github.com/adafruit/pi_video_looper/tree/dev I will also try to install it on a fresh dietpi install |
ah, great. I'll also try that. DietPi don't keep around older versions of their images, so you'd need to get the last Buster image from https://web.archive.org/web/20211030184306/https://dietpi.com/downloads/images/ There's a lengthy auto-update routine that you can't stop. Good to have a screen connected for that. Once logged in as root (pw is dietpi): In dietpi-config set the memory split to 128. There's no pi user so you'd need to
then install it as pi (easier than to amend the looper install script I guess) Then to get omxplayer running you need to link libraries: OMXPLAYER on Bullseye fresh install (32-bit) - DietPi. Test omxplayer on its own if you like. Now installing via pip3 should work. Ideally. How much work would it be to get rid of supervisor in a next step and use systemd instead? :) |
thanks. I will check it out when I have time (will be a while) the issue is that there are problems with the "run-level" (is this correct?) where systemd runs the looper not in the right "session" and so it cant output to the screen. |
I tried that just now. Installing the script brings up this error. Also if I do
The supervisor error log says |
also doesn't properly install it on legacy lite. supervisor gives the same ModuleNotFoundError message. |
okay yes it was totaly untested and I also have 0 experience with this kind of things.. so it seems back to the drawing board... |
edit: sorry, forget what I wrote earlier. I got confused with the location of setup.py. It needs to be in the root dir, not in the Adafruit_Video_Looper folder.
Here's it working now, on my own dev tree: |
just thought about this... if we would place the default video directory somewhere else it would not matter if there is a pi user or not... right? should we move the video folder to a "neutral" location? |
Going forward, I think we need to stop using setuptools to install Python modules. While omxplayer still works on an up-to-date Buster system, it seems that modules installed by setuptools aren't found any more.
To give some background, yes, the video_looper still installs fine on the current Raspbian OS Lite Legacy version. I really like DietPi for its ease of use, robustness and easy addition of audio DACs. So I have spent quite a while to get the video_looper working on a fresh DietPi install (using a Buster image as its base), and it turns out that omxplayer is still working fine, even if you have to go through some manual steps.
But even then the video_looper won't start, because supervisor cannot find the modules, which are installed as egg files in
/usr/lib/python3.7/site-packages
. Manually moving them to/usr/lib/python3/dist-packages/
fixes that problem. This issue here helped me solve that problem.For reference, the install process mentions this problem:
The text was updated successfully, but these errors were encountered: