Skip to content

Syncplay won't open #630

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Pandoroz opened this issue Sep 14, 2023 · 13 comments
Closed

Syncplay won't open #630

Pandoroz opened this issue Sep 14, 2023 · 13 comments

Comments

@Pandoroz
Copy link

Describe the bug
The program doesn't open, I installed the 32bit NET version with the requirements described but nothing, I saw another post where it works with the portable version 1.6.8.

To Reproduce
Steps to reproduce the behavior:

  1. When I open the program

Expected behavior

Screenshots
image

Version and platform:

  • OS: Windows 10 Pro x64
  • Syncplay version and build type: Syncplay 1.7.0
  • Media player and version: VLC 3.0.18 Vetinari

Additional context

@Et0h
Copy link
Contributor

Et0h commented Sep 14, 2023

Hi, some questions:

  1. What do you mean by NET version?
  2. Have you installed Microsoft Visual C++ 2015 Redistributable Update 3 vc_redist.x86.exe available from https://www.microsoft.com/en-us/download/details.aspx?id=53587 ?
  3. Do you get anything in %APPDATA%\Syncplay.log - you may need to run Syncplay with the --debug command line switch.
  4. Does the 1.7.1 RC1 portable available from https://github.com/Syncplay/syncplay/releases/tag/v1.7.1-RC1 work?
  5. Does 1.6.8 portable work for you?
  6. Are you using any anti-virus which might be causing problems?
  7. Are your graphics card drivers up to date?
  8. Does restarting your computer fix it?

@Pandoroz
Copy link
Author

  1. I mean the package year or whatever you can call it
  2. Yes, I also tried to install it from the given link and got an error:
    https://pastebin.com/pJyPFPSK
  3. I didn't think about logs, how should I add --debug?
LogsDuring handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "syncplayClient.py", line 17, in
File "syncplay\ep_client.pyc", line 8, in main
File "syncplay\clientManager.pyc", line 9, in run
File "syncplay\ui\ConfigurationGetter.pyc", line 553, in getConfiguration
File "syncplay\ui\ConfigurationGetter.pyc", line 455, in _forceGuiPrompt
File "syncplay\ui\ConfigurationGetter.pyc", line 419, in _promptForMissingArguments
File "syncplay\players\playerFactory.pyc", line 11, in getAvailablePlayerPaths
File "syncplay\players\mpv.pyc", line 80, in getDefaultPlayerPathsList
File "syncplay\players\mpv.pyc", line 103, in getExpandedPath
File "ntpath.pyc", line 651, in realpath
File "ntpath.pyc", line 601, in _getfinalpathname_nonstrict
FileNotFoundError: [WinError 53] Impossibile trovare il percorso di rete: '\\UnLockCatch\tools\vcruntime;'


5. No
7. No, if I remember the package downloaded from another post didn't have a library or anything similar
8. No
9. Yes
10. No

@Et0h
Copy link
Contributor

Et0h commented Sep 15, 2023

Thanks for answering those questions. The reference to vcruntime in the logs does seem to indicate to me that it relates to the correct Microsoft Visual C++ Redistributable needing to be installed.

I just checked what I installed when I re-installed windows recently, and it wasn't the 2015 Redistributable but a more recent bundle. As such, please try the Visual Studio 2015, 2017, 2019, and 2022 redistributable which as per https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 is available from https://aka.ms/vs/17/release/vc_redist.x86.exe and let me know how it works. If it resolves the problem then I will update the Syncplay guidance accordingly.

@Pandoroz
Copy link
Author

I tried reinstalling it but nothing, the program continues to crash.

@Et0h
Copy link
Contributor

Et0h commented Sep 15, 2023

I'm not talking about re-installing the 2015 Redistributable, but installing the 2015-2022 Redistributable.

@Pandoroz
Copy link
Author

I intended to reinstall the 2015-2022 Redistributable

@Et0h
Copy link
Contributor

Et0h commented Sep 16, 2023

Does syncplayServer.exe run okay for you?

@Pandoroz
Copy link
Author

image

Yes, i think

@Et0h
Copy link
Contributor

Et0h commented Sep 17, 2023

As you are the only Windows user reporting this issue I'm not sure what can be done to fix it, but it seems like a Windows library issue rather than a Syncplay issue. If you figure out how to fix it please let us know so we can update our guidance.

In the meantime I can provide a workaround through a a console version of Syncplay that does not rely on those Windows dependencies. Please download this from: https://github.com/Syncplay/syncplay/actions/runs/6214207919?pr=631

@Pandoroz
Copy link
Author

After an hour of understanding how it works I managed to understand and it works, I'll see if I can fix it and I'll inform you, thank you very much

@MicroMihai4
Copy link

The problem persists.
I've tried all the ways, but nothing is wrong.
The log is full of this:

":259: UserWarning: You are using cryptography on a 32-bit Python on a 64-bit Windows Operating System. Cryptography will be significantly faster if you switch to using a 64-bit Python.
WNDPROC return value cannot be converted to LRESULT
TypeError: WPARAM is simple, so must be an int object (got NoneType)"

@Et0h
Copy link
Contributor

Et0h commented Oct 11, 2023

@MicroMihai4 Is this issue reasolved by running an x64 (64-bit) version of Syncplay.exe/SyncplayConsole.exe?
https://github.com/Syncplay/syncplay/actions/runs/6488218619

@Et0h
Copy link
Contributor

Et0h commented Oct 20, 2023

I've tried running Syncplay.exe and SyncplayConsole.exe from the portable version of Syncplay at https://github.com/Syncplay/syncplay/actions/runs/6488079163 (current GIT HEAD) on fresh VM installs of Windows 10 (32-bit and 64-bit) and Windows 11 and they all work once vc_redist.x86.exe is installed. I also tried syncplayServer.exe on Windows 11 and that worked too. Hopefully that means this issue can now be closed, but I'll leave it open for a bit just in case following those instructions doesn't work for anyone.

@Et0h Et0h closed this as completed Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants