Quote:
Originally Posted by poisondeathray
For me, it just crashes, regardless of export codec. Both x86, x64 versions
But works ok (without highlight issue) when fed through vapoursynth or avisynth
I think it has to do with the caching input driver
|
No crash here with that sample clip. And like I said, the odd thing is that:
Quote:
Originally Posted by WorBry
... it (the aberration) doesn't occur with 4K/HD-AVC (8bit) clips recorded with full luma range i.e. decode format YUV420-709-FS.
|
....and that includes clips recorded on the same camera - a Pana GH5 in this case, which gives the option to select the 'luminance level' (i.e. luma range) - 16-235, 16-255 or 0-255 in 8-bit. As can be seen from the YUV Histogram, the above sample clip was shot in 16-255 range, which is how most camcorders record 8-bit 4K/HD-AVC also - i.e. Rec709 allowing for excursion/overshoot of data values into the super-whites.
Evidently, with these 16-255 range clips something is going on YUV420-709 > YUV420 or YUYV (YUY2) 'conversion' that is preventing transfer of the full data range. Come to that, why does YUV420-709 need to be 'converted' to YUV420 anyway if the decompression format 'interpretation' is set for 'no change' in the component range ? Surely it's just pass-through ?
Anyhow, hopefully Shekh will get to the bottom of it.