Skip to main content

Luvix

Tests

Luvix is a CLI toolkit for HDR gain-map images: inspect, split SDR base and gain map, rebuild edited captures, validate, and export flattened HDR TIFFs.

Current release-candidate scope

The tested backend processes Apple HDR gain-map HEIC captures on macOS using ImageIO/Core Image and Swift. It supports inspect, extract, rebuild, validate, inspect-hdr, and export tiff. A 32-bit linear float TIFF with matching source-supported ICC has been validated in Photoshop. The 16-bit PQ TIFF was visually validated with an externally supplied P3 PQ ICC. General JPEG gain-map input, ISO/Ultra HDR interoperability, and arbitrary ICC source profiles are roadmap items, not current supported features.

Install

Recommended for a command-line application:

uv tool install luvix
luvix --version

Alternatively, use pipx install luvix, or install luvix with pip inside an activated virtual environment.

The installed command is luvix. uv run luvix is only for development from a source checkout.

Quick start

luvix doctor
luvix inspect ~/Pictures/photo.HEIC
luvix extract ~/Pictures/photo.HEIC --output ~/Pictures/work/photo
luvix export tiff ~/Pictures/photo.HEIC \
  --bit-depth 32 --transfer linear --color-space source \
  --output ~/Pictures/work/photo_linear32.tif

For 16-bit PQ output, supply a compatible external PQ ICC and an explicit reference white. See the user guide for the full workflow and current support boundaries.

Documentation

  • User guide: full command walkthrough, output formats, and troubleshooting.
  • Architecture: gain-map model, color handling, and format constraints.
  • Roadmap: planned JPEG, ISO 21496-1, Ultra HDR, multichannel maps, and color-space expansion.
  • Release checklist: CI, package verification, merge, publish, and install smoke tests.
  • Changelog

Development checks

uv run ruff check .
uv run ruff format --check .
uv run pytest -q
uv lock --check
uv build
uv run --locked twine check dist/*

The native Apple backend requires macOS and swiftc. The Python package itself is cross-platform, but this does not imply the Apple HDR features run on Linux.

License

Apache License 2.0. Do not redistribute proprietary reference ICC profiles or private photographs as part of Luvix.

Metadata

Release files for luvix 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for luvix 0.1.3
File Size Uploaded
luvix-0.1.3.tar.gz 27.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for luvix 0.1.3
File Interpreter ABI Platform
luvix-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 58.6 kB

Release files / luvix-0.1.3.tar.gz

Download URL luvix-0.1.3.tar.gz
Size 27.7 kB
Tags Source
SHA-256 checksum
How to use checksums
62b3949e62b975d07fc362d6b9d0d2ba88d13c72bb82e92e2f3a0f265fe4eb7e
BLAKE2b-256 checksum
How to use checksums
b985ed4738d4cb57984fea260a410a116c171a282d4d0984396ce0ffdb0ccb5f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release files / luvix-0.1.3-py3-none-any.whl

Download URL luvix-0.1.3-py3-none-any.whl
Size 30.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8a3760d0a030f8f8a054cd54e69675e49fe296ca81754401cee52821963538ed
BLAKE2b-256 checksum
How to use checksums
cefadf5450ce75070daab6c3ec6af88a465dd68d8623ded083df2c5e4e14b183
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.5

2 release files

0.1.4

2 release files

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page