Live data from Hacker News

Whipper: Accurate Audio CD Ripping

github.com

51–60 of 217 posts

Re: Whipper: Accurate Audio CD Ripping

#51

>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…

Funny, I was already pre-sad that it probably wasn't dockerized. Wonder if I can combine this with another docker project and this will rip CD's and the other will rip DVD's automatically?

> the other will rip DVD's automatically?

Do you have a specific project in mind that does DVDs?

Re: Whipper: Accurate Audio CD Ripping

#52
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.

It's like people forget statically compiled binaries exist

Re: Whipper: Accurate Audio CD Ripping

#53
post #47

I love how this software would have been legend in the 90s/00s but now you are just a weird audiophile nerd for messing around with physical CDs.

In the 00s you just used Exact Audio Copy

Still used in Russia constantly. It's the gold standard.

Re: Whipper: Accurate Audio CD Ripping

#54
post #15
post #11

Can someone explain to me why this is needed vs an imagining tool (say ddrescue)? Is there no tool that actually makes a bit perfect copy yet?

ddrescue can't read audio tracks, Audio CDs doesn't have a file system in the traditional sense either etc. It's not meant for copy Audio CDs but CD-ROMs That's why CDRDAO or CDDA Paranoia exist for decades. https://web.archive.org/web/20160528213242/https://thomas.ap... https://www.xiph.org/paranoia/ https://cdrdao.sourceforge.net/

Well, ddrescue can definitely “read audio tracks” and is perfectly suited for making archival copies of Audio CDs but it sounds like the problem you’re actually trying to solve is interpreting the data as Red Book CD-DA and decoding it into chunks you call files ;)

Re: Whipper: Accurate Audio CD Ripping

#55
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.

It's like people forget statically compiled binaries exist

[deleted]

Re: Whipper: Accurate Audio CD Ripping

#56
Somewhat related question: what's the gold standard for organizing ripped music, ideally with some sort of metadata lookup? Ever since Google Music shut down, I have my exported music in a folder, but it's badly organized and with duplicates. Too daunting a task for me to do manually - especially because some of the id3 tags somehow got messed up.

Re: Whipper: Accurate Audio CD Ripping

#57

>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…

I concur. And a standalone program written in Python. I like Python the language, but running someone else's python code is a mess. Look at the build/dependencies etc sections on the page. What it should be: "Download and install this binary for Win, this for Linux, or this for Mac. Run it to use (or install depending on complexity) the program.

Or, if building from source is desired for whatever reason, it should be "Clone the repo. Run `cargo build --release` or w/e.

Re: Whipper: Accurate Audio CD Ripping

#59

Somewhat related question: what's the gold standard for organizing ripped music, ideally with some sort of metadata lookup? Ever since Google Music shut down, I have my exported music in a folder, but it's badly organized and with duplicates. Too daunting a task for me to do manually - especially because some of the id3 tags somehow got messed up.

Picard has worked really well for me.

https://picard.musicbrainz.org/

Re: Whipper: Accurate Audio CD Ripping

#60
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.

How about flatpak? To fulfil this function?
Post reply on HN