Capture Card gets killed on HyperHDR Boot

iblake12 commented 2 years ago

https://pastebin.com/9SQYSrRG

Bug report, debug log and your config file (FULL LOGS ARE MANDATORY)

https://pastebin.com/9SQYSrRG

Steps to reproduce

Start up HyperHDR on Raspberry Pi 3B+ running Pi OS Lite

What is expected?

Capture card feed to be visible in live video window and capture card loop out to show on TV

What is actually happening?

As soon as HyperHDR loads (and the LEDs play the startup effect) the loop out on capture card goes blank and no video is shown in webpage live video window. Capture card shows up as an option and is selectable. Have tried with different capture cards, hdmi cables and USB cables, powering card externally and via the Pi. Same issue every time

System

HyperHDR Server:

Build: (HEAD detached at dec81c0) (Awawa-2a2ed8d/dec81c0-1631541363)
Build time: Sep 15 2021 16:23:59
Git Remote: https://github.com/awawa-dev/HyperHDR
Version: 17.0.0.0
UI Lang: auto (BrowserLang: en-GB)
UI Access: default
Avail Capt: Linux (V4L2)
Database: read/write

HyperHDR Server OS:

Distribution: Raspbian GNU/Linux 11 (bullseye)
Architecture: arm
CPU Model: ARMv7 Processor rev 4 (v7l)
CPU Type: Raspberry Pi 3 Model B Plus Rev 1.3
CPU Revision: a020d3
CPU Hardware: BCM2835
Kernel: linux (5.10.63-v7+ (WS: 32))
Qt Version: 5.11.3
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.45 Safari/537.36

awawa-dev commented 2 years ago

And what makes you think it's a HyperHDR issue not your video grabber/capture card/power issue? That short logs looks clear to me (too short to detect if the V4L2 captured something).

awawa-dev commented 2 years ago

Well that single last line is few minutes after...your capture card is simply not working.

iblake12 commented 2 years ago

Hi, thanks for the fast reply! I have tried 4 different capture cards all producing the same problem, all of them pass through fine if i unplug and replug them into the Pi (so they get power but not communicating with hyperhdr), and they also work fine on the Pi booting for passthrough until hyperhdr loads. I am using the same capture card as a few other people with the same hardware and they dont seem to have an issue, have also had a couple people more confident with your software have a look and couldnt figure out the issue, they suggested i come here to ask after they tried everything they could think of.

awawa-dev commented 2 years ago

There are 3 most common source of these symptoms: 1) most common is power issues when the systems power supply (or it's USB power cable) is not sufficient or is not stable. The card may be detected on the boot because it is in idle state and does nothing but providing its definition to the system. Internal HDMI splitter may also work then. But when the capture process starts it requires much more power from USB port. If it is not provided the hardware may crash. On Rpi check your dmesg command because sometimes it leaves a trace there.

Next two problems depend on the grabber model.

2) HDMI cable is disconnected from the grabber. The device provide some video capturing interface to the system but when the application tries to use it then it captures nothing. 3) HDMI cable is connected to the grabber but it provides no HDMI source or HDMI source format is out of internal grabber's capabilities (for example 4:2:0 may be not supported). The device provide some video capturing interface to the system but when the application tries to use it then it captures nothing.

For example Av Access behaves in way described in point 2 and 3.

awawa-dev / HyperHDR