Differences

This shows you the differences between two versions of the page.

--- pilot [2024/04/30 15:39] – osnr
+++ pilot [2025/08/31 17:46] (current) – osnr
@@ Line 1: / Line 1: @@
 Do you want to set up your own Folk system?
+**Note: Folk is in a pre-alpha state and isn't yet well-documented or well-exampled.**
+**We're making Folk's source code & instructions free and available to the public, in case you're already excited about trying it, but we haven't formally announced it or made it ready for public use. We make no guarantee of support, of usability, or of continuing backward compatibility. Try at your own risk!**
 ==== Software requirements ====
@@ Line 5: / Line 9: @@
 Folk is open-source software, available to the public under the Apache 2.0 license.
-**See https://git.folk.computer/folk/about/ for software instructions.**
+**See [[https://github.com/FolkComputer/folk?tab=readme-ov-file#folk|the README on GitHub]] for software instructions.**
-If you want to contribute and get access to internal discussion, you'll want to be on our private GitHub repository -- you'll have to sign up for [[https://github.com/sponsors/FolkComputer|our GitHub Sponsors]], which covers our costs for that (until we open that GitHub repository, we have to pay GitHub monthly for each seat we add to the repo).
 ==== Hardware requirements ====
-From scratch, we would estimate somewhere between $50-200 per square foot that you want to cover, depending on decisions like what resolution and framerate you want. You may already have a projector and/or webcam and/or computer -- we would recommend at least getting a dedicated computer and not using your laptop, though.
+From scratch, we would estimate somewhere between $50-200 per square foot that you want to cover, depending on decisions like what resolution and framerate you want. You may already have a projector and/or webcam and/or computer -- note that you will almost certainly need a dedicated computer running Linux to run Folk, not your laptop.
 === Hardware list for setting up a Folk instance ===
@@ Line 24: / Line 26: @@
     * <del>The Raspberry Pi 4 will require a micro-HDMI to HDMI dongle or cable. It can be set up headlessly and automatically.</del>
-  * A high-end Raspberry Pi (Pi 4 or Orange Pi 5) can work in a pinch, but computer power matters a lot for latency and user experience, so we recommend investing in a solid computer.
+  * A high-end Raspberry Pi (Orange Pi 5 or Pi 5) can work in a pinch, but computer power matters a lot for latency and user experience, so we recommend investing in a solid computer.
   * (You will probably need a USB keyboard and USB flash drive to get your computer initially set up.)
@@ Line 32: / Line 34: @@
 == Projector ==
-  * We recommend the **[[https://aaxatech.com/store/products/4k1_pico_projector_store.htm|AAXA 4K1]]** (~$800, available refurbished only) for the brightest, clearest text rendering and largest area.
+  * We recommend the **[[https://aaxatech.com/store/products/4k1_pico_projector_store.htm|AAXA 4K1]]** (~$800, available refurbished only) or (untested) maybe the [[https://www.lg.com/us/projectors/lg-hu710pb-smart-portable-projector|LG CineBeam Q HU710PB]] for the brightest, clearest text rendering and largest area.
   * If you’re on a budget or want a more portable option, the [[https://aaxatech.com/store/products/P400_mini_projector_store.html|AAXA P400]] ($269) is a good option for a portable 1080p projector.
@@ Line 38: / Line 40: @@
   * Any projector will do, but any projector with a native resolution of less than 1080p will only be good for projecting shapes & very large text.
-  * Ultra-short-throw projectors like the Samsung The Premiere are expensive but can be really bright and may allow you to avoid overhead mounting.
+  * Ultra-short-throw projectors like the Samsung The Premiere are expensive but can be really bright and may allow you to avoid overhead mounting. It may be difficult to calibrate an ultra-short-throw projector (because it's hard to tilt the calibration board and the optics are really distorted)
 == Camera ==
-  * Any 720p, 1080p, or 4K webcam will do, but you'll have a better experience if it can at least do 60fps at 720p.
+  * Any 720p, 1080p, or 4K webcam may work, but we recommend you get a webcam that has the ability to **set manual exposure** (including any of the below). (This is so that the camera image doesn't get washed out by light from the projector during calibration.)
+    * You'll also have a better experience if the webcam can do 60fps at whatever resolution you have set.
-    * We use a Logitech BRIO 4K. A Logitech C920 series 1080p webcam is often used & is easy to find & affordable, but the [[https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-for-hd-video-streaming-black/5579380.p?skuId=5579380|Logitech C922]] is probably a better option, because it can do 720p60; the C920 can only do 720p30.
+    * We would recommend a [[https://www.amazon.com/Microphone-NexiGo-N980P-Reduction-Wide-Angle/dp/B08DHPBP65|NexiGo N980P]] (1080p, 60Hz) or Logitech BRIO 4K (4K, 60Hz).
+      * A Logitech C920 series 1080p webcam is often used & is easy to find & affordable, but the [[https://www.bestbuy.com/site/logitech-c922-pro-stream-1080-webcam-for-hd-video-streaming-black/5579380.p?skuId=5579380|Logitech C922]] is probably a better option, because it can do 720p60; the C920 can only do 720p30.
       * (We used to use a Microsoft Azure Kinect, but it can only do 30Hz.)
-      * We want to try the NexiGo N660P (1080p60): look for a webcam like the N660P or BRIO 4K that can do 60Hz if possible.
+    * Hang your webcam as close to the table (projection surface) as possible. You want the tags to be as big in the webcam image as possible to help detection stability. (If ceiling mounting, you will probably find that your webcam should be much lower than your projector.)
 == Printer ==
@@ Line 69: / Line 74: @@
 ==== Support ====
-Note: it's very not-turnkey right now; you'll definitely run into bugs and issues. We plan to do a more comprehensive release and announcement in 2024, including a Linux live USB and opening up our internal GitHub repository, but there's a lot of work to do before then.
+Note: it's very not-turnkey right now; you'll definitely run into bugs and issues. We plan to do a more comprehensive release and announcement, including more examples and explanations, but there's a lot of work to do before then.
 We're happy to talk about consulting work if you want dedicated support or system development. Reach out at [[mailto:omar@folk.computer|omar@folk.computer]] and [[mailto:cwervo@folk.computer|cwervo@folk.computer]].