PTZ ComposerShow what your cameras can do in motion.
Smooth Operator is motion technology: software that changes how the cameras you already ship move in your customers' rooms. We work with camera product and engineering teams to evaluate physical movement on a chosen model, compare it against native control, and assess a licensing path that fits your own product experience.
What you need from us
A demonstration on your camera, not a category claim
One model, one firmware, one control arrangement, filmed on a real stage or set. A gentle move that holds its detail, a diagonal transition, a coordinated move into a final framing, repeated arrivals, and a release that settles.
A comparison your engineers can check
Your native control, configured the way your team would configure it, against ours on the same camera, scene, framing and video path. We keep every run, report the excluded ones and their reasons, and say where a measurement is not reliable.
An integration that fits your product
External software and controller integration is the near path. On-camera deployment is a separate engineering assessment, and we say so before the first meeting rather than after it.
A commercial case built from a result
A bounded evaluation first, then integration scope and deployment licensing defined around the value it demonstrated. We would rather agree the acceptance criteria with your team than open with a royalty.
A route that stays away from your sales funnel
This conversation is about the motion component. PTZ Composer, our customer-facing application, is a separate offering, and an inquiry here reaches a commercial owner rather than a purchase path.
How it works in your business
Start with your camera
Choose a model and a movement your customers ask for and do not get. We prepare the demonstration on that unit, with the native settings your product team considers its proper baseline.
Explore an integration that fits your product
Review the footage, the control arrangement and the results with our team, then decide which integration path is worth assessing: your own software, a controller path, or an on-camera assessment of its own.
Build the commercial case from the result
Begin with a focused evaluation on one model. Define integration scope and deployment licensing afterwards, against a demonstrated difference in how the camera moves.
Program terms
What an evaluation covers
One model, its firmware and an agreed control arrangement. Endpoints, durations and acceptance criteria are agreed with your technical owner before anything is scored, and a result describes that one setup, not a product line.
What we bring
The motion technology, the demonstration, the comparison record and a written claim register: each sentence we would publish, the runs behind it, its limits and its review date.
What we ask for
Access to one camera, a technical owner who can approve the next step, and the native settings your team regards as the fair baseline. We change no firmware and we do not drive the camera past its stated limits.
Licensing terms
We publish no royalty schedule. Terms follow an evaluation and a deployment shape, so the first conversation is about what the camera does and who owns the integration, not a percentage.
What this page does not claim
No manufacturer partnership, no embedded integration and no compatibility claim for a model we have not flown.
Questions
Is there a development kit we can download?
No. A download button would promise a deliverable we have not built. The first step is an evaluation on a model you choose, and an integration shape is defined from its result.
Does this compete with our own control software?
It is a motion component for the movement itself, inside the control experience you already ship. Where the discussion is about a customer-facing application, that is PTZ Composer, and it is a separate offering.
What does the evaluation need from our engineering team?
One camera, its firmware, the native configuration you consider a fair baseline, and an owner who can approve the next step. A first technical conversation is about twenty-five minutes.
Can you run this on a camera line rather than one model?
We begin with one model. A result on one body is evidence about that body, and we will not carry it across a range in a claim. Further models are qualified on their own.
Who sees our footage and our measurements?
Your team and ours. Nothing from an evaluation is published without your written agreement, and the claim register records what each published sentence is allowed to say.
How does this relate to cameras you already work with?
Our customer-facing application works with cameras that speak the control languages we support, and a Tested entry names a model, firmware, control path and recording date. A manufacturer evaluation is a separate conversation about the motion component itself.
Tell us about your business.
We answer every partner inquiry ourselves. Tell us the segments you serve and the rooms you build, and we will come back with the compatibility answer and the program terms that apply to you.