Audio2Face-3D#
Getting Started
Architecture
Interacting with Audio2Face-3D
Deployment
- Audio2Face-3D NIM Container Deployment and Configuration Guide
- Prerequisites
- Configuration files
- Configuration Usage
- Model Cache Management
- Launching A2F-3D NIM with Custom Entrypoint
- Streamlined Configuration Updates
- Flexible Configuration Management
- Advanced Stylization
- Configuration files for Unreal Engine Metahuman
- Parameter Tuning Guide
- Environment variables
- Volumes
- Quick Deployment of Audio2Face-3D Microservices
- TLS Support
- One Click Deployment
- Kubernetes Deployment
Notes and changelog
- Support Matrix
- Migration Guide
- Sharing Audio2Face-3D Compute Resources
- Network Customization and Accessibility
- Glossary of Terms
- Security
- Release Notes
- Troubleshooting
- Known issues
- Lip Sync Issues with Burst Mode (Tokkio)
- Q&A
- Reducing VRAM Usage for Edge Deployments
- gRPC Response Status Code
- Audio2Face-3D NIM Public API
- GPU Device ID Mismatch Warning (nim_list_model_profiles)
- TensorRT Engine Build Fails for Diffusion Models (Insufficient Memory)
- CUDA Error 802 “system not yet initialized” on B200 Multi-GPU Systems
- Sample Scripts Fail with “Connection refused” Traceback
- Invalid Model Name Silently Falls Back to Default (james_v2.3.1)
- Cached TRT Engines Don’t Match Requested Model
- NIM Fails When Using a Profile for a Different GPU
- Permission Denied on Cache Directory (/tmp/a2x)
- CUDA Error: No CUDA-Capable Device Detected
- Stopping and Restarting the A2F Server
- Kubernetes Pod Stuck in Pending Status
kubectlConnection Refused on localhost:8080- MicroK8s Fails to Start (Containerd Config Version Mismatch)
- Snap Tools Fail with “Home Directories Outside of /home”
- Kubernetes Pod Fails with “CUDA-capable device(s) is/are busy or unavailable”