engineering
Why I Built BasebandExpert
An engineering story about turning hard-to-explain professional media behavior into controlled signals, visible state, and useful evidence.
So over the years, I've used baseband products from many product vendors: Evertz, Leader, Phabrix, Tektronix, Dektec, to just name a few. I've always experienced a few common themes:
- These products can be ridiculously expensive, as they're sold in low volume and designed for companies that can afford them.
- Often they have a complex licensing scheme where the base functionality is available at a fixed price, and then there is a huge menu of a la carte features for additional money.
- Sometimes I kept finding myself saying, "This is almost what I want, but I need this one minor feature to make it work for my use case, and I can't simply add that to the product." The feature isn't important enough and/or I don't have enough influence to get the vendor to add the feature.
Now when I have worked in broadcast, the price isn't always the issue. But as a lowly engineer just trying to get his job done, when I need some additional feature then the mechanics of reaching out to Sales, getting a quote, getting approval from my manager, talking to my finance department to get a purchase order issued, and placing the order can be a massive headache. And at each stage I have to justify "why" the item is needed...
I'll admit it: I'm a video nerd. I've spent years building such solutions for in-house applications at different jobs. And I'm a sucker for standards, testing tools, deep protocol analysis, and validation methodology.
BasebandExpert is all about democratizing access to such technology. Let's build first-class applications that compete with the "big boys", but make them available at prices that are either free or cheap enough that you can put it on your credit card and not break the bank.
Do these solutions provide the same hardware level features that some products do? Nope. You won't able to get physical layer eye diagrams and jitter analysis. But in my experience, that's the 5% use case. Everything else can be accomplished with commodity capture/generation hardware running on commodity workstations.