I like this. This reminds me a lot of GStreamer. If you are not familiar with it, it is a decades-old media platform that is still used extensively today in ev

I like this. This reminds me a lot of GStreamer. If you are not familiar with it, it is a decades-old media platform that is still used extensively today in everything from DVD / Music players to deep learning on NVIDIA and Intel hardware. It's a swiss army knife of time-based media. It has this really cool concept where elements can connect together in directed acyclic graphs to create amazingly complex pipelines that are all synchronized and buffered. Like connecting an "RTSP source to an mp4decoder to an image resizer to JPEG images" as a trivial example. Each pad defines a format it speaks (like RGB or YUV) called capabilities, and then GStreamer matches up the pad capabilities transparently to the user. There's no need to explicitly tell the pipeline manager how to connect the two pads, it will automatically pick a shared capability. Of course, the can be forced explicitly, but it doesn't need to be. I wonder if executables that are pipe-friendly could expose formats in much the same way GStreamer pads do instead of your ".typed" properties file. It wouldn't require explicitly coercing the pipe, but it wouldn't be a type, it would be more flexible...