[xiph-commits] r14872 - in trunk/cdparanoia: . interface paranoia
xiphmont at svn.xiph.org
xiphmont at svn.xiph.org
Mon May 12 11:35:13 PDT 2008
Author: xiphmont
Date: 2008-05-12 11:35:13 -0700 (Mon, 12 May 2008)
New Revision: 14872
Added:
trunk/cdparanoia/COPYING-GPL
trunk/cdparanoia/COPYING-LGPL
Removed:
trunk/cdparanoia/FAQ.txt
trunk/cdparanoia/GPL
Modified:
trunk/cdparanoia/README
trunk/cdparanoia/cdparanoia.1
trunk/cdparanoia/header.c
trunk/cdparanoia/header.h
trunk/cdparanoia/interface/cdda_interface.h
trunk/cdparanoia/interface/common_interface.c
trunk/cdparanoia/interface/common_interface.h
trunk/cdparanoia/interface/cooked_interface.c
trunk/cdparanoia/interface/interface.c
trunk/cdparanoia/interface/low_interface.h
trunk/cdparanoia/interface/scan_devices.c
trunk/cdparanoia/interface/scsi_interface.c
trunk/cdparanoia/interface/smallft.c
trunk/cdparanoia/interface/smallft.h
trunk/cdparanoia/interface/test_interface.c
trunk/cdparanoia/interface/toc.c
trunk/cdparanoia/main.c
trunk/cdparanoia/paranoia/cdda_paranoia.h
trunk/cdparanoia/paranoia/gap.c
trunk/cdparanoia/paranoia/gap.h
trunk/cdparanoia/paranoia/isort.c
trunk/cdparanoia/paranoia/isort.h
trunk/cdparanoia/paranoia/overlap.c
trunk/cdparanoia/paranoia/overlap.h
trunk/cdparanoia/paranoia/p_block.h
trunk/cdparanoia/paranoia/paranoia.c
trunk/cdparanoia/version.h
Log:
Relicense libs to LGPL3, update main license to GPL3
Added: trunk/cdparanoia/COPYING-GPL
===================================================================
--- trunk/cdparanoia/COPYING-GPL (rev 0)
+++ trunk/cdparanoia/COPYING-GPL 2008-05-12 18:35:13 UTC (rev 14872)
@@ -0,0 +1,677 @@
+The cdparanoia command line tool is covered by the GNU General Public
+Licence v3.
+
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
Added: trunk/cdparanoia/COPYING-LGPL
===================================================================
--- trunk/cdparanoia/COPYING-LGPL (rev 0)
+++ trunk/cdparanoia/COPYING-LGPL 2008-05-12 18:35:13 UTC (rev 14872)
@@ -0,0 +1,168 @@
+The cdda-interface and cdda-paranoia libraries are covered by the GNU
+Lesser General Public License v3.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+ This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+ 0. Additional Definitions.
+
+ As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+ "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+ An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+ A "Combined Work" is a work produced by combining or linking an
+Application with the Library. The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+ The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+ The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+ 1. Exception to Section 3 of the GNU GPL.
+
+ You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+ 2. Conveying Modified Versions.
+
+ If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+ a) under this License, provided that you make a good faith effort to
+ ensure that, in the event an Application does not supply the
+ function or data, the facility still operates, and performs
+ whatever part of its purpose remains meaningful, or
+
+ b) under the GNU GPL, with none of the additional permissions of
+ this License applicable to that copy.
+
+ 3. Object Code Incorporating Material from Library Header Files.
+
+ The object code form of an Application may incorporate material from
+a header file that is part of the Library. You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+ a) Give prominent notice with each copy of the object code that the
+ Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the object code with a copy of the GNU GPL and this license
+ document.
+
+ 4. Combined Works.
+
+ You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+ a) Give prominent notice with each copy of the Combined Work that
+ the Library is used in it and that the Library and its use are
+ covered by this License.
+
+ b) Accompany the Combined Work with a copy of the GNU GPL and this license
+ document.
+
+ c) For a Combined Work that displays copyright notices during
+ execution, include the copyright notice for the Library among
+ these notices, as well as a reference directing the user to the
+ copies of the GNU GPL and this license document.
+
+ d) Do one of the following:
+
+ 0) Convey the Minimal Corresponding Source under the terms of this
+ License, and the Corresponding Application Code in a form
+ suitable for, and under terms that permit, the user to
+ recombine or relink the Application with a modified version of
+ the Linked Version to produce a modified Combined Work, in the
+ manner specified by section 6 of the GNU GPL for conveying
+ Corresponding Source.
+
+ 1) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (a) uses at run time
+ a copy of the Library already present on the user's computer
+ system, and (b) will operate properly with a modified version
+ of the Library that is interface-compatible with the Linked
+ Version.
+
+ e) Provide Installation Information, but only if you would otherwise
+ be required to provide such information under section 6 of the
+ GNU GPL, and only to the extent that such information is
+ necessary to install and execute a modified version of the
+ Combined Work produced by recombining or relinking the
+ Application with a modified version of the Linked Version. (If
+ you use option 4d0, the Installation Information must accompany
+ the Minimal Corresponding Source and Corresponding Application
+ Code. If you use option 4d1, you must provide the Installation
+ Information in the manner specified by section 6 of the GNU GPL
+ for conveying Corresponding Source.)
+
+ 5. Combined Libraries.
+
+ You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+ a) Accompany the combined library with a copy of the same work based
+ on the Library, uncombined with any other library facilities,
+ conveyed under the terms of this License.
+
+ b) Give prominent notice with the combined library that part of it
+ is a work based on the Library, and explaining where to find the
+ accompanying uncombined form of the same work.
+
+ 6. Revised Versions of the GNU Lesser General Public License.
+
+ The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+ If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
Deleted: trunk/cdparanoia/FAQ.txt
===================================================================
--- trunk/cdparanoia/FAQ.txt 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/FAQ.txt 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,620 +0,0 @@
-
-CDDA Paranoia FAQ
-
-----------------------------------------------------------------------------
-
- "Suspicion Breeds Confidence!"
- --Brazil
-
-----------------------------------------------------------------------------
-
-August 20, 1999
-
-For those new to Paranoia and cdparanoia, this is the
-best, first place to look for information and answers to
-your questions.
-
-More information can be found on the cdparanoia homepage:
-
-http://www.xiph.org/paranoia/
-
-----------------------------------------------------------------------------
-Table of Contents
-
-1. Questions about the Paranoia and cdparanoia projects
- 1. What is cdparanoia?
- 2. Why use cdparanoia?
- 3. What is Paranoia?
- 4. Is cdparanoia / Paranoia portable?
- 5. What is Paranoia's history?
- 6. Is cdparanoia/Paranoia related to cdda2wav?
- 7. What are the differences between Paranoia II, III and IV?
- 8. Are there cdparanoia mailing lists for users or developers?
- 9. What is Paranoia IV's current development status?
- 10. Will cdparanoia, and cdda2wav or xcdroast merge anytime in the future?
-
-2. Questions about using Paranoia and cdparanoia
- 1. Requirements to run cdparanoia (as of alpha 3)
- 2. Does Cdparanoia support ATAPI drives? SCSI Emulation? Parallel port
- drives?
- 3. I can play audio CDs perfectly; why is reading the CD into a file so
- difficult and prone to errors?
- 4. Does cdparanoia lose quality from the CD recording?
- 5. Can cdparanoia detect pregaps? Can it remove the two second gaps
- between tracks?
- 6. Why don't you implement CDDB? A GUI? Four million other features I want?
- 7. The progress meter: What is that weird bargraph during ripping?
- 8. How can I tell if my drive would be OK with regular cdda2wav?
- 9. What is the biggest value of SG_BIG_BUFF I can use?
- 10. Why do the binary files from two reads differ when compared?
- 11. Why does CDParanoia rip files off into WAV format (and other sample
- formats) but not CDDA format?
-
--------------------------------------------------------------------------
-
- Questions about the Paranoia and cdparanoia projects
-
- What is cdparanoia?
-
- Cdparanoia is a Compact Disc Digital Audio (CDDA) extraction tool,
- commonly known on the net as a 'ripper'. The application is built on
- top of the Paranoia library, which is doing the real work (the
- Paranoia source is included in the cdparanoia source distribution).
- Like the original cdda2wav, cdparanoia package reads audio from the
- CDROM directly as data, with no analog step between, and writes the
- data to a file or pipe in WAV, AIFC or raw 16 bit linear PCM.
-
- Cdparanoia is a bit different than most other CDDA extration tools. It
- contains few-to-no 'extra' features, concentrating only on the ripping
- process and knowing as much as possible about the hardware performing
- it. Cdparanoia will read correct, rock-solid audio data from
- inexpensive drives prone to misalignment, frame jitter and loss of
- streaming during atomic reads. Cdparanoia will also read and repair
- data from CDs that have been damaged in some way.
-
- At the same time, however, cdparanoia turns out to be easy to use and
- administrate; It has no compile time configuration, happily
- autodetecting the CDROM, its type, its interface and other aspects of
- the ripping process at runtime. A single binary can serve the diverse
- hardware of the do-it-yourself computer laboratory from Hell...
-
------------------------------------------------------------------------
-
- Why use cdparanoia?
-
- All CDROM drives are not created equal. You'll need cdparanoia if
- yours is a little less equal than others-- or maybe you just keep your
- CD collection in a box of full of gravel. Jewel cases are for wimps;
- you know what I'm talking about.
-
- Unfortunately, cdda2wav and readcdda 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 'nsector' or 'overlap' settings. Cdda2wav also cannot do
- anything about scratches (and they can cause cdda2wav to break).
- Cdparanoia is also smarter about probing CDDA support from SCSI and
- IDE-SCSI drives; many drives that do not work at all with cdda2wav,
- readcdda, tosha, etc, will work just fine with cdparanoia.
-
------------------------------------------------------------------------
-
- What is Paranoia?
-
- Paranoia is a library project that provides a platform independent,
- unified, robust interface for packet-command based devices. In the
- case of CDROM drives for example, handling and programming cdrom
- drives becomes identical whether on Solaris or Linux, or if the Linux
- drive is SCSI, ATAPI or on the parallel port. In this way, Paranoia is
- similar to Joerg Schilling's SCG library.
-
- In addition to device/platform unification, the library provides tools
- for automatically identifying devices, and intelligent
- handling/correction of errors at all levels of the interface. On top
- of a generic low-level packet command layer, Paranoia implements
- high-level error-correcting interfaces for tasks such as CDDA where
- broken or vastly non-standard devices are the rule, rather than the
- exception.
-
- The Paranoia libraries are incomplete; the first release for use will
- be Paranoia IV, to be bundled with cdparanoia alpha release 10.
- Programming documentation for Paranoia IV will appear shortly on the
- documentation page as Programming with Paranoia IV. Programmers
- interested in contributing to Paranoia IV should read the heading
- Paranoia IV development information.
-
------------------------------------------------------------------------
-
- Is cdparanoia / Paranoia portable?
-
- Paranoia III is Linux only (although it runs on all the flavors of
- linux with a 2.0 or later kernel. It is not only for x86).
-
- Paranoia IV (cdparanoia alpha 10 and later) is a port to other UNIX
- flavors and uses a substantially revised infrastructure. NetBSD and
- Solaris will be first; others will be added as time and outside
- assistance allow.
-
- Suggestions on the proper way to handle each OS's native configuration
- idioms are welcome. I want Rhapsody cdparanoia to look just like other
- Rhapsody apps just as much as I want Linux cdparanoia to look like a
- Linux app.
-
------------------------------------------------------------------------
-
- What is Paranoia's history?
-
- Is cdparanoia/Paranoia related to cdda2wav?
-
- Paranoia I/II and cdparanoia began life as a set of patches to Heiko
- Eissfeldt's 'cdda2wav' application. Cdparanoia gained its own life as
- a rewrite of cdda2wav in January of 1998 as "Paranoia III". Paranoia
- III proved to have an inadequate structure for extention and use on
- other platforms, so Paranoia IV began to take form in fall of 1998.
-
- Modern Paranoia no longer has any relation to cdda2wav aside from
- general cooperation in sharing details between the two projects. In
- fact, cdda2wav itself doesn't look much like the cdda2wav of a year or
- two ago.
-
------------------------------------------------------------------------
-
- What are the differences between Paranoia II, III and IV?
-
- Paranoia I and II were a set of patches to Heiko Eissfeldt's cdda2wav
- 0.8. These patches did nothing more than add some error checks to the
- standard cdda2wav. They were inefficient and only worked with some
- drives.
-
- Paranoia III was the first version to be written seperately from
- cdda2wav in the form of a standalone library. It was not terribly
- portable, however, and the API proved to be inadequate for extension.
-
- Paranoia IV is the upcoming new generation of CDDA Paranoia. It is
- both portable and more capable than Paranoia III.
-
------------------------------------------------------------------------
-
- Are there cdparanoia mailing lists for users or developers?
-
- Yes. In addition to the mailing lists below, read-only CVS access to
- Paranoia III and IV will be availble from xiph.org soon (Paranoia IV
- is not yet under CVS). See http://www.xiph.org/paranoia/ for upto
- date information and automated ways of subscribing.
-
- Mailing list for Paranoia and Cdparanoia users (paranoia at xiph.org):
-
- To join: send a message containing only the one-word line
- 'subscribe' in the body to paranoia-request at xiph.org. Do not send
- subscription requests directly to the main list. The list server at
- xiph.org should respond fairly quickly with a welcome message.
-
- Mailing list for Paranoia IV developers: paranoia-dev at xiph.org
-
- The developers list is intended for focused development discussion
- amongst the core Paranoia development team and outside groups
- developing their own applications using Paranoia. Of course, anyone is
- welcome to read.
-
- To join: send a message containing only the one-word line
- 'subscribe' in the body to paranoia-dev-request at xiph.org. Do not
- send subscription requests directly to the main list.
-
- List for general CDROM tools
-
- There's also a general mailing list for those using/developing CDDA
- extraction and CD writing tools
- (cdwrite at other.debian.org). Subscribe by sending mail to
- other-cdwrite-request at lists.debian.org containing only the word
- subscribe in the body. Do not send subscription requests directly to
- the main list.
-
------------------------------------------------------------------------
-
- What is Paranoia IV's current development status?
-
- Paranoia IV code will soon be available for internal evaluation,
- testing and development work to the developers involved in the
- Paranoia project; read-only CVS access should also be available soon.
- A public release does not yet set for any firm date.
-
- Those interested in contributing to the development of Paranoia, or
- who wich to contribute to porting to other platforms, please contact
- us. Paranoia IV prerelease code will be available to porters soon; I
- prefer to be in contact with those porting to other platforms so that
- Paranoia development has consistent quality across platforms.
-
- At the moment, volunteers have contacted me for most major platforms,
- but more help is still welcome on every OS.
-
------------------------------------------------------------------------
-
- Will cdparanoia, and cdda2wav or xcdroast merge anytime in the future?
-
- Probably not beyond the point it already has. Versions of XCDRoast
- (and other GUI frontends; see the links page) that make use of
- cdparanoia already exist.
-
- Although the cdrecord/cdda2wav and Paranoia projects cooperate,
- they're likely to remain seperate as the former is committed to Joerg
- Schilling's libscg (part of the cdrecord package), just as cdparanoia
- is committed to using Paranoia IV.
-
------------------------------------------------------------------------
-
- Questions about using Paranoia and cdparanoia
-
- Requirements to run cdparanoia (as of alpha 3)
-
- 1. A CDDA capable CDROM drive
- 2. Linux 2.0, 2.1, 2.2 or 2.3
- 1. kernel support for the particular CDROM in use
- 2. kernel support for the generic SCSI interface (if using a
- SCSI CDROM drive) and proper device (/dev/sg?) files (get
- them with the MAKEDEV script) in /dev. Most distributions
- already have the /dev/sg? files.
-
- The cdparanoia binary will likely work with Linux 1.2 and 1.3, but I
- do not actively support kernels older than 2.0 I do know for a fact
- that the source will not build on kernel installs older than 2.0, but
- the problems are mostly related to the ever-changing locations of
- proprietary cdrom include files.
-
- Also, although a 2.0 stock SCSI setup will work, performance will be
- better if linux/include/scsi/sg.h defines SG_BIG_BUFF to 65536 (it
- can't be bigger). Recent kernels (2.0.30+?) already set it to 32768;
- that's OK. Cdparanoia will tell you how big your generic SCSI buffer
- is. 2.2+ does not use a static DMA pool for SG, so there is nothing
- to tune.
-
- Unlike cdda2wav, cdparanoia does not require threading, IPC or
- (optionally) sound card support. /proc filesystem support is no longer
- required (but encouraged!), and /dev/sr? or /dev/scd? devices are not
- required for SCSI, although they do add functionality if present.
-
------------------------------------------------------------------------
-
- Does Cdparanoia support ATAPI drives? SCSI Emulation? Parallel port
- drives?
-
- Alpha 9 supports the full ATAPI, IDE-SCSI and SCSI generic interfaces
- under Linux.
-
- Note that the native ATAPI driver is supported, but that IDE-SCSI
- emulation works better with ATAPI drives. This is an issue of control;
- the emulation interface gives cdparanoia complete control over the
- drive whereas the native ATAPI driver insists on hiding the device
- under an abstraction layer with poor error handling capabilities. Note
- also that a number of ATAPI drives that do not work at all with the
- ATAPI driver (error 006: Could not read audio) *will* work with
- IDE-SCSI emulation.
-
- Parallel port based CDROM (paride) drives are not yet supported;
- support for these drives in Linux will appear in alpha release 10
- (Paranoia IV).
-
------------------------------------------------------------------------
-
- I can play audio CDs perfectly; why is reading the CD into a file so
- difficult and prone to errors? It's just the same thing.
-
- Unfortunately, it isn't that easy.
-
- The audio CD is not a random access format. It can only be played from
- some starting point in sequence until it is done, like a vinyl LP.
- Unlike a data CD, there are no synchronization or positioning headers
- in the audio data (a CD, audio or data, uses 2352 byte sectors. In a
- data CD, 304 bytes of each sector is used for header, sync and error
- correction. An audio CD uses all 2352 bytes for data). The audio CD
- *does* have a continuous fragmented subchannel, but this is only good
- for seeking +/-1 second (or 75 sectors or ~176kB) of the desired area,
- as per the SCSI spec.
-
- When the CD is being played as audio, it is not only moving at 1x, the
- drive is keeping the media data rate (the spin speed) exactly locked
- to playback speed. Pick up a portable CD player while it's playing and
- rotate it 90 degrees. Chances are it will skip; you disturbed this
- delicate balance. In addition, a player is never distracted from what
- it's doing... it has nothing else taking up its time. Now add a
- non-realtime, (relatively) high-latency, multitasking kernel into the
- mess; it's like picking up the player and constantly shaking it.
-
- CDROM drives generally assume that any sort of DAE will be linear and
- throw a readahead buffer at the task. However, the OS is reading the
- data as broken up, seperated read requests. The drive is doing
- readahead buffering and attempting to store additional data as it
- comes in off media while it waits for the OS to get around to reading
- previous blocks. Seeing as how, at 36x, data is coming in at
- 6.2MB/second, and each read is only 13 sectors or ~30k (due to DMA
- restrictions), one has to get off 208 read requests a second, minimum
- without any interruption, to avoid skipping. A single swap to disc or
- flush of filesystem cache by the OS will generally result in loss of
- streaming, assuming the drive is working flawlessly. Oh, and virtually
- no PC on earth has that kind of I/O throughput; a Sun Enterprise
- server might, but a PC does not. Most don't come within a factor of
- five, assuming perfect realtime behavior.
-
- To keep piling on the difficulties, faster drives are often prone to
- vibration and alignment problems; some are total fiascos. They lose
- streaming *constantly* even without being interrupted. Philips
- determined 15 years ago that the CD could only be spun up to 50-60x
- until the physical CD (made of polycarbonate) would deform from
- centripetal force badly enough to become unreadable. Today's players
- are pushing physics to the limit. Few do so terribly reliably.
-
- Note that CD 'playback speed' is an excellent example of advertisers
- making numbers lie for them. A 36x cdrom is generally not spinning at
- 36x a normal drive's speed. As a 1x drive is adjusting velocity
- depending on the access's distance from the hub, a 36x drive is
- probably using a constant angular velocity across the whole surface
- such that it gets 36x max at the edge. Thus it's actually spinning
- slower, assuming the '36x' isn't a complete lie, as it is on some
- drives.
-
- Because audio discs have no headers in the data to assist in picking
- up where things got lost, most drives will just guess.
-
- This doesn't even *begin* to get into stupid firmware bugs. Even
- Plextors have occasionally had DAE bugs (although in every case,
- Plextor has fixed the bug *and* replaced/repaired drives for free).
- Cheaper drives are often complete basket cases.
-
- Rant Update (for those in the know):
-
- Several folks, through personal mail and on Usenet, have pointed out
- that audio discs do place absolute positioning information for (at
- least) nine out of every ten sectors into the Q subchannel, and that
- my original statement of +/-75 sectors above is wrong. I admit to it
- being misleading, so I'll try to clarify.
-
- The positioning data certainly is in subchannel Q; the point is moot
- however, for a couple of reasons.
-
- 1. The SCSI and ATAPI specs (there are a couple of each, pick one)
- don't give any way to retrieve the subchannel from a desired
- sector. The READ SUB-CHANNEL command will hand you Q all right,
- you just don't have any idea where exactly that Q came from. The
- command was intended for getting rough positioning information
- from audio discs that are paused or playing. This is audio;
- missing by several sectors is a tiny fraction of a second.
-
- 2. Older CDROM drives tended not to expect 'READ SUB-CHANNEL' unless
- the drive was playing audio; calling it during data reads could
- crash the drive and lock up the system. I had one of these drives
- (Apple 803i, actually a repackaged Sony CD-8003).
-
- 3. MMC-2 *does* give a way to retrieve the Q subchannel along with
- user data in the READ CD command. Although the drive is required
- to recognize the fetaure, it is allowed to simply return zeroes
- (effectively leaving the feature unimplemented). Guess how many
- drives actually implement this feature: not many.
-
- 4. Assuming you *can* get back the subchannel, most CDROM drives
- seem to understand audio discs primarily at the "little frame"
- level; thus sector-level structures aren't reliable. One might
- get a reassembled subQ, but if the read began in the middle of a
- sector (or dropped a little frame in the middle; many do), the
- subQ is likely corrupt and useless.
-
- As reassembling uncorrupted frames is easy without the subchannel, and
- corrupted reads likely result in a corrupted subchannel too,
- cdparanoia treats the subchannel as more trouble than it's worth
- (during verification).
-
- At least one other package (Exact Audio Copy for Win32) manages to use
- the subchannel to enhance the Table of Contents information. I don't
- know if this only works on MMC-2 drives that support returning Q with
- READ CD, but I think I'm going to revisit using the subchannel for
- extra TOC information.
-
------------------------------------------------------------------------
-
- Does cdparanoia lose quality from the CD recording? Does it just
- re-record the analog signal played from the CDROM drive?
-
- No to both. Cdparanoia (and all other true CD digital audio extraction
- tools) reads the values off the CDROM in digital form. The data never
- comes anywhere near the soundcard, and does not pass through any
- conversion to analog first.
-
------------------------------------------------------------------------
-
- Can cdparanoia detect pregaps? Can it remove the two second gaps
- between tracks
-
- Not yet. This feature is slated to appear in a release of alpha 10
- (Paranoia IV).
-
------------------------------------------------------------------------
-
- Why don't you implement CDDB? A GUI? Four million other features I
- want?
-
- Too many features spoil the broth. "Software is not perfect when there
- is nothing left to add, but rather when there is nothing extraneous
- left to take away." The goal of cdparanoia is perfect, rock-solid
- audio from every capable cdrom on every platform. As this goal has not
- yet been met, I'm uninterested in adding unrelated capability to the
- core engine.
-
- Several GUIs that incorporate cdparanoia already exist; I'm in the
- process of compiling a list (see the links page). Other software that
- implements new features by wrapping around cdpar anoia (like CDDB
- lookup) also exist.
-
- 'Cdparanoia' will not play to sound cards (you can always pipe the
- output to a WAV player), do MD5 signatures, read CD catalog or serial
- numbers (this *is* a feature I plan to add), search indexes, do rate
- reduction (use Sox, Ogg or a million others), or generally make use of
- the maximum speed available from a CDROM drive.
-
- If your CDROM drive is *not* prone to jitter and you don't have
- scratched discs to worry about, you might want to look at the original
- cdda2wav for features cdparanoia does not have. Keep in mind however
- that even the really good drives do occasionally stumble. I know of at
- least one cdparanoia user who insists on using full paranoia with his
- Plextor UltraPlex because it once botched a single sector from a rip;
- he'd already burned the track to several CD-Rs before noticing...
-
------------------------------------------------------------------------
-
- The progress meter: What is that weird bargraph during ripping?
-
- It's a progress/status indicator. There's a completion bargraph, a
- number indicating the last sector number completely verified of the
- read currently happening, an overlap indicator, a gratuitous smilie,
- and a heartbeat indicator to show if the process is still alive, hung,
- or spinning.
-
- The bargraph also marks points during the read with characters to
- indicate where various 'paranoia' features were tripped into action.
- Different bargraph characters indicate different things occurred
- during that part of the read. The letters are heirarchical; for
- example if a trasport error occurs in the same sector as jitter, the
- bargraph will print 'e' instead of '-'.
-
- Legend of
- characters
- A hyphen indicates that two blocks overlapped properly,
- - but they were skewed (frame jitter). This case is
- completely corrected by Paranoia and is not a cause for
- concern.
- A plus indicates not only frame jitter, but an
- unreported, uncorrected loss of streaming in the middle
- + of an atomic read operation. That is, the drive lost
- its place while reading data, and restarted in some
- random incorrect location without alerting the kernel.
- This case is also corrected by Paranoia.
- An 'e' indicates that a transport level SCSI or ATAPI
- e error was caught and corrected. Paranoia will
- completely repair such an error without audible
- defects.
- An "X" indicates a scratch was caught and corrected.
- X Cdparanoia wil interpolate over any missing/corrupt
- samples.
- An asterisk indicates a scratch and jitter both
- * occurred in this general area of the read. Cdparanoia
- wil interpolate over any missing/corrupt samples.
- A ! indicates that a read error got through the stage
- one of error correction and was caught by stage two.
- Many '!' are a cause for concern; it means that the
- drive is making continuous silent errors that look
- ! identical on each re-read, a condition that can't
- always be detected. Although the presence of a '!'
- means the error was corrected, it also means that
- similar errors are probably passing by unnoticed.
- Upcoming releases of cdparanoia will address this
- issue.
- A V indicates a skip that could not be repaired or a
- V sector totally obliterated on the medium (hard read
- error). A 'V' marker generally results in some audible
- defect in the sample.
-
- The smilie is actually relevant. It makes different faces depending on
- the current errors it's correcting.
-
- Legend of
- smilies
-
- :-) Normal operation. No errors to report; if any jitter is
- present, it's small.
- :-| Normal operation, but average jitter is quite large.
- A rift was found in the middle of an atomically read
- block; in other words, the drive lost streaming in the
- :-P middle of a read and did not abort, alert the kernel , or
- restart in the proper location. The drive silently
- continued reading in so me random location.
-
- :-/ The read appears to be drifting; cdparanoia is shifting
- all of its reads to make up for it.
- Two matching vectors were found to disagree even after
- first stage verification; this is an indication that the
- drive is reliably dropping/adding bytes at consistent
- locations. Because the verification algorithm is partially
- 8-| based on rereading and comparing vectors, if two vectors
- read incorrectly but identically, cdparanoia may never
- detect the problem. This smilie indicates that such a
- situation *was* detected; other instances may be slipping
- through.
- Transport or drive error. This is normally not a cause for
- concern; cdparanoia can repair just about any error that
- :-0 it actually detects. For more information about these
- errors, run cdparanoia with the -v option. Any all all
- errors and a description will dump to stderr.
- :-( Cdparanoia detected a scratch.
- Cdparanoia gave up trying to repair a sector; it could not
- read consistent enough information from the drive to do
- ;-( so. At this point cdparanoia will make the best guess it
- has available and continue (a V appears in the bargraph at
- this point). This often results in an audible defect.
- Cdparanoia displays this smilie both when finished reading
- :^D a track and also if no error correction mechanism has been
- tripped so far reading a new track.
-
------------------------------------------------------------------------
-
- How can I tell if my drive would be OK with regular cdda2wav?
-
- Easy. Run cdparanoia; if the progress meter never shows any characters
- but the little arrow going across the screen, the CDROM drive is
- probably one of the (currently) few drives that can read a pristine
- stream of data off an audio disc regardless of circumstances. This
- drive will work quite well with cdda2wav (or cdparanoia using the '-Z'
- option)
-
- A drive that results in a bargraph of all hyphens would *likely* work
- OK with cdda2wav, but it's less certain.
-
- Any other characters in the bargraph (colons, semicolons, pluses, Xs,
- etc..) indicate that a fixups had to be performed at that point during
- the read; that read would have failed or 'popped' using cdda2wav.
-
------------------------------------------------------------------------
-
- What is the biggest value of SG_BIG_BUFF I can use?
-
- This is relevant only to 2.0 kernels and early 2.2 kernels.
- Modern Linux kernels no longer have a single static SG DMS pool.
-
- For 2.0, 65536 (64 kilobytes). Some motherboards can use 128kB
- DMA, but attempting to use 128kB DMA on a machine that can't do
- it will crash the machine. Cdparanoia will not use larger than
- 64kB requests.
-
------------------------------------------------------------------------
-
- Why do the binary files from two reads differ when compared?
-
- The problem is the beginning point of the read. Cdparanoia enforces
- consistency from whatever the drive considers to be the starting point
- of the data, and the drive is returning a slightly different beginning
- point each time. The beginning point should not vary by much, and if
- this shift is accounted for when comparing the files, they should
- indeed turn out to be the same (aside from errors duly reported during
- the read; scratch correction or any reported skips will very likely
- also result in different files).
-
------------------------------------------------------------------------
-
- Why do CDParanoia, CDDA2WAV et al. rip files off into WAV format (and
- other sample formats) but not CDDA format?
-
- WAV and AIFC are simply convenient formats that include enough header
- information such that multipurpose audio software can uniquely
- identify the form of the data in the sample. In raw form, mulaw, SND
- and CDDA look exactly alike to a program like xplay, and are very
- likely to blow your ears (and stereo) out when played! Header formats
- are more versatile and safer. By default, cdparanoia and cdda2wav
- write WAV files.
-
- That said, cdparanoia (and cdda2wav) will write raw, headerless
- formats if explicitly told to. Cdparanoia writes headerless, signed 16
- bit, 44.1kHz stero files in little endian format (LSB first) when
- given the -r option, and the same in big endian (MSB) format when
- given -R. All files written by cdparanoia are a multiple of 2352 bytes
- long (minus the header, if any) as required by cd writer software.
-
-
-Cdparanoia and the Laser-Playback-Head-of-Omniscience logo are
-trademarks (tm) of Xiphophorus (xiph.org). This document copyright (C)
-1994-1999 Xiphophorus. All rights reserved. Comments and questions
-are welcome.
Deleted: trunk/cdparanoia/GPL
===================================================================
--- trunk/cdparanoia/GPL 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/GPL 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,339 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- Appendix: How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
- <one line to give the program's name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19yy name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- <signature of Ty Coon>, 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
Modified: trunk/cdparanoia/README
===================================================================
--- trunk/cdparanoia/README 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/README 2008-05-12 18:35:13 UTC (rev 14872)
@@ -12,6 +12,12 @@
http://www.xiph.org/paranoia/
+COPYING
+=======
+
+cdparanoia (the command line tool) is released under the GPLv3. The
+interface and paranoia libraries are covered by the LGPLv3.
+
Requirements
============
Modified: trunk/cdparanoia/cdparanoia.1
===================================================================
--- trunk/cdparanoia/cdparanoia.1 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/cdparanoia.1 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,4 +1,4 @@
-.TH CDPARANOIA 1 "29 Aug 2006"
+.TH CDPARANOIA 1 "12 May 2008"
.SH NAME
cdparanoia 10.0 (Paranoia release III) \- an audio CD reading utility which includes extra data verification features
.SH SYNOPSIS
Modified: trunk/cdparanoia/header.c
===================================================================
--- trunk/cdparanoia/header.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/header.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Public License 3 applies
+ * Copyright (C) 2008 Monty xiphmont at mit.edu
* and Heiko Eissfeldt heiko at escape.colossus.de
*
* Writes wav and aifc headers
Modified: trunk/cdparanoia/header.h
===================================================================
--- trunk/cdparanoia/header.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/header.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Public License 3 applies
+ * Copyright (C) 2008 Monty xiphmont at mit.edu
******************************************************************/
#include <unistd.h>
Modified: trunk/cdparanoia/interface/cdda_interface.h
===================================================================
--- trunk/cdparanoia/interface/cdda_interface.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/cdda_interface.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,7 +1,7 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 2001 Xiph.org
- * and Heiko Eissfeldt heiko at escape.colossus.de
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 2001-2008 Xiph.org
+ * Original version by Heiko Eissfeldt heiko at escape.colossus.de
*
* Toplevel interface header; applications include this
*
Modified: trunk/cdparanoia/interface/common_interface.c
===================================================================
--- trunk/cdparanoia/interface/common_interface.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/common_interface.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998, 2002 Monty monty at xiph.org
+ * CopyPolicy: GNU Lesser Public License 3 applies
+ * Copyright (C) 1998-2008 Monty monty at xiph.org
*
* CDROM communication common to all interface methods is done here
* (mostly ioctl stuff, but not ioctls specific to the 'cooked'
Modified: trunk/cdparanoia/interface/common_interface.h
===================================================================
--- trunk/cdparanoia/interface/common_interface.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/common_interface.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
******************************************************************/
Modified: trunk/cdparanoia/interface/cooked_interface.c
===================================================================
--- trunk/cdparanoia/interface/cooked_interface.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/cooked_interface.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) Monty xiphmont at mit.edu
*
* CDROM code specific to the cooked ioctl interface
Modified: trunk/cdparanoia/interface/interface.c
===================================================================
--- trunk/cdparanoia/interface/interface.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/interface.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* Top-level interface module for cdrom drive access. SCSI, ATAPI, etc
* specific stuff are in other modules. Note that SCSI does use
Modified: trunk/cdparanoia/interface/low_interface.h
===================================================================
--- trunk/cdparanoia/interface/low_interface.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/low_interface.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* internal include file for cdda interface kit for Linux
*
Modified: trunk/cdparanoia/interface/scan_devices.c
===================================================================
--- trunk/cdparanoia/interface/scan_devices.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/scan_devices.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 2006 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* Autoscan for or verify presence of a cdrom device
*
Modified: trunk/cdparanoia/interface/scsi_interface.c
===================================================================
--- trunk/cdparanoia/interface/scsi_interface.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/scsi_interface.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,8 +1,8 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Original interface.c Copyright (C) 1994-1997
* Eissfeldt heiko at colossus.escape.de
- * Current blenderization Copyright (C) 1998-2006 Monty xiphmont at mit.edu
+ * Current incarnation Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* Generic SCSI interface specific code.
*
Modified: trunk/cdparanoia/interface/smallft.c
===================================================================
--- trunk/cdparanoia/interface/smallft.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/smallft.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* FFT implementation from OggSquish, minus cosine transforms,
* minus all but radix 2/4 case
Modified: trunk/cdparanoia/interface/smallft.h
===================================================================
--- trunk/cdparanoia/interface/smallft.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/smallft.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
*
* FFT implementation from OggSquish, minus cosine transforms.
* Only convenience functions exposed
Modified: trunk/cdparanoia/interface/test_interface.c
===================================================================
--- trunk/cdparanoia/interface/test_interface.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/test_interface.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lessger General Public License 3 applies
* Copyright (C) Monty xiphmont at mit.edu
*
* Fake interface backend for testing paranoia layer
Modified: trunk/cdparanoia/interface/toc.c
===================================================================
--- trunk/cdparanoia/interface/toc.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/interface/toc.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,6 +1,6 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
- * Copyright (C) 1998 Monty xiphmont at mit.edu
+ * CopyPolicy: GNU Lesser General Public License 3 applies
+ * Copyright (C) 1998-2008 Monty xiphmont at mit.edu
* derived from code (C) 1994-1996 Heiko Eissfeldt
*
* Table of contents convenience functions
Modified: trunk/cdparanoia/main.c
===================================================================
--- trunk/cdparanoia/main.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/main.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/*
- * Copyright: GNU Public License 2 applies
+ * Copyright: GNU Public License 3 applies
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
@@ -15,7 +15,7 @@
* along with this program; if not, write to the Free Software
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*
- * cdparanoia (C) 2006 Monty <monty at xiph.org>
+ * cdparanoia (C) 2008 Monty <monty at xiph.org>
*
*/
Modified: trunk/cdparanoia/paranoia/cdda_paranoia.h
===================================================================
--- trunk/cdparanoia/paranoia/cdda_paranoia.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/cdda_paranoia.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
*
***/
Modified: trunk/cdparanoia/paranoia/gap.c
===================================================================
--- trunk/cdparanoia/paranoia/gap.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/gap.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,8 +1,8 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
*
- * Gapa analysis support code for paranoia
+ * Gap analysis support code for paranoia
*
***/
Modified: trunk/cdparanoia/paranoia/gap.h
===================================================================
--- trunk/cdparanoia/paranoia/gap.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/gap.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
***/
Modified: trunk/cdparanoia/paranoia/isort.c
===================================================================
--- trunk/cdparanoia/paranoia/isort.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/isort.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
*
* sorted vector abstraction for paranoia
Modified: trunk/cdparanoia/paranoia/isort.h
===================================================================
--- trunk/cdparanoia/paranoia/isort.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/isort.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
***/
Modified: trunk/cdparanoia/paranoia/overlap.c
===================================================================
--- trunk/cdparanoia/paranoia/overlap.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/overlap.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
*
* Statistic code and cache management for overlap settings
Modified: trunk/cdparanoia/paranoia/overlap.h
===================================================================
--- trunk/cdparanoia/paranoia/overlap.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/overlap.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
***/
Modified: trunk/cdparanoia/paranoia/p_block.h
===================================================================
--- trunk/cdparanoia/paranoia/p_block.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/p_block.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
***/
Modified: trunk/cdparanoia/paranoia/paranoia.c
===================================================================
--- trunk/cdparanoia/paranoia/paranoia.c 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/paranoia/paranoia.c 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/***
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Lesser General Public License 3 applies
* Copyright (C) by Monty (xiphmont at mit.edu)
*
* Toplevel file for the paranoia abstraction over the cdda lib
Modified: trunk/cdparanoia/version.h
===================================================================
--- trunk/cdparanoia/version.h 2008-05-12 18:13:24 UTC (rev 14871)
+++ trunk/cdparanoia/version.h 2008-05-12 18:35:13 UTC (rev 14872)
@@ -1,5 +1,5 @@
/******************************************************************
- * CopyPolicy: GNU Public License 2 applies
+ * CopyPolicy: GNU Public License 3 applies
*
* cdda_paranoia generation III release 10.0
* Copyright (C) 2008 Monty monty at xiph.org
More information about the commits
mailing list