Indeed, even if it were simple and reliable to obtain duration (which it is not, as per above) then this could still result in inconsistent behaviour if two files had the same length (which is not unusual) and Syncplay strives to be consistent in how it treats files.
Syncplay large file issue 720p#
Indeed, it is designed so that one person could play a 1080p file and another a 720p file and it would work fine so long as they both had the same filename, so comparing hashes or filesizes is out of the question. In terms of the filenames, Syncplay is designed to be agnostic as to where a file is located so long as it is in a media directory. Your media player might automatically calculate the durations of all files in a playlist, so you might be able to compare files by manually adding them to a media player playlist. There could be performance issues, and confusion if the duration obtained through one method is different from the duration obtained from the media player.
There is no easy cross-platform and cross-player way of getting the duration of a file which is not being played like there is getting the filesize. In some cases there are actually more than one way to calculate a duration and it may require the whole file to be loaded into memory. In terms of duration (length), at present Syncplay is agnostic to what is being played and lets the media player obtain the duration and simply uses that. As such, I don't expect these suggestions to be implemented in Syncplay. I can see why those features would be convenient for certain use cases and it looks simple on the face of it, but actually both of those suggestions would be really difficult to implement and there could be drawbacks/trade-offs to implementing them (not least the general principle that adding complexity can reduce reliability). By the relative path I mean if media directory is c:/videos/movies, it could be shown in the path column like /movies/movie-name/featurettes/Deleted Scenes.mkv or just /movies/movie-name/featurettes/. Either way, simply adding an optional column with a relative path could help dealing with it, and also keeping playlists more visually organized/grouped. I guess it could be fixed with advanced matching that uses length and size, hash sum etc, but it can be a bit complex to implement, or maybe was implemented already and I encountered a bug. In that time some quality-of-life improvement ideas came to mind and I decided to share them.Īt times I noticed that it could be really useful to know the length of each item in the playlist, and maybe even total length at the bottom, cause it makes it easier to decide when to watch what.Īlso when we use shared playlist, and one of us adds a generic named file like Deleted Scenes.mkv, it loads the wrong file if there are others like it in the media folder. We're using syncplay a lot, and are really grateful for the opportunities it provides.
0 kommentar(er)
