rtpmidid VS motion

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?

https://github.com/trypromptly/LLMStack - started working on this as a wrapper over OpenAI's endpoints for another product and it gradually became this.

Another project I worked on for my own use was a network isolated, lightweight video monitoring system. Around 5 years ago, I was looking to install a camera in our living room. I couldn't find anything I trusted that worked completely offline without some companion app pinging their servers. So I bought a basic IP camera on Amazon that supports rtsp and a raspberry pi. Created a fenced wifi network and added the camera to it.

Had an FFmpeg process read camera stream on demand and write to local buffers. Wrote a simple python server to listen for incoming connections on a different interface and stream the video on API requests. Then built an android app that talks to the python server to stream video on demand.

Also installed motion (https://github.com/Motion-Project/motion) on raspberry pi to detect motion in the video and store those snippets to local storage. With motion running, the adapter I was using wasn't delivering enough power resulting in storage occasionally unmounting and raspberry pi restarting taking the camera system offline. With motion detection disabled, the entire setup ran reliably for many years.

We used https://github.com/Motion-Project/motion for crude version of that in our office closet datacenter.

It just detected movement, sent an email with video file attached and a link to stream.

No face detect AI but this is ancient software, and minimum effort to set up

MotionEyeOS

I had a similar setup to see what my pet hedgehog was getting up to at night and I used motion to do motion detection on the stream and save videos when it happened. I think you can also set a script to run whenever motion is detected. Might be worth looking into.

I use Motion for my security camera... it only records motion if you want it to: https://github.com/Motion-Project/motion...

apt-get install ffmpeg libmariadb3 libpq5 libmicrohttpd12 wget https://github.com/Motion-Project/motion/releases/download/release-4.3.2/buster_motion_4.3.2-1_arm64.deb dpkg -i buster_motion_4.3.2-1_arm64.deb

You might consider Motion. It's reliable and uses little resources. It comes with a browser UI.