next-plausible VS rtpmidid

These are the things I've created, some mostly for my own use, and others just for fun:

1. https://gptgames.io - A gaming platform using OpenAI. It came from a silly idea for another project I have, and I ended up putting it together in 1 month.

2. https://creepyface.io - I wanted to animate my face on my resume, and I decided to allow everyone else to do the same.

3. https://react-guitar.com - I wanted to learn guitar theory and tell me a better way to do it than coding a react component :D

4. https://github.com/4lejandrito/fetchbook - I wanted to organize my http requests at work without depending on postman or anything else.

5. https://github.com/4lejandrito/next-plausible - Since I started using Plausible analytics on all my sites, I found the need of reusing some code.

I hope you find any of these interesting!

4lejandrito has made a great tool to connect your Plausible analytics to NextJS.

You can learn more about next-plausible in the related docs.

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?