Hi,
Is it possible to do 1080i25 and 1080i30 h264/mpeg4 encoding in dm368?
If possible , is ther any reference design which supports tvp7002 and h264 encoding with deinterlacing ?
Regards,
Mahendra Kumar
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.
Hi,
Is it possible to do 1080i25 and 1080i30 h264/mpeg4 encoding in dm368?
If possible , is ther any reference design which supports tvp7002 and h264 encoding with deinterlacing ?
Regards,
Mahendra Kumar
Hi,
The processor has the power to encode 1080i25 and 1080i30 (TI IPNC design does 1080p30 H.264).
Regarding to reference design which supports TVP7002, I am checking with other groups to see we have such. I will let you know if we have it.
Regards,
Tai Nguyen
Mahendra,
I think Z3's DM368-RPS may fit your needs:
http://z3technology.com/Z3-DM368-RPS.pdf
Regards,
John Whittington
Hi Mahendra,
You can take look at the DM6467EVM for a reference here. It uses the TVP7002.
Regarding H.264 encoding with deinterlacing, it is not going to fit with the DM36x while doing the encode, so you would need an HD deinterlacer. You should be able to find something that will sit between the TVP7002 and DM36x but it will add some cost.
Hope this helps.
Thanks and regards,
Tai Nguyen
Hi Tai Nguyen,
Thank you for the reply.
Do you have some numbers regarding the performance of DM36x doing "deinterlacing and/or h264" with tvp7002 to check ?
Hi Mahendra,
Just to confirm, do you want to encode 30 fields per second or 60 fields per second?
DM36x H.264 encoder supports field based encoding so you can encode a field at a time and it refers to previous field/frame for motion estimation.
We can do 1080P30 on DM368. But for field based encoding, it should be around 54 fields per second. This is because of more number of process calls for the encoder (double the number from frame based encoding) and also due to little degradataion in performance of the codec.
Regards,
Anshuman
PS: Please mark this post as verified, if you think it has answered your question. Thanks.
Anshuman,
Just to confirm...
Does this mean that the DM368 cannot encode a standard 1080i60 signal?
BR,
Steve
Thanks for the reply. We would like to do deinterlacing and then enocding with dm368. I assume this can not be done with dm368.
Do you have any ipnc reference design that supports tvp 7002 ADC and Dm368 based system?
Steve,
On DM368, we are at the boundary for 1080P30 performance (which is equivalent to 1080i60). Once we increase the number of process calls (2 per frame in interlaced mode), we are going to see a drop in fps. The number of 54 fps that i mentioned is the worst case in the system. If you just refer to codec performance, we should be able to hit around 58-59 field/s and with a very tuned system we can hit the number between 57-58 field/sec
Mahendra,
Currently, we dont have any IPNC ref design with TVP7002. But some customers have tried that approach with 1080p30 mode.
Deinterlacing and encoding for 1080i stream would not be possible on DM368, until you are willing to drop framerate. One crude way though can be, dropping one field and upscaling the other field to a frame (although this is not really deinterlacing).
Regards,
Anshuman
We use DM368 + TVP7002 in DVSDK 3.x
input source : 1080i / 60Hz , in Capture_detectVideoStd() can get std is V4L2_STD_1080I_60 and set videoStdPtr = VideoStd_1080I_30;
for encode demo ap , output is set to correct 1080i/60Hz .
But we review the h.264 stream(use v2.1 and v2.2 version) , the format is : Progressive .
What we need to check ?
Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.0
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Width : 1 920 pixels
Height : 1 088 pixels
Display aspect ratio : 16:9
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive