I am a bit confused to discover that there are 3 different SDK's to be used with DM8168: ezsdk, rdk and vcsdk. It makes the decision of which SDK is best a bit complicated when there are so many SDK's and each one is totally different from the other in every perspective (support different drivers, has totally different framework, supported video codecs,supported audio codecs, capture, ...), and also becuase the length of work for merging one feature from one sdk into other sdk is a complicated task.
I would like to ask if anyone here help me to understand:
1. what is the purpose of each one ( especially vcrdk which I can't find any information about)
2. why there is no single generic configurable sdk for all different purposes, and products?
3. it seems that only ezsdk is the formal, why is that ?
4. What is TI's future expectation from each one of the SDK's ?
There is only EZSDK available for broad market. Other SDKs/RDKs are only for focused markets/applications that use reference designs.
Thanks for the reply.The main problem here is that some of the features in the RDK are suitable for our product (NVR, multi channels, etc.), but unfortunately RDK does not includes support for other features we expected it to have (which are included in the EZSDK):
- audio codecs in DSP - exist in EZSDK, including xDM , but not in RDK (RDK does not use xDM in DSP !)- video codec MPEG-4 encoder exists in EZSDK, but not in RDK. - HD support - exist in EZSDK, but is it supported in RDK ? We got different answers from different TI's employee.
This issues brings up major problem for us, and we are not sure what is the best SDK's for us from the perspective of minimum gaps in each SDK.
Thank you again for your time,
I just responded you on the other thread. Please note that RDKs are very specific to the end application they are targeted for. Also, they are not available for customers outside those specific applications. Please contact your local TI representative for more details on both.
Thank you very much for the reply.
I would like to ask for your advice...
if I use RDK I have many gaps in ducati: add support for mpeg-4 encoder, and add support for audio encoder (aac) maybe in dsp, which is not xDM in rdk.It seems that there is a lot of work in ducati, and I also see that there is poor support for such big changes in ducati.
if I use EZSDK I already have the codecs I need in the released version, but ezsdk does not support multichanneling. I think we can overcome this, by using FPGA and into single HD. the application can later use openmax for the video streams. multichannel is required only for encoding.
We also have latency requirements (50msec for decoding, 700msec for encoding).
It seems that choosing EZSDK is a better choice here, although I got recommendation to use RDK (becuase of the SD multichannel ?).
Thank you very much for your time!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.