SOLVED: VLC dll Issues with CQC Interface Template Viewer

[gReatAutomation]

Solution for those who do not care for the details. It appears CQC is looking in C:\Windows\system32\ for the VLC dlls. 

That is, it does not appear that you need to install VLC Player.

Simply download the latest 32-bit versions of libvlc.dll and libvlccore.dll from https://www.dll4free.com/ and copy them both to C:\Windows\system32\ and the problem is solved.

== Troubleshooting Details ==
I downloaded and installed latest version of VLC (32-bit) from the VLC web site onto Windows 10. Was able to open RTSP stream from VLC.

I opened up Interface Template Viewer and received the error, "The code execution cannot proceed because libvlc.dll was not found. Reinstalling the program may fix this problem."

I added VLC program path to system path as a System Variable under Environment Variables. Same issue.

I reinstalled VLC. Same issue.

I then downloaded libvlc.dll from https://www.dll4free.com/ and coped it to the VLC program directory. Same issue.

On a hunch from my software engineering days, I copied libvlc.dll to C:\Windows\system32\ 

Different error, "The code execution cannot proceed because libvlccore.dll was not found. Reinstalling the program may fix this problem."

I reinstalled VLC. Same issue.

I then downloaded libvlccore.dll from https://www.dll4free.com/ and coped it to the VLC program directory. Same issue.

I copied libvlccore.dll to C:\Windows\system32\ 

No more errors.

I uninstalled VLC completely.

Am able to open up the Interface Template Viewer with no errors. My video stream does not display, but I am not receiving dll errors.

[Dean Roddey]

CQC doesn't look any particular place. It just invokes some VLC library code. So their library must be looking for it there. I don't think it's good for programs to install their own stuff in system directories, but presumably they put those there and install the program itself in the usual Program Files location. If the library only uses those DLLs in the system directory, then it would be the case that the VLC program itself isn't required.

Though I'd be more likely to install VLC somewhere and grab those DLLs myself from that image than download prebuilt DLLs from some other place on the internet. Who knows what kind of ugliness might be in such things.

[gReatAutomation]

I don't think it's good for programs to install their own stuff in system directories, but presumably they put those there and install the program itself in the usual Program Files location. If the library only uses those DLLs in the system directory, then it would be the case that the VLC program itself isn't required.

This is what I am saying: you do not have to install VLC at all. All you need are the two DLL's copied to the System32 directory.

If you do install VLC, the two DLL's are located in the VLC program directory and no where else on the file system.

Though I'd be more likely to install VLC somewhere and grab those DLLs myself from that image than download prebuilt DLLs from some other place on the internet. Who knows what kind of ugliness might be in such things.

That is another option.

[gReatAutomation]

Turns out the VLC issues were related to me trying to run CQC in a Windows 10 Pro virtual machine (VMWare Fusion on Mac Mini). I upgraded to an Intel NUC and have no other issues with VLC or viewing IP cameras.