We have looked into this before and it turned out that because MPC-BE did not support the latest version of the MPC-HC API there was nothing we could do from within Syncplay to support it. As such, you should be asking MPC-BE to support Syncplay rather than asking Syncplay to support MPC-BE. If MPC-BE ever supports the current MPC-HC API (i.e. the features which Uriziel added to MPC-HC back in 2012) then we'd love for someone to let us know because then we could just tweak our MPC-HC code to support MPC-BE.
It also seems like they haven't fixed the bug which prevents 32-bit applications from working with the 64-bit version, which is to add " : unsigned int" after "typedef enum MPCAPI_COMMAND" (MPC-HC ticket #2470)
Seems to work on a cursory test with MPC-BE 18.104.22.16848 x64, but haven't done a thorough test. If you are using MPC-BE 22.214.171.12423 or above then please copy mpc-be64.exe and rename it mpc-hc64.exe (or mpc-be.exe and rename it mpc-hc.exe), set that as the path to player executable in Syncplay 1.5.0, and tell me how well it works. If we can confirm it works without issue then we can add recognition of the MPC-BE executable filenames to Syncplay. If there are issues we can see if they can be resolved Syncplay-side or if they need further changes to MPC-BE.
@joeoe asked about MPC-BE support back in 2015 (#68) so they might be able to test it too.
I use MPC-BE (Like MPC-HE, but with black UI and some improvements..)
It seems to not be usable. Can you add support, thanks
Exe name: mpc-be64.exe
The text was updated successfully, but these errors were encountered: