From 52b83433e6839399772093ca2ccf76951b854354 Mon Sep 17 00:00:00 2001 From: kevinlekiller Date: Sun, 23 Jun 2019 13:55:49 -0400 Subject: [PATCH] Update README.md --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 0ec7056..109d98c 100644 --- a/README.md +++ b/README.md @@ -14,6 +14,8 @@ If your display is 3840x2160 and you put in -s 10, the image sent to Hyperion wi You should set this option so the image resolution sent to Hyperion is at least the size of your LED array, if you have for example 64 high by 36 wide of LED's, you would want to set -s to 60 or smaller (between 1 and 60) on a 3840x2160 display. The closer to 1 this setting is, the more CPU / bandwith will be used. Ideally you want a perfect dividor, for example if your LED array is 70x39 and screen sis 3840x2160, then you get (3840/70) 54.86 for the width and (2160/39) 55.38 for the height, the nearest perfect dividor is 48 (3840/48 = 80 ; 2160/48 = 45), if you were to use 54, then there would be rounding error (3840/54 = 71.111, but is truncated to 71) and the image sent to hyperion will not be correctly scaled. +While watching a video with a 3840x2160 60hz display, frameskip at 1 (30fps), divisor at 24 (160x90 output resolution) CPU usage is about 2% of one cpu thread, memory usage is 17.3 KB according to HTOP. + There are probably bugs, please submit a pull request if you can. To compile run `cmake . && make`, qt5 / x11 libraries are required.