Nightly Build

Latest successful build from 'development' branch. Not a stable release.

v1.1.0

Major feature release introducing new audio formats, enhanced compression profiles, and quality-of-life improvements.

What's New

• Executable renamed: The main binary has been renamed from chisel to chsl.
• OGG Vorbis support: Added full support for lossless OGG Vorbis recompression across all platforms, via OptiVorbis.
• MP3 support: Added support for MP3 optimization (for now available on macOS and Linux only), via mp3packer.
• Improved FLAC & WavPack compression: Upgraded WavPack to use extra compression mode and xmode 6. Enhanced FLAC encoding by expanding apodization window functions and increasing residual partition orders to achieve better compression ratios.
• Hierarchical logging: The logging system has been completely redesigned into a detailed, cascading level-based architecture (ALL, DEBUG, INFO, WARNING, ERROR, OFF).
• Enhanced progress bar: The terminal progress bar now dynamically displays the number of files currently being processed.
• Automatic magic database: The --regenerate-magic flag has been removed. Magic file generation is now handled automatically.

macOS: removing the Gatekeeper quarantine

When downloading binaries from the internet, macOS automatically marks them as “quarantined”.
If you try to run chsl and macOS shows a warning like:

“chsl cannot be opened because it is from an unidentified developer”
…you need to remove the quarantine attribute manually.

How to remove the quarantine flag
Open Terminal in the folder where you downloaded chsl and run:

xattr -d com.apple.quarantine ./chsl

To verify that the quarantine flag is gone:

xattr ./chsl

If com.apple.quarantine no longer appears, you're good to go.
Now you can run:

./chsl ...

Note
This issue does not occur if you compile chsl yourself.

v1.0.1

First maintenance release addressing CLI behavior and logging.

What's New

• Fixed -o (output) behavior: The -o flag now correctly supports renaming single files. Previously, it incorrectly treated the output path as a directory in single-file mode.
• New --log-file option: Added a specific flag to write logs to a file (e.g., --log-file chisel.log). Chisel no longer creates a chisel.log file in the working directory by default.
• Logging improvements: The default log level has been corrected to ERROR to reduce console noise.
• Version reporting: Fixed the output of --version to correctly display the release number.

If you're having problems on Linux/macOS, run chisel with --regenerate-magic.

macOS: removing the Gatekeeper quarantine
When downloading binaries from the internet, macOS automatically marks them as “quarantined”.
If you try to run chisel and macOS shows a warning like:

“chisel cannot be opened because it is from an unidentified developer”

…you need to remove the quarantine attribute manually.

How to remove the quarantine flag
Open Terminal in the folder where you downloaded chisel and run:

xattr -d com.apple.quarantine ./chisel

To verify that the quarantine flag is gone:

xattr ./chisel

If com.apple.quarantine no longer appears, you're good to go.
Now you can run:

./chisel ...

Note
This issue does not occur if you compile chisel yourself.

v1.0.0

First release! Most formats should work pretty well.
If you're having problems on Linux/macOS, run chisel with --regenerate-magic.

Known issues

1. The -o option is broken when used in single‑file processing.
2. The default logging level is WARNING instead of ERROR.

---

macOS: removing the Gatekeeper quarantine

When downloading binaries from the internet, macOS automatically marks them as “quarantined”.
If you try to run chisel and macOS shows a warning like:

“chisel cannot be opened because it is from an unidentified developer”

…you need to remove the quarantine attribute manually.

How to remove the quarantine flag

Open Terminal in the folder where you downloaded chisel and run:

xattr -d com.apple.quarantine ./chisel

To verify that the quarantine flag is gone:

xattr ./chisel

If com.apple.quarantine no longer appears, you're good to go.

Now you can run:

./chisel ...

Note
This issue does not occur if you compile chisel yourself.