Quote:
Originally Posted by LigH
Running x86-64 (AMD64) Windows applications requires both a CPU with x86-64 instruction set and a 64-bit code variant of a Windows operating system (optional and common as private user OS since Vista, more or less mandatory since 8).
Thanks to the extended compatibility in the x86-64 architecture developed by AMD (in contrast to the Itanium IA-64 architecture by intel which is incompatible to x86 / IA-32), 32-bit x86 processes still run in a SysWoW64 (Windows on Windows-64) environment, but all DLL's used by a 32-bit process must also be programmed for 32-bit x86 architecture, and all DLL's used by a 64-bit process must be programmed for 64-bit x86-64 architecture. Windows will check the DLL header and refuse to load libraries not matching the bitness of the calling process.
To be able to load the 64-bit variant of madVR (and LAV Filters), you have to run a 64-bit player application on a 64-bit Windows.
64-bit code can already be faster simply because CPU registers in 64-bit mode have a) twice the width and b) twice the number, compared to the 32-bit mode. Every instruction which can avoid RAM access by using data still stored in another CPU register is a little improvement.
|
OK, i was maybe not enough clear.
System is in Win10 64 bits.
The installation included lav32bits, reclock32bits, mpc-be32bits and madVR.
Linked to the issue with CPU 4k hevc decoding (multiple drop with "queue decoder" at 1 while CPU is not above 40% of usage), player potplayer64 bits has been installed without any other modification and fixed the problem.
Lav is still in 32 bits. Reclok also (of course)
It seems to work fine. i was surprised.
Question is : in this case, what is the mode used by madVR (32 or 64 bits) ?