It would be great to make Bigscreen compatible with SyncPlay protocol to be able to watch movies together even with those who has no VR headset. SyncPlay is one of the most popular FOSS apps for organizing watch parties. We dont use any of the subscription services and this come in nicely to substitute akward "3.2.1.1Now". I've not yet experienced any issue with shared playlists but I haven't used them extensively either.Syncplay : This one lets me and my partner watch our downloaded movies toghether. Is there some other reason that folders which are 'too big' is a problem? Because I don't understand, "it could encourage people using folders which are too big". Unfortunately it is impossible for me personally to use local drives as there is simply too much content to store it in a normal machine and I sort of want it in a NAS anyway for others. I just want it to actually load in the first place.
SYNCPLAY LARGE FILE ISSUE UPDATE
Personally I don't care how big the update interval is because it's no skin off my teeth to take 5s to reopen syncplay, it doesn't really take that long to reload. In that case may I suggest upping the FOLDER_SEARCH_DOUBLE_CHECK_INTERVAL to 120s or even 300s and adding a button to the UI allowing the user to force an update in the case where they've just put something in and want it now?Īlternatively allow the user to set both values in misc and cap FOLDER_SEARCH_TIMEOUT to be at most 20% of whatever they set FOLDER_SEARCH_DOUBLE_CHECK_INTERVAL to and keep their defaults as they are now.
It would be useful to hear from other users whether they experience any notifications during their usage of Syncplay and if so when, or if they use shared playlists without any problems.Īh ok, I understand the issue regarding the way FOLDER_SEARCH_TIMEOUT and FOLDER_SEARCH_DOUBLE_CHECK_INTERVAL work together.
SYNCPLAY LARGE FILE ISSUE CODE
The reasons this doesn't already happen is because (1) it would result in less consistency of behaviour, (2) it could encourage people using folders which are too big, and (3) it is more complicated and therefore harder to code and test. One potential way that Syncplay could address this would be to update the cache less frequently in the event of things taking too long, and/or potentially changing how frequently it refreshes the cache depending on if there are any unfound files. Values could be increased, but if the value for FOLDER_SEARCH_TIMEOUT is greater or equal to FOLDER_SEARCH_DOUBLE_CHECK_INTERVAL then it could result in situations where Syncplay is constantly updating the cache, and I'm guessing that this isn't a good thing.
Generally speaking it is recommended that users use local drives rather than network shares as their media directory, and avoid directories with way too many files in them. FOLDER_SEARCH_DOUBLE_CHECK_INTERVAL = 30.0 # Secs - Frequency of updating cache.FOLDER_SEARCH_TIMEOUT = 6.0 # Secs - How long to wait until searches in folder to update cache are aborted (after first file is found).FOLDER_SEARCH_FIRST_FILE_TIMEOUT = 15.0 # Secs - How long to wait to find the first file in folder search (to take account of HDD spin up).
This could be made more clear in the notification.Ĭurrent default options for the File Switch / Folder Search feature are: That should reset the flag which told Syncplay to ignore the network drive, and things should work again. If it gives an error then I think that you don't need to restart Syncplay to get it to work again, you just need to go File -> Set Media Directories, and press 'Okay'.
0 kommentar(er)
