About Ray
The person behind FFmpeg Commander — why this exists, and how it got built.
Ray Miecznik — data engineer, tool builder, and the one person behind FFmpeg Commander. Based in Snohomish, WA.
I've been building tools and wrangling data for over 20 years. Data engineering, automation, statistics — that's been my day job, and honestly it bleeds into everything I do. When I run into a problem I can't solve with what's already out there, I build something.
FFmpeg Commander started exactly that way.
Why I Built It
I'd been using FFmpeg for a few years — it's genuinely one of the most powerful pieces of software ever written. If you're into video, you already know it. If you're not, you've probably never heard of it — well, now you have. But every time I needed to do something with it, I was back at the command line, digging through documentation, my saved commands, rebuilding the same commands I'd built a dozen times before - that got old pretty fast. Every tool that claimed to wrap FFmpeg was either abandoned, half-baked, or buried in a subscription model. Nothing felt like it was made for someone who actually uses this stuff regularly.
So I built my own.
How It Started
The first version showed up on KodiakBrewing.com — a blog I've been running since 2009. It started as a beta idea, something I was tinkering with and sharing informally. The response was good enough that it felt worth doing properly, with its own home. That's how ffmpegcommander.com happened. If you see a referrer link from there, that's why.
A Note on AI-Assisted Development
Yes, I used AI assistance during development. I'm not going to pretend otherwise — nobody building serious software in 2026 should be.
Here's my honest take: the AI models that exist today were trained on more code than any single developer could read in a lifetime. They catch edge cases I'd miss, suggest implementations I wouldn't think of at 11pm, and dramatically compress the time between "I need this feature" and "this feature works." Pretending that's not useful would be like refusing to use a compiler because "real programmers write machine code."
Every feature in FFmpeg Commander exists because I needed it. Every design decision reflects how I actually use the tool. The AI helped me build it faster and with fewer bugs — it didn't tell me what to build or why. That's the right way to use it.
How It Runs
One person built it
I use FFmpeg Commander myself, every week. When something breaks or feels clunky, I notice immediately — and I fix it.
One person answers your questions
There's no support team, no ticket queue. You email me directly and I respond personally, usually the same day.
One person maintains it
Updates ship when something needs fixing or a feature is worth adding. No marketing calendar, no artificial release schedule.
That's the whole operation.
Ready to try it? One-time purchase, no subscription, yours to keep.
Get FFmpeg Commander →FFmpeg Commander Video Toolbox — 2026