Sat Jan 09, 2021 4:21 am
This bug still occurs in ver.17b6.
It seems to occur when decoding H.264 MP4 with Direct X. You can avoid this problem by installing FFmpeg and using it for decoding at present.
(However, since FFmpeg may not be available depending on the working environment, this is not a fundamental solution.)
Incidentally, whether this bug occurs or not seems to depend on your PC configuration.
As far as I have verified, the problem occurs on AMD CPUs and NVIDIA GeForce series graphics board machines.
On the other hand, I have not encountered this problem on Intel CPUs and NVIDIA Quadro series graphics boards, not only in ver.17b6, but also in ver. 9 and 16.
Also, the Fusion page in Resolve can play H.264 MP4 without any problem regardless of the PC configuration.
From the above, I personally suspect that the cause is the decoder, or some kind of non-optimization in the software, or both.