I wonder if there is a plan to support the custom image strides(or called pitches), with which the users can set the special strides of each plans for a YUV format.
My work relates to lots of aligned raw YUV/RGB formats, which means there are some padding after the real valid data at the end of each line of an image. For example, the following images cannot be analyzed correctly:
YUV444SP with 720x480 size and 64 bytes alignment to each plan independently, the image strides are [768, 1472]. But only we flow the default strides (which are [768, 768x2=1536]) can the image be analyzed correctly.
RGB888 with 720x480 size and 64 bytes alignment, the image stride is (720x3+63)/64x64=2176. But 2176 is not a multiple of 3, so the image cannot be analyzed neither.
As far as I know, this feature is valid on PixelViewer. Let me know your opinions, and I'm willing to help.
Thanks.
I wonder if there is a plan to support the custom image strides(or called pitches), with which the users can set the special strides of each plans for a YUV format.
My work relates to lots of aligned raw YUV/RGB formats, which means there are some padding after the real valid data at the end of each line of an image. For example, the following images cannot be analyzed correctly:
As far as I know, this feature is valid on PixelViewer. Let me know your opinions, and I'm willing to help. Thanks.