sunburn.nvim VS rtpmidid

A while back I read about the Oklab color space, and long story short I decided I wanted to create my own Neovim coloscheme. That led to sunburn.nvim[1], which aims to take advantage of the hue and brightness uniformity that Oklab provides.

At first I was using lush.nvim to build sunburn.nvim, but quickly it became a hassle to only be able to specify colors via RGB or HSL. My initial thought was a PR to add Oklab support to lush, but that framework does so much that it was hard to see where to start. So I ended up writing polychrome.nvim[2], which is a dead simple micro framework in comparison to lush.nvim, but does enough to take care of all the boilerplate, and supports a bunch of color spaces (which are converted to RGB on the fly).

I also wanted push notifications for when certain RSS feeds I follow were updated, because I suck at remembering to check in on things or check an RSS feed app. But I didn't want to pay for IFTTT or other bespoke solutions, so I wrote notifeed[3]. It's designed to run as a service on a server, and then check all your feeds at predetermined intervals and send the necessary webhooks based on your configuration. Feeds and clients are configured via the CLI and stored in a SQLite DB for simplicity.

[1] https://github.com/loganswartz/sunburn.nvim

rtpmidid[1]. After getting some hardware synthesizers and wanting to connect them without using a computer.. but being able to use them too using the computer I stumbled upon with rtpmidi the protocol and it ticked all the boxes I needed. I could connect all my gear to a raspberry pi, use ALSA sequencer to connect devices to each other with another of my programs AseqRC[2], and then use my synths from my DAW without touching any cable.

So after a fast prototype I created rtpmidid and I'm quite happy on how it works.

And it also helps with the USB ground loop noise that it seems unavoidable some times.

For some time I had even two Orange Pis connected to two sections of my gear, using USB gadget support so my MPC One could speak rtpmidi. MPC One has support to connect as host to MIDI devices, but as guest (connect to the computer) only in controlled mode which is not what I needed to convert my MIDI tracks to my DAW.

[1] https://github.com/davidmoreno/rtpmidid

My hope is that they finish the MIDI 2.0 rtpmidi protocol, and that starts to be truly used in real hardware, not half used as current rtpmidi.

This would allow easy connectivity with very low latency over normal LAN, including switches, power over Ethernet...

Disclaimer: I created a rtpmidi implementation for linux https://github.com/davidmoreno/rtpmidid

I've been using rtp-midi, using rtpmidid and it's working fine.

I'm trying to figure out how to use rtpmidid by David Moreno with my iConnectivity Mio XL. Just running rtpmidid makes all ports show up in Carla and in Reaper, but no MIDI seems to be sent. In Bitwig i can't even see the ports. Maybe because it uses jackmidi and rtpmidid uses alsamidi?