Closed ambanmba closed 5 years ago
GPIO screens, being rather small are not really the targeted use case. Expectation is an HDMI display.
Try to prepend your feeds with "--display=4 "
If that throws errors during testing, replace /usr/bin/displaycameras with this version, https://raw.githubusercontent.com/Anonymousdog/displaycameras/layers/displaycameras
Thanks for that... I replaced /usr/bin/displaycameras with the version you suggested (otherwise it was throwing errors).
--display=4 stopped showing the display on the HDMI, but was not showing on the GPIO screen. I tried --display=n where n=1-5 and in all cases except n=4 the image was showing on the HDMI. With n=4 the display wasn't showing anywhere.
No idea. Unless there's some command line parameter we can pass to omxplayer to get it to display video on that screen, you're out of luck.
I'll do a bit of research on this one and get back.
Dependency constraint: omxplayer's --display parameter doesn't support CPIO displays.
Describe the bug The window that opens with the video stream will not open on a screen that is attached via the GPIO pins. These screens use a driver such as this one to output the video via GPIO instead of HDMI. https://github.com/goodtft/LCD-show
To Reproduce Steps to reproduce the behavior:
Expected behavior Expected the sudo displaycameras start command to display output on the screen connected to the GPIO.
Screenshots N/A
Raspberry Pi (please complete the following information):
**Display Configuration
Camera information (please complete the following information):
Features enabled (please complete the following information):
NVR information (please complete the following information):
Additional context N/A
**Files N/A