* standardise program/sox.py formatting, add test case
* add program/sox.peak_level() docstring
* update .travis.yml to include sox as a test dependency
* move sox from test dependency to normal dependency
* update README to mention sox, remove small autoconf mention
* use .splitlines() instead of .split('n')
* slightly updated the README file
* updated morituri version number in cue tests
* commented out a portion of testAccurateRipChecksum (it should be updated/fixed later on)
* update README to force python2
* add support for PRE_EMPHASIS detection; mark pre-emphasis as FLAGS PRE in .cue
* correct typo, s/ivar/type/ for pre_emphasis element in track table
* add SoxPeakTask, program/sox module, sox.peak_level()
* use sox peak detection in lieu of gstreamer
There are still some changes required to make whipper handle ARv2 checksums,
currently doesn't call the Task for a V2 checksum. V1 should keep working as-is.
* Address issue #24
* Remove getReadCaches() & replace it with getCache()
Now whipper always follows XDG specifications. All changes were documented into the README file.
The changes introduced here aren't backward compatible so, after updating whipper, you may need to configure it again (old config file are retained, though).
* update README to force python2
* add support for PRE_EMPHASIS detection; mark pre-emphasis as FLAGS PRE in .cue
* correct typo, s/ivar/type/ for pre_emphasis element in track table
Hopefully this one fixes a privately reported regression introduced
with the previous commit.
```python
TypeError: unsupported operand type(s) for %: 'NoneType' and 'tuple'
```
Changes:
* whipper is now capable of handling musicbrainzngs’ bad server
responses (it throws an exception).
* whipper is now aware of musicbrainzngs’ possible “cdstub” response
and should handle it fine (ignoring the result because the informations
received are incomplete e/o unverified).
This commit should fixJoeLametta/whipper#22
* Avoid including AccurateRip result for HTOA (corrected)
* Pedantic fix
* Check (and mention in the logfile) if the rip was done with the
`--force-overread` (or `-x`) switch enabled
