DM365 EVM Decode H264 1080p

Did you upgrade the h.264 codec?  I am using DVSDK 2.10.01.18 with all the default software and can encode and decode 720p just fine.  The demos do not support 1080p by default, so I am guessing you added this functionality; however, please note that our dm365 part does not support a pixel clock to achieve 1080p @ 60 (normally progrssice resolutions are at 60 fps).  Therefore, assuming our codec support 1080p (see corresponding codec data-sheet) and that DM365 has enough horse-power to decode 1080p stream, you will not be able to capture or display 1080p @ 60 with this part.  You may be able to do 1080p at a lower refresh rate, which may require even more changes to demos....just things to consider.

Thanks for your replay.

Yes, I already update my dm365 H264 codec engine (Encoder & Decoder) inside my dvsdk.

And I already can encode H264 1080p bitstream from a YUV file. (I modify the dvsdk_demos_2_10_00_17 encode example).

When I try to use the decode example to do decode I can not make it.

Event the 720p decode will be fail, It can work if I use the original dvsdk release codec engine.

this is interesting; unfortunately, I have not tried the new h.264 codecs, but will forward this to our codec team to see if they can offer any insights.  Where did you get the new h.264 codecs?

Thanks for your replay.

I got the codec form TI web page.

And I hear some information the DVSDK2.x the default support is 720p resolution, and DVSDK3.x will default support up to 1080p.

So, I think I should wait for it.

Not try by DVSDK2.x.

Am I right?

Thanks

Thanks for your help.

Finally, I can use mpeg4enc to encode 1080i ,and use mpeg4dec to decode 1080i via component to LCD TV.

It look good.

But I still a problem.

When I keep to try H264 codec, the H264 encoder is fine, I can encode 1080i .

When I try to decode 1080i, the decoder told my it need a memory pool 18321120.

It more tnan 18M bytes, It make me hard to arrange memory pool.

Why the decoder need such big memory pool?

Thanks

Kenneth Tu said:

When I try to decode 1080i, the decoder told my it need a memory pool 18321120.

Thanks

From the experience I have with encoders and decoders, their memory and CPU needs typically grow exponentially with the size of the video frame.  This is not a linear relationship.  The corresponding codec data-sheet should have information on the memory requirements for some of the more popular resolutions.

Kenneth Tu said:

I got the codec form TI web page.

Do you have a link to the web page; I want to ensure we are looking at the same one.

Kenneth Tu said:

And I hear some information the DVSDK2.x the default support is 720p resolution, and DVSDK3.x will default support up to 1080p.

So, I think I should wait for it.

Not try by DVSDK2.x.

Am I right?

I have not heard this myself.  However if 1080p support was added to drivers, codec(s) and demos in DVSDK 3.1, you would still need the hardware to support it; although I am not at liberty to say (without an NDA) if and when we will have 1080p parts on our roadmap, the current DM365 EVM hardware cannot support 1080p @ 60 capture or display, hence I hesitate to suggest it will have full 1080p support as this normally implies 60 fps and our DM365 was not designed to support such high pixel clocks.  Sure you may be able to do 1080p and lower refresh rate, but some may not consider this true 1080p hence we want to be careful here. 

That said, I will see if I can find more info on DVSDK 3.xx's ability to support 1080p.

Kenneth Tu said:

Finally, I can use mpeg4enc to encode 1080i ,and use mpeg4dec to decode 1080i via component to LCD TV.

It look good.

When I keep to try H264 codec, the H264 encoder is fine, I can encode 1080i .

Thanks

did you succeed with dvsdk 2.10?

i read http://wiki.davincidsp.com/index.php/DM365_Codec_Availability_Schedule 

it support 1080p available.

http://software-dl.ti.com/dsps/dsps_public_sw/codecs/DM365/index_FDS.html

so i changed linked codec and compiled.

but it showed error message during play ..

could you please give some idea or the point to fix it? 

thanks

Melon, Kenneth,

Please let us know about the respective exact error messages you are getting during compile or runtime. Based on those error messages, we can try to provide further help.

For the memory requirements and allocation, all codec requirements can be met by creating pools listed in the codec datasheet. For application requirements, i would suggest you remove the display from decode application and just do a file read write decode test which writes output YUV data to a file.

Regards,

Anshuman

Thanks eveyone,

After I change the codec lib from DVSDK, It been solved.

Could I ask one more question?

My project need to replace the component in/out to HDMI in/out on DM365 EVM.

Does anyone give me suggestion for this ?

Have any solution for me?

Thanks againe!