Skip to main content

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
Releases by major version what each minor version brought, across the SACD projects

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.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 pysacd 0.4.3
File Size Uploaded Provenance Actions
pysacd-0.4.3.tar.gz 185.0 kB With provenance Details for pysacd-0.4.3.tar.gz

Built distributions (wheels)

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

Total release size: 10.9 MB

Release files / pysacd-0.4.3.tar.gz

Download URL pysacd-0.4.3.tar.gz
Size 185.0 kB
Tags Source
SHA-256 checksum
How to use checksums
75e9b2e7bece2c670f7178cd268ca0a0cf40fae21fcaf30a3f84b0e5a0e7d126
BLAKE2b-256 checksum
How to use checksums
0728b9db72d692cb07dd953c756fbd0a552eec20391f0628af6c2505623fc68f
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.3-py3-none-win_amd64.whl

Download URL pysacd-0.4.3-py3-none-win_amd64.whl
Size 2.2 MB
Tags Python 3 Windows x86-64
SHA-256 checksum
How to use checksums
900515a832671610fde6811bf26c1229262b26118a86a355acc5ae2e500948a0
BLAKE2b-256 checksum
How to use checksums
41db0410d83753cde36677bbac8c415c8274caf100e396691e0fb27ecc85f5aa
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.3-py3-none-musllinux_1_2_x86_64.whl

Download URL pysacd-0.4.3-py3-none-musllinux_1_2_x86_64.whl
Size 2.0 MB
Tags Linux musl 1.2+ x86-64 Python 3
SHA-256 checksum
How to use checksums
ddfbbcb64cf3750ba4d82eb05bab7350f9eba7c5cb999e6332e546bd9f8f1152
BLAKE2b-256 checksum
How to use checksums
f65bd3109404e030a16c8e41e856eebeec0adca71e69722b65b916f7ee1dfe9c
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.3-py3-none-manylinux_2_28_x86_64.whl

Download URL pysacd-0.4.3-py3-none-manylinux_2_28_x86_64.whl
Size 1.9 MB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
292d15439e7ab5c3a0369baddec06083932cbaa27f8649ee37c335ee3d50e435
BLAKE2b-256 checksum
How to use checksums
9e2ce53bb770211ef0b373daf5165a4237f56630504d74db38800d748db41ff3
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.3-py3-none-manylinux_2_28_aarch64.whl

Download URL pysacd-0.4.3-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
61a32345cacc90ae087e9dea7c6769445e283f26067c86399342b782ccde39ce
BLAKE2b-256 checksum
How to use checksums
d70fa3aad76bfdc1c65237df643f1836b599bfe130b80a04331883d66f7bcb75
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.3-py3-none-macosx_15_0_x86_64.whl

Download URL pysacd-0.4.3-py3-none-macosx_15_0_x86_64.whl
Size 1.8 MB
Tags Python 3 macOS 15.0+ x86-64
SHA-256 checksum
How to use checksums
f69e1426914c767875ba3c39db3f6ae958980654bc538d6391e6979951375162
BLAKE2b-256 checksum
How to use checksums
c173e26412572dd2712cc8a3693210409466f3f0bf93a7a04279422d2ca85cd2
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.3-py3-none-macosx_15_0_arm64.whl

Download URL pysacd-0.4.3-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
028e24524fba658e58e85c56c68af7544533f5e856cd8b075522ae9679a4960c
BLAKE2b-256 checksum
How to use checksums
6ae2529eea5ae4498898039705dc5ac0dfff4ac2893470a6930bb2d37345af03
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.3

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