CMC Forums

New installation of Windows 10 and CMC 7.1.
Getting errors while starting both movies and trailers, but only from CMC. I have CMC set to playback videos through MPC-BE: Movie error example: Trailer error example: I'm using the latest available MPC-BE.1.7.1.x64.exe (just downloaded today after testing my previous version exe and having this issue; the new version made no difference with this). I also installed this new version on a working CMC test machine and it continued to work with the new MPC-BE.
On the non-working PC I've uninstalled MPC-BE and reinstalled, tried different installation settings, compared to a working install, etc.

The same movie launches in MPC-BE fine if I go direct to the movie folder, click on it and allow MPC-BE to launch it.
I haven't had this issue before on any of the PCs I've done testing on. Not sure what else to look at and would like your suggestions.

Here is the Playback Debug Log, which I'm guessing you'd want to see next:

PlayClick Debug Log Generated 2024-05-19 9:34:37 PM with CMC v7.1.2024.0001
---------------------------------------------------------------------------
*** BEGIN OF PLAYCLICK DEBUG LOG ***
* Disc Number=0
* Disc Location=\\CRYPT\Movies\Road House (2024)
* Disc Type=dtBluray
* Container=ctUnknown
[9:34:37 PM] Validating Disc Location: \\CRYPT\Movies\Road House (2024)
[9:34:37 PM] Checking if network device "CRYPT" is online.
[9:34:37 PM] "CRYPT" is online.
[9:34:37 PM] "CRYPT" is NOT configured for Wake on LAN for Playback, skipping Share Online validation.
Scanning Folder: \\CRYPT\Movies\Road House (2024)
Found Playable Media, checking to see if assigned to another Disc: ROAD.HOUSE.2024.1080P.WEB.H264.MKV
Media File not in use, selecting for playback
Not Exiting Folder Scan, looking for ISO's in case this is just a movie trailer
Could not find ISO or DVD Folder for playback
* Player=MPCBE
* Player Commandline= "\\CRYPT\Movies\Road House (2024)\ROAD.HOUSE.2024.1080P.WEB.H264.MKV" /fullscreen /play /close
[9:34:37 PM] Launching 'Media Player Classic'
[9:34:46 PM] *** END OF PLAYCLICK DEBUG LOG ***
[9:34:47 PM] Focused has returned to CMC, playback ended
[9:34:47 PM] Processing Movie Return
[9:34:47 PM] Automark Watched Threshold not met, Logging Watch Event with Duration 0minutes


Plus one more CMC error box that came up after another attempt to launch a trailer:

The problem is that the MPC-BE executable was not found.

Please post the path to the MPC executable so I can determine why it wasn't found.

Just a regular installation of the newest MPC-BE.1.7.1.x64.exe with default installation path which seems to be "C:\Program Files\MPC-BE"

I checked, and "C:\Program Files\MPC-BE\mpc-be64.exe" is a combo I've not seen before.

Currently, CMC checks for:

• "C:\Program Files\MPC-BE x64\mpc-be64.exe"
• "C:\Program Files\MPC-BE\mpc-be.exe"
• "C:\Program Files (x86)\MPC-BE\mpc-be.exe"

So CMC looks for mpc-be64.exe, but only inside an MPC-BE x64 folder. And it only looks for mpc-be.exe inside the non-x64 folder.

Since you did the default path, I'm guessing that they've made a change. I've updated the code, and it will be on the next CMC v7.1 Release Candidate.

FYI, I uninstalled the MPC-BE x64 installation again in order to verify/check what I told you before.
The installation I had grabbed was from here:
https://github.com/Aleksoid1978/MPC-BE/ ... /tag/1.7.1

And when I go to install it, the default folder for the 64bit version of MPC-BE is definitely defaulting to C:\Program Files\MPC-BE I changed the install folder by adding the " x64" to the folder name and all is well with the world now.
The "mpc-be64.exe" file created by the install is indeed found and used by CMC as expected. Thanks for adding the additional PATH to your code; it will be useful for the future if the MPC-BE Developers do in fact want to start using the folder without the x64 in the name, which makes sense to me.

Yep, agreed, I never liked that they had multiple install folder names based upon the bit-version installed, especially when they were already going into different paths anyway (Program Files (x86) vs Program Files). Seemed convoluted. Hopefully this is just them finally cleaning up that logic.