Extend MCM API implementation in Media Proxy and SDK

[tszumski]

1. Extend MCM API implementation in Media Proxy and SDK with new ST2110 Transport Pixel Format field
2. Update MCM pixelFormat based on architect feedback

[ko80]

Are you going to add parsing of transportPixelFormat in parse_json()?

[ko80]

Please notice you need to update the video frame calculation in calc_payload_size() according to the introduced pixel format changes.

[tszumski]

Are you going to add parsing of transportPixelFormat in parse_json()?

Fixed in 9b32813

[tszumski]

Please notice you need to update the video frame calculation in calc_payload_size() according to the introduced pixel format changes.

Fixed in 9b32813

[ko80]

Can you check if the traffic goes?

I'm getting an error reported by ST2110_20Tx->configure()

Command line:

sudo ffmpeg -stream_loop -1 -re -video_size 640x360 -pixel_format yuv422p10le -i netflix_crosswalk_640x360_60fps_10bit_le.yuv -f mcm -conn_type st2110 -transport st2110-20 -ip_addr 192.168.96.11 -port 9002 -frame_rate 60 -video_size 640x360 -pixel_format yuv422p10le -

[tszumski]

Can you check if the traffic goes?

I'm getting an error reported by ST2110_20Tx->configure()

Command line:

sudo ffmpeg -stream_loop -1 -re -video_size 640x360 -pixel_format yuv422p10le -i netflix_crosswalk_640x360_60fps_10bit_le.yuv -f mcm -conn_type st2110 -transport st2110-20 -ip_addr 192.168.96.11 -port 9002 -frame_rate 60 -video_size 640x360 -pixel_format yuv422p10le -

New parameter transport_format in configuration structure MeshConfig_ST2110 is not set to proper value, on my platform
it is set to "-1", while allowed value is 0 (macro MESH_CONN_ST2110_20_TRANSPORT_FMT_YUV422_10BIT). This structure comes from gRPC connection

[ko80]

Looks good to me

[moleksy]

Looks Good