This is a device that converts uncompressed PCM audio stream from an OPTICAL OUT connection into analog audio that can be connected to a LINE IN of some device. It does NOT support decoding 5.1 audio streams.
Design considerations and other details were written up in a blog post here: https://irq5.io/2011/03/10/optical-to-analog-audio-converter/
The hardware design files are in the CadSoft EAGLE format, now known as Autodesk EAGLE. You can download and use EAGLE for free to open the files, view the schematics and generate Gerber files for manufacture.
For convenience, generated files may have been made available under the Releases or Downloads section of the repository, but otherwise, you have to do it yourself.
Some footprints used in the design may have come from the SparkFun EAGLE libraries.
spdif2analog is licensed under the TAPR Open Hardware License (https://www.tapr.org/OHL).
Copyright (C) 2011 Darell Tan
The TAPR Open Hardware License ("OHL") agreement provides a legal framework for Open Hardware projects. The OHL addresses unique issues involved in the creation of tangible, physical things, but does not cover software, firmware, or code loaded into programmable devices. While the terms and conditions of the License take precedence, here are some key points, provided solely for convenience:
-
You may modify the documentation and make products based upon it.
-
You may use products for any legal purpose without limitation.
-
You may distribute products you make to third parties, if you either include the documentation on which the product is based, or make it available without charge for at least three years to anyone who requests it.
-
You may distribute unmodified documentation, but you must include the complete package as you received it.
-
You may distribute modified documentation or products based on it, if you license your modifications under the OHL and include those modifications.
-
Any time the OHL requires you to make documentation available to others, you must include all the materials you received from the upstream licensors. In addition, if you have modified the documentation, you must identify the modifications in a text file, and include any new files you created.