Yamaha BRX-610 – page 12

Manual for Yamaha BRX-610

Table of contents

Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.

FILE FORMAT WARS

The ISO JPEG standards committee actually promotes different formats like JPEG-

(Adjacent articles in that issue discuss MPEG motion picture compression, applications

2000 or JPEG-XR which are incompatible with original DCT-based JPEG and which

of JPEG, and related topics.) If you don’t have the CACM issue handy, a PostScript file

are based on faulty technologies. IJG therefore does not and will not support such

containing a revised version of Wallace’s article is available at http://www.ijg.org/files/

momentary mistakes (see REFERENCES). We have little or no sympathy for the

wallace.ps.gz. The file (actually a preprint for an article that appeared in IEEE Trans.

promotion of these formats. Indeed, one of the original reasons for developing this free

Consumer Electronics) omits the sample images that appeared in CACM, but it

software was to help force convergence on common, interoperable format standards for

includes corrections and some added material. Note: the Wallace article is copyright

JPEG files. Don’t use an incompatible file format! (In any case, our decoder will remain

ACM and IEEE, and it may not be used for commercial purposes.

capable of reading existing JPEG image files indefinitely.)

A somewhat less technical, more leisurely introduction to JPEG can be found in “The

Data Compression Book” by Mark Nelson and Jean-loup Gailly, published by M&T

TO DO

Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides good

v7 is basically just a necessary interim release, paving the way for a major breakthrough

explanations and example C code for a multitude of compression methods including

in image coding technology with the next v8 package which is scheduled for release in

JPEG. It is an excellent source if you are comfortable reading C code but don’t know

the year 2010.

much about data compression in general. The book’s JPEG sample code is far from

Please send bug reports, offers of help, etc. to jpeg-info@jpegclub.org.

industrial-strength, but when you are ready to look at a full implementation, you’ve got

one here...

About International Components for Unicode

The best currently available description of JPEG is the textbook “JPEG Still Image

ICU License - ICU 1.8.1 and later

Data Compression Standard” by William B. Pennebaker and Joan L. Mitchell,

COPYRIGHT AND PERMISSION NOTICE

published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1. Price US$59.95,

Copyright (C) 1995-2003 International Business Machines Corporation and others

638 pp. The book includes the complete text of the ISO JPEG standards (DIS 10918-1

All rights reserved.

and draft DIS 10918-2).

Permission is hereby granted, free of charge, to any person obtaining a copy of this

Although this is by far the most detailed and comprehensive exposition of JPEG

software and associated documentation files (the “Software”), to deal in the Software

publicly available, we point out that it is still missing an explanation of the most

without restriction, including without limitation the rights to use, copy, modify, merge,

essential properties and algorithms of the underlying DCT technology.

publish, distribute, and/or sell copies of the Software, and to permit persons to whom

If you think that you know about DCT-based JPEG after reading this book, then you are

the Software is furnished to do so, provided that the above copyright notice(s) and this

in delusion. The real fundamentals and corresponding potential of DCT-based JPEG are

permission notice appear in all copies of the Software and that both the above copyright

not publicly known so far, and that is the reason for all the mistaken developments

notice(s) and this permission notice appear in supporting documentation.

taking place in the image coding domain.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY

The original JPEG standard is divided into two parts, Part 1 being the actual

KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE

specification, while Part 2 covers compliance testing methods. Part 1 is titled “Digital

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

Compression and Coding of Continuous-tone Still Images, Part 1: Requirements and

PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO

guidelines” and has document numbers ISO/IEC IS 10918-1, ITU-T T.81. Part 2 is

EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS

titled “Digital Compression and Coding of Continuous-tone Still Images, Part 2:

NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR

Compliance testing” and has document numbers ISO/IEC IS 10918-2, ITU-T T.83.

CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER

The JPEG standard does not specify all details of an interchangeable file format. For the

RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN

omitted details we follow the “JFIF” conventions, revision 1.02. A copy of the JFIF

ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,

spec is available from:

ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE

Literature Department

OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in

C-Cube Microsystems, Inc.

advertising or otherwise to promote the sale, use or other dealings in this Software

1778 McCarthy Blvd.

without prior written authorization of the copyright holder.

Milpitas, CA 95035

All trademarks and registered trademarks mentioned herein are the property of their

phone (408) 944-6300, fax (408) 944-6314

respective owners.

A PostScript version of this document is available at http://www.ijg.org/files/jfif.ps.gz.

About libpng

There is also a plain text version at http://www.ijg.org/files/jfif.txt.gz, but it is missing

the figures.

This copy of the libpng notices is provided for your convenience. In case of any

The TIFF 6.0 file format specification can be obtained by FTP from ftp://ftp.sgi.com/

discrepancy between this copy and the notices in the file png.h that is included in the

graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme found in the TIFF 6.0 spec

libpng distribution, the latter shall prevail.

of 3-June-92 has a number of serious problems. IJG does not recommend use of the

COPYRIGHT NOTICE, DISCLAIMER, and LICENSE:

TIFF 6.0 design (TIFF Compression tag 6). Instead, we recommend the JPEG design

If you modify libpng you may insert additional notices immediately following this

proposed by TIFF Technical Note #2 (Compression tag 7). Copies of this Note can be

sentence.

obtained from http://www.ijg.org/files/. It is expected that the next revision of the TIFF

spec will replace the 6.0 JPEG design with the Note’s design. Although IJG’s own code

This code is released under the libpng license.

does not support TIFF/JPEG, the free libtiff library uses our library to implement TIFF/

JPEG per the Note.

libpng versions 1.2.6, August 15, 2004, through 1.2.45, July 7, 2011, are Copyright (C)

ARCHIVE LOCATIONS

2004, 2006-2009 Glenn Randers-Pehrson, and are distributed according to the same

The “official” archive site for this software is www.ijg.org. The most recent released

disclaimer and license as libpng-1.2.5 with the following individual added to the list of

version can always be found there in directory “files”. This particular version will be

Contributing Authors

archived as http://www.ijg.org/files/jpegsrc.v7.tar.gz, and in Windows-compatible

Cosmin Truta

“zip” archive format as http://www.ijg.org/files/jpegsr7.zip.

libpng versions 1.0.7, July 1, 2000, through 1.2.5 - October 3, 2002, are Copyright

The JPEG FAQ (Frequently Asked Questions) article is a source of some general

(C) 2000-2002 Glenn Randers-Pehrson, and are distributed according to the same

information about JPEG. It is available on the World Wide Web at http://www.faqs.org/

disclaimer and license as libpng-1.0.6 with the following individuals added to the

faqs/jpeg-faq/ and other news.answers archive sites, including the official

list of Contributing Authors

news.answers archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/

jpeg-faq/. If you don’t have Web or FTP access, send e-mail to mail-

Simon-Pierre Cadieux

server@rtfm.mit.edu with body

Eric S. Raymond

send usenet/news.answers/jpeg-faq/part1

Gilles Vollant

send usenet/news.answers/jpeg-faq/part2

and with the following additions to the disclaimer:

ACKNOWLEDGMENTS

There is no warranty against interference with your enjoyment of the library or

Thank to Juergen Bruder of the Georg-Cantor-Organization at the Martin-Luther-

against infringement. There is no warranty that our efforts or the library will fulfill

University Halle for providing me with a copy of the common DCT algorithm article,

any of your particular purposes or needs. This library is provided with all faults,

only to find out that I had come to the same result in a more direct and comprehensible

and the entire risk of satisfactory quality, performance, accuracy, and effort is with

way with a more generative approach.

the user.

Thank to Istvan Sebestyen and Joan L. Mitchell for inviting me to the ITU JPEG (Study

Group 16) meeting in Geneva, Switzerland.

libpng versions 0.97, January 1998, through 1.0.6, March 20, 2000, are Copyright (C)

Thank to Thomas Wiegand and Gary Sullivan for inviting me to the Joint Video Team

1998, 1999 Glenn Randers-Pehrson, and are distributed according to the same

(MPEG & ITU) meeting in Geneva, Switzerland.

disclaimer and license as libpng-0.96, with the following individuals added to the list of

Thank to John Korejwa and Massimo Ballerini for inviting me to fruitful consultations

Contributing Authors:

in Boston, MA and Milan, Italy.

Tom Lane

Thank to Hendrik Elstner, Roland Fassauer, and Simone Zuck for corresponding

business development.

Glenn Randers-Pehrson

Thank to Nico Zschach and Dirk Stelling of the technical support team at the Digital

Willem van Schaik

Images company in Halle for providing me with extra equipment for configuration

libpng versions 0.89, June 1996, through 0.96, May 1997, are Copyright (C) 1996, 1997

tests.

Andreas Dilger Distributed according to the same disclaimer and license as libpng-0.88,

Thank to Richard F. Lyon (then of Foveon Inc.) for fruitful communication about JPEG

with the following individuals added to the list of Contributing Authors:

configuration in Sigma Photo Pro software.

Last but not least special thank to Thomas G. Lane for the original design and

John Bowler

development of this singular software package.

Kevin Bracey

vii

Sam Bushell

source code samples/webserver. To use all of the software commercially, a commercial

license has to be obtained

Magnus Holmgren

from www.genivia.com.

Greg Roelofs

1 DEFINITIONS.

Tom Tanner

1.0.1.

1.1. “Contributor” means each entity that creates or contributes to the creation of

libpng versions 0.5, May 1995, through 0.88, January 1996, are Copyright (C) 1995,

Modifications.

1996 Guy Eric Schalnat, Group 42, Inc.

1.2. “Contributor Version” means the combination of the Original Code, prior

For the purposes of this copyright and license, “Contributing Authors” is defined as the

Modifications used by a Contributor, and the Modifications made by that particular

following set of individuals:

Contributor.

Andreas Dilger

1.3. “Covered Code” means the Original Code, or Modifications or the combination of

the Original Code, and Modifications, in each case including portions thereof.

Dave Martindale

1.4. “Electronic Distribution Mechanism” means a mechanism generally accepted in

Guy Eric Schalnat

the software development community for the electronic transfer of data.

1.5. “Executable” means Covered Code in any form other than Source Code.

Paul Schmidt

1.6. “Initial Developer” means the individual or entity identified as the Initial

Tim Wegner

Developer in the Source Code notice required by Exhibit A.

The PNG Reference Library is supplied “AS IS”. The Contributing Authors and Group

1.7. “Larger Work” means a work which combines Covered Code or portions thereof

42, Inc. disclaim all warranties, expressed or implied, including, without limitation, the

with code not governed by the terms of this License.

warranties of merchantability and of fitness for any purpose. The Contributing Authors

1.8. “License” means this document.

and Group 42, Inc. assume no liability for direct, indirect, incidental, special,

1.8.1. “Licensable” means having the right to grant, to the maximum extent possible,

exemplary, or consequential damages, which may result from the use of the PNG

whether at the time of the initial grant or subsequently acquired, any and all of the rights

Reference Library, even if advised of the possibility of such damage.

conveyed herein.

Permission is hereby granted to use, copy, modify, and distribute this source code, or

1.9. “Modifications” means any addition to or deletion from the substance or structure

portions hereof, for any purpose, without fee, subject to the following restrictions:

of either the Original Code or any previous Modifications. When Covered Code is

released as a series of files, a Modification is: A.

1. The origin of this source code must not be misrepresented.

Any addition to or deletion from the contents of a file containing Original Code or

2. Altered versions must be plainly marked as such and must not be misrepresented

previous Modifications. B.

as being the original source.

Any new file that contains any part of the Original Code, or previous Modifications.

1.10. “Original Code” means Source Code of computer software code which is

3. This Copyright notice may not be removed or altered from any source or altered

described in the Source Code notice required by Exhibit A as Original Code, and which,

source distribution.

at the time of its release under this License is not already Covered Code governed by

The Contributing Authors and Group 42, Inc. specifically permit, without fee, and

this License.

encourage the use of this source code as a component to supporting the PNG file format

1.10.1. “Patent Claims” means any patent claim(s), now owned or hereafter acquired,

in commercial products. If you use this source code in a product, acknowledgment is

including without limitation, method, process, and apparatus claims, in any patent

not required but would be appreciated.

Licensable by grantor.

A “png_get_copyright” function is available, for convenient use in “about” boxes and

http://www.cs.fsu.edu/~engelen/license.html

the like:

1.11. “Source Code” means the preferred form of the Covered Code for making

modifications to it, including all modules it contains, plus any associated interface

printf(“%s”,png_get_copyright(NULL));

definition files, scripts used to control compilation and installation of an Executable, or

Also, the PNG logo (in PNG format, of course) is supplied in the files “pngbar.png” and

source code differential comparisons against either the Original Code or another well

“pngbar.jpg (88x31) and “pngnow.png” (98x31).

known, available Covered Code of the Contributor’s choice. The Source Code can be in

Libpng is OSI Certified Open Source Software. OSI Certified Open Source is a

a compressed or archival form, provided the appropriate decompression or de-archiving

certification mark of the Open Source Initiative.

software is widely available for no charge.

Glenn Randers-Pehrson

1.12. “You” (or “Your”) means an individual or a legal entity exercising rights under,

glennrp at users.sourceforge.net

and complying with all of the terms of, this License or a future version of this License

July 7, 2011

issued under Section 6.1. For legal entities, “You” includes any entity which controls, is

controlled by, or is under common control with You. For purposes of this definition,

About tinyxml

“control” means (a) the power, direct or indirect, to cause the direction or management

www.sourceforge.net/projects/tinyxml

of such entity, whether by contract or otherwise, or (b) ownership of more than fifty

Original code (2.0 and earlier )copyright (C) 2000-2006 Lee Thomason

percent (50%) of the outstanding shares or beneficial ownership of such entity.

(www.grinninglizard.com)

2 SOURCE CODE LICENSE.

This software is provided ‘as-is’, without any express or implied warranty. In no event

2.1. The Initial Developer Grant. The Initial Developer hereby grants You a world-

will the authors be held liable for any damages arising from the use of this software.

wide, royalty-free, non-exclusive license, subject to third party intellectual property

Permission is granted to anyone to use this software for any purpose, including

claims:

commercial applications, and to alter it and redistribute it freely, subject to the

(a)

following restrictions:

under intellectual property rights (other than patent or trademark) Licensable by Initial

1. The origin of this software must not be misrepresented; you must not claim that you

Developer to use, reproduce, modify, display, perform, sublicense and distribute the

wrote the original software. If you use this software in a product, an acknowledgment in

Original Code (or portions thereof) with or without Modifications, and/or as part of a

the product documentation would be appreciated but is not required.

Larger Work; and

2. Altered source versions must be plainly marked as such, and must not be

(b)

misrepresented as being the original software.

under patents now or hereafter owned or controlled by Initial Developer, to make, have

3. This notice may not be removed or altered from any source distribution.

made, use and sell (“offer to sell and import”) the Original Code, Modifications, or

portions thereof, but solely to the extent that any such patent is reasonably necessary to

About dtoa and strtod

enable You to utilize, alone or in combination with other software, the Original Code,

The author of this software is David M. Gay.

Modifications, or any combination or portions thereof.

Copyright (C) 1991, 2000, 2001 by Lucent Technologies.

(c)

Permission to use, copy, modify, and distribute this software for any purpose without

(d)

fee is hereby granted, provided that this entire notice is included in all copies of any

2.2. Contributor Grant.

software which is or includes a copy or modification of this software and in all copies

Subject to third party intellectual property claims, each Contributor hereby grants You a

of the supporting documentation for such software.

world-wide, royalty-free, non-exclusive license

THIS SOFTWARE IS BEING PROVIDED “AS IS”, WITHOUT ANY EXPRESS OR

(a)

IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR

under intellectual property rights (other than patent or trademark) Licensable by

LUCENT MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND

Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the

CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS

Modifications created by such Contributor (or portions thereof) either on an unmodified

FITNESS FOR ANY PARTICULAR PURPOSE.

basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and

(b)

About gSOAP

under patents now or hereafter owned or controlled by Contributor, to make, have

gSOAP Public License

made, use and sell (“offer to sell and import”) the Contributor Version (or portions

Version 1.3b

thereof), but solely to the extent that any such patent is reasonably necessary to enable

The gSOAP public license is derived from the Mozilla Public License (MPL1.1). The

You to utilize, alone or in combination with other software, the Contributor Version (or

sections that were deleted

portions thereof).

from the original MPL1.1 text are 1.0.1, 2.1.(c),(d), 2.2.(c),(d), 8.2.(b), 10, and 11.

(c)

Section 3.8 was added. The

(d)

modified sections are 2.1.(b), 2.2.(b), 3.2 (simplified), 3.5 (deleted the last sentence),

3 DISTRIBUTION OBLIGATIONS.

and 3.6 (simplified).

3.1. Application of License.

This license applies to the gSOAP software package, with the exception of the wsdl2h

source code located in

gsoap/wsdl, all code generated by wsdl2h, the UDDI source code gsoap/uddi2, and the

Web server sample

viii

The Modifications which You create or to which You contribute are governed by the

6.3. Derivative Works.

terms of this License, including without limitation Section 2.2. The Source Code

If You create or use a modified version of this License (which you may only do in order

version of Covered Code may be distributed only under the terms of this License or a

to apply it to code which is not already Covered Code governed by this License), You

future version of this License released under Section 6.1, and You must include a copy

must (a) rename Your license so that the phrase “gSOAP” or any confusingly similar

of this License with every copy of the Source Code You distribute. You may not offer

phrase do not appear in your license (except to note that your license differs from this

or impose any terms on any Source Code version that alters or restricts the applicable

License) and (b) otherwise make it clear that Your version of the license contains terms

version of this License or the recipients’ rights hereunder. However, You may include

which differ from the gSOAP Public License. (Filling in the name of the Initial

an additional document offering the additional rights described in Section 3.5.

Developer, Original Code or Contributor in the notice described in Exhibit A shall not

3.2. Availability of Source Code.

of themselves be deemed to be modifications of this License.)

Any Modification created by You will be provided to the Initial Developer in Source

7 DISCLAIMER OF WARRANTY.

Code form and are subject to the terms of the License.

COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS” BASIS,

3.3. Description of Modifications.

WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED OR

You must cause all Covered Code to which You contribute to contain a file

STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED

documenting the changes You made to create that Covered Code and the date of any

WARRANTIES OF MERCHANTABILITY, OF FITNESS FOR A PARTICULAR

change. You must include a prominent statement that the Modification is derived,

PURPOSE, NONINFRINGEMENT OF THIRD PARTY INTELLECTUAL

directly or indirectly, from Original Code provided by the Initial Developer and

PROPERTY RIGHTS, AND ANY WARRANTY THAT MAY ARISE BY REASON

including the name of the Initial Developer in (a) the Source Code, and (b) in any notice

OF TRADE USAGE, CUSTOM, OR COURSE OF DEALING. WITHOUT

in an Executable version or related documentation in which You describe the origin or

LIMITING THE FOREGOING, YOU ACKNOWLEDGE THAT THE SOFTWARE

ownership of the Covered Code.

IS PROVIDED “AS IS” AND THAT THE AUTHORS DO NOT WARRANT THE

3.4. Intellectual Property Matters.

SOFTWARE WILL RUN UNINTERRUPTED OR ERROR FREE. LIMITED

(a) Third Party Claims.

LIABILITY THE ENTIRE RISK AS TO RESULTS AND PERFORMANCE OF THE

If Contributor has knowledge that a license under a third party’s intellectual property

SOFTWARE IS ASSUMED BY YOU. UNDER NO CIRCUMSTANCES WILL THE

rights is required to exercise the rights granted by such Contributor under Sections 2.1

AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL,

or 2.2, Contributor must include a text file with the Source Code distribution titled

EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND OR NATURE

“LEGAL” which describes the claim and the party making the claim in sufficient detail

WHATSOEVER, WHETHER BASED ON CONTRACT, WARRANTY, TORT

that a recipient will know whom to contact. If Contributor obtains such knowledge after

(INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, ARISING

the Modification is made available as described in Section 3.2, Contributor shall

OUT OF OR IN ANY WAY RELATED TO THE SOFTWARE, EVEN IF THE

promptly modify the LEGAL file in all copies Contributor makes available thereafter

AUTHORS HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGE

and shall take other steps (such as notifying appropriate mailing lists or newsgroups)

OR IF SUCH DAMAGE COULD HAVE BEEN REASONABLY FORESEEN, AND

reasonably calculated to inform those who received the Covered Code that new

NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY

knowledge has been obtained.

EXCLUSIVE REMEDY PROVIDED. SUCH LIMITATION ON DAMAGES

(b) Contributor APIs.

INCLUDES, BUT IS NOT LIMITED TO, DAMAGES FOR LOSS OF GOODWILL,

If Contributor’s Modifications include an application programming interface and

LOST PROFITS, LOSS OF DATA OR SOFTWARE, WORK STOPPAGE,

Contributor has knowledge of patent licenses which are reasonably necessary to

COMPUTER FAILURE OR MALFUNCTION OR IMPAIRMENT OF OTHER

implement that API, Contributor must also include this information in the LEGAL file.

GOODS. IN NO EVENT WILL THE AUTHORS BE LIABLE FOR THE COSTS OF

(c) Representations.

PROCUREMENT OF SUBSTITUTE SOFTWARE OR SERVICES. YOU

Contributor represents that, except as disclosed pursuant to Section 3.4(a) above,

ACKNOWLEDGE THAT THIS SOFTWARE IS NOT DESIGNED FOR USE IN ON-

Contributor believes that Contributor’s Modifications are Contributor’s original

LINE EQUIPMENT IN HAZARDOUS ENVIRONMENTS SUCH AS OPERATION

creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this

OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR CONTROL, OR LIFE-

License.

CRITICAL APPLICATIONS. THE AUTHORS EXPRESSLY DISCLAIM ANY

3.5. Required Notices.

LIABILITY RESULTING FROM USE OF THE SOFTWARE IN ANY SUCH ON-

You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not

LINE EQUIPMENT IN HAZARDOUS ENVIRONMENTS AND ACCEPTS NO

possible to put such notice in a particular Source Code file due to its structure, then You

LIABILITY IN RESPECT OF ANY ACTIONS OR CLAIMS BASED ON THE USE

must include such notice in a location (such as a relevant directory) where a user would

OF THE SOFTWARE IN ANY SUCH ON-LINE EQUIPMENT IN HAZARDOUS

be likely to look for such a notice. If You created one or more Modification(s) You may

ENVIRONMENTS BY YOU. FOR PURPOSES OF THIS PARAGRAPH, THE

add your name as a Contributor to the notice described in Exhibit A. You must also

TERM “LIFE- CRITICAL APPLICATION” MEANS AN APPLICATION IN

duplicate this License in any documentation for the Source Code where You describe

WHICH THE FUNCTIONING OR MALFUNCTIONING OF THE SOFTWARE

recipients’ rights or ownership rights relating to Covered Code. You may choose to

MAY RESULT DIRECTLY OR INDIRECTLY IN PHYSICAL INJURY OR LOSS

offer, and to charge a fee for, warranty, support, indemnity or liability obligations to

OF HUMAN LIFE. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN

one or more recipients of Covered Code. However, You may do so only on Your own

ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS

behalf, and not on behalf of the Initial Developer or any Contributor.

AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

3.6. Distribution of Executable Versions.

8 TERMINATION.

You may distribute Covered Code in Executable form only if the requirements of

8.1.

Section 3.1-3.5 have been met for that Covered Code. You may distribute the

This License and the rights granted hereunder will terminate automatically if You fail to

Executable version of Covered Code or ownership rights under a license of Your

comply with terms herein and fail to cure such breach within 30 days of becoming

choice, which may contain terms different from this License, provided that You are in

aware of the breach. All sublicenses to the Covered Code which are properly granted

compliance with the terms of this License and that the license for the Executable

shall survive any termination of this License. Provisions which, by their nature, must

version does not attempt to limit or alter the recipient’s rights in the Source Code

remain in effect beyond the termination of this License shall survive.

version from the rights set forth in this License. If You distribute the Executable version

8.2.

under a different license You must make it absolutely clear that any terms which differ

8.3.

from this License are offered by You alone, not by the Initial Developer or any

If You assert a patent infringement claim against Participant alleging that such

Contributor. If you distribute executable versions containing Covered Code as part of a

Participant’s Contributor Version directly or indirectly infringes any patent where such

product, you must reproduce the notice in Exhibit B in the documentation and/or other

claim is resolved (such as by license or settlement) prior to the initiation of patent

materials provided with the product.

infringement litigation, then the reasonable value of the licenses granted by such

3.7. Larger Works.

Participant under Sections 2.1 or 2.2 shall be taken into account in determining the

You may create a Larger Work by combining Covered Code with other code not

amount or value of any payment or license.

governed by the terms of this License and distribute the Larger Work as a single

8.4.

product. In such a case, You must make sure the requirements of this License are

In the event of termination under Sections 8.1 or 8.2 above, all end user license

fulfilled for the Covered Code.

agreements (excluding distributors and resellers) which have been validly granted by

3.8. Restrictions.

You or any distributor hereunder prior to termination shall survive termination.

You may not remove any product identification, copyright, proprietary notices or labels

9 LIMITATION OF LIABILITY.

from gSOAP.

UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER

4 INABILITY TO COMPLY DUE TO STATUTE OR REGULATION.

TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL

If it is impossible for You to comply with any of the terms of this License with respect

YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY

to some or all of the Covered Code due to statute, judicial order, or regulation then You

DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH

must: (a) comply with the terms of this License to the maximum extent possible; and

PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL,

(b) describe the limitations and the code they affect. Such description must be included

INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER

in the LEGAL file described in Section 3.4 and must be included with all distributions

INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL,

of the Source Code. Except to the extent prohibited by statute or regulation, such

WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND

description must be sufficiently detailed for a recipient of ordinary skill to be able to

ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY

understand it.

SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.

5 APPLICATION OF THIS LICENSE.

THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR

This License applies to code to which the Initial Developer has attached the notice in

DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’S

Exhibit A and to related Covered Code.

NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH

6 VERSIONS OF THE LICENSE.

LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR

6.1. New Versions.

LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS

Grantor may publish revised and/or new versions of the License from time to time.

EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.

Each version will be given a distinguishing version number.

10 U.S. GOVERNMENT END USERS.

6.2. Effect of New Versions.

11 MISCELLANEOUS.

Once Covered Code has been published under a particular version of the License, You

12 RESPONSIBILITY FOR CLAIMS.

may always continue to use it under the terms of that version. You may also choose to

use such Covered Code under the terms of any subsequent version of the License.

ix

As between Initial Developer and the Contributors, each party is responsible for claims

Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts

and damages arising, directly or indirectly, out of its utilization of rights under this

accompanying this license (“Fonts”) and associated documentation files (the “Font

License and You agree to work with Initial Developer and Contributors to distribute

Software”), to reproduce and distribute the modifications to the Bitstream Vera Font

such responsibility on an equitable basis. Nothing herein is intended or shall be deemed

Software, including without limitation the rights to use, copy, merge, publish,

to constitute any admission of liability.

distribute, and/or sell copies of the Font Software, and to permit persons to whom the

EXHIBIT A.

Font Software is furnished to do so, subject to the following conditions:

“The contents of this file are subject to the gSOAP Public License Version 1.3 (the

“License”); you may not use this

The above copyright and trademark notices and this permission notice shall be included

file except in compliance with the License. You may obtain a copy of the License

in all copies of one or more of the Font Software typefaces.

athttp://www.cs.fsu.edu/ engelen/soaplicense.html

Software distributed under the License is distributed on an “AS IS” basis, WITHOUT

The Font Software may be modified, altered, or added to, and in particular the designs

WARRANTY OF ANY KIND, either express or implied. See the License for the

of glyphs or characters in the Fonts may be modified and additional glyphs or

specific language governing rights and limitations under the License.

characters may be added to the Fonts, only if the fonts are renamed to names not

The Original Code of the gSOAP Software is: stdsoap.h, stdsoap2.h, stdsoap.c,

containing either the words “Tavmjong Bah” or the word “Arev”.

stdsoap2.c, stdsoap.cpp,

stdsoap2.cpp, soapcpp2.h, soapcpp2.c, soapcpp2_lex.l, soapcpp2_yacc.y, error2.h,

This License becomes null and void to the extent applicable to Fonts or Font Software

error2.c, symbol2.c, init2.c,

that has been modified and is distributed under the “Tavmjong Bah Arev” names.

soapdoc2.html, and soapdoc2.pdf, httpget.h, httpget.c, stl.h, stldeque.h, stllist.h,

stlvector.h, stlset.h.

The Font Software may be sold as part of a larger software package but no copy of one

The Initial Developer of the Original Code is Robert A. van Engelen. Portions created

or more of the Font Software typefaces may be sold by itself.

by Robert A. van Engelen are

Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.

THE FONT SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF

Contributor(s):

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY

“________________________.”

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

[Note: The text of this Exhibit A may differ slightly form the text of the notices in the

PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT,

Source Code files of the Original code. You should use the text of this Exhibit A rather

TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL TAVMJONG BAH BE

than the text found in the Original Code Source Codefor Your Modifications.]

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING

EXHIBIT B.

ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL

“Part of the software embedded in this product is gSOAP software.

DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR

Portions created by gSOAP are Copyright (C) 2001-2009 Robert A. van Engelen, Genivia

OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE

inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART

FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.

PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

Except as contained in this notice, the name of Tavmjong Bah shall not be used in

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

advertising or otherwise to promote the sale, use or other dealings in this Font Software

DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,

without prior written authorization from Tavmjong Bah. For further information,

INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

contact: tavmjong @ free. fr.

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR

BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF

LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING

NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.”

http://www.cs.fsu.edu/~engelen/license.html

About fonts

Fonts are (c) Bitstream (see below). DejaVu changes are in public domain.

Glyphs imported from Arev fonts are (c) Tavmjong Bah (see below)

Bitstream Vera Fonts Copyright

------------------------------

Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream Vera is a

trademark of Bitstream, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts

accompanying this license (“Fonts”) and associated documentation files (the “Font Software”),

to reproduce and distribute the Font Software, including without limitation the rights to use,

copy, merge, publish, distribute, and/or sell copies of the Font Software, and to permit persons

to whom the Font Software is furnished to do so, subject to the following conditions:

The above copyright and trademark notices and this permission notice shall be included

in all copies of one or more of the Font Software typefaces.

The Font Software may be modified, altered, or added to, and in particular the designs

of glyphs or characters in the Fonts may be modified and additional glyphs or

characters may be added to the Fonts, only if the fonts are renamed to names not

containing either the words “Bitstream” or the word “Vera”.

This License becomes null and void to the extent applicable to Fonts or Font Software

that has been modified and is distributed under the “Bitstream Vera” names.

The Font Software may be sold as part of a larger software package but no copy of one

or more of the Font Software typefaces may be sold by itself.

THE FONT SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF

ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT,

TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL BITSTREAM OR THE

GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER

LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL,

OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT,

TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO

USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT

SOFTWARE.

Except as contained in this notice, the names of Gnome, the Gnome Foundation, and

Bitstream Inc., shall not be used in advertising or otherwise to promote the sale, use or

other dealings in this Font Software without prior written authorization from the Gnome

Foundation or Bitstream Inc., respectively. For further information, contact: fonts at

gnome dot org.

Arev Fonts Copyright

------------------------------

Copyright (c) 2006 by Tavmjong Bah. All Rights Reserved.

x

TLF

CAUTION

LASER Specification:

Use of controls or adjustments or performance of procedures

Class 1 LASER Product

other than those specified herein may result in hazardous

Wave length: 790 nm (CDs)/658 nm (DVDs)/405 nm (BDs)

radiation exposure.

Laser output: max. 1 mW

Especificaciones LÁSER:

PRECAUCIÓN

Producto LÁSER de Clase 1

El uso de los controles, los ajustes o los procedimientos que

Longitud de onda: 790 nm (CD)/658 nm (DVD)/405 nm (BD)

no se especifican enste manual pueden causar una exposición

Salida de láser: máxima de 1 mW

peligrosa a la radiación.

LASER Технические характеристики:

BRX-610

ПРЕДОСТЕРЕЖЕНИЕ

Класс 1 LASER продукт

Использование органов управления или произведение

Длина волны: 790 nm (CD)/658 nm (DVD)/405 nm (BD)

Blu-ray Disc Receiver

настроек или выполнение процедур, не указанных в

Выходная мощность лазера: не более 1 мВт

данной инструкции, может отразиться на выделении

опасной радиации.

BRX-610

The laser component in this product is capable of emitting radiation

exceeding the limit for Class 1.

CAUTION:

INVISIBLE LASER RADIATION WHEN OPEN.

El componente láser de este producto es capaz de emitir radiación

DO NOT STARE INTO BEAM.

que sobrepasa el límite establecido para la clase 1.

DANGER:

INVISIBLE LASER RADIATION WHEN OPEN.

Лазерный компонент данного изделия может выделять

радиацию, превышающую ограниченный уровень

AVOID DIRECT EXPOSURE TO THE BEAM.

радиации для Класса 1.

Owner’s Manual

Manual de Instrucciones

Инструкция по эксплуатации

© 2011 Yamaha Corporation

Printed in China BRX-610_TLF-1