From Helix Community
Helix Producer Category FAQ
This document provides answers to common questions that are common to all projects associated with the with Helix DNA Producer Category.
- Why can't I access URL xyz?
- Where can I download application xyz?
- How can I download "mspsdk_81" and "qt5sdk" through the CVS? I get a "file not found" error though the build system.
- How is Helix Producer SDK Licensed?
- Does the Helix DNA Producer include RealAudio and RealVideo?
- Are the RealAudio and RealVideo codecs available in source code?
- Why aren't the RealAudio and RealVideo codecs available in source code under the RPSL?
- Which operating systems does the Helix DNA Producer run on?
- What codecs does the Helix DNA Producer output?
- What is in RealNetworks' product, Helix Producer, that is not in the Helix DNA Producer?
- What programming language does Helix use?
- When developers have issues using Helix DNA, where can they turn for help?
- What does the Helix DNA Producer cost to license?
- What restrictions exist in the RCSL for the DNA Producer?
- What is the TCK?
1. Why can't I access URL xyz?
Many documents in helixcommunity.org require agreement to one or more licenses before they can be accessed.
To access any project pages except the project home page, you need to agree to either the RPSL or RCSL.
To submit or edit issues, you need to agree to either the RPSL or RCSL.
To download binaries (or get to the binary download page) you need to agree to the Binary EULA.
You can find out which groups you have agreed to by viewing your group memberships here:
You should see something like this under "Group Memberships" if you are registered correctly:
- RPSL Licensees
- Binary EULA Licensees
2. Where can I download application xyz?
Downloads for different applications build on Helix DNA Producer can be accessed by clicking on the "Binaries" link in the left hand navigation bar of helixcommunity.org. To access binary downloads, you will need to agree to the Binary EULA (see previous FAQ).
3. How can I download "mspsdk_81" and "qt5sdk" through the CVS? I get a "file not found" error though the build system.
The DirectShow and QuickTime SDKs are required for some of file plug-ins compiled with the Producer SDK. Specifically, the QuickTime SDK is required for the QuickTime file reader while the DirectShow SDK is reuqired by the DirectShow file reader and capture.
Before compiling the Producer SDK, the DirectShow and QuickTime SDKs must be downloaded from Microsoft and Apple websites respectively.
The DirectShow SDK is part of DirectX and can be downloaded from http://msdn.microsoft.com by searching for DirectX and then downloading the DirectX SDK.
The QuickTime SDK for Windows can be downloaded from http://developer.apple.com/sdk/index.html by looking for the "QuickTime Windows SDK".
Configuration for 3rd Party SDKs
Once these SDKs are downloaded and installed, the .buildrc file should be updated to reflect their location as follows:
How is Helix Producer SDK Licensed?
4. The license is not included in the SDK because there are two different ways you can license the SDK as follows:
RealNetworks Producer SDK License Agreement
License agreement available when you download the RealProducer SDK from RealNetworks.com <http://www.realnetworks.com/resources/sdk/index.html>. This agreement allows the SDK to be distributed in any commercial application free of royalty.
RCSL - RealNetworks Commercial Source License <https://helixcommunity.org/content/licenses#commercial>
Helix Community License agreement that provides access to binary and source code for purposes of extending the functionality or platform support of the Helix Producer. This license agreement requires that export to RealAudio/RealVideo be available on equal footing as other formats in your application.
RPSL & GPL - Free and Open Source License <https://helixcommunity.org/content/licenses#foss>
Helix Community License agreement that provides access to binary and source code for purposes of extending the functionality or platform support of the Helix Producer. This license agreement requires that you contribute changes made back to the public (either into Helix Community or otherwise publicly available).
All agreements are click-through license agreements (you accept before downloading but do not need to sign any documents). All agreements have somewhat standard terms protecting RealNetworks from misuse of the SDK as defined by RealNetworks.
Both the RCSL and RPSL require additional paperwork to be completed and signed in order to distribute an application based on the source or binary code.
Additionally there is the Binary EULA (End User License Agreement) <https://helixcommunity.org/content/licenses#personal>. This document allows you to get the most recent builds of the binary SDK from Helix Community to develop with those builds. This license agreement only allows the SDK to be used for research and development purposes and is intended to give early access to the most recently developed functionality.
5. Does the Helix DNA Producer include RealAudio and RealVideo?
Yes. RealAudio and RealVideo are supplied in binary code form as part of the Helix DNA Producer. If you need access to source code for the codecs for commercial porting purposes, a source code porting license is available as an attachment to the RCSL.
6. Are the RealAudio and RealVideo codecs available in source code?
They are available for commercial porting to non-supported processors and operating systems. If you need to port the codecs, Attachment G of the RCSL grants a specific license to port the source code of the RealAudio and RealVideo codecs. For processors and operating systems that are already supported, RealNetworks wanted to ensure that developers could quickly build media applications that use RealAudio and RealVideo without the rigorous testing requirements that are associated with the codec source code license.
7. Why aren't the RealAudio and RealVideo codecs available in source code under the RPSL?
While RealNetworks owns most of the intellectual property for RealAudio and RealVideo, RealNetworks has licensed 3rd party technology for certain aspects of those codecs. RealNetworks does not have the rights to license that technology under an open source license.
8. Which operating systems does the Helix DNA Producer run on?
Today, the DNA Producer runs on Windows, Linux and Mac OS X. Also, you can freely start porting initiative for other environments.
9. What codecs does the Helix DNA Producer output?
The Helix DNA Producer contains output support for the following data types:
- RealAudio 10
- RealAudio 8
- RealAudio G2
- RealVideo 10
- RealVideo 9
- RealVideo 8
- RealVideo 7
- RealVideo G2
- Ogg Vorbis
Developers who want MP3 encoding can license the code directly from RealNetworks for a fee. This code will be made available directly through the Helix community in the future, again for a fee.
10. What is in RealNetworks' product, Helix Producer, that is not in the Helix DNA Producer?
Two main features: the graphical user interface and the RMEditor.
11. What programming language does Helix use?
The Helix DNA is written primarily in C/C++.
12. When developers have issues using Helix DNA, where can they turn for help?
Helix community members have a broad range of mailing lists and real-time chat options for receiving help from community members, which include RealNetworks' employees. Additionally, fee-based support programs are available directly from RealNetworks.
13. What does the Helix DNA Producer cost to license?
Both the RPSL and the RCSL license are free for the DNA Producer.
14. What restrictions exist in the RCSL for the DNA Producer?
Licensees must make RealAudio and/or RealVideo at least an equally visible and available output option to users of the licensee's products, if not the default option.
15. What is the TCK?
The Technology Compatibility Kit (TCK) is the test suite for the Helix DNA technology that ensures compatibility and compliance of the core APIs. Developers must ensure that their applications work with the TCK. This is the mechanism that helps ensure that all developers building on the Helix platform can "write once, run anywhere."