public_git
/
pikvm
mirror of https://github.com/pikvm/pikvm.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update faq.md (#1350) 

* Update faq.md

Verbiage added for clarification

* Update faq.md

Changed the verbiage to better reflect the reason.
This commit is contained in:
arch1mede 2024-08-15 11:22:10 -07:00 committed by GitHub
parent f5cb272dfa
commit 37df890faa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/faq.md
View File

@ -83,6 +83,9 @@ As a first step, we recommend carefully reading our documentation on [GitHub](ht
100-200ms is very, very fast for this. But we are working to speed things up even more.
??? question "I am expecting to see 60fps and I am not, why?"
PiKVM receives the entire signal, but then the encoding is the bottleneck. For 1080p, this is no more than 30 fps. V4 throws out every second frame of 60 hz/fps, and 30 fps is encoded. V3 and DIY can't process 60 hz and is only able to capture 50 hz, and in the same way they take every second frame, all you get out is 25 fps. The reason why V3 and DIY does not encode 30 out of 50 is that the picture will be jerky, but smooth at 25.
??? question "Does PiKVM support sound?"
Yes but the only officially supported version is the PiKVM V3+ devices, V2 we will attempt best effort but ultimatly we do not support CSI modules or USB.