-
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
Video plays with omxplayer directly, but script shows black screen #219
Comments
for now I'm just hard coding it like this, but any tips on fixing it properly would be appreciated
|
Hi have you tried adding |
Thanks for your quick response. If you read my report, you can see that I've added the argument to the extra_args config and your script is adding those arguments correctly. Can you help me figure out how to get omxplayer to generate a log file when it is called from your script? I add the |
sorry for missing that.. |
hm, I read your post now properly - not sure why you would get a black screen as far as I can see pivideolooper runs omxplayer exactly like you so there is no reason why it would not display an image... not that it should matter (because it works with directly calling omx) what OS are you using? is the screen connected to a normal hdmi output? |
Using HDMI0 of a raspberry pi 4 connected to the HDMI input of a very niche e-ink monitor from philips. Here are the only active entries in my config.txt which I pulled from a similar monitor's info via WaveShare.
nothing is written to video_looper-stderr.. supervisord.log
video_looper-stdout constantly repeats the same log entry 5 times per second:
|
Oh, and I'm using your distro .zip file directly for the install, not compiling it myself. |
hm yes the playing movie entry appears because omxplayer is constantly crashing so pi_video_looper is starting the "next" video... |
removing -g doesn't fix the issue. the only tiny outlier I can think of is that when I initially configured the OS, I set the username as an alternative username. I subsequently added the
|
tldr, I reformatted the drive with balena etcher which doesn't give you all the tweaking options that the raspberry pi imager provides and now it's working as expected. I think it was the extra settings portion of the raspberry pi imager which dorked everything up. |
Ok, sorry for the many notifications, but I was wrong, this is still a problem, even with a fresh install, then upgrade to 1.0.18 with install.sh Can you try testing on your end passing a custom resolution via extra_args? |
I can replicate this issue, however in a slightly different scenario. I am using a Raspberry pi 3B with a SCART HAT based on VGA666. I am using the image supplied by video-looper.de and upgrading manually to v1.0.19 I can also replicate the black screen when playing via the python script. Using the same arguments as supplied in the .ini I can run it via the shell using omxplayer directly without issue, however when using the video-looper I get a black screen |
As which user are you running the omxplayer command? Does it work/not work if run it as root/non root? |
When I run the omxplayer command manually, I am only using the "pi" user account via ssh which should be non-root (as I need to elevate via sudo to read the looper logs in /var/log/supervisor |
Okay and if you run it as root manually? Does it still work (I would expect not, because video looper runs omx as root) |
It actually runs fine as root when playing a single file from /home/pi/video If I reboot my device, I get no video playback, although I do see the rpi output during the boot process. As it's connected via WiFi I can't capture any htop instances during this time. If I ssh into the device, and issue a reload command, I see the omxplayer processes spawn and a random video will play successfully. However, when that video finishes playing no new processes are spawned, even though the
However, during my testing I found some inconsistencies with when omxplayer actually ran. For example, if I issued the "stop" command to prepare for more testing, suddenly the omxplayer process would pop up in htop and play 1 random file and then stop. There are 6 video files in the video path but it would choose one, and one only randomly to play and then stop. I have also removed all spacing from my video files so they are named 1.avi, 2.avi etc I have also replicated the "fix" that @githubarooski suggested as below and that works correctly upon reboot. However I don't want to loop one video, I want to loop thru my specified media folder randomly
What else can I do to try and narrow down what is causing this. I get no errors logs in the stdout and stderr files either. |
If I call omxplayer directly with my custom resolution, it works fine. If I use your script to call omxplayer with the same arguments, it just shows a black screen and it seems to keep crashing based on looking at
ps aux
If I kill your script and then run it manually, I see this:
You can see that the script is using my custom args successfully from your config file:
But nothing appears on my screen and I can't find the omxplayer.log file on the filesystem anywhere, so I don't think it's creating the log file, even though I am passing it
-g
in the custom arguments config.When I run the command manually, the video plays just fine
When I run my omxplayer command manually and create a log file, I see this in the log file
The text was updated successfully, but these errors were encountered: