-
Notifications
You must be signed in to change notification settings - Fork 215
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
Syncplay can unknowingly uses old VLC lua script #193
Comments
For purposes of having Google return this issue to people trying to debug, these are the relevant Notifications:
This issue happened to me, even though I started using Syncplay at 1.5.3 |
Just downloaded 1.6.0 and this caught me out, even though I downloaded both the application and the Lua script fresh today. The cause of this, for me, was that the script in the VLC addon repository is not up-to-date. Edit: if the addon from the VLC repository is not needed any more, to the point where it's no longer updated (because SyncPlay can use its own copy), perhaps it should be removed from VLC's repository to prevent this from happening to new users who only discover it via VLC. |
@benplumley Thank you for letting me know that the version in the VLC repository needed updating. I have now updated the version in the VLC repository. |
Currently working on https://github.com/Syncplay/syncplay/commits/vlc-copy-intf to resolve this issue. If anyone wants to test it then let me know how it goes. |
#220 hopefully resolves this issue. |
Auto copy/update syncplay.lua when running with VLC (addresses #193)
Syncplay 1.4.0 fixed issue #108 back in January 2017, preventing erroneous jumps from VLC that were caused by VLC changing the unit used for reporting position.
The Syncplay installer will place the newest version of syncplay.lua in the %PROGRAMFILES% folder which will resolve the issue. Normally this is fine, but if someone has an old version of syncplay.lua in their VLC %APPDATA% folder then VLC will use that in favour of the more recent version in %PROGRAMFILES%.
Even worse, Syncplay won't notice it's on an old version, meaning on some version mismatches it will act incorrectly without the user knowing why.
The text was updated successfully, but these errors were encountered: