search

tiny-pilot / tinypilot

Use your Raspberry Pi as a browser-based KVM.
https://tinypilotkvm.com
MIT License
2.99k stars 249 forks source link

Issues with Lusya capture device #688

Closed sander0105 closed 3 years ago

sander0105 commented 3 years ago

Hi All,

I'm trying to get TinyPilot running on an RPi 4 - 4G, with POE HAT and a Lusya capture device. At first I could not even get the capture device to run and report results using v4l2-ctl --query-dv-timings. As it turns out the fan controller of the POE hat conflicts with the Lusya (see: https://github.com/pikvm/pikvm/issues/6). Luckily this was a simple fix.

Now I can see the output of v4l2-ctl --query-dv-timings:

Active width: 1920
    Active height: 1080
    Total width: 2200
    Total height: 1125
    Frame format: progressive
    Polarities: -vsync -hsync
    Pixelclock: 148500000 Hz (60.00 frames per second)
    Horizontal frontporch: 0
    Horizontal sync: 280
    Horizontal backporch: 0
    Vertical frontporch: 0
    Vertical sync: 45
    Vertical backporch: 0
    Standards:
    Flags:

But the TinyPilot UI gives me a "No Signal"

Diving into the logs shows the following

May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.591    stream] -- Device fd=9 opened
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.591    stream] -- Using input channel: 0
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.608    stream] -- Got new DV timings: resolution=1920x1080, pixclk=148500000
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.655    stream] -- Using resolution: 1920x1080
May 12 20:50:15 tinypilot ustreamer[634]: -- ERROR [367.655    stream] -- Could not obtain the requested pixelformat=JPEG; driver gave us RGB24
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.655    stream] -- Falling back to pixelformat=RGB24
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.655    stream] -- Using pixelformat: RGB24
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.655    stream] -- Querying HW FPS changing is not supported
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.655    stream] -- Using IO method: MMAP
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.689    stream] -- Requested 5 device buffers, got 5
May 12 20:50:15 tinypilot ustreamer[634]: -- ERROR [367.691    stream] -- Unable to start capturing: Invalid argument
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.712    stream] -- Device fd=9 closed
May 12 20:50:15 tinypilot ustreamer[634]: -- INFO  [367.712    stream] -- Sleeping 1 seconds before new stream init ...

Note the ERROR [367.691 stream] -- Unable to start capturing: Invalid argument

Now, this is where I can't find why this happens... Does anyone have a suggestion where to look?

mtlynch commented 3 years ago

Thanks for reporting this!

The standard installer assumes that you're using the HDMI to USB dongle. You can fix this by editing your settings.yml and re-running the installer:

https://github.com/mtlynch/tinypilot/wiki/Installation-Options#example-tc358743-hdmi-to-csi-capture-chip