• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 302 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.

TMS320DM368 video codec capability question

Mark Latham
Intellectual 275 points

Hi,

Q.  Can the TI-supplied codec can be used to encode the composite video + OSD image, or is it only capable of encoding the incoming video stream?

I'm new to the DM368 and cannot find any documentation to answer this question.  Thanks in advance for your reply.

  • 0
    Genius 3510 points

    Mark, answer YES. You can capture stream from composite input. Please see documentation on DMAI module Capture.

  • 0 in reply to Kirill Brilliantov
    Intellectual 275 points

    Hi Kirill,

    I'm asking if the capability exists to encode the OSD + video, in other words, what the user sees on the LCD with graphic OSD blending.

    If there is some web location that lists all the capabilities, could you point me to it?  I think TI gaurds the architechture so I cannot answer this from a hardware perspectivve.

    Thanks in advance for your reply. 

  • 0 in reply to Mark Latham
    Genius 3510 points

    Hello, Mark!

    I do not see different in video stream and video stream with OSD. Can you expand this differents?

    You can see documentation in repository Capture.h

  • 0 in reply to Kirill Brilliantov
    Intellectual 275 points

    Kirill,

    Again, since I don't have access to the video coprocessor hardware specifications, this may be a silly question.  However, our client wants to record what they see on the LCD, which is a combination of video (does not matter composite, s-video, etc) *plus* the OSD graphics.  So there is an output stream for video out and LCD that includes the combined images from the frame buffers, and this is what we want to encode.  Hope that makes sense.

    I did review the .h file (thanks for the link) and only see raw video inputs for the encoder.  Thanks again in advance for your reply on this.

  • 0 in reply to Mark Latham
    TI__Mastermind 37340 points

    The answer to this lies on Figure 2 of Video Processing Back End User Guide (VPBE UG)

    In order to encode a video frame, you must pass a buffer to the video encoder; the memory address of this buffer is passed via video encode APIs and this video frame normally lies in DDR2.  The video frame can have any content on it (e.g. video along with graphics on top) as long as it is available in memory.  However, if you are using OSD to place graphics on top of video, as you can see from Figure 2 above, there is no path from OSD back to memory buffer (output of OSD goes directly to video output port and does not get placed in any memory buffers); therefore graphics generated via OSD cannot be encoded.  A workaround would be to use software (instead of OSD) to write graphics on top of video frame in memory and then pass this memory buffer to encoder.

    Hope this helps

  • 0 in reply to Juan Gonzales
    Intellectual 275 points

    Thanks, Juan for the clarification.  I had studied the VPBE but the video coprocessors remain closed IP, and I was just hoping that they could tap the output stream.