starred/pikvm-pikvm
1
0
Fork 0
mirror of https://github.com/pikvm/pikvm.git synced 2026-03-02 18:16:56 -05:00
Code Issues 133 Projects Packages Wiki Activity

Webrtc test feedback on Raspberry Pi 2B and zerow #282

New issue
Closed
opened 2026-02-20 13:23:53 -05:00 by deekerman · 11 comments
deekerman commented 2026-02-20 13:23:53 -05:00
Owner
Copy link

Originally created by @wnark on GitHub (Jun 24, 2021).

Originally assigned to: @mdevaev on GitHub.

Describe the bug

[root@ipmi ~]# systemctl status kvmd-janus
* kvmd-janus.service - Pi-KVM - Janus WebRTC Gateway
     Loaded: loaded (/usr/lib/systemd/system/kvmd-janus.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2021-05-19 22:11:58 CST; 1 months 5 days ago
   Main PID: 305 (kvmd-janus)
      Tasks: 11 (limit: 1750)
        CPU: 3.417s
     CGroup: /system.slice/kvmd-janus.service
             |-305 /usr/sbin/python /usr/bin/kvmd-janus --run
             `-322 /usr/bin/janus --disable-colors --plugins-folder=/usr/lib/ustreamer/janus --configs-folder=/etc/kvmd/janus --interface=192.168.31.66 --stun-server=stun.l.google.com:19302

Jun 24 17:07:32 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => [ERR] [src/plugin.c:_clients_thread:224] [ustreamer] Can't open memsink: No such file or directory
Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => [WSS-0x70800b60] Destroying WebSocket client
Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => Destroying session 8045646714052955; 0x71d00df8
Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => Detaching handle from ustreamer; 0x71d01260 0x70801030 0x71d01260 (nil)
Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => == ustreamer -- Removing session 0x70801030 ...
Jun 24 17:07:54 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => == ustreamer -- No active watchers, memsink disconnected
Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => Creating new session: 5124019920183655; 0x70802068
Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => Creating new handle in session 5124019920183655: 7650495398367946; 0x70802068 0x71d04820
Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => == ustreamer -- Creating session 0x71d01070 ...
Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner            INFO --- => [ERR] [src/plugin.c:_clients_thread:224] [ustreamer] Can't open memsink: No such file or directory

Hello, I try to use WebRTC on Raspberry Pi 2B, when I execute it manually
systemctl enable --now kvmd-janus
Although there are open options on the web page, WebRTC cannot be used.
Is webrtc only available for Raspberry Pi 4B, is this determined by the hardware?

To Reproduce

  1. Compile the image on June 24
  2. systemctl enable --now kvmd-janus
  3. reboot
  4. webrtc did not work

Expected behavior
i can use h264

Screenshots
image

Desktop (please complete the following information):

  • OS: Windows
  • Browser chrome & edge
  • Version new

Pi-KVM info:

  • RPi 2
  • v0-hdmi
  • CSI bridge
    [root@ipmi ~]# pacman -Q | grep kvmd
    kvmd 3.6-1
    kvmd-fan 0.1-1
    kvmd-oled 0.3-1
    kvmd-platform-v0-hdmi-rpi2 3.6-1
    kvmd-webterm 0.39-1

ustreamer 4.4-1

Linux ipmi 5.10.23-2-ARCH #1 SMP Fri Mar 19 00:22:18 MSK 2021 armv7l GNU/Linux

Additional context
By the way, what does memsink do? I can't find it on Google

Originally created by @wnark on GitHub (Jun 24, 2021). Originally assigned to: @mdevaev on GitHub. **Describe the bug** ``` [root@ipmi ~]# systemctl status kvmd-janus * kvmd-janus.service - Pi-KVM - Janus WebRTC Gateway Loaded: loaded (/usr/lib/systemd/system/kvmd-janus.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2021-05-19 22:11:58 CST; 1 months 5 days ago Main PID: 305 (kvmd-janus) Tasks: 11 (limit: 1750) CPU: 3.417s CGroup: /system.slice/kvmd-janus.service |-305 /usr/sbin/python /usr/bin/kvmd-janus --run `-322 /usr/bin/janus --disable-colors --plugins-folder=/usr/lib/ustreamer/janus --configs-folder=/etc/kvmd/janus --interface=192.168.31.66 --stun-server=stun.l.google.com:19302 Jun 24 17:07:32 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => [ERR] [src/plugin.c:_clients_thread:224] [ustreamer] Can't open memsink: No such file or directory Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => [WSS-0x70800b60] Destroying WebSocket client Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => Destroying session 8045646714052955; 0x71d00df8 Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => Detaching handle from ustreamer; 0x71d01260 0x70801030 0x71d01260 (nil) Jun 24 17:07:53 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => == ustreamer -- Removing session 0x70801030 ... Jun 24 17:07:54 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => == ustreamer -- No active watchers, memsink disconnected Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => Creating new session: 5124019920183655; 0x70802068 Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => Creating new handle in session 5124019920183655: 7650495398367946; 0x70802068 0x71d04820 Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => == ustreamer -- Creating session 0x71d01070 ... Jun 24 17:07:57 ipmi kvmd-janus[305]: kvmd.apps.janus.runner INFO --- => [ERR] [src/plugin.c:_clients_thread:224] [ustreamer] Can't open memsink: No such file or directory ``` Hello, I try to use WebRTC on Raspberry Pi 2B, when I execute it manually systemctl enable --now kvmd-janus Although there are open options on the web page, WebRTC cannot be used. Is webrtc only available for Raspberry Pi 4B, is this determined by the hardware? **To Reproduce** 1. Compile the image on June 24 2. systemctl enable --now kvmd-janus 3. reboot 4. webrtc did not work **Expected behavior** i can use h264 **Screenshots** ![image](https://user-images.githubusercontent.com/24355466/123236904-c7e79200-d50f-11eb-95fe-0cfb0f6e3fb0.png) **Desktop (please complete the following information):** - OS: Windows - Browser chrome & edge - Version new **Pi-KVM info:** - RPi 2 - v0-hdmi - CSI bridge [root@ipmi ~]# pacman -Q | grep kvmd kvmd 3.6-1 kvmd-fan 0.1-1 kvmd-oled 0.3-1 kvmd-platform-v0-hdmi-rpi2 3.6-1 kvmd-webterm 0.39-1 ustreamer 4.4-1 Linux ipmi 5.10.23-2-ARCH #1 SMP Fri Mar 19 00:22:18 MSK 2021 armv7l GNU/Linux **Additional context** By the way, what does memsink do? I can't find it on Google
deekerman commented 2026-02-20 13:23:55 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 24, 2021):

Because I think the CPU and memory usage of Raspberry Pi 2B is not high, I want to try it on Raspberry Pi 2B.

@wnark commented on GitHub (Jun 24, 2021): Because I think the CPU and memory usage of Raspberry Pi 2B is not high, I want to try it on Raspberry Pi 2B.
deekerman commented 2026-02-20 13:23:55 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Jun 24, 2021):

Add to /etc/kvmd/override.yaml:

kvmd:
    streamer:
        h264_bitrate:
            default: 5000
        cmd_append:
            - "--h264-sink=kvmd::ustreamer::h264"
            - "--h264-sink-mode=0660"
            - "--h264-bitrate={h264_bitrate}"
            - "--h264-gop={h264_gop}"
@mdevaev commented on GitHub (Jun 24, 2021): Add to `/etc/kvmd/override.yaml`: ```yaml kvmd: streamer: h264_bitrate: default: 5000 cmd_append: - "--h264-sink=kvmd::ustreamer::h264" - "--h264-sink-mode=0660" - "--h264-bitrate={h264_bitrate}" - "--h264-gop={h264_gop}" ```
deekerman commented 2026-02-20 13:23:55 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Jun 25, 2021):

PS: Memsink is my own shared memory protocol.

@mdevaev commented on GitHub (Jun 25, 2021): PS: Memsink is my own shared memory protocol.
deekerman commented 2026-02-20 13:23:55 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 25, 2021):

Add to /etc/kvmd/override.yaml:

kvmd:
    streamer:
        h264_bitrate:
            default: 5000
        cmd_append:
            - "--h264-sink=kvmd::ustreamer::h264"
            - "--h264-sink-mode=0660"
            - "--h264-bitrate={h264_bitrate}"
            - "--h264-gop={h264_gop}"

image
Hello, how do you see the real frame rate of the transmission? I checked the information and found that the Raspberry Pi uses 2-channel CSI, which should only support 1080P 25 frames at most. The higher frame rate is now supported because the tc358743 chip is used to compress the video stream into h264 and then transmit it to the Raspberry Pi ? I find the CPU usage of the Raspberry Pi is not high.

@wnark commented on GitHub (Jun 25, 2021): > Add to `/etc/kvmd/override.yaml`: > > ```yaml > kvmd: > streamer: > h264_bitrate: > default: 5000 > cmd_append: > - "--h264-sink=kvmd::ustreamer::h264" > - "--h264-sink-mode=0660" > - "--h264-bitrate={h264_bitrate}" > - "--h264-gop={h264_gop}" > ``` ![image](https://user-images.githubusercontent.com/24355466/123402135-021d6600-d5da-11eb-9549-c340a2dbe913.png) Hello, how do you see the real frame rate of the transmission? I checked the information and found that the Raspberry Pi uses 2-channel CSI, which should only support 1080P 25 frames at most. The higher frame rate is now supported because the tc358743 chip is used to compress the video stream into h264 and then transmit it to the Raspberry Pi ? I find the CPU usage of the Raspberry Pi is not high.
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 25, 2021):

https://www.raspberrypi.org/forums/viewtopic.php?t=120702&start=575
https://fluxcoil.net/wiki/hardwarerelated/raspberry_pi_4_tc358743
image

I have checked some information. Even if the video stream is compressed to h264 using tc358743, the video on the Raspberry Pi 2/3/4B is only up to 1080P50 frames? That is, the picture above me is 50 frames? Although I can't detect it.

@wnark commented on GitHub (Jun 25, 2021): https://www.raspberrypi.org/forums/viewtopic.php?t=120702&start=575 https://fluxcoil.net/wiki/hardwarerelated/raspberry_pi_4_tc358743 ![image](https://user-images.githubusercontent.com/24355466/123408305-71e21f80-d5df-11eb-9b08-902a8418ad30.png) I have checked some information. Even if the video stream is compressed to h264 using tc358743, the video on the Raspberry Pi 2/3/4B is only up to 1080P50 frames? That is, the picture above me is 50 frames? Although I can't detect it.
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 25, 2021):

By the way, when I play the game with pikvm, the screen is torn. I don't know if it is because the acquisition rate of tc358743 is not high enough, and it needs 1080P60 frames to be better?

@wnark commented on GitHub (Jun 25, 2021): By the way, when I play the game with pikvm, the screen is torn. I don't know if it is because the acquisition rate of tc358743 is not high enough, and it needs 1080P60 frames to be better?
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 25, 2021):

It’s a bit strange. According to the information found, when the Raspberry Pi 4B is used in conjunction with tc358743, even if 2-csi is used, it can reach 1080P50 frames. This seems to be the limit, but the limit of PIKVM is 25 frames, which is different. The reason for encoding?

@wnark commented on GitHub (Jun 25, 2021): It’s a bit strange. According to the information found, when the Raspberry Pi 4B is used in conjunction with tc358743, even if 2-csi is used, it can reach 1080P50 frames. This seems to be the limit, but the limit of PIKVM is 25 frames, which is different. The reason for encoding?
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@wnark commented on GitHub (Jun 25, 2021):

image
image

In view of the weak CPU performance of the Raspberry Pi zerow and the ability to communicate only via wifi, it is recommended that if you use the Raspberry Pi zerow, only use webrtc to transmit images, which will put a lot of pressure on bandwidth. Even 1080P can run smoothly. Of course, you can also add a w5500 to the Raspberry Pi zerow, but after calculating the cost, it is actually similar to 3B. If you add a network port, it is better to buy a 3B.
The SPI communication speed is 10Mb/s. Using webrtc+zero(w)+w5500 may be the lowest cost solution, and you can even watch videos remotely.
I don't know whether the CPU occupies higher using spi or the CPU occupancy of WiFi.
If anyone is interested, you can try it.

@wnark commented on GitHub (Jun 25, 2021): ![image](https://user-images.githubusercontent.com/24355466/123437600-6c4a0100-d602-11eb-883b-bc69fb0a3528.png) ![image](https://user-images.githubusercontent.com/24355466/123438452-48d38600-d603-11eb-96e3-ad7a7c0b933e.png) In view of the weak CPU performance of the Raspberry Pi zerow and the ability to communicate only via wifi, it is recommended that if you use the Raspberry Pi zerow, only use webrtc to transmit images, which will put a lot of pressure on bandwidth. Even 1080P can run smoothly. Of course, you can also add a w5500 to the Raspberry Pi zerow, but after calculating the cost, it is actually similar to 3B. If you add a network port, it is better to buy a 3B. The SPI communication speed is 10Mb/s. Using webrtc+zero(w)+w5500 may be the lowest cost solution, and you can even watch videos remotely. I don't know whether the CPU occupies higher using spi or the CPU occupancy of WiFi. If anyone is interested, you can try it.
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@arch1mede commented on GitHub (Jun 25, 2021):

RPI 2X is NOT recommended, RPI3B "shouldn't" be recommended, its just not worth the effort to get one of these working but can understand why one would use it. 0w works but is very slow compared to a RPI4. The max you are going to get from this is 1920x1080p50Hz, 25 is the max fps you are going to get from this from a perfect scenario but the way its being utilized, you are not going to see this. What you are looking at is DYNAMIC FPS.

Please review: https://github.com/pikvm/pikvm/blob/master/pages/Community_FAQ.md#why-so-much-latency-between-the-screen-and-target

I would invest in a RPI4 and reuse your 2/3B's for something else, like pihole or something. Recommending this be closed.

@arch1mede commented on GitHub (Jun 25, 2021): RPI 2X is NOT recommended, RPI3B "shouldn't" be recommended, its just not worth the effort to get one of these working but can understand why one would use it. 0w works but is very slow compared to a RPI4. The max you are going to get from this is 1920x1080p50Hz, 25 is the max fps you are going to get from this from a perfect scenario but the way its being utilized, you are not going to see this. What you are looking at is DYNAMIC FPS. Please review: https://github.com/pikvm/pikvm/blob/master/pages/Community_FAQ.md#why-so-much-latency-between-the-screen-and-target I would invest in a RPI4 and reuse your 2/3B's for something else, like pihole or something. Recommending this be closed.
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Jul 4, 2021):

@wnark

By the way, when I play the game with pikvm, the screen is torn. I don't know if it is because the acquisition rate of tc358743 is not high enough, and it needs 1080P60 frames to be better?

I suppose so.

This seems to be the limit, but the limit of PIKVM is 25 frames, which is different. The reason for encoding?

The reason is the limited bandwidth of CSI. You can't transfer more than 25 fps. RPi4 has only 2 lanes. For a larger frame rate, you need 4.

Due to the CPU weakness, I don't recommend using WebRTC on anything other than Pi 4. Officially adding this functionality for older boards is a low priority task. I really recommend that you buy a Pi 4 with the smallest amount of RAM and forget about all the problems.

@mdevaev commented on GitHub (Jul 4, 2021): @wnark > By the way, when I play the game with pikvm, the screen is torn. I don't know if it is because the acquisition rate of tc358743 is not high enough, and it needs 1080P60 frames to be better? I suppose so. > This seems to be the limit, but the limit of PIKVM is 25 frames, which is different. The reason for encoding? The reason is the limited bandwidth of CSI. You can't transfer more than 25 fps. RPi4 has only 2 lanes. For a larger frame rate, you need 4. Due to the CPU weakness, I don't recommend using WebRTC on anything other than Pi 4. Officially adding this functionality for older boards is a low priority task. I really recommend that you buy a Pi 4 with the smallest amount of RAM and forget about all the problems.
deekerman commented 2026-02-20 13:23:56 -05:00
Author
Owner
Copy link

@mdevaev commented on GitHub (Jul 4, 2021):

However, if you find a way to use WebRTC, it will be great.

@mdevaev commented on GitHub (Jul 4, 2021): However, if you find a way to use WebRTC, it will be great.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
gh-pages
No results found.
Labels
Clear labels   
component:documentation

   
help wanted

   
resolution:delayed

   
resolution:duplicate

   
resolution:fixed

   
resolution:invalid

   
resolution:rejected

   
resolution:wontfix

   
success story

   
type:bug

   
type:bug

   
type:feature

   
type:question

   
type:question
No labels
component:documentation
help wanted
resolution:delayed
resolution:duplicate
resolution:fixed
resolution:invalid
resolution:rejected
resolution:wontfix
success story
type:bug
type:bug
type:feature
type:question
type:question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/pikvm-pikvm#282
No description provided.