Differences

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

--- newsletters:2023-11 [2023/11/30 21:32] – osnr
+++ newsletters:2023-11 [2023/11/30 22:48] (current) – Remove Govind TODO, constrain keyboard GIF admin
@@ Line 20: / Line 20: @@
     * {{newsletters:pxl_20231103_191517745.ts.mp4?150}} {{newsletters:pxl_20231107_213647133.ts.mp4?450}}
     * {{:newsletters:pasted:20231130-161747.png?350}}
-  * TODO: Govind?
 ==== Tabletop / in-system editor ====
@@ Line 30: / Line 28: @@
   * Andrés working on multi-keyboard, moving keyboard into virtual program
     * (we'll finally be able to dump tcl-thread and pi.tcl and have everything in virtual programs and subprocesses and statement communication!)
+    * Here's a preview of it monitoring key presses from multiple keyboards plugged into %%folk0%%:
+    * {{:newsletters:pasted:20231130-223928.gif?350}}
 ==== Calibration and CNC ====
@@ Line 43: / Line 43: @@
   * Early November: the first 3D calibration test/demo, using a calibration pattern based on [[http://www.ok.sc.e.titech.ac.jp/res/PCS/research/procamcalib/|Audet (2009)]] but using AprilTag fiducials and printing on the outer perimeter instead of alternating even/odd
     * {{:newsletters:pasted:20231130-183930.png?0x300}}
-    * It's useful to leave gaps in the printed and projected patterns so it's easy to move the board & get the tags 'aligned enough' that the system can see at least 1 projected + 1 printed tag on the same plane, which is then enough information to properly rewarp all the projected tags to fit into the calibration board. Then once you can see most of the projected + printed tags on the board, you record that as a set of example points for calibration
+    * It's useful to leave gaps in the printed and projected patterns so it's easy to move the board & get the tags 'aligned enough' that the system can see at least 1 projected + 1 printed tag on the same plane, which is then enough information to properly rewarp all the projected tags to fit into the calibration board.
+    * Then once you can see most of the projected + printed tags on the board, you record that as a set of example points for calibration (you now have both board-plane coordinates in meters and camera and/or projector coordinates in pixels for all corners of all those tags)
     * Notice how tags in the center of the calibration board are projected dynamically, while tags on the outer perimeter are printed:
       * {{:newsletters:pasted:20231106-180904.jpeg?250}} {{newsletters:img_1095.mp4?250}}
@@ Line 168: / Line 169: @@
     * Fun interim on-a-wall stage during setup, before we pointed it down at the table:
       * {{:newsletters:pasted:20231130-161524.png?250}}
-      * (whenever I see a projection mapping demo, I always feel like we should be able to subsume it and make it really easy to set up and reprogram, like it was trivial to make the meow text here wiggle around over time)
+      * I think this image is a fun provocation because it's sort of //about the wall//, the drawing on the whiteboard, instead of being about the system. Imagine wheeling a system over in 10 seconds and pointing it at part of your environment because you want a thin layer of computation or sharing or dynamism on top of what's there (and not because you want a generic "Folk system" set up that could be set up anywhere)
+      * (btw, whenever I see a projection mapping demo, I always feel like we should be able to subsume it and make it really easy to set up and reprogram, like it was trivial to make the meow text here wiggle around over time)
   * Simplified install instructions to just use Vulkan binaries from apt, instead of compiling mesa from scratch
@@ Line 177: / Line 179: @@
       * Got a Logitech C922 camera for folk-beads: at least it can do 60fps at 720p, much smoother-feeling than the C920 or Azure Kinect which can only do 30fps at any resolution
+===== Hmm =====
+{{newsletters:pasted:20231130-213756.png?550|one observation re: how people pattern-match and overfit to the examples they see is we get a lot of questions and comments about the AprilTag black-and-white markers we use, even though I would say we view those as much less essential than the programming system and database
+and there are a lot of applications like CNC preview or various projection-mapping demos where I think you should be able to get lots of value out of using Folk w/o having any tags visible in the end interface at all}}
+(I think part of our job has to be to just broaden the examples so that fitting to them still gives you a pretty productive working set)
 ===== What we'll be up to in December =====
+  * **[[https://partiful.com/e/MJ6V5SfEKRPPjOskxeti|The next Folk open house]] will be on the evening of Wednesday, December 13, at our studio in East Williamsburg, Brooklyn.** :-)
   * Still need to complete RFID refactor. I need to make the ringbuffer faster and I need to wait on less data to start parsing ..