ltx-2-internal/README.md

# LTX-2


https://github.com/user-attachments/assets/1922e7f0-cc5d-430c-9e1a-93c589e85fb4


## Setup

To set up ltx-2 repository for development:
* `uv sync` creates and installs the virtual environment. To activate the environment, run `source .venv/bin/activate`.
* Set up pre-commit:
```bash
$ PIP_NO_INPUT=1 pre-commit install-hooks --config .pre-commit-config.yaml
$ pre-commit install
```
* `pytest` runs all tests in the repository. `pytest --pyargs packages/ltx-core` runs only tests specific to `ltx-core`.
* `uv build --package ltx-core` builds only the ltx-core package.
* Dependencies declared in the main `pyproject.toml` file apply to the entire repository. Always prefer specifying dependencies for specific packages.

## Folder structure

```
├── README.md
├── packages
│   └── ltx-core
│       ├── README.md
│       ├── pyproject.toml
│       ├── src
│       │   └── ltx_core
│       │       ├── __init__.py
│       │       ├── # package-specific modules go here
│       └── tests
│           └── ltx_core
│               ├── # test folder structure mirrors src of the package.
│               ├── conftest.py
│               └── unit
│                   └── test_placeholder.py
├── pyproject.toml
├── pytest.toml
└── uv.lock
```


## Comments mentioning ComfyUI or internal company code

Comments relating to ComfyUI, its LTX repo or any other internal
Lightricks resource should be wrapped in LT_INTERNAL tags. Tagged
sections should be placed inside comments or docstrings. The
following examples demonstrate proper usage:
```python
# LT_INTERNAL: check PR to understand better

# conditioning is applied before the step LT_INTERNAL: http://...

# condition is applied after the step to integrate LT_INTERNAL_BEGIN http://... LT_INTERNAL_END

"""
Consult with the paper, https://arxiv.org
LT_INTERNAL_BEGIN
Most important PRs to check
http://...
http://...
LT_INTERNAL_END
"""

```