-
Notifications
You must be signed in to change notification settings - Fork 112
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
Screen Flashing/Blanking/Restart? #2
Labels
Comments
Your logs are interesting. I've never tried camera names that are numeric
only, and omxplayer is objecting to a DBUS address specified in the
omxplayer command switches. For each camera, the DBUS address is the
default address (which should be totally fine) appended with
".camera_name". I suspect that numeric camera names must violate some
basic namespace restrictions for the DBUS address. I suspect all is well
until the first watchdog run where players won't return a play status via
DBUS.
Try camera names that aren't numeric, eliminate the extra feeds in the
layout file, and retry. Please, report back: If numeric names are a
problem, I'll need to include that warning in the documentation.
Thanks,
A
…On Sun, Jul 15, 2018, 1:58 PM mcmcomput ***@***.***> wrote:
*Describe the bug*
The PI boots up fine, starts loading cameras approx 5 sec apart then after
about a minute the screen goes black like it lost connection, sometimes
flickers once or twice over a period of a minute or two before the camera
service restarts i think and re-opens the cameras one by one. I may just
have something configured wrong, but it seemed pretty easy to figure out
between the two configs. Both are attached for reference.
*Raspberry Pi (please complete the following information):*
- Hardware model: Raspberry Pi 3 Model B Plus Rev 1.3
- OS: 2018-06-27-raspbian-stretch-lite / Linux version 4.14.52-v7+
- gpu memory split: 256MB
- displaycameras Version: 0.8.3.3
**Display Configuration
- Display/Monitor resolution: 1920x1080
- Window matrix: 2x2 (3 cameras)
- Feed resolution: 640x360
*Camera information (please complete the following information):*
- Number of cameras: 3
- Camera models: Hikvision
- Unmanaged
*Features enabled (please complete the following information):*
- Rotation: no
- Display Blanking: yes (tried both)
- Display Detection: no
**Files
Attached the log and config files,
layout.conf.default.txt
<https://github.com/Anonymousdog/displaycameras/files/2195963/layout.conf.default.txt>
displaycameras.conf.txt
<https://github.com/Anonymousdog/displaycameras/files/2195965/displaycameras.conf.txt>
logs.txt
<https://github.com/Anonymousdog/displaycameras/files/2195966/logs.txt>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AdGEKSmdeJVQP4CSQybC_LZj0iPDo6FHks5uG4LXgaJpZM4VQVJS>
.
|
I changed them to "One Two Three" instead. :) Feeds are holding solid now for 30+ minutes. |
Fixed with documentation of DBUS namespace restrictions in README.md with commit c61e4c1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
The PI boots up fine, starts loading cameras approx 5 sec apart then after about a minute the screen goes black like it lost connection, sometimes flickers once or twice over a period of a minute or two before the camera service restarts i think and re-opens the cameras one by one. I may just have something configured wrong, but it seemed pretty easy to figure out between the two configs. Both are attached for reference.
Raspberry Pi (please complete the following information):
**Display Configuration
Camera information (please complete the following information):
Features enabled (please complete the following information):
**Files
Attached the log and config files,
layout.conf.default.txt
displaycameras.conf.txt
logs.txt
The text was updated successfully, but these errors were encountered: