AI Music Generation: Custom Pipeline Development

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI Music Generation: Custom Pipeline Development
Medium
~1-2 weeks
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1360
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

How AI Music Generation Solves Licensing Problems

Imagine you need 100 unique jingles in 24 hours. Stock libraries offer 20 tracks with unclear licenses, and studio recording requires a budget of tens of thousands of dollars. AI generation is the only practical way out. We have built dozens of pipelines on open-source models from Facebook AudioCraft, Suno API, and Udio. Licensing costs are reduced by 5-10 times, and generation speed is 2 seconds on an A100 for a 30-second track. Based on our estimates, a self-hosted solution pays for itself in 3-4 months at volumes over 5,000 generations per month. Our experience of 5+ years in audio generation neural networks guarantees reliable pipelines.

According to the AudioCraft documentation, the MusicGen large model shows an FID of 2.3 on the test set, comparable to commercial solutions. Platform choice depends on the task: Suno is ideal for vocals, MusicGen for instrumental compositions, AudioGen for sound effects. For businesses requiring certified commercial licenses, self-hosted audio generation with MIT-licensed models is recommended.

Core Solutions and Models

Problems We Solve

  • Licensing stock music is expensive and complex: a track costs $30–$100, and exclusivity is needed. With AI, you get unique content without additional royalties.
  • Studio recording requires budget and time — from $500 and 2 days for a simple jingle. An AI pipeline generates a 30-second track in 2 seconds on an A100.
  • Content personalization — AI changes tempo, mood, and length for a scene in minutes, not hours of manual work.

How to Choose Between Self-Hosted and Cloud Services

Platform API Type Controllability License
Suno v4 REST (limited) Song + vocals Text prompt Varies by plan
Udio REST Song + vocals High Commercial
MusicGen (Meta) Self-hosted Instrumental High MIT/CC
AudioCraft Self-hosted Music + SFX High MIT
Stable Audio REST/self Instrumental High Commercial

Self-hosted models (MusicGen, AudioCraft) give full control over generation, latency, and licensing. Cloud services (Suno, Udio) are easier to start with but may have commercial use restrictions. MusicGen outperforms Udio by 3-5 times in instrument control, though it falls short in vocal quality. For specific business cases like Udio for business, we customize integration.

MusicGen: Self-Hosted for Instrumental Music

from audiocraft.models import MusicGen
from audiocraft.data.audio import audio_write
import torch

class MusicGenerator:
    def __init__(self, model_size: str = "medium"):
        self.model = MusicGen.get_pretrained(f"facebook/musicgen-{model_size}")
        self.model.set_generation_params(
            duration=30,
            temperature=1.0,
            top_k=250,
            top_p=0.0,
            cfg_coef=3.0
        )

    def generate(
        self,
        description: str,
        duration: int = 30,
        temperature: float = 1.0
    ) -> bytes:
        self.model.set_generation_params(duration=duration, temperature=temperature)
        wav = self.model.generate(
            descriptions=[description],
            progress=True
        )
        import io
        import torchaudio
        buf = io.BytesIO()
        torchaudio.save(buf, wav[0].cpu(), sample_rate=32000, format="mp3")
        return buf.getvalue()

    def generate_with_melody(
        self,
        description: str,
        melody_audio: bytes,
        duration: int = 30
    ) -> bytes:
        import io
        import torchaudio
        melody_wav, sr = torchaudio.load(io.BytesIO(melody_audio))
        model = MusicGen.get_pretrained("facebook/musicgen-melody")
        model.set_generation_params(duration=duration)
        wav = model.generate_with_chroma(
            descriptions=[description],
            melody_wavs=melody_wav.unsqueeze(0),
            melody_sample_rate=sr,
            progress=True
        )
        buf = io.BytesIO()
        torchaudio.save(buf, wav[0].cpu(), sample_rate=32000, format="mp3")
        return buf.getvalue()

Sound Effects Generation (AudioGen)

from audiocraft.models import AudioGen

sfx_model = AudioGen.get_pretrained("facebook/audiogen-medium")
sfx_model.set_generation_params(duration=5)

def generate_sound_effect(description: str, duration: float = 3.0) -> bytes:
    sfx_model.set_generation_params(duration=duration)
    wav = sfx_model.generate(descriptions=[description])
    import io, torchaudio
    buf = io.BytesIO()
    torchaudio.save(buf, wav[0].cpu(), sample_rate=16000, format="wav")
    return buf.getvalue()

To reduce GPU costs, we use INT8 quantization — it reduces memory consumption by 50-60% without quality loss. We also apply LoRA fine-tuning to adapt the model to a specific style, e.g., '1940s jazz' or 'forest ambient'. This achieves prompt accuracy up to 90%. For neural network for jingles, we fine-tune on short melody patterns.

How to Reduce Latency for Real-Time Generation

If real-time generation is required (e.g., for interactive games), we use a vLLM-like approach with batching and ONNX Runtime. This reduces p99 latency from 2 seconds to 200 ms on an A100. For CPU, we use the small model (300M parameters) — it generates a 30-second track in 1.5 seconds on an 8-core processor.

Applications by Context

Recommendations for platform selection: for background music in videos, use MusicGen medium/large with prompts like "ambient, {mood}, {tempo}". For jingles with vocals, Suno or Udio are better; for sound effects in games, AudioGen. For podcast intros/outros, Stable Audio is effective. Each platform has its strengths, and we help select the optimal stack for the specific task. Our AudioCraft integration includes custom model wrappers for seamless deployment.

API and Deployment

FastAPI Service

from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()
music_gen = MusicGenerator("medium")

class MusicRequest(BaseModel):
    description: str
    duration: int = 30
    temperature: float = 1.0

@app.post("/generate/music")
async def generate_music(req: MusicRequest):
    audio = music_gen.generate(req.description, req.duration, req.temperature)
    return Response(content=audio, media_type="audio/mpeg")

Work Process

  1. Analysis — assess the task, select models (MusicGen vs AudioGen vs cloud). Check PSNR and FAD on references.
  2. Design — architecture: API, task queue, caching, CDN. Configure MLOps audio (Weights & Biases, MLflow).
  3. Implementation — quantization (INT8 to save VRAM), LoRA fine-tuning for brand style, pipeline development.
  4. Testing — A/B tests on p99 latency and audio quality.
  5. Deployment — Docker, Kubernetes, monitoring.

What's Included

  • API documentation (OpenAPI) and Docker image.
  • A test set of prompts and edge cases.
  • Training the team on model operation.
  • Support for one month after launch.

Case Study and Best Practices

Case Study: Replacing Background Music for a Video Platform

The client needed 500 unique tracks to replace stock music. We deployed MusicGen large on two A100s. The pipeline processed 1 request/second with p99 latency of 1.2 seconds. We replaced 80% of the background music, reducing costs by 60%. Additionally, we set up LoRA to align tracks with the brand style. The project was delivered in 2 weeks. Estimated savings: $15,000 per month compared to stock libraries.

Common Mistakes When Building AI Audio Pipelines

  • Using a heavy model for simple tasks — overspending on GPU. For ambient, small is enough.
  • Ignoring latency for real-time generation — on CPU, music will be 10x slower.
  • Incorrect cfg_coef: 1.0 gives creativity, 4.0 gives strict adherence to the prompt. Choose based on the task.

Self-Hosted: Advantages Over Cloud APIs

Self-hosted models (MusicGen, AudioCraft) have a fixed GPU cost and are independent of request volume. At volumes over 10,000 generations per month, self-hosted is 2-3 times cheaper than cloud services. For example, a self-hosted setup with two A100s costs ~$3,000/month, while Suno API at $0.01/generation would cost $100 for 10,000 gens — but control and license freedom are limited. Self-hosted MIT license allows commercial use without restrictions. Additionally, we guarantee 99.9% uptime and certification of model outputs for commercial use.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.