StudioPrivate beta

One scene. Millions of variations.

Studio is the first app on the Physicl platform. Describe the scene your model is missing, choose what changes, and every frame comes back with its ground truth.

How a run goes

From a prompt
to a dataset.

01

Describe the scene

A warehouse aisle, a stockroom, a child's bedroom with the floor covered. You describe the space your model works in and Studio finds it in the catalogue.

02

Choose what varies

Clutter, layout, light, camera path. You name the axis your model is weak on and Studio holds everything else still.

03

Pick the ground truth

Chosen once, then written onto every frame of every run. Nothing is estimated afterwards because the scene is built before it is photographed.

04

Approve the run

Resolution, samples, stride and how many runs. Studio shows the full run and how long it will take before anything renders.

05

Take the output

One folder per run in the bucket you connected. The frames, the layers beside them, the camera for each one, and a record of which axes were turned and to what.

A child’s bedroom, toys across the floor. Our home robot misses small objects down there.
Found it. Low furniture, open floor, one window. This is the room before anything is changed.
Which axis should vary? Whatever you leave out is held still.
Clutter density, and where things sit. Keep the furniture and the light where they are.
Clutter density sparse to covered Object placement reshuffled each run Camera path held on one route
Two axes turning, the rest fixed, so every run is comparable.
Which ground truth do you want on every frame?
Depth metres, EXR Surface normals RGB Segmentation + instance IDs Camera pose per frame 2D boxes + classes
600 runs of this room.
Batch queued · 600 runs · 5 passes per frame
Run 121080p · 24 fps
Rendered frame of the bedroom
Frame
Depth pass of the same frame
Depth
Surface normals of the same frame
Normals
Instance segmentation of the same frame
Instances
The same frame with a labelled box around every object
Boxes
Rendering 600 clips0 / 600Placement
The library

10,000+ scenes. 100,000+ objects.
Growing every day.

Warehouses, hospitals, labs, shops and offices, curated by people. New scenes land every day, and every Studio user gets the whole library.

Loading yardWarehousing
Freight depotLogistics
Industrial plantIndustrial
Car garageAutomotive
Hotel lobbyHospitality
LaboratoryScience
Hospital wardMedical
ClassroomEducation
Event receptionPublic
Control roomSecurity
GymSport
BakeryRetail
CafeFood service
LibraryCulture
OfficeWorkplace
What teams use it for

Six jobs from one batch.

One run can serve several of these at once, because every layer is written onto the same frames.

01

Detection and instance segmentation

Boxes and masks come off the geometry. A rare arrangement costs one render, at the same label quality as a common one.

Segmentation · Instance IDs · Boxes
02

Monocular metric depth

Depth in metres on every pixel, written by the renderer, dense all the way to the edges of the frame.

Depth · Metres · EXR
03

Surface normal estimation

One orientation per pixel, taken from the geometry and registered to the frame it belongs to.

Normals · Camera pose
04

Feed-forward reconstruction

Models that predict geometry straight from images train on pose and dense depth together, the pairing real capture is least likely to hand over.

Camera pose · Depth · Beauty
05

Robustness evaluation

Hold the room still, move one axis, and read the point where the score falls off.

Permutations · The axes, recorded
06

Spatial reasoning

Distances and sizes a model can be questioned on, read off the scene rather than estimated from the picture afterwards.

Depth · Instance IDs · Camera pose
The run

Every setting on the run
is yours.

01Resolution and samples Set per run, so a quick look and a training batch are not the same job.
02Passes Beauty, depth, surface normals, segmentation and 2D boxes, chosen per run.
03Stride How often along the trajectory a frame is written out.
04Permutations Declared axes with controlled randomness, so one scene yields many runs.
05Annotations COCO shaped and documented, with any delta from the standard stated.

Try it on the room your model gets wrong.

Studio is open to a small group of researchers and design partners.

Questions

About Studio.

What is synthetic training data for computer vision?

Synthetic training data is imagery rendered from 3D geometry, which means the labels come out of the scene instead of out of a labelling queue. Every frame Studio renders carries depth in metres, surface normals, instance segmentation, 2D boxes and the camera pose, all read off the geometry as the frame is drawn.

How do you generate training data without a 3D artist?

You describe the scene in words. Studio finds the scene, you choose which axes vary, and you approve the run before anything renders. There is no 3D software to open, no scene to assemble and no modelling step.

What ground truth comes with each rendered frame?

Five passes and a pose on every frame. The beauty pass is the colour image a model would see as a photograph. Depth gives distance in metres at every pixel. Surface normals give the direction each surface faces. Instance segmentation gives every object its own ID, and 2D boxes come with a class each. Camera pose is written per frame, and annotations are COCO shaped.

Is rendered training data the same as simulation?

No. Simulation runs physics forward in time. Rendering turns a 3D scene into images. Studio renders, which is why depth, normals and instance IDs are exact rather than predicted.

What if the scene I need is not in the library?

Say so in your access request, with the space you need.

How do I get access to Physicl Studio?

Studio is in private beta. Request access and tell us what you are training.