ram
ram
@kmilos this may not be completely true, with this pull request all the names are in sync https://github.com/google/libultrahdr/pull/96
Thank you for reporting this. We know why this is happening. Recently we have made few changes that is causing this problem. We are working on addressing the same. Can...
extremely sorry for this additional work, the earlier shared image was sufficient. sorry again. will publish changes that would resolve this problem soon. thank you.
@suhailphotos Thank you for raising this issue. I have looked at the shared images. The problem is trin_rain_base_sdr_high_quality.jpeg internal color format is yuv444. Currently library is handling jpeg inputs with...
@DichenZhang1 Some more changes are needed. We are decoding the file but the data is 444. GenerateGainMap has to make use of this correctly. Currently I am working on this.
With reference to comment "xml parse error, could not find attribute hdrgm:Version" The problem is while parsing the gainmap metadata, it sees that metadata contains, separate gainmap min, max, lambda...
I think this is the correct approach, execute_process(COMMAND ${CMAKE_COMMAND} -E remove "$ENV{DESTDIR}${file}" OUTPUT_VARIABLE rm_out RESULT_VARIABLE rm_retval)
Does this change affects the entries of ICC box
@JunLai1 thank you for pointing this out. ~~Upon going through the DataFormat spec of khronos, it seems you are correct~~. The reason for using bt601 weights for display p3 was...
@JunLai1 https://www.kernel.org/doc/html/v4.8/media/uapi/v4l/pixfmt-007.html#colorspace-dci-p3-v4l2-colorspace-dci-p3. This link has some interesting notes with respect to DCI-P3. Quoting from there, This colorspace does not specify a Y’CbCr encoding since it is not meant to be...