Hello hello, dear readers!
Recently at work I came across a situation where I needed to simulate video systems to understand low performance and failure modes under some network conditions.
And since nobody has time to create useful tools for work at work1, I decided to build one outside of work.
The result is Viq, a tool that simulates video traffic, integrates with Wireshark, and plots the resulting data. It is programmable and scriptable, which allows for testing multiple different simulated video patterns, and very quickly testing what different video parameters lead to in terms of video quality.
In many ways it is similar to the popular iPerf3 tool, but it’s a tad more programmable and focused on video instead of generic throughput benchmarking.
This is what it looks like, currently:
I really like how it turned out. The design is inspired by Gnome/Adwaita at places, which is a funny story in itself: initially I was planning on using GTK for the UI, but turns out, as usual, cross compiling is such a pain in the butt I decided o spin up a web-sever inside of the program and server a GUI to the browser as a simpler solution to adding a GUI. At this point what I really wanted is wxWidgets, but that is as big of a pain to compile as GTK is2.
In Other News
- Had a weird idea. A compiler for boxes? Maybe a boxpiler?.
- Lots of work no the Tinycalc project.
- Having a meh time at work as usual, except worse because everyone keeps shoving half assed AI stuff in my face.
Until next, folks! Have a good one!
-
Well, now with LLMs everyone thinks they do, but what I have noticed is actually a very permissive environment for doing pointless prototypes and dashboards while the quality of the work that matters drops further than ever. ↩︎
-
All of this is from the perspective of a Rust codebase, and Windows, Musl & ARM support. Perhaps simpler for C/pp? Or perhaps even more complicated. ↩︎