-
Notifications
You must be signed in to change notification settings - Fork 459
jpeg decoder can't output 444P format for YUV444 jpeg file #1575
Comments
What output format we should use (in sample_decode pipeline)? AYUV? we have no suitable FOURCC in api now. |
this case can decode successfully on local machine. |
chuanli1 could you provide your command? |
Is this output format the default?I use the default and output format '-ayuv' |
It is using VPP to convert NV12 to AYUV.
|
Thanks @xhaihao and @wangyan-intel ,I try to enable this output format in our msdk. |
Hi, output format ayuv is supported in sample_decode |
Hi, it is using VPP to convert NV12 to AYUV, but sample app can't output 444P format for YUV444 jpeg file directly. |
@SofyaBalandina Could you please confirm with @chuanli1's comments? If yes, could you please add it? Thanks. |
@SofyaBalandina Did you mean JPEG decoder in the SDK supports NV12, RGB32, and YUY2 only, right ? JPEG in the media driver may support other formats, see https://github.com/intel/media-driver/blob/master/docs/media_features.md#jpeg-decoding-format-support, e.g. 444P for 4:4:4 8-bit jpeg file and 400P for 4:0:0 8-bit jpeg file. Is it possible to support these formats in the SDK too ? |
@wangyan-intel, adding more formats to sample_decode should be possible. But biggest part is in MSDK #1960 (comment). |
Sample clip: https://github.com/Intel-Media-SDK/MediaSDK/files/2720196/smpte_444P.jpeg.zip.zip
MSDK doesn't support 444P fourcc and the output is always NV12.
The text was updated successfully, but these errors were encountered: