What is your role at Pixlo and what does your company do?
I’m the Chief Technology Officer at Pixlo AB. I’m responsible for all technical decisions, including infrastructure, workflows, and tool selection. We deliver a wide range of video content to multiple partners—each with unique technical specifications—so we need a flexible and robust environment that lets us scale delivery while maintaining quality.
How did you first come across Capella and Cambria FTC?
I’ve known the Capella team since their Rhozet days, so I was already confident in their technical expertise and product quality. When we began evaluating new transcoding solutions, Capella was a natural inclusion. We were looking for something high-performance, easy to license, and backed by real support—not a generic ticketing system.
What were the key factors that influenced your decision?
There were a few standout drivers:
- First, quality and format support. We handle everything from ProRes and XAVC to XDCAM and some H.264 delivery, so we needed a platform that could meet all our professional-grade requirements without limitations.
- Second, licensing simplicity. We didn’t want a usage-based or convoluted model—we needed clarity. Capella’s per-machine license with an upfront and annual fee was exactly what we were looking for.
- But perhaps most importantly, support. When something breaks, we don’t need Tier 1 agents asking if we’ve restarted our systems. We need fast, qualified answers from people who understand media workflows. Capella delivers that—every time.
How does Cambria FTC fit into your media processing workflows?
We use Cambria FTC for the majority of our transcoding needs. It’s fully integrated into our infrastructure and handles both intermediate and delivery formats. Compared to previous tools we’ve used—especially those requiring FFMpeg-level config knowledge—Cambria allows our operators to work more independently, which frees up engineering time and speeds up delivery.
What was the onboarding and learning experience like?
The user interface was intuitive, and the API integration was smooth. We work dynamically with configurations—adjusting things like audio layouts and cut points on the fly—and Cambria’s XML-based profiles made that very straightforward to automate. Even complex tasks are easy to manage once the system is up and running.
Has Cambria FTC had a measurable impact on your workflows?
Yes—significantly. It’s allowed us to streamline operations, reduce dependencies on engineering, and increase the flexibility of our delivery workflows. Tasks that previously required technical intervention are now handled by operations staff. That’s not just time saved—it’s cost saved and risk reduced.
Were cost or licensing structure major factors in your decision?
Licensing wasn’t the main driver, but it certainly helped. A clear, fixed license model makes forecasting easy and eliminates the unpredictable costs that come with usage-based pricing. For a company like ours—where delivery volumes can spike depending on customer needs—that kind of predictability is essential.
Has the product lived up to your expectations?
Absolutely. We did a deep technical evaluation before adopting Cambria, and since then it’s met or exceeded expectations consistently. Performance is stable, integration is smooth, and support has been excellent. It just works—and that’s rare in this space.
