71–80 of 217 posts
Earlier quoted context omitted.
Always makes me sad remembering what was lost when What.CD went offline.
And Oink before it. But the torch has been passed to the next community, not all has been lost
>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 undeniably useful and pragmatic, but its existence should be a source of shame, a constant reminder that we failed.
>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.
As a user/self-administrator, I really do not appreciate a developer throwing a ton of incidental complexity over the wall. Docker is basically a scaling up of the "works on my system" cop out.
I get that there are a lot of oddball distros, but it would seem that a policy of only digging into bug reports on specific well known distros would be more appropriate than basically forgoing the entire concept of a distribution in favor of what are essentially huge static binaries.
It's especially a problem when projects go nuts with this Dockerization anti-pattern, and become actively hostile to distributions shipping plainly administerable versions of their software (looking at you Home Assistant).
Earlier quoted context omitted.
This type of ripping, comparing to other rips (paranoia) for bit-for-bit error correction integrity is part of XLD for Mac et al. However, even as a full time audio person, I consider paranoia overkill, and in someways backwards - I want my rip to be my unique rip and not precisely anyone else's - though of course, it most likely is anyway. You do realise, assuming you ripped to a lossless audio format, your cd rips…
> 8-12x more accurate than anything streamed of Spotify Maybe in theory. In practice, the difference will be very hard to hear (for most people, in most scenarios). Have you ever done an ABX test to determine whether you would be able to tell the difference between lossless and Spotify's quality?[1] I did, a while back, and while I was able to tell the difference somewhat reliably for music I knew well (and only for…
My go-to CD ripper is https://github.com/cyanreg/cyanrip
So why would ripping CDs result in less than perfect copies - I thought digital information would almost always be read correctly?
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.
How about flatpak? To fulfil this function?