Supporting FPP development since 2022. Proceeds go to help further FPP development.

FAQs – Cape Vendors

ALL FAQs

c Expand All C Collapse All

You may sell (or give away) the License Key Voucher as part of a bundle with a cape, but vouchers are not to be sold or given away without a cape.

As always, consult your accountant or tax attorney, but we believe they could be considered as an expense on your side so therefore would deduct from your net profit.

No, we do not support transferring a license key from a vendor to a customer. If you want to provide licenses to your customers as part of their purchase, you can bulk purchase license key vouchers from us and give a voucher to your customer when they purchase a cape. This way the license key does not have to be transferred to the customer.

No. In order to (re)sign an EEPROM, the user must supply the license key and order number. We do want to allow individual users to transfer a license if a cape is sold, but we do not support that in a vendor bulk purchase scenario. Vendors may purchase license key vouchers in bulk and give them to their customers when a cape is purchased.

Yes. You are welcome to purchase vouchers ahead of time and give one away with each cape purchased. Make sure that you are getting a voucher for the correct number of outputs.

In order to keep a level playing field, we do not allow cape vendors to sign their own EEPROMs. You can pre-purchase a license key voucher and give it away with a cape to allow the purchaser to get a free license key and sign the EEPROM via the signing UI.

I’m sure if there were enough X’s in that number we might debate it, but we would prefer that people were contributing to FPP and the community. Currently we do not allow cape vendors to sign their own EEPROMs.

For the purpose of discussion around FPP, a “3rd party” refers to a non-developer who is selling capes.

We do want to provide a level playing field for cape vendors, but feel that the capes made by the FPP developers deserve an exception. Over the years the FPP developers have spent tens of thousands of hours developing and supporting FPP. Dan wrote the code which all Beagle Capes are using to drive pixels. David is the original author of FPP and his Pi cape which uses the DPIPixels Channel Output was designed working with Chris Pinkham. We feel strongly that this pre-signed EEPROM ‘advantage’ is warranted given the time these developers have spent on FPP. If another Cape Vendor were to step in and start contributing to FPP with the same level of dedication, we would consider allowing that vendor’s capes to be pre-signed.

There are several ways to contact the development team including direct email using the email addresses in our commit logs. You can also send an email to vendors@falconplayer.com or message Chris Pinkham (CaptainMurdoch) or Dan Kulp (dkulp) on the web forum at https://FalconChristmas.com/forum/ On the forum, we currently maintain a private dedicated sub-board for vendor discussion which you are welcome to join. We are also contactable via Facebook and the FPP group there.