I see similar problem with the colors. It is probably due to the Hable operator implemented with DGTonemap plugin with its dafaults.
At least, I’ve seen same results with ffmpeg tonemapping filters.
Three of above screens are results of Hable tonemapping. The fourth is from the source UHD .hevc.
Working with 240 frames cut from the source Gladiator 2000 UHD I've encountered two more problems:
- DGDecNV(), when works, processes 236 frames.
Code: Select all
>avs2yuv64 -depth 10 -raw DGTonemap.avs - | x265-64bit-8bit-2018-10-08 - ...
yuv [info]: 1920x1080 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file:
...
x265 [info]: HEVC encoder version 2.8+74-fd517ae68f93
...
x265 [info]: tools:
avisynth 16-bit hack enabled
DGTonemap.avs: 960x1080, YV12, 10-bits, progressive, 24000/1001 fps, 236 frames
encoded 236 frames in 293.53s (0.80 fps), 59210.41 kb/s, Avg QP:16.28
If I use FFMS2() as a source instead I have
Code: Select all
>avs2yuv64 -depth 10 -raw DGTonemapMod.avs - |
...
DGTonemapMod.avs: 960x1080, YV12, 10-bits, progressive, 24 fps, 240 frames
encoded 240 frames in 314.47s (0.76 fps), 58830.89 kb/s, Avg QP:16.23
- HDR2SDR plugin doesn't work properly.
It process more than 500 frames and I cancel it. Seems like a program loop.
The result seems as if color channels' frames are overlaid.
Working environment
Window 10 Pro v.1803 Build 17134.345
GeForce GTX 1050 Video driver v.398.82