New
#21
A player such as VLC uses its own built-in codecs in order to work its way around problems related to codecs like missing codecs, installed buggy/outdated versions of codecs or broken codec installations, and misconfigured codecs. I'm not sure if Potplayer also does this, or partially does this, or whether some codecs are installed or (re)configured during the installation procedure of Potplayer, as I never felt the need to even try it out. There might be issues with the internal renderer that it uses, or with how exactly it handles (some) external renderer(s), I don't know.
The only renderer I've been using for the past 8 years or probably longer is madVR (by madshi). It has been working seamlessly together with MPC-HC x64 (by clsid2 et al.) built-in LAV Splitter (by nevcairiel) and the LAV Video decoder that it uses (with the default setting of 'DXVA2 copyback' for the hardware acceleration method, and keeping the HEVC checkbox for it in the decoder's settings window checked...) for such a very long time now, that I actually lost track of how long. People use this with their multithousand dollar cinema projectors and their multithousand dollar multichannel audio setups. It was the proverbial rock in the ocean, like a milestone achievement had been brought to the HTPC enthusiast community─and it still is.