You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm planning to use an ESP32 in a commercial (and Open Source) project of a Bluetooth Audio DAC and was very happy when I found your work regarding the aptXs and LDAC codecs implementation inside ESP-IDF.
Everything is working as expected (not without some headaches but anyway) but now I'm facing some legal concerns about :
1 : You fork of the ESP-IDF
2 : The CODEC you implement which are license free for the encoder part but not for the decoder
So, question #1 : Does an commercial use of your fork of the ESP-IDF is possible (I supposed it has to follow the same license as the orginal IDF)
Question #2 : Do you have an idea regarding the legal part with these codecs? Am I still supposed to pay a license fee to Qualcomm and Sony ? If I'm not doing it, do I have the right to expose the compliance with these CODEC in my product description?
If you got answers to any of these questions it would help a lot.
The text was updated successfully, but these errors were encountered:
Aptx and Ldac need a licensed to use in commercial. If you have contacted Qualcomm or its licensed supplies you may get there own chip and there programing tools.
Hi there,
I'm planning to use an ESP32 in a commercial (and Open Source) project of a Bluetooth Audio DAC and was very happy when I found your work regarding the aptXs and LDAC codecs implementation inside ESP-IDF.
Everything is working as expected (not without some headaches but anyway) but now I'm facing some legal concerns about :
So, question #1 : Does an commercial use of your fork of the ESP-IDF is possible (I supposed it has to follow the same license as the orginal IDF)
Question #2 : Do you have an idea regarding the legal part with these codecs? Am I still supposed to pay a license fee to Qualcomm and Sony ? If I'm not doing it, do I have the right to expose the compliance with these CODEC in my product description?
If you got answers to any of these questions it would help a lot.
The text was updated successfully, but these errors were encountered: