hackerb9

Ah, you are referring to **processlabel()**, the seamy underbelly of lsix that features `sed | tr | awk | sed`. While it might seem a natural place to put your...

Good question! I'd love to have an answer to that on the lsix page. I mostly use `XTerm`, the second slowest sixel interpreter I've ever seen, which is good enough...

So, I just tried my ancient sixvid gif viewer on the sixel capable terminals that are packaged with the current Debian GNU/Linux (11, bullseye) and got some results that were...

Here's my sixvid gif viewer if you'd like to see relative speeds of sixel implementations on your own computers: https://github.com/hackerb9/sixvid Usage: `sixvid nyantocat.gif` (Hit the `b` key to toggle benchmarking...

> were you running `foot` in a standalone Wayland, or xwayland? i'm not sure the latter would be a particularly fair comparison. A good question and one I am gratified...

> I couldn't get sixvid to work - the screen just went black. Huh. I wonder if ImageMagick is calling `ffmpeg` even for GIF decoding.

@j4james I've put in some sanity checks so hopefully you'll get an error message now instead of a blank screen.

> Technically you shouldn't need to avoid the bottom row with sixel either - that's just a bug in most implementations. @j4james just schooled me on that one this week....

@dankamongmen wrote: > I've found the total time to generally be dominated by transfer, not by actual rendering. Interesting. I added a `--shm` option to [sixvid](https://github.com/hackerb9/sixvid) to create the temporary...

@dankamongmen writes: > I'm a big believer in the superiority of the kitty protocol in just about every sense, even (perhaps counter-intuitively) implementation complexity (no need to deal with heights...