Instructions to use Viggle/Meridian with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Diffusers
How to use Viggle/Meridian with Diffusers:
pip install -U diffusers transformers accelerate
import torch from diffusers import DiffusionPipeline # switch to "mps" for apple devices pipe = DiffusionPipeline.from_pretrained("Viggle/Meridian", dtype=torch.bfloat16, device_map="cuda") prompt = "Astronaut in a jungle, cold color palette, muted colors, detailed, 8k" image = pipe(prompt).images[0] - Notebooks
- Google Colab
- Kaggle
Release preparation — internal checklist
Keep Viggle/Meridian private. Do not publish it without the user's explicit approval.
Release-facing wording does not authorize changing repository visibility.
Outstanding publication checks
- Public-use clearance, including for the NBA footage and figures, remains pending. The presentation examples are research previews; retain source credits and edit records before choosing publication assets.
- Confirm and upload the intended transformer and LoRA weights before calling the model download complete.
The old
Viggle/Viggle-Recamidentifier was inaccessible during verification; do not restore it as a working download. - Low-memory configurations, including RTX 4090, are community integration targets, not validated support.
- Fast point-cloud preview helps inspect an authored path; it does not guarantee generated-view fidelity.
Presentation and review
- Replace local preview links with cleared publication assets.
- Method video strips use actual matched frames; the 3D points and camera path are explicitly schematic. Retain this distinction and the source provenance.
- Studio overview is recorded and preview-only; capture and review a matching generated take before extending it to demonstrate final generation.
- Complete continuous visual motion review; automated playback and sampled frames are not sufficient.
- Retain exact camera controls if presenting an isolated space/time ablation.
- Confirm permission to use every source clip and to publish the corresponding demonstrations.
- Keep source-time labels accurate when comparing live, retimed, and held sequences.
- Verify the reported timing against a retained run log before publishing it as a headline result.
- Do not add a speedup ratio, quality comparison, ablation, or metric without supporting results.
- Hub destination: Viggle/Meridian (private). Do not point weight-download commands here until the weights are present.
- Upload referenced presentation media with the Markdown; keep the private Hub snapshot separate from public-use clearance. The legacy push_docs.py targets a different repository.