Differences

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

--- newsletters:2026-03 [2026/04/22 23:05] – [Mounting research] osnr
+++ newsletters:2026-03 [2026/04/23 01:39] (current) – osnr
@@ Line 3: / Line 3: @@
 {{htmlmetatags>metatag-og:title=(Folk Computer March 2026 newsletter)
 metatag-media-og:image=(newsletters:pasted:20260311-191224.jpeg)
-metatag-og:description=(TODO: Description)
+metatag-og:description=(New studio move-in and mounting; SAM2 image view; editing built-in programs; GIFs; block stats)
 }}
@@ Line 10: / Line 10: @@
 [[{}https://luma.com/toq7zpc7|RSVP for the Folk open house on April 27]]
-We're a nonprofit doing unique open-source research on physical computing and programming -- please consider sponsoring us:
+We're a nonprofit doing unique open-source research on physical computing and programming -- we'd appreciate it if you sponsored us on GitHub:
 [[{}https://github.com/sponsors/FolkComputer|**Sponsor Folk on GitHub Sponsors**]]
@@ Line 147: / Line 147: @@
   * Text rendering optimizations: [[https://github.com/FolkComputer/folk/commit/db34ab34844e8aa25757282af8d2698002f43bcb|make the font object an opaque pointer]] since we only operate on it from C anyway, so we don't have to reparse it for every text render. Makes text render go from 1ms -> 300us.
     * [[https://github.com/FolkComputer/folk/commit/780c34ab4dc39fd864ea43fef1f54cd805b0ac8c|Build the shaped text object directly as a string]], so we don't need to serialize for every value, also saving a few hundred microseconds I think
+  * [[https://github.com/FolkComputer/folk/commit/f4560366f1c2371e369b1b5cef466842981944a5|Fixed blink bug with /camera where it would distractingly blink out if frame retrieval failed; wait for success before changing frame]]
+  * Fixed GPU crashes and warpQuad out-of-bounds when holding page in weird orientation (allocating way too big an image)
 === Default calibration ===
@@ Line 177: / Line 179: @@
 {{.:pasted:20260422-220525.png?450px}}
-Realized that it was a bad move to do JPEG-space crop and decompression for each slice -- it's almost as slow as a full decompress -- should go back to doing the full decompress for every camera frame and then putting the raw color frame in a statement. But this adds a lot of latency, because it takes a few ms (!) to do a full decompress, so now we decompress both gray and RGB in parallel. I feel like we can do more here.
+Realized that it was a bad move to do JPEG-space crop and decompression for each slice -- it's almost as slow as a full decompress -- should go back to doing the full decompress for every camera frame and then putting the raw color frame in a statement. But this adds a lot of latency, because it takes a few ms (!) to do a full decompress, so now we decompress both gray and RGB in parallel.
+{{newsletters:screenshot-2026-03-23-at-4.39.56-pm.png?300px}} {{.:pasted:20260422-230930.png?300px}}
+I feel like we can do more here -- reduce rest-of-system latencies, use hardware-accelerated JPEG decoding, whatever. There shouldn't be a 2ms difference between gray decode and RGB decode, and a 2ms difference shouldn't wreck system throughput.
 === Multi-projector support ===