awawa-dev
commented
3 months ago Hi
2024-07-09T11:36:00.437Z [PERFORMANCE] [USB: FPS = 60.02, decoding = 1ms, frames = 3601, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.02, processed = 3601], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0] 2024-07-09T11:37:00.440Z [PERFORMANCE] [USB: FPS = 60.02, decoding = 1ms, frames = 3602, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.02, processed = 3602], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0] 2024-07-09T11:37:01.454Z [SIGNAL_AUTO] No signal detected. The cognition model's probability: 100% 2024-07-09T11:37:06.469Z [SIGNAL_AUTO] THE SIGNAL IS LOST 2024-07-09T11:37:07.655Z [MUXER0] Priority 240 is now inactive
this is your work ;) because you have configured and enabled signal detection
and this
2024-07-09T12:35:00.445Z [PERFORMANCE] [USB: FPS = 59.99, decoding = 2ms, frames = 3600, invalid = 0, mode = direct], [INSTANCE0: FPS = 59.99, processed = 3599], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0] 2024-07-09T12:36:00.444Z [PERFORMANCE] [USB: FPS = 60.00, decoding = 2ms, frames = 3600, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.00, processed = 3600], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0] 2024-07-09T12:37:00.445Z [PERFORMANCE] [USB: FPS = 60.00, decoding = 2ms, frames = 3600, invalid = 0, mode = direct], [INSTANCE0: FPS = 60.00, processed = 3600], [LED0: FPS = 50.00, send = 3000, processed = 3000, dropped = 0] 2024-07-09T12:37:04.470Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 829440 2024-07-09T12:37:04.470Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 829440 2024-07-09T12:37:04.470Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 829440 2024-07-09T12:37:04.470Z [V4L2:USB3.0 UHD: US] Frame too small: 0 != 829440
is probably some hardware problem. Next time it appears run dmesg and upload its output to pastebin.
What is your RPi power supply?
Moving the subject to the discussion.
Hello Awawa!
First of all I'd like to thank you for all the work you've put into this project, which is quite simply the most accomplished on the ambilight scene!
I'm back from the early days of ambilight on rapsberry, and I wanted to update my lighting infrastructure. I was using RPI3b with an internal grabber for about ten years, now I'm using RPI4b with an external grabber.
The information on my current equipment :
Everything seems to be working, only one small problem persists. After 15 - 30 minutes, the grabber disconnects unexpectedly, and I have to restart the RPI to get it working again. This problem can be solved by using the "auto resume" function, which restarts the grabber; the LEDs are only switched off for a few seconds, usually 5.
I can't find the cause of this problem. And the "auto resume" function causes the grabber to stop for a few seconds, which is slightly disturbing. I think the problem might be with the grabber, but I've probably missed something in the settings? Maybe something to force the grabber to stay connected non-stop?
Here's the log:
In this log the crash appeared at the end, and the option auto resume was not enabled.
I tried going through hyperion, but the problem is much worse, the grabber output is blurry, etc ...
Another persistent problem that seems to have been solved without explanation. When I changed the source from RPI to another source there was no problem, but when I returned to the RPI source the grabber gave me a green image with white text. To solve this problem I had to change sources several times between the RPI and a second device and the RPI image returned to normal. I don't know if this would help with the overall problem.
Thanks for your help!
Edit : I changed the grabber settings to full automatic, the problem persist. And with only the "auto resume" option checked it still stop just few seconds.