aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMaZderMind <git@mazdermind.de>2015-12-06 20:28:10 +0100
committerMaZderMind <git@mazdermind.de>2015-12-06 20:30:16 +0100
commitc7dba7a241a2da92a8919b4800e8c929330c144a (patch)
tree15dd6e824261e27c65fb62a895ac0086bedf6475
parent39c8cb3a0e3813ef77c61c601d0028281c04ad2d (diff)
[voctocore] add a hint to change the source resolution when testing
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 751c60a..9043b26 100644
--- a/README.md
+++ b/README.md
@@ -42,7 +42,7 @@ cd voctomix
## A word on CPU-Usage
Voctomix requires a fair amount of CPU-Time to run in the default configuration of 1920×1080 at 25fps. Our Production-Systems have these CPUs: `Intel Core i7-3770 CPU 4x 3.40GHz` but we're also experimenting with newer ones like these: `Intel Core i7-6700K, 4x 4.00GHz`.
-For testing and development you may want to use a `config.ini` that reduces the resolution and also turns off the JPEG-Preview-Encoders, which take a huge amount of the required CPU-Power and are not required, as long as the GUI and the Core run on the same machine (or have a 10GE Link between them, FWIW).
+For testing and development you may want to use a `config.ini` that reduces the resolution and also turns off the JPEG-Preview-Encoders, which take a huge amount of the required CPU-Power and are not required, as long as the GUI and the Core run on the same machine (or have a 10GE Link between them, FWIW). Don't forget to modify your source-scripts to provide the correct resolution.
Such a config.ini might look like this:
````