Instructions to use nvidia/Cosmos-Tokenize1-CV4x8x8-360p with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Cosmos
How to use nvidia/Cosmos-Tokenize1-CV4x8x8-360p with Cosmos:
# No code snippets available yet for this library. # To use this model, check the repository files and the library's documentation. # Want to help? PRs adding snippets are welcome at: # https://github.com/huggingface/huggingface.js
- Notebooks
- Google Colab
- Kaggle
You have been granted access to this model
Configuration Parsing Warning:Invalid JSON for config file config.json
Cosmos-Tokenize1: A suite of image and video tokenizers
Cosmos | Code | Paper | Paper Website
Model Overview
Description:
Cosmos-Tokenize1 is a suite of visual tokenizers for images and videos that delivers various compression rates while maintaining high reconstruction quality. Cosmos Tokenizer can serve as an effective and efficient building block in both diffusion-based and autoregressive models for image and video generation. The models are ready for commercial use.
Our tokenizers come in two types: Continuous (C) and Discrete (D), each with Image (I) and Video (V) variants:
- Continuous tokenizers encode visual data into continuous latent embeddings, as shown in latent diffusion models like Stable Diffusion. These embeddings are suitable for models that generate data by sampling from continuous distributions.
- Discrete tokenizers encode visual data into discrete latent codes, mapping them into quantized indices, as seen in autoregressive transformers such as VideoPoet. This discretization is required for models that generate data by optimizing the cross-entropy loss, such as the GPT models.
| Continuous ( C ) | Discrete ( D ) | |
|---|---|---|
| Images ( I ) | Cosmos-Tokenize1-CI | Cosmos-Tokenize1-DI |
| Videos ( V ) | Cosmos-Tokenize1-CV | Cosmos-Tokenize1-DV |
Model: Cosmos-Tokenize1-CV4x8x8-360p, a continuous video tokenizer with 4x temporal and 8x8 spatial compression rates.
Model Developer: NVIDIA
Model Versions
The Cosmos-Tokenize1 includes the following tokenizers:
Continuous Tokenizers
- Cosmos-Tokenize1-CI8x8-360p (8x8 spatial compression, 360p and above)
- Cosmos-Tokenize1-CI16x16-360p (16x16 spatial compression, 360p and above)
- Cosmos-Tokenize1-CV4x8x8-360p (4x temporal compression, 8x8 spatial compression, 360p and above, 49 frames context)
- Cosmos-Tokenize1-CV8x8x8-720p (8x temporal compression, 8x8 spatial compression, 720p and above, 121 frames context)
Discrete Tokenizers
- Cosmos-Tokenize1-DI8x8-360p (8x8 spatial compression, 360p and above)
- Cosmos-Tokenize1-DI16x16-360p (16x16 spatial compression, 360p and above)
- Cosmos-Tokenize1-DV4x8x8-360p (4x temporal compression, 8x8 spatial compression, 360p and above, 49 frames context)
- Cosmos-Tokenize1-DV8x16x16-720p (8x temporal compression, 16x16 spatial compression, 720p and above, 49 frames context)
License:
This model is released under the NVIDIA Open Model License. For a custom license, please contact cosmos-license@nvidia.com.
Under the NVIDIA Open Model License, NVIDIA confirms:
- Models are commercially usable.
- You are free to create and distribute Derivative Models.
- NVIDIA does not claim ownership to any outputs generated using the Models or Derivative Models.
Model Architecture:
Cosmos-Tokenize1-CV4x8x8-360p is a lightweight and computationally efficient architecture. The encoder starts with a 1-level Haar wavelet transform layer, which down-samples inputs by a factor of 2 in both spatial and temporal dimension. Likewise, the decoder ends with an inverse wavelet transform. We employ the vanilla autoencoder (AE) formulation to model the latent space for continuous tokenizers. For more details, refer to the technical blog.
Input/Output Specifications
Input
- Type: Images or Videos
- Format: RGB (Red, Green, Blue)
- Parameters: Two-Dimensional (2D) for images and Three-dimensional (3D) for videos
- Properties:
- Resolution: Minimum: 256px (shorter side). Maximum: Up to 1K
Output
- Type: Tokens
- Format: 16-Channel Vector
- Parameters: Two-Dimensional (2D) for images and Three-dimensional (3D) for videos
- Properties:
- Continuous-valued feature vectors with a dimensionality of 16
Decoder
Input
- Type: Tokens
- Format: 16-Channel Vector
- Parameters: Two-Dimensional (2D) for images and Three-dimensional (3D) for videos
- Properties:
- Continuous-valued feature vectors with a dimensionality of 16
Output
- Type Images or Videos (matching input type)
- Format: RGB (Red, Green, Blue)
- Parameters: Two-Dimensional (2D) for images and Three-dimensional (3D) for videos
- Properties:
- Resolution: Same as input resolution. The output image or video is a reconstruction of the input image or video.
Software Integration:
Runtime Engine(s):
Supported Hardware Microarchitecture Compatibility:
- NVIDIA Ampere (e.g., A100)
- NVIDIA Hopper (e.g., H100)
Note: We have only tested Cosmos Tokenizer with BF16 precision on Ampere and Hopper GPUs. If you are using older versions of NVIDIA GPUs (e.g., NVIDIA Volta GPUs), you may need to switch to FP32 precision.
Operating System(s):
- Linux (We have not tested on other operating systems.)
Usage
Inference Engines:
- See Cosmos-Predict1 (PyTorch) for details.
Evaluation
Tokenization Performance Comparison
We have evaluated the additional Cosmos Tokenizer models on DAVIS video benchmark dataset.
| Tokenizer | Compression Ratio | Height | Num. of Frames | Quantization | PSNR (DAVIS) | SSIM (DAVIS) | rFVD (DAVIS) |
|---|---|---|---|---|---|---|---|
| CogVideoX | 4×4×4 | - | - | VAE | 31.74 | 0.860 | 19.58 |
| OmniTokenizer | 4×8×8 | - | - | VAE | 29.04 | 0.710 | 117.66 |
| Cosmos-Tokenizer-CV | 4×8×8 | 720 | 49 | AE | 35.28 | 0.890 | 15.93 |
| Cosmos-Tokenizer-CV | 8×8×8 | 720 | 49 | AE | 34.10 | 0.850 | 30.16 |
| Cosmos-Tokenizer-CV | 8×8×8 | 720 | 121 | AE | 34.32 | 0.867 | 23.49 |
| Cosmos-Tokenizer-CV | 8×16×16 | 720 | 49 | AE | 32.55 | 0.770 | 93.82 |
- We compare with the state-of-the-art discrete video tokenizer, OmniTokenizer.
- Evaluation metrics:
- Peak Signal-to-Noise Ratio (PSNR)
- Structural Similarity (SSIM)
- Reconstruction Fréchet Video Distance (rFVD)
Runtime Comparison
The following table shows the number of parameters and the averaged encoding and decoding times per image or video frame, measured on a single A100 80GB GPU. For comparison, we also list the parameters and average speeds of prior state-of-the-art tokenizer(s) with the same compression ratio.
| Tokenizer | Resolution | Compression Ratio | Parameters | Time (ms) |
|---|---|---|---|---|
| CogVideoX | 720x1280 | 4×8×8 | 216M | 414 |
| OmniTokenizer | 720x1280 | 4×8×8 | 54M | 82.9 |
| Cosmos-Tokenizer-CV | 720x1280 | 4×8×8 | 105M | 34.8 |
Note: We benchmarked the runtime for images under the 8x8 compression and videos under the 4×8×8 compression. Tokenizers with different compression ratios are not included in this comparison.
Ethical Considerations
NVIDIA believes Trustworthy AI is a shared responsibility and we have established policies and practices to enable development for a wide array of AI applications. When downloaded or used in accordance with our terms of service, developers should work with their internal model team to ensure this model meets requirements for the relevant industry and use case and addresses unforeseen product misuse.
For more detailed information on ethical considerations for this model, please see the subcards of Explainability, Bias, Safety & Security, and Privacy below. Please report security vulnerabilities or NVIDIA AI Concerns here.
Plus Plus (++) Promise
We value you, the datasets, the diversity they represent, and what we have been entrusted with. This model and its associated data have been:
- Verified to comply with current applicable disclosure laws, regulations, and industry standards.
- Verified to comply with applicable privacy labeling requirements.
- Annotated to describe the collector/source (NVIDIA or a third-party).
- Characterized for technical limitations.
- Reviewed to ensure proper disclosure is accessible to, maintained for, and in compliance with NVIDIA data subjects and their requests.
- Reviewed before release.
- Tagged for known restrictions and potential safety implications.
Bias
| Field | Response |
|---|---|
| Participation considerations from adversely impacted groups protected classes in model design and testing: | None |
| Measures taken to mitigate against unwanted bias: | None |
Explainability
| Field | Response |
|---|---|
| Intended Application & Domain: | Tokenization of images and videos |
| Model Type: | Auto-Encoder |
| Intended Users: | Generative AI developers for image and video generation models |
| Output: | Images/Videos and Latent Tokens |
| Describe how the model works: | Compresses and decompresses visual input (image/video). |
| Technical Limitations: | Due to tokenizer compression limitations, some visual information (such as small text and other structured fine details) may not be reconstructed accurately. |
| Verified to have met prescribed NVIDIA quality standards: | Yes |
| Performance Metrics: | Peak Signal-to-Noise Ratio (PSNR), Structural Similarity (SSIM), Reconstruction Fréchet Video Distance (rFVD), Reconstruction Fréchet Inception Distance (rFID), Latency |
| Potential Known Risks: | Tokenizer's output can parse all forms of input, including what may be considered toxic, offensive, or indecent. |
| Licensing: | NVIDIA Open Model License |
Privacy
| Field | Response |
|---|---|
| Generatable or reverse engineerable personal information? | No |
| Protected class data used to create this model? | None Known |
| Was consent obtained for any personal data used? | None Known |
| How often is dataset reviewed? | Before Release |
| Is there provenance for all datasets used in training? | Yes |
| Does data labeling (annotation, metadata) comply with privacy laws? | Yes |
Safety
| Field | Response |
|---|---|
| Model Application(s): | Tokenization of images and videos |
| Describe the life critical impact (if present). | None Known |
| Use Case Restrictions: | See NVIDIA Open Model License |
| Model and dataset restrictions: | The Principle of least privilege (PoLP) is applied limiting access for dataset generation and model development. Restrictions enforce dataset access during training, and dataset license constraints adhered to. Model checkpoints are made available on Hugging Face, and may become available on cloud providers' model catalog. |
- Downloads last month
- 63
