From 37df890faa68dcf48edebea00ab5b1009816dbd6 Mon Sep 17 00:00:00 2001 From: arch1mede Date: Thu, 15 Aug 2024 11:22:10 -0700 Subject: [PATCH] Update faq.md (#1350) * Update faq.md Verbiage added for clarification * Update faq.md Changed the verbiage to better reflect the reason. --- docs/faq.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index e1124343..eeb0fb98 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -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.