No, but if you get a license key, you are able to get your onboard audio back. The PiCap from PixelController.com and all other PiCap clones use the RPIWS281X Channel Output in FPP. This Channel Output does not require a license key for full functionality and will continue to work […]
FAQ Category: License Keys
30 posts
No. All current-version Kulp capes come with a pre-signed EEPROM. This includes capes purchased directly from KulpLights.com as well as capes purchased from other vendors which sell Kulp capes such as WiredWatts.com. If you have an older Kulp cape which pre-dates the inclusion of EEPROMs, you should be able to […]
We do not intend to require licenses for any currently existing features other than the two primary pixel channel outputs which are part of the controller portion of FPP. We are constantly improving FPP adding new features and functionality and we want the core of FPP to remain open and […]
Yes. License keys are stacked on an EEPROM based on their $$ value, not the number of outputs they cover. Stacking two 2-output $5 keys is the same as adding a single 8-output $10 key. If you stack a $5 key with a $10 key it will enable 16 outputs […]
The License Key flavor does not have to cover the total number of string outputs on a cape. If you have an 8-port cape with 3 quad-differential outputs and a 16-output expansion header, the total number of output is 36. If you are only using the 8 onboard string outputs […]
License Keys come in 4 tiers based on the number of pixel string outputs being licensed. The four options cover up to 2 outputs, 8 outputs, 16 outputs, and 48 outputs. License Keys may be stacked, but normally it would make sense to just get the higher tier, for instance […]
License Keys are used to digitally sign the EEPROM for a cape. This can be an EEPROM included on the cape or a Virtual EEPROM provided with FPP. FPP checks for a signed EEPROM at startup. If the EEPROM is signed, the enhanced functionality in the controller portion of FPP […]
No. The FPP developers are strong proponents of Open Source, Open Hardware, and the DIY community. As a way of showing this support for our DIY cape users, we are providing free vouchers which can be used to “purchase” a License Key from Shop.FalconPlayer.com for free. If you have a […]
FPP is made up of two primary parts, the “player” portion and the “controller” portion. The controller part of FPP allows FPP to control pixels which are directly attached to a Raspberry Pi, BeagleBone, or PocketBeagle SBC (Single Board Computer). The player portion of FPP is everything else. FPP can […]
Yes! The Falcon Player developers are strong proponents of Open Source, Open Hardware, and the DIY community. If you are using a cape that you built yourself for your own personal use, send a pic of your assembled board to diy@falconplayer.com and we will send you a voucher which will […]
