issues with Capture device after 1.9.2 update

[Scherzingetorix]

Description

in MJPEG mode (with default settings), the image disappears after a few minutes, and in H.264 mode (default settings), the lower quarter of the image occasionally flickers. By flickering, I mean that the image disappears in a strip or changes color briefly and after some time image freezes.

Hardware Deatils

Raspberry Pi 4 Model B Rev 1.4

I have no idea about the exact model of the HDMI Capture device or the chip it uses; all I know is what it looks exactly like this one:

I tested the device on a Windows 11 machine, and it worked properly there, no flickering or freezing

What are the steps to reproduce this behavior?

1. Open TinyPilot in Chrome and error shows up after couple of minutes

Screenshots

Logs

132 Jan 30 13:01:51 raspberrypi launch[532]: -- ERROR [10.057 stream] -- Could not obtain the requested format=JPEG; driver gave us MJPEG
136 Jan 30 13:01:51 raspberrypi launch[532]: -- ERROR [10.059 stream] -- Device doesn't support setting of HW encoding quality parameters
144 Jan 30 13:01:51 raspberrypi launch[532]: -- ERROR [10.367 stream] -- Can't decompress JPEG: Unsupported marker type 0x15.

The log dump creation script is not in the specified location. What do you suggest I do to collect the logs? Maybe I should install the developer version as described on the Wiki page?

-bash: /opt/tinypilot/dev-scripts/dump-logs: No such file or directory

[cghague]

Hi, Scherzingetorix; thanks for your message. I'm sorry you're experiencing intermittent video.

The error message in your shared logs suggests that the HDMI capture device sent a corrupted video frame. There could be several explanations for corrupted video frames, so we'll need to investigate further.

Can you please provide a link to your logs? You can do this by going to System, then Logs, or by running the following command over SSH or in a terminal:

sudo /opt/tinypilot-privileged/scripts/collect-debug-logs

[Scherzingetorix]

Hi Cghague,

https://logs.tinypilotkvm.com/5Xsm8KZ6

I reassembled the KVM solution after testing the Video Capture device on a win11 machine, and suddenly it started working again. I don't necessarily understand what caused the issue and why it suddenly improved. The only change made was that I began installing the Typilot developer version, but I got stuck somewhere in the process, obviously lacking the necessary knowledge for it. I hope the log files reveal something about what might have happened and why it deteriorated right after the update.

However, the issue of significantly slower video transmission still persists compared to version 1.6.2, where even videos appeared seamless. Now, there is a considerable lag. In summary, it is currently functioning but quite slow. Unfortunately, I cannot specify the FPS or the lag in milliseconds. If there is a measurement solution for this, I would gladly perform it.

Thank you for your help!

[cghague]

Thanks for getting back to me!

Based on your description and the content of the logs you provided, I suspect there may have been a loose connection and that disconnecting and reconnecting the cables has resulted in a better, more stable connection. The quality of cables and adapters can vary substantially, so this is a fairly common problem.

In terms of lag, there could be a few explanations. One possible explanation is that your Raspberry Pi isn't receiving enough power, as shown by these lines in the logs:

CPU throttled since boot: yes
Voltage issues: yes - Jan 31 16:07:26 raspberrypi kernel: hwmon hwmon1: Undervoltage detected!

Your Raspberry Pi will reduce its performance when this happens, which could result in increased lag, so you might need to upgrade your power supply.

I also see you are using MJPEG mode rather than H.264 mode. Once you have resolved the power supply issue, I suggest switching to H.264, as it offers substantially better video performance with reduced lag.