A virtual camera is the thing that makes CG camera work stop looking like CG camera work. Hand-keyed camera moves are smooth in a way real operators are not; the small corrections, overshoots and weight of a person holding a camera are hard to fake and instantly readable when missing.
PocketCam is a Blender add-on that uses a phone as that camera.
How the tracking is split
The interesting engineering choice is that PocketCam does not use one sensor for everything. It uses a custom-built 6DoF tracker that divides the problem:
- Rotation comes from the gyroscope — every turn and tilt.
- Translation comes from the camera, following the operator as they move through the room.
That split matches what each sensor is actually good at. A gyro gives fast, low-latency angular rates but drifts and cannot tell you that you have walked three metres. Visual tracking gives real positional change but is slower and struggles with fast rotation, when the image smears. Using each for the axis it handles well is the standard approach in inside-out tracking, and doing it without any dedicated hardware is the point here.
In practice that means you can crouch for a low angle, crane up, and orbit a subject, and the result records to the timeline with real handheld motion rather than a smoothed approximation of it.
The viewfinder matters more than it sounds
PocketCam streams Blender’s render of the camera’s view back to the phone, live, while shooting.
Without that you are not operating a camera, you are waving a phone and watching a monitor. Framing is the entire job of a camera operator, and framing requires seeing the frame in the thing you are pointing. A live viewfinder on the device in your hands is what converts the add-on from a motion-capture gimmick into something you can actually shoot with.
It also exposes real lens focal lengths, from 14 mm to 135 mm, so the operator is choosing a lens rather than a numeric field-of-view value.
What to check before buying
It is a paid add-on — BlenderNation flags it as commercial, and we are not quoting a figure we have not confirmed on the vendor’s own checkout.
The specific things worth establishing for your setup, none of which are answered by the feature list:
- What the camera-based translation needs from the room. Visual tracking wants texture and light. A bare studio wall or a dark room is the failure case for this class of tracker, and the demos are shot in furnished spaces.
- Phone-to-Blender transport and latency. Streaming the viewport to a phone and motion back implies a network path; how much lag sits between a movement and the viewfinder updating determines whether you can frame on action.
- Whether the recorded curve is editable. Handheld motion is desirable; handheld motion you cannot subsequently smooth, retime or trim is a liability.
Where it sits
The existing options are a tracked VR controller or headset driving a camera, a commercial virtual-production app with a subscription, or keyframing by hand. PocketCam’s pitch is that the hardware requirement is a phone you own, and the tracking is built rather than borrowed from an AR framework.
For anyone making animation, product shots or environment flythroughs in Blender alone, that is a short path to camera work that reads as photographed.
Sources
- PocketCam: Virtual Camera for Blender — BlenderNation
- PocketCam: Virtual Camera for Blender — Lewis Martin (YouTube)
- Blender add-on documentation