LTX-2 19B
lightricks/ltx-2-19b/audio-to-video/loraLtx 2 19b Audio To Video Lora by Lightricks - advanced AI model for audio-to-video. Delivers high-quality results with fast inference, suitable for both creative and production workflows.
- Base price
- $0.002USD / run
- Execution
- async
- Model type
- video
- Input fields
- 12
Try the model
Playground
PNG, JPEG, WebP, or GIF · 20 MiB maximum
PNG, JPEG, WebP, or GIF · 20 MiB maximum
Your output will appear here
Complete the inputs, then click Run.
Model card
Specifications
Pricing
- Base price
- $0.002 / run
Context & modalities
- Input
- Schema-defined
- Output
- video
Capabilities
- Chat
- Not supported
- Vision
- Not supported
- Reasoning
- Not supported
- Structured output
- Not supported
- Function calling
- Not supported
- Audio input
- Not supported
Access
- Provider
- Lightricks
- Model ID
- lightricks/ltx-2-19b/audio-to-video/lora
- Execution
- async
- Base URL
- https://api.sandbase.ai
- API
- Unified Run API
- Endpoint
- /v1/run
API README
LTX-2 19B
LTX-2 19B is a audio-guided video creation with custom LoRA adapters endpoint in the LTX 2 19B family. It is built for creators who need to turn a concrete creative brief into a controlled visual sequence: the request establishes the source material, the intended subject behavior, the camera language, and the atmosphere of the finished shot. The LoRA-enabled route keeps that workflow explicit instead of hiding its input assumptions behind a generic video-generation label.
In practice, this route accepts image, audio, end image, loras as creative context and exposes image strength for delivery planning. That makes it suitable for shot-based pipelines where teams must preserve a source, direct a transformation, or control the final format without losing sight of the model's central task. Write prompts as a compact shot plan—subject, action, setting, camera, light, and timing—then use the structured fields for constraints that should remain deterministic across iterations.
Highlights
- Soundtrack-led performance. The
audioinput supplies timing and performance cues, while the prompt explains what should happen visually. - Anchored opening composition. A required opening
imageestablishes the subject and first-frame composition before motion follows the soundtrack. - Audio influence control.
audio_strengthis available on this route where documented, letting a request tune adherence to the supplied sound rather than changing the prompt. - Route-specific LoRA conditioning. The
lorasarray adds learned styling or concepts to this audio to video workflow without replacing its required source inputs. Forlightricks/ltx-2-19b/audio-to-video/lora, this task-specific control is documented alongside the route’s own required inputs.
Pricing
| Billing unit | Price |
|---|---|
| Base request | $0.002000 |
When to Use
| Scenario | Recommendation |
|---|---|
| Choose this route | Use it when the deliverable specifically calls for audio-guided video creation with custom LoRA adapters, rather than a neighboring generation mode. |
| Prepare the source | Provide image, audio in the format described by the request schema. |
| Direct the shot | Describe the subject, action, environment, camera movement, lighting, and temporal progression in that order. |
| Control continuity | Use endpoint frames, reference media, strength, or audio controls when those fields are available instead of burying hard constraints in prose. |
| Plan delivery | Set duration, frame count, resolution, and aspect ratio explicitly when the schema exposes them, then compare iterations with a stable seed where supported. |
Prompt Guide
For audio-guided video creation with custom LoRA adapters, describe one coherent shot rather than a list of visual keywords. Put the main subject and action first, follow with location and staging, then add camera movement, lens or framing, lighting, mood, and any timed change. Keep URLs and hard delivery choices in their dedicated fields.
{
"prompt": "A woman speaks to the camera",
"image": "https://static.sandbase.ai/examples/lightricks/ltx-2-19b/audio-to-video/lora/input_image_0.png",
"audio": "https://static.sandbase.ai/examples/lightricks/ltx-2-19b/audio-to-video/lora/input_audio_1.mp3",
"end_image": "https://example.com/reference.jpg"
}
Technical Specs
| Specification | Value |
|---|---|
| Model ID | lightricks/ltx-2-19b/audio-to-video/lora |
| Required inputs | prompt, image |
| Execution | Asynchronous generation job |
| Request controls | 12 documented fields |
| Output | url, content_type |
Request fields
| Field | Type and constraints |
|---|---|
seed | integer; Optional |
audio | string; Optional |
image | string; Required |
loras | array; Optional |
prompt | string; Required |
end_image | string; Optional |
audio_strength | number; Optional; Range: 0–1; Default: 1 |
guidance_scale | number; Optional; Range: 1–10; Default: 3 |
image_strength | number; Optional; Range: 0–1; Default: 1 |
preprocess_audio | boolean; Optional; Default: true |
end_image_strength | number; Optional; Range: 0–1; Default: 1 |
num_inference_steps | integer; Optional; Range: 8–50; Default: 40 |
Related Models
Start building
Send your first request
OpenAI-compatible endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/run" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"model": "lightricks/ltx-2-19b/audio-to-video/lora",
"audio": "https://static.sandbase.ai/examples/lightricks/ltx-2-19b/audio-to-video/lora/input_audio_1.mp3",
"image": "https://static.sandbase.ai/examples/lightricks/ltx-2-19b/audio-to-video/lora/input_image_0.png",
"prompt": "A woman speaks to the camera",
"audio_strength": 1,
"guidance_scale": 3,
"image_strength": 1,
"preprocess_audio": true,
"end_image_strength": 1,
"num_inference_steps": 40
}
SANDBASE_JSON
)
run_id=$(printf '%s' "$result" | jq -r .id)
for attempt in $(seq 1 120); do
status=$(printf '%s' "$result" | jq -r .status)
case "$status" in completed|failed|timeout) break ;; esac
sleep 2
result=$(curl --fail-with-body --silent \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
"https://api.sandbase.ai/v1/run/$run_id")
done
status=$(printf '%s' "$result" | jq -r .status)
[ "$status" = completed ] || { echo "Generation ended: $status" >&2; exit 1; }
printf '%s\n' "$result"Choose your model
Compare models
| Model | Type | Default price | Released |
|---|---|---|---|
LTX-2 19BThis model Lightricks | Video | $0.00 / run | Jan 27, 2026 |
Lightricks | Video | $0.36 / run | Mar 5, 2026 |
Lightricks | Video | $0.36 / run | Mar 5, 2026 |
Lightricks | Video | $0.48 / run | Mar 5, 2026 |
Lightricks | Video | $0.48 / run | Mar 5, 2026 |
Lightricks | Video | $0.50 / run | Mar 5, 2026 |
Questions
FAQ
How do I call Lightricks LTX-2 19B through SandBase?
Create a SandBase API key, then send requests with the model ID "lightricks/ltx-2-19b/audio-to-video/lora" to Unified Run API (/v1/run) at https://api.sandbase.ai. The request examples on this page show the exact payload.
Do I need a separate Lightricks account?
No. One SandBase API key and balance gives you access to Lightricks LTX-2 19B and the other models in the catalog; you do not need to sign up with Lightricks separately.
