Need help with whipper?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

566 Stars 68 Forks GNU General Public License v3.0 1.6K Commits 91 Opened issues


Python CD-DA ripper preferring accuracy over speed

Services available


Need anything else?

Contributors list


license Build Status GitHub (pre-)release IRC GitHub Stars GitHub Issues GitHub contributors

Whipper is a Python 3 (3.6+) CD-DA ripper based on the morituri project (CDDA ripper for *nix systems aiming for accuracy over speed). It started just as a fork of morituri - which development seems to have halted - merging old ignored pull requests, improving it with bugfixes and new features. Nowadays whipper's codebase diverges significantly from morituri's one.

Whipper is currently developed and tested only on Linux distributions but may work fine on other *nix OSes too.

In order to track whipper's latest changes it's advised to check its commit history (README and CHANGELOG files may not be comprehensive).

Table of content


For a detailed description, see morituri's wiki page: The Art of the Rip.


  • Detects correct read offset (in samples)
  • Detects whether ripped media is a CD-R
  • Has ability to defeat cache of drives
  • Performs Test & Copy rips
  • Verifies rip accuracy using the AccurateRip database
  • Uses MusicBrainz for metadata lookup
  • Supports reading the pre-emphasis flag embedded into some CDs (and correctly tags the resulting rip)
    • Currently whipper only reports the pre-emphasis flag value stored in the TOC
  • Detects and rips non digitally silent Hidden Track One Audio (HTOA)
  • Provides batch ripping capabilities
  • Provides templates for file and directory naming
  • Supports lossless encoding of ripped audio tracks (FLAC)
  • Allows extensibility through external logger plugins



For detailed information, please check the commit history.


Whipper still isn't available as an official package in every Linux distributions so, in order to use it, it may be necessary to build it from its source code.


You can easily install whipper without needing to care about the required dependencies by making use of the automatically built images hosted on Docker Hub:

docker pull whipperteam/whipper

Please note that, right now, Docker Hub only builds whipper images for the

architecture: if you intend to use them on a different one, you'll need to build the images locally (as explained below).

Building the Docker image locally is required in order to make it work on Arch Linux (and its derivatives) because of a group permission issue (for more details see issue #499).

To build the Docker image locally just issue the following command (it relies on the Dockerfile included in whipper's repository):

optical_gid=$(getent group optical | cut -d: -f3) uid=$(id -u) docker build --build-arg optical_gid --build-arg uid -t whipperteam/whipper .

It's recommended to create an alias for a convenient usage:

alias whipper="docker run -ti --rm --device=/dev/cdrom \
    --mount type=bind,source=${HOME}/.config/whipper,target=/home/worker/.config/whipper \
    --mount type=bind,source=${PWD}/output,target=/output \

You should put this e.g. into your

. Also keep in mind to replace the path definitions to something that fits to your needs (e.g. replace
… -v ${PWD}/output:/output …
… -v ${HOME}/ripped:/output \ …

Essentially, what this does is to map the /home/worker/.config/whipper and ${PWD}/output (or whatever other directory you specified) on your host system to locations inside the Docker container where the files can be written and read. These directories need to exist on your system before you can run the container:

mkdir -p "${HOME}/.config/whipper" "${PWD}/output"

Please note that the example alias written above only provides access to a single disc drive: if you've got many you will need to customise it in order to use all of them in whipper's Docker container.

Finally, you can test the correct installation as such:

whipper -v
whipper drive list


This is a noncomprehensive summary which shows whipper's packaging status (unofficial repositories are probably not included):

Packaging status

NOTE: if installing whipper from an unofficial repository please keep in mind it is your responsibility to verify that the provided content is safe to use.


If you are building from a source tarball or checkout, you can choose to use whipper installed or uninstalled but first install all the required dependencies.

Required dependencies

Whipper relies on the following packages in order to run correctly and provide all the supported features:

  • cd-paranoia, for the actual ripping
    • To avoid bugs it's advised to use
      versions ≥ 10.2+0.94+2
    • The package named
      , available on certain Debian and Ubuntu versions, is affected by a bug: it doesn't include the
      binary (needed by whipper). Only Debian bullseye (testing) / sid (unstable) and Ubuntu focal (20.04) and later versions have a separate
      package where the binary is provided. For more details on this issue check the relevant bug reports: #888053 (Debian), #889803 (Debian) and #1750264 (Ubuntu).
  • cdrdao, for session, TOC, pre-gap, and ISRC extraction
  • GObject Introspection, to provide GLib-2.0 methods used by
  • PyGObject, required by
  • musicbrainzngs, for metadata lookup
  • mutagen, for tagging support
  • setuptools, for installation, plugins support
  • pycdio, for drive identification (required for drive offset and caching behavior to be stored in the configuration file).
    • To avoid bugs it's advised to use the most recent
      version with the corresponding
      release or, if stuck on old pycdio versions, 0.20/0.21 with
      0.900.94. All other combinations won't probably work.
  • discid, for calculating Musicbrainz disc id.
  • ruamel.yaml, for generating well formed YAML report logfiles
  • libsndfile, for reading wav files
  • flac, for reading flac files
  • sox, for track peak detection
  • git or mercurial
    • Required either when running whipper without installing it or when building it from its source code (code cloned from a git/mercurial repository).

Some dependencies aren't available in the PyPI. They can be probably installed using your distribution's package manager:

PyPI installable dependencies are listed in the requirements.txt file and can be installed issuing the following command:

pip3 install -r requirements.txt

Optional dependencies

  • Pillow, for completely supporting the cover art feature (
    option values won't work otherwise).
  • docutils, to build the man pages.

These dependencies are not listed in the

. To install them, just issue the following command:

pip3 install Pillow docutils

Fetching the source code

Change to a directory where you want to put whipper source code (for example,

git clone
cd whipper

Finalizing the build

Install whipper:

python3 install

Note that, depending on the chosen installation path, this command may require elevated rights.

To build the man pages, follow the instructions in the relevant README which is located in the



Whipper currently only has a command-line interface called

which is self-documenting:
whipper -h
gives you the basic instructions.

Whipper implements a tree of commands: for example, the top-level

command has a number of sub-commands.

Positioning of arguments is important:

whipper cd -d (device) rip

is correct, while

whipper cd rip -d (device)

is not, because the

argument applies to the

A more complete set of usage instructions can be found in the

man pages.

Getting started

The simplest way to get started making accurate rips is:

  1. Pick a relatively popular CD that has a good chance of being in the AccurateRip database
  2. Analyze the drive's caching behavior

whipper drive analyze
  1. Find the drive's offset.

Consult the AccurateRip's CD Drive Offset database for your drive. Drive information can be retrieved with

whipper drive list

whipper offset find -o insert-numeric-value-here

If you omit the

argument, whipper will try a long, popularity-sorted list of drive offsets.

Please note that whipper's offset find feature is quite primitive so it may not always achieve its task: in this case using the value listed in AccurateRip's CD Drive Offset database should be enough.

If you can not confirm your drive offset value but wish to set a default regardless, set

read_offset = insert-numeric-value-here

Offsets confirmed with

whipper offset find
are automatically written to the configuration file.

If specifying the offset manually, please note that: if positive it must be written as a number without sign (ex:

), if negative it must include the sign too (ex:
  1. Rip the disc by running

whipper cd rip

Configuration file documentation

The configuration file is stored in

, or
is undefined.

See XDG Base Directory Specification and ConfigParser with


The configuration file consists of newline-delineated

key = value
pairs. The sections
are special config sections for options not accessible from the command line interface. Sections beginning with
are written by whipper; certain values should not be edited. Inline comments can be added using

Example configuration demonstrating all

path_filter_dot = True          ; replace leading dot with _
path_filter_posix = True        ; replace illegal chars in *nix OSes with _
path_filter_vfat = False        ; replace illegal chars in VFAT filesystems with _
path_filter_whitespace = False      ; replace all whitespace chars with _
path_filter_printable = False       ; replace all non printable ASCII chars with _

[musicbrainz] server = ; use MusicBrainz server at host[:port]

use http as scheme if connecting to a plain http server. Example below:

server =

[drive:HL-20] defeats_cache = True ; whether the drive is capable of defeating the audio cache read_offset = 6 ; drive read offset in positive/negative frames (no leading +)

do not edit the values 'vendor', 'model', and 'release'; they are used by whipper to match the drive

command line defaults for whipper cd rip

[] unknown = True output_directory = ~/My Music

Note: the format char '%' must be represented '%%'.

Do not add inline comments with an unescaped '%' character (else an 'InterpolationSyntaxError' will occur).

track_template = new/%%A/%%y - %%d/%%t - %%n disc_template = new/%%A/%%y - %%d/%%A - %%d


Running uninstalled

To make it easier for developers, you can run whipper straight from the source checkout:

python3 -m whipper -h

Logger plugins

Whipper allows using external logger plugins to customize the template of


The available plugins can be listed with

whipper cd rip -h
. Specify a logger to rip with by passing
-L loggername
whipper cd rip -L eac

Whipper searches for logger plugins in the following paths:

  • $XDG_DATA_HOME/whipper/plugins
  • Paths returned by the following Python instruction:

[x + '/whipper/plugins' for x in site.getsitepackages()]
  • If whipper is run in a
    , it will use these alternative instructions (from
    • get_python_lib(plat_specific=False, standard_lib=False, prefix='/usr/local') + '/whipper/plugins'
    • get_python_lib(plat_specific=False, standard_lib=False) + '/whipper/plugins'

On a default Debian/Ubuntu installation, the following paths are searched by whipper:

  • $HOME/.local/share/whipper/plugins
  • /usr/local/lib/python3.X/dist-packages/whipper/plugins
  • /usr/lib/python3.X/dist-packages/whipper/plugins


stands for the minor version of the Python 3 release available on the system.

Please note that locally installed logger plugins won't be recognized when whipper has been installed through the official Docker image.

Official logger plugins

I suggest using whipper's default logger unless you've got particular requirements.


Licensed under the GNU GPLv3 license.

Copyright (C) 2009 Thomas Vander Stichele
Copyright (C) 2016-2021 The Whipper Team: JoeLametta, Samantha Baldwin,
                        Merlijn Wajer, Frederik “Freso” S. Olesen, et al.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA


Make sure you have the latest copy from our git repository. Where possible, please include tests for new or changed functionality. You can run tests with

python3 -m unittest discover
from your source checkout.

Developer Certificate of Origin (DCO)

To make a good faith effort to ensure licensing criteria are met, this project requires the Developer Certificate of Origin (DCO) process to be followed.

The Developer Certificate of Origin (DCO) is a document that certifies you own and/or have the right to contribute the work and license it appropriately. The DCO is used instead of a much more annoying CLA (Contributor License Agreement). With the DCO, you retain copyright of your own work :). The DCO originated in the Linux community, and is used by other projects like Git and Docker.

The DCO agreement is shown below, and it's also available online: HERE.

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors. 1 Letterman Drive Suite D4700 San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

DCO Sign-Off Methods

The DCO requires a sign-off message in the following format appear on each commit in the pull request:

Signed-off-by: Full Name 

The DCO text can either be manually added to your commit body, or you can add either

to your usual Git commit commands. If you forget to add the sign-off you can also amend a previous commit with the sign-off by running
git commit --amend -s

Bug reports & feature requests

Please use the issue tracker to report any bugs or to file feature requests.

When filing bug reports, please run the failing command with the environment variable

set. For example:
WHIPPER_DEBUG=DEBUG WHIPPER_LOGFILE=whipper.log whipper offset find
gzip whipper.log

Finally, attach the gzipped log file to your bug report.


set, logging messages will go to stderr.
accepts a string of the default python logging levels.

If you can, please try to help to solve THIS issue which also has an open bounty on Bountysource.


Thanks to:

And to all the contributors.


You can find us and talk about the project on:

Other relevant links: - Whipper - Hydrogenaudio Knowledgebase - Repology: versions for whipper - Unattended ripping using whipper (by Thomas McWork)

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.