AVENC
Video compression and lazy access for meteorological GRIB grids.
Install with pip
pip install avenc
First release is being prepared; not yet published. The commands above become
available after the authorized PyPI release. Use a virtual environment. Supported
binary-wheel targets: Python 3.11–3.14, Linux x86_64/aarch64 (glibc >=2.28), macOS
Intel/Apple Silicon (>=15). Install prebuilt FFmpeg separately with
brew install ffmpeg-full or sudo apt install ffmpeg; no FFmpeg compilation required.
Check the installation
grib2avenc --help
avenc2grib --help
python -c "import avenc; print(avenc.__version__)"
Convert GRIB to AVENC and back
grib2avenc input.grib output.mp4
avenc2grib output.mp4 reconstructed.grib
The default is video-lossless with finite quantization; it does not promise byte-identical scientific values.
Open using xarray
import xarray as xr
with xr.open_dataset("output.mp4", engine="avenc", cache=False) as ds:
print(ds) # inspect variable/dimension names
field = ds[next(iter(ds.data_vars))]
print(field.isel({field.dims[0]: 0}).load())
The wheel installs the native tools automatically and preserves avenc and
avenc_xarray. See installation for pipx, Homebrew, standalone
archives, source builds, dependencies and troubleshooting, and releases
for maintainers.
AVENC design and detailed usage: meteorological grids as video streams
AVENC packs GRIB fields into MP4 video streams and embeds the metadata needed to reconstruct scientific grids. It provides command-line encoding, GRIB/Float32/Zarr reconstruction, lazy Python/xarray reads and a browser viewer/extractor.
Repository: https://github.com/filippi/avenc
Build the command-line tools
Native builds target Linux and macOS. Windows users should use a Linux/WSL environment; the native implementation uses POSIX facilities.
Install a C++17 compiler, CMake 3.18+, ecCodes, zlib and FFmpeg/ffprobe. Available encoders and pixel formats depend on the FFmpeg build.
# Debian/Ubuntu prerequisites:
sudo apt install build-essential cmake libeccodes-dev zlib1g-dev ffmpeg
# From this repository:
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --parallel 4
bin/grib2avenc --help
On macOS, install the corresponding dependencies with Homebrew, including
cmake, eccodes and ffmpeg. If ecCodes is not found, set ECCODES_HOME
or pass -DCMAKE_PREFIX_PATH=/path/to/dependencies.
./build.sh is a convenience wrapper for the same build commands.
Optional installation:
cmake --install build --prefix "$HOME/.local"
export PATH="$HOME/.local/bin:$PATH"
The subset library is installed beside the tools and the HTTP helper under
share/avenc/. HTTP CLI input additionally requires python3 on PATH.
Builds are portable by default; -DENABLE_NATIVE_ARCH=ON opts into optimization
for the build CPU. Keep ENABLE_FAST_MATH=OFF for missing-value correctness.
Encode GRIB fields
bin/grib2avenc input.grib output.mp4
bin/grib2avenc --compact source/*.grib output.compact.mp4
bin/grib2avenc --high source/*.grib output.high.mp4
bin/grib2avenc --list-options
Without an option, AVENC selects Video-lossless. One input with no output
name writes <input>.mp4; multiple inputs require an explicit MP4 output path.
| Option | Resolved profile | Purpose |
|---|---|---|
default / --lossless |
av1_lossless12_auto_400 |
Lossless 12-bit AV1 video; quantization error remains |
--high |
hevc_vgood12 |
Low additional codec error |
--medium |
vp9_hq10_auto_420 |
Balanced trade-off |
--compact / --low |
av1_good10_auto_400 |
Compression priority |
--fast |
avc_xcr8 |
Speed priority |
--apple |
hevc_xcr8 |
Software HEVC alias; does not select VideoToolbox |
Very small grids may not fit a profile's tile arrangement (the default AV1
profile currently fails on a 64 × 64 synthetic field). Use --fast or a custom
encoder configuration with suitable tiling for such inputs.
All shortcuts use automatic quantization-range selection. auto selects the
range policy per grouped stream; it can mix frameMinMax and groupMinMax in
one MP4. --enc selects a named configuration; --enc_config_table profiles.csv
loads custom configurations. See grib2avenc --help and avpack --help for
advanced codec, normalization, grouping and metadata options.
The original GRIB bitmap is authoritative for missing cells. Stable shared
bitmaps are stored in metadata; the default taper3 fill reduces discontinuities
in masked video regions before the original mask is restored. --mask-fill min
selects minimum fill instead. Fill is not a change to the scientific valid-cell
mask and does not guarantee an error bound on neighboring valid values.
Video losslessness is not scientific losslessness. Mapping physical values to finite integer codes, precision conversion and subsequent GRIB repacking can introduce error even with a lossless video codec. Evaluate each dataset/profile.
Inspect, reconstruct and compare
bin/avenc2grib --list output.mp4
bin/avenc2grib --stats output.mp4
bin/avenc2grib output.mp4 reconstructed.grib
bin/avenc2grib --group stream:0 output.mp4 one_stream.grib
bin/avenc-compare --full input.grib output.mp4 --json errors.json
bin/avenc-compare --fast input.grib output.mp4 --json sampled-errors.json
Use an identically concatenated reference for multi-file inputs:
cat source/*.grib > reference.grib. Comparison matches scientific identity,
not positional message order. Full and sampled comparison are distinct scopes.
Detailed metrics, normalization and output options: avenc-compare.md.
The legacy ComputeError utility remains for compatibility.
Subset output is little-endian Float32, ordered (frame, row, column):
bin/avenc2grib --stream-id 0 --frame-start 0 --frame-count 4 \
--ni-start 20 --nj-start 30 --width 16 --height 12 output.mp4 > subset.f32
Python/xarray
Install the unified package from the repository root; it includes the C++ CLI tools.
python3 -m venv .venv
. .venv/bin/activate
python -m pip install .
import xarray as xr
with xr.open_dataset("output.mp4", engine="avenc", cache=False) as ds:
print(ds)
field = next(iter(ds.data_vars))
# Inspect the variable's dimensions before selecting a point or window.
first_frame = ds[field].isel({ds[field].dims[0]: 0}).load()
GRIB-packed MP4 files are decoded through avenc2grib. Native Python array
packages use a separate pybind11 codec. The Python compress_dataarray API can
encode a three-dimensional DataArray with a time dimension; its options,
metadata and masking policy are not interchangeable with grib2avenc profiles.
It materializes a contiguous Float32 input and is not a streaming Dask encoder.
See the Python guide and the runnable examples there.
HTTP access
from avenc import open_avenc
with open_avenc("https://your-server.example/output.mp4") as ds:
name = next(iter(ds.data_vars))
first_frame = ds[name].isel({ds[name].dims[0]: 0}).load()
print(ds.avenc.http_stats)
The CLI also accepts HTTP(S) input URLs. A shared seekable source provides a bounded byte-range cache and transfer statistics. Servers ignoring Range can use a bounded temporary-file fallback. Lazy opening does not prove minimal transfer or spatially selective decoding: preceding GOP frames/full spatial frames may still need decoding. Measure the actual request and bytes transferred.
Experimental Zarr export
bin/avenc2grib --zarr-compress gzip output.mp4 decoded.zarr
bin/avenc2grib --stream-id 0 --frame-start 0 --frame-count 4 \
--ni-start 20 --nj-start 30 --width 16 --height 12 \
--zarr-out subset.zarr output.mp4
The exporter writes Zarr v2 arrays per stream, plus quantization/time metadata. The layout is experimental, not a universal training-ready schema. This is an export from reconstructed values, not a new accuracy guarantee.
Browser tools
www/viewer.html and www/extractor.html use WebCodecs and MP4Box. Serve the
folder over HTTP on localhost; put your files under www/datasets/ (not tracked).
python3 -m http.server 8000 --directory www
# Open http://localhost:8000/viewer.html?dataset=./datasets/output.mp4
www/index.php is an optional dataset listing and requires PHP rather than the
Python server. The metadata inspector uses Range, but the shared viewer/extractor
model currently loads the whole MP4. Browser codec support, secure-context
requirements, CORS and CDN availability apply. See www/README.md.
Tests
ctest --test-dir build --output-on-failure
python -m pip install '.[test]'
python -m pytest -q python/avenc/tests/test_metadata_v2.py
python -m unittest discover -s tests -p 'test_avenc_compare.py'
python -m unittest discover -s python/avenc/tests -p 'test_http_input.py'
node www/tests/metadata.mjs
node www/tests/decoder.mjs
The comparison and local HTTP tests generate small synthetic fields. External
network tests are opt-in. Dataset-dependent xarray/Dask checks require
AVENC_TEST_MP4, optionally AVENC_TRUTH_GRIB and AVENC2GRIB_BIN, and skip if
inputs are unavailable. AVENC_BIN_DIR selects an out-of-tree native test build.
Research data and licence
The manuscript and large experiments are maintained separately from the software. Dataset identifier: https://doi.org/10.5281/zenodo.23502851 (reserved for the accompanying archive; availability depends on publication).
AVENC is licensed under Apache-2.0. FFmpeg, ecCodes, codecs and browser libraries retain their own licences. Hardware acceleration depends on the encoder, FFmpeg build and device; it is not enabled merely by choosing a profile name. Agent-oriented usage and limitations: skills.md.
Metadata
Release files for avenc 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| avenc-1.0.0.tar.gz | 261.1 kB | With provenance | Details for avenc-1.0.0.tar.gz |
Built distributions (wheels)
Total release size: 165.2 MB
Release files / avenc-1.0.0.tar.gz
| Download URL | avenc-1.0.0.tar.gz |
|---|---|
| Size | 261.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1adcf8f31578f7d71e17c281607686a5b18633395d08ef37eb9ea53f1760a079
|
|
BLAKE2b-256 checksum How to use checksums |
dcd0dc2ea67ee8e768976cf3fc7e5b7f5ffc8c556fadd4199c31b0754332a8f5
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | avenc-1.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
6a185286812464c5249593fb83ff551d916d5e08df985d244899e89439bc83f2
|
|
BLAKE2b-256 checksum How to use checksums |
f3a7a6187ae465e1ce1b4eacf1ff24d1c5c140ff240174fec810131b0ad00f54
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | avenc-1.0.0-cp314-cp314-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
6fdfb1446f90797d534209fe67f2c1514ec695a02693d272226942a68fea1022
|
|
BLAKE2b-256 checksum How to use checksums |
022d17dfed9c975979afbdef002a9e58b299529a1e779cc7d6ac35466101f5c6
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp314-cp314-macosx_15_0_x86_64.whl
| Download URL | avenc-1.0.0-cp314-cp314-macosx_15_0_x86_64.whl |
|---|---|
| Size | 11.7 MB |
| Tags | CPython 3.14 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
ff717d387947eab3b3828dd01d2ef4eea230e34ef5beb529fa6d70b1c7dc4a98
|
|
BLAKE2b-256 checksum How to use checksums |
a526189e6220411b5d1981d68544242f3cd79fe4d6df39c32e98168e6b572ca6
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp314-cp314-macosx_15_0_arm64.whl
| Download URL | avenc-1.0.0-cp314-cp314-macosx_15_0_arm64.whl |
|---|---|
| Size | 11.8 MB |
| Tags | CPython 3.14 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0f4b752a4186badc8976d6aee09f2edecdcc5b6914c54336cea404dfaf5f0f23
|
|
BLAKE2b-256 checksum How to use checksums |
4c583506bcd11bb1f974a4bb40fc7883b2e380fd1e38998d65038d29707bba5e
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | avenc-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
051ce62510b2850e687ffd20e11b10b611b478bde67bc66668ce944c1a49d9c8
|
|
BLAKE2b-256 checksum How to use checksums |
4f72a3b68108e7f730b9d5639d4268e9ae2a37adc2d82757b56701ac81036190
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | avenc-1.0.0-cp313-cp313-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
2891b6dc4b9104362b6acd305267bc81a8b7a83c9c259c30b53ed829b55bc200
|
|
BLAKE2b-256 checksum How to use checksums |
83706b45fa69f5b10c4664752ec767bfd381a2b225ea09b0f21a9c3ce068d5ea
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp313-cp313-macosx_15_0_x86_64.whl
| Download URL | avenc-1.0.0-cp313-cp313-macosx_15_0_x86_64.whl |
|---|---|
| Size | 11.6 MB |
| Tags | CPython 3.13 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
3000e79d5ad3a6c0030a6f7bc0866015374bc0217747edac51fce8440165668e
|
|
BLAKE2b-256 checksum How to use checksums |
9cc7e9451ef73ecd428eec5e43728528b9fca036cf8a75469ee0af4250c9477c
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp313-cp313-macosx_15_0_arm64.whl
| Download URL | avenc-1.0.0-cp313-cp313-macosx_15_0_arm64.whl |
|---|---|
| Size | 11.8 MB |
| Tags | CPython 3.13 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8d9674e4d6a8e25ff935da5efa844448b9e27f501b28a9b34b9d9d4a57cb61a8
|
|
BLAKE2b-256 checksum How to use checksums |
597d2beacfdc621ef3583fc7b0fe2c2a4460256b8ead1f7175d4dc86bf46ca66
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | avenc-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
e3db6d997440d84d61c5bf1e977f56fb52896503f9e7ba568c167035f8701c73
|
|
BLAKE2b-256 checksum How to use checksums |
43d658edb0a538b7a1a465bc9b4689bb295903806e2899ee8e51a2af4ace4e36
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | avenc-1.0.0-cp312-cp312-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
edbb084d9b1965d872891a72f420f969e3112314411ec710fa121c48bda130c7
|
|
BLAKE2b-256 checksum How to use checksums |
1f19c7e7cedb93db42746a46fdb7028b49343d9b5258300e74d4af1e5d29bf2f
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp312-cp312-macosx_15_0_x86_64.whl
| Download URL | avenc-1.0.0-cp312-cp312-macosx_15_0_x86_64.whl |
|---|---|
| Size | 11.6 MB |
| Tags | CPython 3.12 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
456823a71f491cea732c9c021df5870fa78832d124eda2e10250a487ce60f47f
|
|
BLAKE2b-256 checksum How to use checksums |
76e542e905c703f73143d72e78ff099f9ea84014a5c467793432149895731ab3
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp312-cp312-macosx_15_0_arm64.whl
| Download URL | avenc-1.0.0-cp312-cp312-macosx_15_0_arm64.whl |
|---|---|
| Size | 11.8 MB |
| Tags | CPython 3.12 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
df953f3c0aae3e1148aa69082a7f28b9d91721097618383b0986e32097716e74
|
|
BLAKE2b-256 checksum How to use checksums |
8d4cae633e4fd08db8100cf8c122b1e9009cbd2645d15c84eeab637957075121
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | avenc-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.0 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
461102882d6de4ceceefa69c64510a33d89faf6e4365757cc498cc036c880749
|
|
BLAKE2b-256 checksum How to use checksums |
6f5efdf184d903345c2ed31e66ea9b057a6fd2492c69eab6633d778b5772c0d3
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
| Download URL | avenc-1.0.0-cp311-cp311-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 8.8 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
da310c6411f36656a92f07cb73abe43b263a3e24b74b9ecc01f850ea2b93a138
|
|
BLAKE2b-256 checksum How to use checksums |
5eaae89050928529a540de47ae07ac3f15f32a3cfe0e5dc14e0c3bb465925d09
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp311-cp311-macosx_15_0_x86_64.whl
| Download URL | avenc-1.0.0-cp311-cp311-macosx_15_0_x86_64.whl |
|---|---|
| Size | 11.7 MB |
| Tags | CPython 3.11 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
f23d2a2039135d6de918614534e08da72f7d49e63ee3d223ff939be6d3753d9b
|
|
BLAKE2b-256 checksum How to use checksums |
baf4fd086f3618081a15fab5575ef0ef6f0b7bf87c378a34ba7b2a66617e7090
|
| 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 20, 2026.
Transparency logRelease files / avenc-1.0.0-cp311-cp311-macosx_15_0_arm64.whl
| Download URL | avenc-1.0.0-cp311-cp311-macosx_15_0_arm64.whl |
|---|---|
| Size | 11.8 MB |
| Tags | CPython 3.11 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d71ce19e566b8fe44e0bfa3229253bbeac07981c48386f88289467e775b88345
|
|
BLAKE2b-256 checksum How to use checksums |
fe266e3318223466f81870584bb672db9b39a1ac598adb9900f525b91b91eb53
|
| 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 20, 2026.
Transparency logSecurity for avenc 1.0.0
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.
Full provenance
All 17 files in this release have been uploaded with provenance metadata.
Attestation for avenc-1.0.0.tar.gz
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 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.