-
Notifications
You must be signed in to change notification settings - Fork 216
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
Cannot use spaces or quotes in player arguments for vlc #665
Comments
Thanks for reporting this issue. I've had a look and I think it's a bug. As far as I can see if you want a space in a snapshot path that for now you will need to either manually set it in VLC preferences or use mpv/mpv.net. |
Thanks for your reply! I specifically wanted to be able to specify the snapshot location by entering arguments. By the way, when I try with mpv, I get the same result, in the perplayerarguments = {'c:\\program files\\videolan\\vlc\\vlc.exe': ['--extraintf=luaintf:http', '--http-port=12342', '--http-password=vlcpassword', '--snapshot-path="D:\\stok\\test', 'folder\\snapshots"', '--snapshot-format="jpg"', '--snapshot-prefix="image-"', '--drawable-hwnd=1'], 'd:\\stok\\test folder\\snapshots\\mpv.exe': ['--screenshot-dir="D:\\stok\\test', 'folder\\snapshots"']} |
Just checked and you're right, it is incorrectly splitting stuff in syncplay.ini. |
I've tried to fix the issue in PR #668 @zuluwi could you please test out the Syncplay build at https://github.com/Syncplay/syncplay/actions/runs/7671885102?pr=668 (Syncplay-1.7.1-Setup.exe or Syncplay_1.7.1_Portable) to let me know if it fixes the issue and allows |
I tried it and it worked with no problem. Thank you so much for your hard work 🙏 |
I've also tested this with mpv and mpv.net using the arguments |
When I enter the following code to specify the snapshot folder in the player arguments, it gives an error due to spaces even though the folder path is in quotation marks
also the arguments where I use quotation marks without spaces don't work. In cmd I can run the following code properly
Is this a bug or am I not entering these characters properly?
Version and platform:
The text was updated successfully, but these errors were encountered: