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, and the layout of DSF and DSDIFF files) 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.4.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.4.1rc1
File Size Uploaded Provenance Actions
pysacd-0.4.1rc1.tar.gz 183.4 kB With provenance Details for pysacd-0.4.1rc1.tar.gz

Built distributions (wheels)

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

Total release size: 10.5 MB

Release files / pysacd-0.4.1rc1.tar.gz

Download URL pysacd-0.4.1rc1.tar.gz
Size 183.4 kB
Tags Source
SHA-256 checksum
How to use checksums
6443358e2a321d77a47e508318b4cbe563d81d05177629ac6e7aaccc38e11ee8
BLAKE2b-256 checksum
How to use checksums
efc02cad15b0ae18f79f37e348f261bc9359b8456516d64629430fb0e736fcf3
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-win_amd64.whl
Size 2.2 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
1259b2808d0abee6675ecf4e49d61e67e8afe82169902f2c874bb0ded7c83a33
BLAKE2b-256 checksum
How to use checksums
9cbb8c2aa1a055bc34e6f5b21f5d4008fba6298e1b500624a765c9e80e2d90e5
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-musllinux_1_2_x86_64.whl
Size 1.9 MB
Tags Linux musl 1.2+ x86-64 Python 3
SHA-256 checksum
How to use checksums
9a579bb2ad4ea6f4dfc9530bf2942faa601f135eed3583e067bc63d4179bd608
BLAKE2b-256 checksum
How to use checksums
c9317184c8a924e33d99dde04485bc2e5be3b0863d97e13f3c164525fca73925
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-manylinux_2_28_x86_64.whl
Size 1.8 MB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
39e33d1e8117795adeedb7df1e67253cd20f16ec4b71b871025f0a3da5065bd5
BLAKE2b-256 checksum
How to use checksums
79534a6b3167ddc1fb5a14ca875a1e68f4b7d692d7597d820b81af2cb9273c4c
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-manylinux_2_28_aarch64.whl
Size 1.5 MB
Tags Linux glibc 2.28+ ARM64 Python 3
SHA-256 checksum
How to use checksums
b65ab6b2b2cb46f578ebf517fe55d6ba450037481fe8892aff173c82824a76a3
BLAKE2b-256 checksum
How to use checksums
2e95d8c78c711fa3415967aee5b5c4c6fe7c5c2978e47eb647543e1bb74e2379
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-macosx_15_0_x86_64.whl
Size 1.7 MB
Tags Python 3 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
0ddef512093d8c4cb62f11b5fa9e329d15b1b89dbc6d2c6ebbe218b16bbe77c9
BLAKE2b-256 checksum
How to use checksums
7cd3fbd40732d39ec1f9012462b91a239ea4275ddd66f16f4207fe8bbdd1b762
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 2, 2026.

Transparency log

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

Download URL pysacd-0.4.1rc1-py3-none-macosx_15_0_arm64.whl
Size 1.3 MB
Tags Python 3 macOS 15.0+ ARM64
SHA-256 checksum
How to use checksums
f3431d5287dc408087def05094580c377b8a3db46af01fa4179131b8b3c74d19
BLAKE2b-256 checksum
How to use checksums
e3d5ce72bd827c1ef739d10cf029067133fe366a6360102d8ebe89a08757b353
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 2, 2026.

Transparency log

Security for pysacd 0.4.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.4.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 2, 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