21–30 of 36 posts
A fun experiment, and cute if not for the lag. A full 14 seconds between the pen stopping writing and the result, What I'd find interesting is the trace of that 14 seconds. How much is the Remarkable processing, how much is the claude transcription, how much is the let-go start-up / processing, etc.
The author mentions that in the blog. The majority is the delay of the updated file actually being written to disk by the device. The author did not find a solution to trigger file write earlier/more frequently.
Searching the article again, I see in the FAQ:
> Xochitl takes approximately 12 seconds to update the notebook on-disk
12 definitely isn't "several" in my understanding, but regardless, I guess there's little the author can do then.
Now I have a reason to get reMarkable :)
Caveat: reMarkable have not said they will supply spare parts but this should be on their radar
I tried the model on your handwriting and it worked great. My handwriting is bad enough that it doesn't work :)
You must be a Recurser, right? This is so very Recurser.
Ok this might be the coolest thing I've seen all month. You must be a Recurser, right? This is so very Recurser.
Ok this might be the coolest thing I've seen all month. You must be a Recurser, right? This is so very Recurser.
I have no idea who or what a Recurser is, but I guess I’ll be checking it out. :D
I find getting stuff up on the rM2 screen a hassle. The challenge comes from the way the e-paper works. To turn a pixel from white to black (or vice versa) it needs multiple actual frames. The pixel data must also be packed in a specific format. Instructions for how many frames a single operation requires are coded in a wbf[0] file, which comes included with the OEM firmware. The most commonly used approach is hookin…
I really want to try for further reverse engineering of xochitl now that I've heard those AI tools have gotten so good at doing it.
Man I really wish one day I could run mainline Linux kernel on this tablet with the display just works.