Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

pysacd

PyPI Python Wheel Implementation Downloads License

CI Coverage CodeQL Fuzzing Checked with mypy Ruff OpenSSF Scorecard SLSA Build L2

SACD in your Python process, and a clean-room, drop-in replacement for sacd_extract: the same options, the same file names, the same bytes.

from pysacd import read_toc                 # in-process: no subprocess, no text to parse

disc = read_toc("album.iso")
print(disc.artist, "-", disc.title)
for t in disc.stereo.tracks:
    print(t.number, t.title, t.duration)

pysacd reads SACD (Scarletbook) disc images, and PS3 SACD Ripper servers, straight from Python. Its multithreaded C engine runs inside your process, so a script, a tagger or a library catalogue drives it with function calls and gets back structured results. It never spawns sacd_extract and parses its text.

Coming from sacd_extract? pysacd-extract is a drop-in replacement, verified file by file against the real thing:

ln -s "$(command -v pysacd-extract)" ~/bin/sacd_extract    # that's the whole migration
pip install pysacd     # wheels for Linux, macOS and Windows; engine and libFLAC included

Why pysacd

Why it exists, in the author's words: author's note.

  • No fork, no scraping.
    • What you get back: objects (or --json), not sacd_extract -P text.
    • Failures are exceptions, not exit codes and stderr.
    • Progress is a callback; to cancel, raise from it.
    • The TOC reader runs in-process, through scarletbook-rs: one call returns objects (see the Python library).
  • One pass, every output. One call reads an area once and writes DSF, DSDIFF, WAV and FLAC (any mix), plus an ISO copy. DST is decoded on every core, with the GIL released.
  • Byte-for-byte compatible with sacd_extract, apart from a few deliberate exceptions.
  • Clean by construction. No Philips/ISO reference code, ever. The SACD engine (TOC, sectors, DST decoding) is scarletbook-rs, a clean-room library written only from published specifications. See clean room and licences.
  • Goes further than sacd_extract:
    • gapless 24-bit FLAC/WAV;
    • MusicBrainz tags and cover art, with your own naming;
    • resume after a dropped PS3 connection;
    • raw-sector (2064/2054-byte) images;
    • protection against hostile disc text;
    • logs you can diagnose a failure from.
  • Faster than sacd_extract: plain-DSD discs extract to DSF 3.6–4.0× faster, and DST discs 2.5× (all threads; measured on 0.3.0's scarletbook engine). See performance.

Why you shouldn't use pysacd (yet)

  • Never tested against a real PS3. The network client is verified against a protocol simulator and sacd_extract, but not against hardware (#10).
  • Optical drives: like sacd_extract, it can't read a PC drive's SACD layer. You need an ISO or a PS3.

Documentation

The documentation index lists every document and its sections.

Quick start install, and a tour of the commands
pysacd-extract migrating from sacd_extract, compatibility policy, verification
Converting naming templates, tags, MusicBrainz, gapless PCM
The Python library the API, what's parsed, image formats
Performance benchmarks and their conditions
Reading from a PS3 usage, the wire protocol and the PS3's quirks
Logging what to attach when something fails
Security hostile discs, servers and text; report vulnerabilities via SECURITY.md
Clean room and licences where the code came from, acknowledgements
Development building, tests, CI; contributor rules in CLAUDE.md
Contributing reporting bugs, the pull-request process, project rules
Changelog what changed in each release

License

GPL-2.0-or-later. The engine links the scarletbook-rs C library statically, which pysacd uses under MIT (it is MIT OR Apache-2.0). See clean room and licences.

Metadata

Release files for pysacd 0.3.1rc1

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

Source distribution (sdist)

Source distribution for pysacd 0.3.1rc1
File Size Uploaded Provenance Actions
pysacd-0.3.1rc1.tar.gz 177.3 kB With provenance Details for pysacd-0.3.1rc1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for pysacd 0.3.1rc1
File Actions
pysacd-0.3.1rc1-py3-none-win_amd64.whl Python 3 none Windows x86-64 Details for pysacd-0.3.1rc1-py3-none-win_amd64.whl
pysacd-0.3.1rc1-py3-none-musllinux_1_2_x86_64.whl Python 3 none Linux musl 1.2+ x86-64 Details for pysacd-0.3.1rc1-py3-none-musllinux_1_2_x86_64.whl
pysacd-0.3.1rc1-py3-none-manylinux_2_28_x86_64.whl Python 3 none Linux glibc 2.28+ x86-64 Details for pysacd-0.3.1rc1-py3-none-manylinux_2_28_x86_64.whl
pysacd-0.3.1rc1-py3-none-manylinux_2_28_aarch64.whl Python 3 none Linux glibc 2.28+ ARM64 Details for pysacd-0.3.1rc1-py3-none-manylinux_2_28_aarch64.whl
pysacd-0.3.1rc1-py3-none-macosx_15_0_x86_64.whl Python 3 none macOS 15.0+ x86-64 Details for pysacd-0.3.1rc1-py3-none-macosx_15_0_x86_64.whl
pysacd-0.3.1rc1-py3-none-macosx_15_0_arm64.whl Python 3 none macOS 15.0+ ARM64 Details for pysacd-0.3.1rc1-py3-none-macosx_15_0_arm64.whl

Total release size: 8.8 MB

Release files / pysacd-0.3.1rc1.tar.gz

Download URL pysacd-0.3.1rc1.tar.gz
Size 177.3 kB
Tags Source
SHA-256 checksum
How to use checksums
28d4bc64bbc2a8079ee65a92b39776f4228dc13177dd28aa751573aa3e889d2a
BLAKE2b-256 checksum
How to use checksums
0283e1a2cddbd18fc2d3b492f23d32bd6379d31ac76815304252ee1a57348721
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-win_amd64.whl

Download URL pysacd-0.3.1rc1-py3-none-win_amd64.whl
Size 1.8 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
306107f4e9e4075a3324441048e48fdc97360d44c07bd0aeb3f6e06ba0efd0c2
BLAKE2b-256 checksum
How to use checksums
34a373f277a89801312f3d19994a28177b05741ba0be602ed3d822c0bc77df77
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-musllinux_1_2_x86_64.whl

Download URL pysacd-0.3.1rc1-py3-none-musllinux_1_2_x86_64.whl
Size 1.5 MB
Tags Linux musl 1.2+ x86-64 Python 3
SHA-256 checksum
How to use checksums
c8ce6a998f1bdaab4797126a4a2250613a6b3727413995430f9e088bddefe435
BLAKE2b-256 checksum
How to use checksums
8c6e7285742462a6bfc1044ee5c6cf785a0a90d2aa2e8c32e176724e95f2a03a
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-manylinux_2_28_x86_64.whl

Download URL pysacd-0.3.1rc1-py3-none-manylinux_2_28_x86_64.whl
Size 1.4 MB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
e014c5224499aa2559d02d670eab4fe4f17dd2bec527a1fbf620b310d6f811fc
BLAKE2b-256 checksum
How to use checksums
25df31180dc7681e07fc61d56c50d3c067a7daeb4f7a6e7464eb1414b25a5541
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-manylinux_2_28_aarch64.whl

Download URL pysacd-0.3.1rc1-py3-none-manylinux_2_28_aarch64.whl
Size 1.4 MB
Tags Linux glibc 2.28+ ARM64 Python 3
SHA-256 checksum
How to use checksums
724c79c37b319d726ab174cd20387eba342b0798837e5aaa1b373d8da4e1e52d
BLAKE2b-256 checksum
How to use checksums
64a47016e105091bd21521778966826f6175a4064148d7796d5ee8d8c2836e54
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-macosx_15_0_x86_64.whl

Download URL pysacd-0.3.1rc1-py3-none-macosx_15_0_x86_64.whl
Size 1.3 MB
Tags Python 3 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
92ee73bf192e8099020cb371ec9fb791ceef0823313d438bb9432dbe3f6e695c
BLAKE2b-256 checksum
How to use checksums
8d509c764a5c651e80a3487d9fbfc79db6fae264cdaca25cb529c1427d28505a
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 Nov 1, 2026.

Transparency log

Release files / pysacd-0.3.1rc1-py3-none-macosx_15_0_arm64.whl

Download URL pysacd-0.3.1rc1-py3-none-macosx_15_0_arm64.whl
Size 1.2 MB
Tags Python 3 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
e2cb1d7919797f9284f3a6fe17b811c9d2ec17636935759c0bd6102d4bbec882
BLAKE2b-256 checksum
How to use checksums
2cd85519a98cbb9b9011c57b9427c6eaa32c342235c93d3fd9cdb7e3853eb63b
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 Nov 1, 2026.

Transparency log

Security for pysacd 0.3.1rc1

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 7 files in this release have been uploaded with provenance metadata.

Select from 7 files

Attestation for pysacd-0.3.1rc1.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 Nov 1, 2026.

Transparency log

A 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.

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