Talk:cdparanoia

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


[untitled][edit]

Eh??

Paranoia III is NOT Linux-specific. I'm using it on BeOS. BeOS isn't Linux. --Kiand 13:07, 28 May 2005 (UTC)[reply]

It is definitely Linux/GCC specific. The code depends on GCC extensions that are unknown in C and there is definitely no BEOS support in the source. — Preceding unsigned comment added by 87.158.110.240 (talk) 21:48, 13 September 2008‎
Surely GCC is GNU, not Linux. —Ringbang (talk) 14:20, 30 January 2017 (UTC)[reply]

Definitely more portable[edit]

It is most definitely not Linux-only. For example, the pkgsrc package for cdparanoia has:

ONLY_FOR_PLATFORM= FreeBSD-*-* NetBSD-*-* Linux-*-* DragonFly-*-* Darwin-*-*

And it's part of FreeBSD ports and works perfectly.

I am not sure to what extent multiple platforms are supported in the upstream repository, but certainly from a practical standpoint cdparanoia is available on multiple platforms. Scode

It's also in OpenBSD's native packages/ports. --Mike 22:15, 24 May 2007 (UTC)[reply]
Cdparanoia started as a patch on cdda2wav in 1997. libparanoia did not exist before the cdrtools project extracted the code from cdparanoia and made the code portable in April 2002. The code conversion made for the cdrtools project includes rewriting the code to clean C and changing the interfaces to allow it to be used as a clean library. Later (in February 2007) the interfaces was slightly changes again to support problems found in the Mac OS X dynamic linker. On May 6th 2006, Monty did give the permission to change the license from GPL to LGPLv2.1. The code in cdrtools now includes many bug-fixes mainly to prevent memory leaks and core dumps from memory access problems. The code in cdparanoia-III-10.2 still does not include the library version, it just added comments to the paranoia code. 87.158.110.240 (talk) 21:48, 13 September 2008 (UTC)[reply]

argument validity[edit]

Unfortunately, most rippers cannot work properly with a large number of CDROM drives in the desktop world today. The most common problem is sporadic or regular clicks and pops in the read sample, regardless of options or settings. The great lesson from coding software for CDROMS the past 15 years is that drives that don't have bugs reading digital audio are exceptionally rare.

(http://xiph.org/paranoia/faq.html#usecdparanoia) — Preceding unsigned comment added by 2A02:908:D510:6D20:4448:6861:A258:874F (talk) 07:58, 28 May 2016 (UTC)[reply]