[bugfix] Fix STFT dtype mismatch

[kevin314]

Changes

• Fix STFT dtype mismatch for bf16 inference in LTX-2.3

Test Plan

# Commands you ran

Test Results

Test output

# Paste output here

Checklist

• I ran pre-commit run --all-files and fixed all issues
• I added or updated tests for my changes
• I updated documentation if needed
• I considered GPU memory impact of my changes

For model/pipeline changes, also check:

• I verified SSIM regression tests pass
• I updated the support matrix if adding a new model

[gemini-code-assist]

Code Review

This pull request updates the forward pass in ltx2_audio_vae.py to cast self.forward_basis to the data type of y before performing the 1D convolution. The reviewer suggested using self.forward_basis.to(y) instead of self.forward_basis.to(y.dtype) to ensure both the device and data type are matched, preventing potential device mismatch errors.

[gemini-code-assist]

Using self.forward_basis.to(y) is more robust than self.forward_basis.to(y.dtype) because it automatically matches both the device and the data type of y. This prevents potential runtime errors due to device mismatches if y and self.forward_basis happen to be on different devices.

Suggested change

	spec = F.conv1d(y, self.forward_basis.to(y.dtype), stride=self.hop_length, padding=0)
	spec = F.conv1d(y, self.forward_basis.to(y), stride=self.hop_length, padding=0)

[mergify]

⚠️ PR title format required

Your PR title must start with a type tag in brackets. Examples:

• [feat] Add new model support
• [bugfix] Fix VAE tiling corruption
• [refactor] Restructure training pipeline
• [perf] Optimize attention kernel
• [ci] Update test infrastructure
• [infra] Add activation trace hooks
• [docs] Add inference guide
• [misc] Clean up configs
• [new-model] Port Flux2 to FastVideo
• [skill] Add add-model agent skill

Valid tags: feat, feature, bugfix, fix, refactor, perf, ci, infra, doc, docs, misc, chore, kernel, new-model, skill, skills

Please update your PR title and the merge protection check will pass automatically.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 PR merge requirements

Waiting for

• #approved-reviews-by>=1
• check-success=fastcheck-passed
• check-success~=pre-commit

This rule is failing.

• #approved-reviews-by>=1
• check-success=fastcheck-passed
• check-success~=pre-commit
• check-success=full-suite-passed
• title~=(?i)^\[(feat|feature|bugfix|fix|refactor|perf|ci|doc|docs|misc|chore|kernel|new.?model|skill|skills|infra)\]

[mergify]

Pre-commit checks failed

Hi @kevin314, the pre-commit checks have failed. To fix them locally:

# Install pre-commit if you haven't already
uv pip install pre-commit
pre-commit install

# Run all checks and auto-fix what's possible
pre-commit run --all-files

Common fixes:

• yapf: yapf -i <file> (formatting)
• ruff: ruff check --fix <file> (linting)
• codespell: codespell --write-changes <file> (spelling)

After fixing, commit and push the changes. The checks will re-run automatically.

For future commits, pre-commit will run automatically on changed files before each commit.

[SolitaryThinker]

/merge