WavPack

WavPack

Hybrid Lossless Audio Compression
Developer(s)	David Bryant
Release information
Initial release	{{{released}}}
Stable release	5.5.0 (2022-07-07)
Preview release	None
Compatibility
Operating system	Windows, MacOSX, Linux/BSD/Unix, ...
Additional information
Use	Encoder/Decoder
License	BSD license
Website	http://www.wavpack.com/

WavPack (pronounced "wave-pack") is a lossless audio codec, also offering optionally a hybrid lossless/lossy mode. It is distributed as a free open-source encoder/decoder with a library and a large number of tools, including a Windows GUI and a range of plugins for both audio players and other software. Third party implementations are available, including ffmpeg. WavPack supports and/or can be played back on a large number of platforms/OSes including mobile (Android, iOS), portable (Rockbox) and even web apps.

WavPack is arguably the most feature-rich lossless compressor, supporting a unique range of audio signals including Direct-Stream Digital. Everyday use is supported by a wide range of players and taggers, but conversion is likely safest done with applications that invoke the official tools (rather than e.g. ffmpeg's implementation) – and special features might require the user to apply the WavPack executable directly, for example with drag+drop, see the Using WavPack section below.

Performance-wise, WavPack defaults to a fast codec – less CPU intensive than ALAC, but typically not as fast as FLAC or TAK, especially in decoding CPU usage. In the age of low-power portable Rockbox-equipped players, WavPack could be seen as a reasonable middle ground between FLAC's low CPU footprint and long battery life, and the smaller files but more CPU-intensive Monkey's Audio – invoking WavPacks high mode and extra compression that would compress to smaller sizes than FLAC.

WavPack has inspired other codecs and their features. For more on WavPack, including on its history and technology, see the Wikipedia entry.

Features

For an end-user considering WavPack as a an audio format, its feature-richness might be the big selling point. WavPack supports pretty much all the more common features noted at HA Wiki's Lossless Codec Comparison as in the following first list, but several users might consider the more unique features listed under the subsequent headline.

• Seekable and streaming playback.
• Error handling: upon playback, it will detect and report corrupted frames, mute to protect against static/noise output, and continue playback. Since version 5, WavPack can also check for corruption without decoding, hence quicker than any decoding format. Optional MD5 audio checksum can also be added upon encoding for file fingerprinting.
• High-resolution audio support (see next headline)
• Multichannel support: currently capped at 256 channels, supports WAVEFORMATEXTENSIBLE channel masks.
• Piping support for encoding, and support for RAW PCM input/output.
• RIFF chunks supported for recreating also non-audio chunks of the original files; by default, WavPack will restore to a file bit-identical to the original.
• Tagging: APEv2. (ID3v1 is possible, but not advisable.)
• Cuesheet support. In practice, some applications handle embedded cuesheets better in WavPack than in some other formats.
• Unicode support.
• Can be used in the Matroska container.
• Windows GUI available.

WavPack also handles bit depths not divisible by 8, and is known to employ a "wasted bits" strategy: For, say, a 20 bit signal in a 24 bit container, WavPack will detect that bits 21 to 24 are "wasted" and compressed as 20-bits without size penalty.

Special/unique features

Most of these features are shared with only a few if any notable codecs, or extend to signal types or file types others do not support (comparisons given).

• DSD support: can losslessly compress Philips DSDIFF and Sony DSF files (see "Using WavPack" below); can import ID3v2.3 tags from DSF. (No other end-user codec compresses DSD.)
• High-resolution support for bit depth 1-bit to 32-bit integer and sampling rates up to 2 GiHz in integer steps. (Officially, 1 GHz is supported – it is gigaherz, not MHz, the upper limit being in the UHF radio frequency band. Monkey's Audio, OptimFROG and MPEG-4 ALS support the entire WAVE range up to 4 GiHz.)
• 32-bit floating-point supported – also including CoolEdit/Adobe Audition's own float format (use the -a option only if the .wav was generated by CoolEdit/Audition). (This line like OptimFROG.)
• As much as 256 channels currently supported (version 5.5.0; can be extended to the thousands – for even more, MPEG-4 ALS supports 66536.)
• Hybrid lossy/lossless mode (can also be used as lossy). (Like OptimFROG.)
• Can in addition to PCM in WAVE files also read and output to RF64, Sony's Wave64, and CAF (including > 4 GB files and both endianness CAF – the latter apparently unique among lossless formats). Also, WavPack will upon decoding recreate any (standards-compliant) file bit by bit including non-audio parts, to whatever input format it supports. (Monkey's/OptimFROG/TAK do the same to the input formats they support.)
• Recompression: Can recompress .wv files in place, with tag transfer. (Like FLAC on .flac files.)
• Drag and drop support: Dropping a file on to wavpack.exe/wvunpack.exe will encode/decode it to source directory. (Like FLAC.) From 5.5.0, one can also apply options to drag and drop by renaming the executable, and drop several files.

Limitations

The following limitations are certainly not unique to WavPack. Among competing formats, only Monkey's supports AIFF with full file structure restore (big-endian only) or the legacy AU/SND format. None seem to be able to force WAVE version (though some can force RF64) in output, and only FLAC can force decoding to AIFF (and only to big-endian).

• Despite being available for several platforms, PCM in AIFF is currently not supported. (See below for workarounds.)
• Although output can be forced to various filetypes, there seems not to be an easy way to force output to a given version of the WAVE format (apparently no other codec does this either) – nor to force RF64 if less than 4 GiB output.
• DSD: Will reject DST-compressed DSD (which are already compressed heavier than WavPack does); can currently not import ID3v2.4, only ID3v2.3 (use Mp3tag to copy tags).
• Some third-party implementations have limitations and bugs waiting to be fixed.

As of version 5.4.0, some features are discontinued. XP support is officially dropped (though an "unofficial" build is available – otherwise, 5.3.0 released April 2020 supports XP), version 5 does no longer offer compression to Windows .sfx self-extracting file (cf. OptimFROG) nor the -p feature. Furthermore, WavPack version 3.x files are no longer supported. To recompress these files (if any are still around, WavPack 4 was released in 2004) to WavPack 5 files (for the fast decoding-free error checking feature), one must first recompress by WavPack 4.80 (still available) or lower, and then by WavPack 5.

As of 5.5.0, MacOS versions must be built with e.g. HomeBrew.

WavPack has traditionally had less hardware support than FLAC (Rockbox having been the most notable platform, others listed at https://www.wavpack.com/index.html#Hardware ), but with WavPack playback through Android and iOS players, the distinction between "hardware" and "software" is arguably blurred. There have been issues getting certain Android solutions to recognize media files including WavPack. Third-party support for hybrid-encoded lossless playback (the correction files, see below) might be limited.

Using WavPack

WavPack files can be played back in supported players (see below), and several of these can encode to WavPack, invoking the official tools. However, there are situations where certain WavPack features are accessible only through the WavPack executables directly. For example, you cannot count on RIFF support by encoding through players which often deliver only the audio to the encoder – and you cannot count on such players to restore non-audio data faithfully when decoding. Also, the input format might exceed the player's internal decoding; e.g. trying to convert 32-bit integer or DSD with foobar2000 will yield a warning that it will not be lossless (also, converting DSD to PCM leads to files many times the size, being inherently different formats).

Unlike most other codecs, WavPack has separate encoding and decoding executables (wavpack and wvunpack).

Drag and drop (Windows)

The simplest encoding/decoding might be dragging and dropping a (supported) file to wavpack.exe (/wvunpack.exe). Then the file will be encoded/decoded with the default options. Dropping a .wv file onto wavpack.exe will recompress it, prompting before overwrite (again, using default settings – possibly a bad deal if it was encoded with high -x switches). Drag and drop also works on a shortcut to the executable. It is not possible to drop a folder, but from version 5.5.0, there is a way to drag and drop several files.

From version 5.5.0, drag and drop supports options by renaming the executable. The user can rename a copy of the executable according to preferred settings, which will be applied to the process upon drag and drop. The example given by the developer in in this HA forum post uses encoding options that many WavPack users will recommend (better compression than default, verification and MD5 fingerprinting), and novice users can choose to copy that filename for the executable. For fine-tuning performance or for more specialized tasks, more options are described below.

Basic command line usage (for Windows: command-line hints here)

The basic encoding usage is wavpack filename.extension (which creates filename.wv) – this is what drag and drop accomplishes. Wildcards are supported, e.g. wavpack *.wav. For a single input file, one can specify output like e.g. wavpack infilename.wav -o outfilename.wv (on Windows, the -o can be omitted). Input file extension ".wav" can be dropped, and output ".wv" extension as well – but wavpack foo will only find foo.wav, not e.g. foo.w64.

The basic decoding usage – as will be accomplished by drag and drop – is wvunpack filename.wv. By default, wvunpack will restore the exact same file (metadata and file structure and all), with suffix as appropriate: filename.wav / filename.w64 / filename.caf. (Though WavPack then knows the original input format, it does not store the original file name – but timestamp can be stored by using -t.) If only audio was encoded (from a player, pipe or using -r), output defaults to filename.wav. Just like for the wavpack encoder, file extensions can be dropped; e.g., using wvunpack foo bar will decode foo.wv to bar.wav/bar.w64/bar.caf, extension chosen from original format. This can be overridden by assigning an output fileextension – e.g. wvunpack foo bar.w64 will write a Wave64 file regardless of input format.

Several input files

Wildcards are supported, like wavpack *.wav. To give several filenames as input to wavpack/wvunpack, there are slight differences between the Windows version and the *n*xes: Windows (requires WavPack 5.5.0): use the --drop option as in the above example given by the developer. It is intended for drag and drop (hence the name of the option) and will write the output to same directory as source. However it can also be used with command-line: wavpack --drop firstfile secondfile will compress firstfile.wav to firstfile.wv and secondfile.wav to secondfile.wv. Note that without the --drop, the command wavpack firstfile secondfile will compress firstfile.wav to secondfile.wv, as -o is optional on Windows – indeed that is why the --drop had to be introduced. An arbitrary number of files can be processed, e.g. wvunpack --drop firstfile secondfile thirdfile fourthfile fifthfile will decode firstfile.wv, ..., fifthfile.wv. For *n*x, one can omit the --drop, and it also works with older WavPack versions.

Applying options

For tuning performance or other settings, one might want to apply command-line options. Some external applications can apply options without the user having to type – e.g. encoding with foobar2000, there are two compression sliders, one for the fast-to-extra-high and one for the -x settings (see below) – but in the Windows GUI one will want to type them in. Options can be concatenated for short, like for example writing -hh -x2 -m -v -y as -hhx2mvy.

The user should beware that the wavpack encoder and the wvunpack decoder (and wvtag/wvgain) have to "re-use letters" for different purposes, and e.g. -b, -c do not have related functions upon decoding as upon encoding. However some do the same in the wvunpack and wavpack (like -d for delete input file, -y for "yes to all" and -l for "run with low priority" (Windows only)) – and others cover the same purpose in both executables (like -m and -v).

Encoding options (lossless)

Encoding using -hxm seems a sensible trade-off between compression and CPU load. The manual (online, or included as wavpack_doc.html in the distribution) gives an exhaustive reference, and the following is merely a selection.

• Compression. WavPack has four compression modes that affect compression as well as encoding and decoding time: fast (-f), default, high (-h) and very high (-hh). The CPU load of -hh is measured to around twice that of -f (and could in the early 2000s be too heavy for portable players, although it does decode faster than any Monkey's). On top these modes, the optional extra processing -x1 to -x6 settings will apply extra compression effort that does not increase decoding CPU load. -x without number is synonymous to -x1, which is often recommended (in all modes, fast/normal/high/extra high). The official manual calls -x4 to -x6 "extremely slow", but the size gains might be significant for high resolution audio in particular (van Beurden's revision 5, testing -x4).

With DSD files, there are only two compression settings, normal and high; the option -f will select normal, -h/-hh will both select high, and the -x switches are silently ignored. 5.5.0 introduces optional switches for the default compression: -g for normal mode and -x0 for "no -x". These are redundant for basic use, but can be used to switch off options already given (e.g. in renamed executables, or custom builds): -x6 -x0 will switch off the extra processing, and -h -f -g will encode as normal, whereas previous versions would abort with an error.

• Guarding against errors upon encoding: The "-m" switch will compute an audio MD5 sum (like FLAC does by default) and store it for later verification. The "-v" switch will verify by decoding the file after encoding and writing the file to disk. -vm will do both – that is, calculate the MD5s to verify, and store it. (Using the corresponding switches in wvunpack will check without producing output file, however wvunpack also has a faster corruption check switch -vv for WavPack 5-encoded files.)
• --import-id3 will import ID3v2.3 tags (currently not v2.4 nor v2.2) present in the source file – typically in Sony DSF files – and convert them to WavPack's preferred APE tags. (It will still keep the chunk for restoring the original file.) By default, importing is limited to 1 MB; for more, use --allow-huge-tags. Same option works in wvtag.
• -r: remove extra (non-audio) chunks. By default, WavPack will store these in the .wv file for later bit-by-bit restoration of everything, not only the audio. Use -r to throw them away and encode audio only – like encoding through most players appear to do.
• -t: copy input file's time stamp. (To restore the file with the original time stamp, use -t both when encoding and when decoding.)
• --pause: (Windows only!) waits for keypress at the end. Useful for reading output before exit when calling wavpack/wvunpack in a separate window (which both drag-and-drop the Windows front-end do).
• -y: "yes" to everything. Use with caution, will overwrite. From 5.5.0 there is also a --no-overwrite that will skip instead of asking to overwrite.
• -d: delete source file upon successful completion. Again, use with caution.
• -l will force WavPack to run at low priority (Windows only)
• -c with -b to select lossy quality: hybrid lossless/lossy use, see below.

WavPack can recompress .wv files in place (using a temporary file until done). For example, wavpack -hx4mvy wavpackfile.wv will recompress wavpackfile.wv the file in high mode using -x4 extra processing, write audio MD5 to it, open the temp file and re-read for verification – and once verified, replace the old wavpackfile.wv. Tags will be transferred. wavpack -hx4rlmvy wavpackfile.wv will also run with low priority (assuming the Windows platform), and will discard non-audio chunks – that is, the ones used to restore the original file's metadata; the .wv file's APE tags will still be copied. As an example, one can compress an ID3v2.4-tagged DSF file by drag and drop; WavPack will then store the tag chunk, but WavPack cannot import v2.4. Then open both in Mp3tag, copy the ID3v2.4 tags to the WavPack file, decide that there is no need to restore the original file's ID3v2.4 upon any unpacking, and apply the wavpack -hx4rlmvy wavpackfile.wv command; it will then discard that chunk (but keep the tags that Mp3tag wrote!), recompress using high (silently ignoring the -x4 that has no effect on DSD) with low priority, write an MD5 sum, verify the process and replace the .wv file by the new recompressed file.

(Incomplete:) hybrid lossless & lossy encoding

(Needs to be expanded. Notes: DSD can currently not be hybrid-encoded and floating-point files should not be. The correction file will be omitted by a lot of applications/players, including ffmpeg; thus, using ffmpeg or ffmpeg-based players to convert/play hybrid-encoded WavPack will be lossy.)

Basic use: the -b switch – and for losslessness, with -c to create a correction file. The b takes a numerical value signifying bits per sample if < 24 and kbit/second if 24 to 9600. E.g. -b12.5 (no space in between, with . even if your locale uses comma for decimal point). wavpack -b234.56 -c filename will create filename.wv file and correction file filename.wvc. As long as both are present, playback and decoding (by wvunpack filename the ordinary way) will be lossless. The file filename.wv – which is at most 234.56 kbit/s – can be copied to a different location and played back stand-alone as a lossy compressed file. The same will happen if the .wvc file is deleted or not found (it has to be same path/filename except with the ".wvc" suffix in place of ".wv") – or equivalently, if the -c is omitted during encoding, then no correction file will be created in the first place. For example: wavpack -b13.5 -hx filename will create a lossy filename.wv compressed with the -hx option, size constrained to 13.5 bits per sample. (Should 13.5 bits be sufficient for lossless encoding, WavPack will tell you at the end of the encoding process – but that information is not stored in the file.)

WavPack will refuse to recompress lossy-generated .wv to "lossless .wv" as that would make a false pretense of being a lossless file. It will also refuse so even in the presence of .wvc; you will have to wvunpack it and and then wavpack it again.

(Incomplete:) decoding options

In addition to the basic usage above (drag and drop or wvunpack filename.wv or wvunpack infilename.wv -o outfilename_possibly_with_desired_suffix_to_override_input_filetype.caf), the wvunpack executable offers several options. For use with the Windows front-end or drag and drop, the Windows-only --pause (waits for keypress at the end, like for wavpack.exe) is essential to read the output report. Also Windows-only options like --drop and -l work as for wavpack.exe, and so do -d (use with caution!) and -y (ditto!).

Many of the options are arguably for power users, like for example:

• -b: "blindly" decode until end (potentially useful if a .wv file is corrupted)
• -t: copy input file's time stamp to output file(s)
• switches to force output file format: --wav, --w64, --caf-be, --caf-le, --raw
• some switches to perform lossy operations on floating-point files, DSD streams or dropping hybrid-encoded correction files. See the documentation.
• --skip and/or --until: only decode a portion of the file (again, see documentation)

wvunpack is also the utility to display information from .wv files even when it does not involve decoding, see the next section.

Other file handling

{stub-subsections, incomplete}

Error checking and other file info

wvunpack can get information about WavPack files without decoding to file:

• -vv: Quick verify without decoding (WavPack 5 files only). This functionality seems to be unavailable outside the official wvunpack (other applications which verify will fall back to the next item, -v):
• -v: Verify (will decode to check that everything is OK – but not write any file).
• -s/-ss: -s displays summary of the file, -ss a long summary including tags
• -x FIELD: Shows tag, e.g. -x comment shows the <comment> field. Also wvtag -x does the same thing.
• -c: Like -x cuesheet. Also wvtag -c does the same thing.

(To fill in:) Tagging (wvtag) and replaygain management (wvgain)

(... most of these options are available in HA's fave taggers/player?)

Using WavPack with 3rd party tools (FFmpeg & more)

Some applications may behave slightly surprising. FFmpeg has its own WavPack implementation and has a few known quirks, some which are expected to be fixed and others of unknown status. As referenced above Android users may need to use the player application's folder to get WavPack files recognized. The tl;dr are that as long as it plays, it plays – but to failsafe against loss of information, use the official tools.

Splitting WavPack files by cuesheet

WavPack is a format with good support for storing an album as one .wv file with embedded cuesheets, but splitting into tracks by way of cuesheets is not straightforward without external tools. Audio players like foobar2000 which support cue sheets can also split upon conversion. Other external applications that will do this splitting – also with more variations of the cue sheet format(s) supported – include

• CUETools can if it is CDDA (44.1 kHz 16-bit stereo), and can re-encode back to WavPack.
• refalac can decode & split by cuesheets with the appropriate (official) WavPack library DLL file, outputting WAVE or ALAC-in-MP4.

Both refalac, CUETools and foobar2000 use the official WavPack tools to for the decoding(/encoding).

FFmpeg's WavPack implementation: differences and quirks

FFmpeg can encode/decode to/from WavPack – which may be seen as attractive from how it also can transfer metadata in one go – but with some limitations and maybe unfamiliar behaviour.

• FFmpeg can decode WavPack 5 files, but will only write WavPack 4 (thus, no fast verification). Also, compression presets are different, defaulting to fast but not particularly good compression. On the other end, FFmpeg offers even slower modes than -hhx6.
• A rare bug in FFmpeg's WavPack decoder was discovered in August 2022. A fix was coded, and is expected to find its way into official ffmpeg in a few months. However, players and converters that employ ffmpeg as a decoding engine may or may not update that quickly. The bug is "rare" in that a signal that triggers it was not found in the wild over several years, but the example file found will have dropouts when decoded by ffmpeg.
• There is potential information loss in using FFmpeg; it will ignore hybrid correction files, so decoding/playing hybrid-encoded WavPack with ffmpeg or ffmpeg-based players will be lossy. Furthermore, ffmpeg will not honour the input bitrate: it will default to 16 bits when outputting WAVE/AIFF, whether or not the input file is 16 bits; this could even induce clipping (with no warning!) if the source is a 32-bit float. To force lossless decoding of a 24-bit/32-bit .wv to WAVE/AIFF, 24-bit/32-bit output must be specified using ffmpeg's command-line syntax; users who do not have this at their fingertips, are advised to use official wvunpack to .wav. For AIFF, a method going by way of CAF is given below.
• Also ffmpeg will discard RIFF chunks and file structure. It has no ambition of preserving file structure, but it will by default transfer metadata it supports.
• FFmpeg will sometimes – depending on input format – output 32-bit WavPack files and lose the information that the source was indeed only 24. Not all players support 32-bit files, and verifying that the operation (or an attempted downconversion to 24) was lossless is not straightforward as even fewer applications are willing to compare a 32-bit and a 24-bit file for differences.

From/to AIFF – preserving bit depth, using FFmpeg

Reference WavPack will encode a 20-bit (or 17, for that matter) .wav file and keep the information that it is 20 (/17) bits. FFmpeg on the other hand, will delete the information that it was ever 20 (/17) bits. Also, FFmpeg will by default produce 16-bits WAVE/AIFF files, and additional specification must be applied to ensure lossless decoding of 24-bit files; safest is to use wvunpack to decode, but reference WavPack cannot handle .aiff. It does handle .caf, so the following procedure and preserve bit depth, divisible by 8 or not:

• To decode .wv to .wav or .caf and preserve bit depth: Use wvunpack and not ffmpeg.
• To decode .wv to AIFF and preserve bit depth: wvunpack "infile.wv" --caf-be - | ffmpeg -i - -codec copy "outfile.aiff". This will use wvunpack to decode to a .caf file that preserves bit depth, and then tell ffmpeg to only transfer this stream to an .aiff container.
• To encode AIFF, possibly with bit depths like 17 preserved: There are AIFF to WAVE conversion software that will preserve bit depth flags (here ffmpeg doesn't), but presuming a a lossless audio user has flac.exe around: flac --fast --lax "AIFF-infile.aiff" -o - | flac -d - -o - | wavpack - "WavPack-outfile.wv" will do a flac encode/decode (provided bit depth is supported by FLAC; use a recent one for 25 to 32).

Software support (& hardware)

With Android support and playback through ffmpeg, it might no longer be feasible to maintain a list of applications that can play WavPack files, and the following is most certainly incomplete – as is the list at https://www.wavpack.com/#Software . Also, the distinction between "hardware" and "software" support is not clear in the age of smart devices running Android, and the list at https://www.wavpack.com/#Hardware does not cover those.

Players

• foobar2000 advanced freeware audio player plays/decodes WavPack out of the box on both Windows, MacOS, Android and iOS (Windows: supports encoding if wavpack.exe is installed, and redistributes the official wavpack.exe through its "Free encoder pack" addon for encoding. With ReplayGain & cuesheets support.) Also Boom from the same author.
• VLC multiplatform media player
• VUPlayer (official plugin, supports encoding)
• NullSoft Winamp (plugin with ReplayGain & Media Library support) and Winamp-compatible players
• Windows Media Player and other directshow-based players (MPC, TCMP, RadLight) (with CoreWavPack directshow filter)
• Cog Audio player for MacOS X.
• JRiver Media Center
• XMMS (with Kuniklo's plugin)
• LAMIP (official plugin)
• MPXplay for DOS!
• Aqualung for GNU/Linux
• Cowon JetAudio Player and CD ripper
• XMPlay Plugin required (WavPack input plugin) and (bass library) to play 'wv' files

Converters, CD rippers etc.

Several of the players, like Cowon JetAudio, foobar2000 and VUplayer, also have converters that can create WavPack files. More:

• Custom Windows WavPack frontend (by Speekenbrink)
• dBpowerAMP Music Converter CD ripper/writer / Audio Player / (official addon)
• fre:ac multi-platform CD ripper/converter
• Exact Audio Copy CD Ripper (guide at this wiki)
• Nero
• CDex CD ripper
• Ease Audio Converter (Shareware / NOT Freeware)
• Media.io Online Audio Converter
• Konvertor
• CUETools converter and AccurateRip/CTDB checker
• refalac

Taggers

• Mp3tag Universal Tag Editor
• MusicBrainz Picard Tagger with audio identification
• The GodFather Tagger / Music manager
• Case's Tag command line tagger

Other tools

• Adobe Audition and Cool Edit (filter with 32-bit floats & extra info save support)
• Mr. QuestionMan
• mkvtoolnix – tool to multiplex WavPack streams inside the Matroska container

It's worth mentioning the Matroska guys decided to concentrate on WavPack as the lossless compressor of choice for their container. Quite an honor... :-)

• PKWare's .zip format compresses audio by WavPack since version 6.3.2 (2007). Beware that there is no expectation that other decompression software handles these zip files; even if PKWare co-designed the format and PKZip was the original .zip implementation, their subsequent compression methods are outside the ISO/IEC standardized zip format specification.

Links

• Official website
• Github repository
• Unofficial 4.32 multiplatform versions at RareWares
• WavPack at Wikipedia
• WavPack at Multimediawiki (not updated with version 5)
• HA Wiki's Lossless Codec Comparison originally by Rjamorim
• An older (2005) performance comparison of lossless audio compressors (archived on October 27, 2015) by Speek, using WavPack version 4.0