Synthetic Data Generation for Computer Vision

Labeling 10,000 images with polygon masks takes months of annotator work and significant expense. Yet the real problem is that a client has 400 labeled photos of defects on a conveyor belt, and a YOLOv8 model trained on this volume achieves [email protected] = 0.51. Synthetic data is not a replacement for real data—it is a tool that bridges this gap without hiring an army of labelers. Our experience shows that a properly designed synthetic generation pipeline increases mAP by 30–50% compared to training only on real data. Labeling cost savings reach 80%, which in a typical project translates to savings of $10,000–$50,000 depending on volume.

More about the concept can be read on Wikipedia.

Generation Methods Overview

How to Choose a Synthetic Data Generation Method?

3D rendering yields more predictable labeling quality than GANs but requires 2–3 times more preparation time. Copy-paste augmentation is 10x cheaper than manual labeling for the same volume.

When Synthetic Data Really Helps and When It Doesn't

Three scenarios where synthetic data provides measurable improvement:

• Class imbalance. On a production line, a rare defect occurs once in 5,000 units. Recall for this class is 0.23. Generating 2,000 synthetic instances via copy-paste augmentation on real backgrounds raises recall to 0.71 without changing the architecture.

• Privacy constraints. Medical images, documents, faces—real data either cannot be used outside a secure environment or the volume is clinically insufficient. GAN or diffusion generation with distribution preservation is a workable solution.

• New task without historical data. The warehouse hasn't been built yet, the robot hasn't been purchased, but the model is needed at launch. Rendering 3D scenes in Blender/NVIDIA Omniverse delivers a pre-trained model ahead of time.

Synthetic data does not help if the domain gap is too large—a model trained on renders will fail on real photos without domain adaptation.

What Tools Are Used for Generation?

3D Rendering

NVIDIA Omniverse Replicator is the most mature tool for CV synthetic data. It allows generating images with automatic labeling: bounding boxes, segmentation masks, depth maps, normal maps—all from a single pipeline. Randomization of materials, lighting, and camera position is built-in. According to the official documentation, generating a scene with 10,000 objects takes 2 days.

import omni.replicator.core as rep

with rep.new_layer():
    # Randomize object position
    cube = rep.create.cube(semantics=[("class", "defect")])
    with rep.trigger.on_frame(num_frames=5000):
        with cube:
            rep.modify.pose(
                position=rep.distribution.uniform((-50, 0, -50), (50, 0, 50)),
                rotation=rep.distribution.uniform((0, -180, 0), (0, 180, 0))
            )
        rep.randomizer.lights()

Blender + Python scripting is a more flexible option for custom scenes. Basic knowledge of the Blender API and a batch rendering script suffice.

GAN and Diffusion Models

Stable Diffusion with ControlNet generates photorealistic images from masks or skeletons. For CV tasks, it is relevant: provide a defect mask, and get texture and lighting variations on that mask.

StyleGAN3 works well for faces and medical images with controlled variability. FID (Fréchet Inception Distance) < 10 is achieved on datasets from 10,000 real samples.

Pix2Pix / CycleGAN perform domain transfer: from synthetic to realistic images. This helps close the domain gap without re-labeling.

Copy-paste Augmentation

The cheapest method for detection—cut a real object and paste it onto different backgrounds. Use the albumentations library with CopyPasteAugmentation or a custom script. With proper blending (Gaussian blur on edges, lighting alignment), mAP gain is 5–15% without any new labeling.

Why Validation on Real Data Is Critical?

The main mistake is to mix synthetic data into validation/test sets. Model evaluation should be done only on real data. Otherwise, metrics look good but the model fails in production.

Metrics for evaluating synthetic quality:

• FID — distribution closeness between synthetic and real data (< 30 is acceptable)
• KID (Kernel Inception Distance) — more robust on small samples
• Transfer via model: train on synthetic, test on real—this is the only honest test

Common pitfalls and how to avoid them:

• Using identical backgrounds — the model overfits to floor texture. Solution: randomize background (HDRI maps, random images).
• Ignoring light physics — shadows and reflections don't match reality. Solution: use path tracing or HDR environment.
• Generating only perfect samples — the model doesn't see capture defects (blur, noise). Solution: add realistic noise and blur.

How Much Synthetic Data Is Needed?

In practice, adding 5–10 thousand synthetic images to 500 real ones often increases mAP by 10–15%. For rare classes, up to 20 thousand may be required. Do not mix synthetic data into validation.

Case Study: Glass Defect Detection

Our client is an automotive glass manufacturer. The defectoscopy task: detection of scratches, chips, bubbles, inclusions, cracks, and cloudiness. Initial dataset: 380 real images labeled with bounding boxes. Classes are highly imbalanced — the "inclusion" class has only 23 instances.

Initial model: YOLOv8m with COCO pretrained weights. Result after fine-tuning on the real dataset: [email protected]:0.95 = 0.38, recall for "inclusion" class = 0.19.

Solution:

1. 3D modeling of defects in Blender: an industrial designer created 12 high-detail models (chips, cracks, bubbles) with different materials and textures.
2. Rendered 8,000 images with randomization: 3 lighting types (top, side, backlight), 5 camera angles, random position on the conveyor belt. Used Cycles engine for photorealism.
3. Copy-paste for rare classes: cut real inclusions from 20 original photos, pasted onto 3,000 synthetic backgrounds with Gaussian blur and color correction.
4. Domain adaptation via CycleGAN: translated the style of renders into the style of real line photos (custom dataset of 200 real frames). This reduced FID from 45 to 22.
5. Final dataset: 380 real + 11,000 synthetic. Split 80/10/10 only on real data for val/test.

YOLOv8m hyperparameters:

• batch size = 16, imgsz = 640, optimizer = AdamW (lr=1e-3)
• mosaic augmentation, mixup (0.2), copy-paste (0.5)
• early stopping patience = 10 epochs, max epochs = 100
• trained on single NVIDIA A100 (80 GB) — training took 4.5 hours

Results on real test set:

Savings: the cost of synthetic generation (server time + designer) was several times lower than manual labeling of 11,000 images, reducing the dataset preparation budget by an estimated $20,000.

What's Included

• Initial data audit and problem statement
• Optimal generation method selection (3D rendering / GAN / copy-paste)
• Pipeline development with automatic labeling
• Domain adaptation to reduce domain gap
• Quality validation on real data
• Integration into your MLOps pipeline
• Documentation and team training

Timeline

Cost is calculated individually based on volume and complexity. Our experience: 5+ years in Computer Vision, 20+ projects in synthetic data. We guarantee transparent reporting and post-implementation support.

Get a consultation for your project — we will help select the optimal generation method and estimate timelines. Contact us to assess your task. We will prepare a commercial proposal within one business day.