pysacd
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 # pure Python: no binary, no subprocess
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
- No fork, no scraping.
- What you get back: objects (or
--json), notsacd_extract -Ptext. - Failures are exceptions, not exit codes and stderr.
- Progress is a callback; to cancel, raise from it.
- The TOC reader is pure Python and needs no binary.
- What you get back: objects (or
- 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. DST decoding comes from FFmpeg's LGPL decoder, completed through an auditable two-agent clean room. 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.
- Plain-DSD discs extract 2.5–3.6× faster. On DST discs it's essentially a tie, because both tools saturate every core. 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). - It isn't faster on DST discs.
- 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 |
| DST bitstream | the clean-room specification |
| Development | building, tests, CI; contributor rules in CLAUDE.md |
License
GPL-2.0-or-later, with csrc/dstdec.c under LGPL-2.1-or-later. See
clean room and licences.
1 maintainer
Metadata
1 maintainer
Release files for pysacd 0.2.1
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 |
|---|---|---|---|---|
| pysacd-0.2.1.tar.gz | 157.3 kB | With provenance | Details for pysacd-0.2.1.tar.gz |
Built distributions (wheels)
Total release size: 2.0 MB
Release files / pysacd-0.2.1.tar.gz
| Download URL | pysacd-0.2.1.tar.gz |
|---|---|
| Size | 157.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
696cb4a0d090c1537129f6cd86f10ed0df6850477c4f640f89a341200c755f44
|
|
BLAKE2b-256 checksum How to use checksums |
da0d64174290fcc460a5557dd2d0480c2078397429f785b43f63b015c3a1607b
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-win_amd64.whl
| Download URL | pysacd-0.2.1-py3-none-win_amd64.whl |
|---|---|
| Size | 381.4 kB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
97ffae45cb7496ac695f517074961589dcec3a96b687d582327da0ab29544859
|
|
BLAKE2b-256 checksum How to use checksums |
05bf53dd2d1f76a1798e81b71b0942ef85d76f4c5e8394ad7eeb346b15be16c8
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-musllinux_1_2_x86_64.whl
| Download URL | pysacd-0.2.1-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 341.7 kB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
2261c90fb4c11efb5a5932df5657deb74d35d49e0ff5055f58549b46f31dc444
|
|
BLAKE2b-256 checksum How to use checksums |
169eeda57eb2e362d7f3c700bcf9fa71b959daecedbedc0c4787474ed7e9d636
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | pysacd-0.2.1-py3-none-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 336.1 kB |
| Tags | Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
6203d5fcd630799b81f579517e27b1720329ad58b81c4227a5dc41c8323e04b8
|
|
BLAKE2b-256 checksum How to use checksums |
51b36f2bcb713f9e63ce9e85e0f97160d4f6a81cdec918a3ea2fc190f8ce1493
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | pysacd-0.2.1-py3-none-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 289.7 kB |
| Tags | Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
75fbc58f77f384966121c80e00f02bf447eb242e069b86952e30bb144ebf3d4e
|
|
BLAKE2b-256 checksum How to use checksums |
d9519825900f224fdff7f7cd2cf05f604dfe65cab989857ecc2fd380cfefec1d
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-macosx_15_0_x86_64.whl
| Download URL | pysacd-0.2.1-py3-none-macosx_15_0_x86_64.whl |
|---|---|
| Size | 253.1 kB |
| Tags | Python 3 macOS 15.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
f71e137a6ede86075cf0c105690ed05abf054c7d05c5c88a897694ec6a2b54e8
|
|
BLAKE2b-256 checksum How to use checksums |
44187e7e17ffee6754e7983d5bc552a2fb1dda5806d206b84f06b285ef63d1fd
|
| 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 29, 2026.
Transparency logRelease files / pysacd-0.2.1-py3-none-macosx_15_0_arm64.whl
| Download URL | pysacd-0.2.1-py3-none-macosx_15_0_arm64.whl |
|---|---|
| Size | 232.4 kB |
| Tags | Python 3 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
ee1505991f552a88af6524a2b2a0f037bc2d27bc1be3d2ad5705a79259b6a529
|
|
BLAKE2b-256 checksum How to use checksums |
b13157124c6119a684c37311d23b17d3b045132cfd847ebf6f82067d91382c22
|
| 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 29, 2026.
Transparency logSecurity for pysacd 0.2.1
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.
Attestation for pysacd-0.2.1.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 29, 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.
