• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 101 subscribers
  • Views 1287 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

McFW Links API documentation?

John J Wu
Genius 3870 points

I'm looking for the equivalent of a document that has been removed: DVR_RDK_McFW_Link_API_Training.pdf

 I need more documentation on the McFW Link API.  I'm trying to modify one of the usecases in the RDK.  It uses both merge and dup links.  I'm trying to understand what they do, but there is ZERO documentation that I can find.

 The only documentation I can find in the RDK is this: IPNC_RDK_McFW_UserGuide.pdf

 But it doesn't go into details about what the various links within a chain are for.

  • 0
    TI__Expert 7765 points

    Which RDK you are referring IPNC RDK or DVR RDK? please mention version as well. DVR_RDK_McFW_Link_API_Training.pdf gives overview of how links internally work. DVR_RDK_ApiGuide.CHM is doxygen based API guide and it has Link API documented in detail. Have you referred that already?

  • 0 in reply to Yogesh Marathe
    TI__Expert 6950 points

    DVR_RDK_McFW_Link_API_Training.pdf is not available in external link. It is part of DVR RDK release. Please contact local FAE to get this document.

  • 0
    TI__Guru 71526 points

    Hi John,

      I will send it to you directly via email.  It is “TI Selective Disclosure” so cannot post it here, and only can be shared with NDA customer. 

    -Leonard 

           

  • 0 in reply to Yogesh Marathe
    TI__Guru 71526 points

    Engineer looked at the .pdf and replied:

    It's a good document, but doesn't help with what a merge link is useful for.  It did point me to some other documentation within my Source directory:   IPNC_RDK_ApiGuide.CHM  

    But this .chm did not work on LINUX development machine using the .chm viewer.  Unfortunately, IPNC_RDK_ApiGuide.CHM doesn't tell me why I might want to use a merge link.  I'm basically trying to create two encoded H264 streams at different resolutions (720p and 352x288) both at 30fps.  I started with the triple stream use case and am trying to modify it to produce 2 streams.  So I'm trying to implement:

    capture -> dup -> encode -> out

                   \-> scalar -> encode -> out

    Can you tell me if this is the right way to go about it?  Eventually I would like these two streams to be sent out by wis-streamer (at least to start with).

    -end-

     

    What advice can we give to solve this?

       

  • 0 in reply to LeonardEllis
    TI__Guru 59700 points

    Yes a mergelink is required before encode.Data flow should be:

     

    capture -> dup ->                   -- In Q0-- Merge -> encode -> out

                              \-> scalar    -- In Q1

    All mcfw links are capable of multi channel processing.

    A link like encode has a single input queue and channel numbers received in the input queue should range from channel 0 --> (maxNumChannel - 1) where maxNumChannels is the number of channels configured at encLink create time.

    Assuming 2 channel capture

    Capture (ch 0,1) --> dup --Q0--(ch 0,1) -----------------------------> Q0--->Merge (ch 0,1,2,3) -----> encLink

                                           --Q1--(ch 0,1) --> Scaler --(ch 0,1) -->  Q1--->

    As explained in the DVR_RDK_linkTraining document, mergelink will take multiple input queues and convert them into unique channel numbers on the output queue.MergeLink is needed wherever you have input to a link coming from different links.