Live data from Hacker News

Whipper: Accurate Audio CD Ripping

github.com

81–90 of 217 posts

Re: Whipper: Accurate Audio CD Ripping

#81
post #39

>Docker Maybe it's just me but when I see Docker with a project like this I already zone out. This is still just based on cdparanoia/cdrdao [0]. I wish people would just push single portable binaries instead of starting the whole process with Docker (especially when the source code is alreaedy available) 0, https://github.com/whipper-team/whipper/blob/develop/whipper... 0, https://github.com/whipper-team/whipper/blob…

Docker is a life saver if your shipping software on Linux. Otherwise you’re going to have to deal with endless bug reports from oddball distros. Docker lets you test with a stable set of dependencies and know that’s what your users will see.

There's no obligation to support every distro on the planet.

Re: Whipper: Accurate Audio CD Ripping

#83
post #3

This is pretty cool, it's like a Python and *nix version of Exact Audio Copy (EAC) for Windows. I enjoy the ritual of perfectly ripping a CD. I can spend an hour or two scanning the artwork, verifying the track names, performing the rip, losslessly compressing (I prefer FLAC), generating .cue files, checksuming everything, then sitting down to experience the best possible digital copy of a physical item I can self pr…

Years ago, I had most of my music ripped to AAC in iTunes, easily accessible, browsable, and shuffleable. I now rip each of my CDs to a single FLAC and cue sheet (using XLD on Mac), on the theory that it's the most accurate way to archive a disc. However, I haven't found anything that offers the same accessibility to such a collection as iTunes did. I look through folders, and drag a few cue sheets at a time into Foo…

Hard drive space is cheap. Do both.

Re: Whipper: Accurate Audio CD Ripping

#84
That's a nice package. I use some of the components on the command line to get my CD data to the music server.

Extract data to wav:

    cdparanoia -B
Compress all wavs to mp3 (in parallel, takes like 1 second, crazy!):

    parallel lame --preset extreme {} -o {.}.mp3 ::: *.wav
Clean up folder

    rm *.wav
Import into mopidy library and lookup/apply metadata with beets

    beet import .
    sudo su - mopidy -s /bin/bash -c 'mopidy --config /etc/mopidy/mopidy.conf local scan'
(I actually have a bash script for that, obviously)

Done. Next step is to go into Mopidy-Iris UI and hit play and it plays all around the house thanks to snapcast. Garsh darn glorious.

https://mopidy.com/ext/iris/

https://mjaggard.github.io/snapcast/

https://beets.readthedocs.io/en/stable/

Re: Whipper: Accurate Audio CD Ripping

#85

>Docker Maybe it's just me but when I see Docker with a project like this I already zone out. This is still just based on cdparanoia/cdrdao [0]. I wish people would just push single portable binaries instead of starting the whole process with Docker (especially when the source code is alreaedy available) 0, https://github.com/whipper-team/whipper/blob/develop/whipper... 0, https://github.com/whipper-team/whipper/blob…

Packages are available for just about any distro in the next heading. Source is available as well (obviously). Still not a single binary but as you note with it being written in python and based on cdparanoia, etc how would that work? It's based on python with relatively obscure requirements[0] that also calls out to system binaries. Looking at the Dockerfile[1] it is built with specific revs of component software to…

> Still not a single binary but as you note with it being written in python and based on cdparanoia, etc how would that work?

Cosmopolitan python is a good starting point: https://ahgamut.github.io/2021/07/13/ape-python/

> IMO Docker is one of the "best" and most straightforward ways to package up all of this

No. Using containers has its place. But would you use containers on hello world?

Likewise, if you've got to use a container for cd ripping tool, you've failed somewhere.

Re: Whipper: Accurate Audio CD Ripping

#86
post #81
post #39

Earlier quoted context omitted.

Docker is a life saver if your shipping software on Linux. Otherwise you’re going to have to deal with endless bug reports from oddball distros. Docker lets you test with a stable set of dependencies and know that’s what your users will see.

There's no obligation to support every distro on the planet.

[deleted]

Re: Whipper: Accurate Audio CD Ripping

#87
post #81
post #39

Earlier quoted context omitted.

Docker is a life saver if your shipping software on Linux. Otherwise you’re going to have to deal with endless bug reports from oddball distros. Docker lets you test with a stable set of dependencies and know that’s what your users will see.

There's no obligation to support every distro on the planet.

If you’ve run an open source project you will get these bug reports. It’s also not obvious if it’s a bug in your code or a dependency many times so you’re going to want to debug it.

As an example alpine has a smaller default stack size. It’s not obvious if that stack overflow is expected or not.

Re: Whipper: Accurate Audio CD Ripping

#88
post #85

Earlier quoted context omitted.

Packages are available for just about any distro in the next heading. Source is available as well (obviously). Still not a single binary but as you note with it being written in python and based on cdparanoia, etc how would that work? It's based on python with relatively obscure requirements[0] that also calls out to system binaries. Looking at the Dockerfile[1] it is built with specific revs of component software to…

> Still not a single binary but as you note with it being written in python and based on cdparanoia, etc how would that work? Cosmopolitan python is a good starting point: https://ahgamut.github.io/2021/07/13/ape-python/ > IMO Docker is one of the "best" and most straightforward ways to package up all of this No. Using containers has its place. But would you use containers on hello world? Likewise, if you've got to u…

The post you're replying to gave several reasons why something like Cosmopolitan Python is not sufficient.

This is nothing like hello world.

Re: Whipper: Accurate Audio CD Ripping

#89

So why would ripping CDs result in less than perfect copies - I thought digital information would almost always be read correctly?

Some CDs are very scratched. Some CDs are CDRs with dye that hasn't aged well. Some CDs just don't read well (poor manufacturing tolerance, perhaps). Some drives silently return bad data on error. Some drives return a lot of errors towards the last tracks even when there is no problem. Drives vary on where they think tracks start and end (generally a uniform offset per drive). Sometimes, reading audio before the claimed start of the CD takes extra trickery. There are many more issues, besides. By ripping multiple times to verify and comparing to a global database of checksums (and in some cases doing error correction), you can be sure of getting exactly the intended audio.

Re: Whipper: Accurate Audio CD Ripping

#90
post #3

This is pretty cool, it's like a Python and *nix version of Exact Audio Copy (EAC) for Windows. I enjoy the ritual of perfectly ripping a CD. I can spend an hour or two scanning the artwork, verifying the track names, performing the rip, losslessly compressing (I prefer FLAC), generating .cue files, checksuming everything, then sitting down to experience the best possible digital copy of a physical item I can self pr…

Just in case anyone was wondering, EAC works without a hitch with WINE on Linux.
Post reply on HN