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.

What kind of resolution dm365 codec support?Must I attach other chip (eg FPGA) to be 60p down to 30p at high frame rate video streaming into the dm365 the process?

Questions on the dm365 is as follows:
1. What kind of resolution dm365 codec support? Was measured according to pixel clocks do? How much is it up to the pixel clock?
2. If my video input source is 720p60 or 1080p60, since the dm365 does not support the 60 frames, so I have to add another chip (FPGA) the frame rate down to 30 or 10, making video resolution into a 720p30 or 1080p10, yes so? Is an additional chip (FPGA) necessary? Can DM365 itself, drop the frame rate from 60fps to 30fps (or 12 fps)?
3. Whether it can support the encoding and decoding at the same time?
4. Codecs, whether it is real-time do? Its latency is the number of milliseconds?
Thanks!

  • 1) The maximum pixel clock supported by DM365 video input port is 120 MHz; this means that (resolution x refresh) rate must be less than or equal to 120 MHz.  Per SMPTE video standards, 720p60 and 1080i30 both require 74.25 MHz  pixel clock, hence this should not be an issue; however 1080p60 requires 148.5 MHz pixel clock which is beyond the capabilities of the video port.

    2) 720p60 should be fine, and our demos do captrue 720p60 but only encode 720p30 (the drop in frame rate is handled by software).  1080p60 however, is a prolem since our video port cannot handle 148.5 MHz pixel clock and hence a drop down to the appropriate pixel clock would have to be done externally.

    3) this part does support enconding and decoding at the same time and even enconding of multiple channels while decoding; however, you should consider the system resources such as DDR2 memory available, DMA channels, and the fact that only one codec instance can use the MJCP at any given time.  Therefore, the resolution and refresh rate you choose to work with will dictate how many instances of a particular codec you can have.

    4) The term real-time is often mis-used, so I want to be careful here.  There is always a small delay in our encoding and decoding process but this does not mean they prevent this part from being used in real-time applications.  The delay should be in the order of a few msec, but it will depend on the size of the image being encoded or decodec.  We have shown encoding and decoding of 720p video at 30 fps, which means the encoding and decoding had to complete in less than 1/30th of a second or 33 msec, the keywaord here being less.  How much less will depend on the resolution of the image and what else is going on in your system,(e.g. is there contention for DDR2 bandwidth while encoding or decoding).

     

  • Thank you very much!

    In additon,I have a question.

    Our applications are as follows

    VGA Video:
    1920*1080*30
    1280*1024*60
    1280*960*60           =============>  A/D ==============> DM365 ============>USB  Wifi Wireless Adapter
    1280*800*60
    1280*720*60
    1024*768*60
    800*600*60

    1.There are many different formats of video vga interface,can DM365 detect them by software

    ?either, Do I  have to detect them to notify dm365 by external chips?

    2.Where do I find the datasheet of the DM368. What's the difference to DM365?

    Thanks!

  • When you say VGA video, I assume you mean digital video interface correct?  VGA video normally refers to 640x480 video resolution.  Many also refer to DE15 connector as VGA connector, but this would be in the analog space and DE15 is a more accurate term.  Anyway, I do not mean to go off on a tangent here, just wanted to clear things up for the benefit of other readers of this post.

    That said, an interesting thing to note with regards to my previous post is that  resolution x refresh rate should be less than or equal to the maximum pixel clock supported (120 MHz for video input on DM365).  The resolution in this equation includes the blanking interval.  For example, when supporting TV resolutions per SMPTE standards, SMPTE296M defines a 720p frame as 1650*750 (of which 1280x720 is active video and the rest blanking intervals); this is how they arrive at the 74.25 MHz pixel clock requirement (1650*750*60fps = 74.25 MHz).  I point this out because if you are NOT adhearing to the SMPTE standards, then depending on the size of your blanking intervals you may be able to support all of the resolutions listed above (the biggest of which 1280*1024*60 = 75 MHz pixel clock < 120 MHz MAX, which means you have plenty room for blanking intervals).  That said, you would have to analyze your video input source to determine what size blanking intervals it is providing to determine it it exceeds the max pixel clock requirement of 120 MHz.

    now to answer your questions

    1) DM365 video input port is very flexible, you can tell it to act as a master (where it defines the video format expected) or as a slave (where it determines the video format by sensing the hsync, vsync, field signal pins that are provided by the external video source part).  Of course, in the slave case, you would have to make sure you have allocated your software buffers to a large enough size to support the largest resolution size you will need to support. 

    2) I have not heard of DM368 and cannot find information on it internally (I normally can even for parts that have not been released); either way, if you cannot find the data-sheet via www.ti.com, it likely means this part does not exist or has not been released yet.

  • ok found some info on DM368; unfortunately, as suggested above this part has not been released so I cannot disclose much information on it on this forum.  You can try contacting your local sales representative who may be able to provide more NDA type information.

  • Your answer made me know much more about the dm36x. Of course, it also improve my knowledge of video processing.Thank you very much!