DM365 H.264 High Profile Encoder API

You should be able to find the appropriate document in your DVSDK install for DM365, for example dvsdk_xx_xx_xx_xx\dm365_codecs_xx_xx_xx\packages\ti\sdo\codecs\h264enc\docs\h264_encoder_dm365_userguide.pdf.

For a more direct answer, I have attached the version from the DVSDK beta (2.10.00.13) here, note that as this is beta this is subject to change, but it should give you some idea of what to expect.

Hey Bernie,

                     It looks like the H.264 Encoder in the newer DM365 Beta SDK (2.10.00.13) still does not support YUV 4:2:2 interleaved input - is this correct? The reason why i ask is that any video encoding involving raw video capture always requires using the resizer to do the 4:2:2 to 4:2:0 conversion, and consequently, the output widths of the downscaled stream has to be a multiple of 32.

I don't mind using the resizer, but I'm stuck with the x32 limitation.

Jerry,

I must admit I am rather new to DM365, but I suspect the 32- byte limitation you are referring to is die to the DMA engine used in our video processing blocks (similar to other DaVinci platforms).  This means that ideally, if you are using 16-bit (2 byte) YCbCr pixels, you would want to work with mutiples of 16 pixels (2 bytes x 16 = 32 bytes alignment) for optimal efficiency.  However, if you are working with resolutions that are not 32 byte aligned what I have seen done in the past is

1) crop off some of the line length to make it 32 byte aligned (e.g. use 704 line width instead of 720 assuming 1 pixel per byte)

2) manipulate memory so that you have some padding at the end of each line to make it 32-byte aligned (line length becomes 736 instead of 720); yes, you will resize some meaningless data, but as long as you keep this in mind, you can decide to save only the meaningful data to a file.  Alternatively, if you are displaying, the fact that you are reading in 736 bytes of data via DMA engine does not mean you have to display all of it, you can set your video display window to 720 (underneath, the DMA engine will still read-in 736 bytes, but will only display 720).