01-09-2019 07:12 PM
I have a YUV file which format is 4:2:2 10bit. Then I use VCU to encode it, as
gst-launch-1.0 filesrc location="input.yuv" ! videoparse format=nv16-10le32 width=3840 height=2160 framerate=25/1 ! omxh264enc ! filesink location ="output.h264"
The file output.h264 cannot be decoded rightly!
I used zcu106 with TRD-2018.3
01-11-2019 02:31 AM
Unfortunately, the VCU TRD 2018.3 does not support 10 bit data (i.e. NV16 is not supported). It should be supported in a future release.
01-13-2019 05:55 PM
ok! Thanks for your response!
But when I use the command like this
gst-launch-1.0 filesrc location=/mnt/input.h264 ! h264parse ! omxh264dec ! queue max-size-bytes=0 ! omxh264enc num-slices=8 control-rate=2 b-frames=0 gop-length=1 target-bitrate=400000 ! filesink location=/mnt/output.h264
the Encoded file output.h264 can be played well with the VLC player!
the input.h264 is 4:2:2 10bit, while the output.h264 is 4:2:2 10bit too!
I do not know why
01-14-2019 01:00 AM
01-14-2019 10:50 PM
I have tested 2018.3-zcu106-release.
It can not work too.
so, I wonder to know whether the VCU support NV16-10le32 encoder or NV16 encoder?
01-15-2019 01:37 AM
According to PG252, the VCU can do both:
Are you sure your YUV file is correct?
01-16-2019 01:48 AM
The raw yuv file is stored by this command:
ctrlsw_decode -i 4k_input.h264 -out output.yuv -avc --prealloc-args 3840x2160:progr:422:10:11:52
while the 4k_input.h264 is 4:2:2 10bit format, and the YUV file can be showed rightly with pYUV tool.