You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
move the video file to another volume or unmount the volume
open the playlist in Screen - the video will be marked "unreadable" in the playlist sidebar
close Screen
What is the expected behavior?
The playlist should retain markers and other user data for the offline file, so it can be accessed when the video is online again.
What happens instead?
The playlist gets auto-saved without prompting the user upon closing Screen, and all user data is removed for the offline file. Only a skeleton with { "type" : "media", "sourceURL" : "…", "sourceRelativePath" : "…" } remains in the JSON.
Related issues
There seems to be no way to relink a playlist to moved files. A workaround could be manual editing of the JSON, but the stripping and overwriting of the playlist currently prevents this.
Screen does not ask for user confirmation when saving the modified playlist upon quitting the application.
Screen warns the user about not being able to save playlist versions on some filesystems (eg. exFAT) the first time the playlist is saved, but there is no warning upon subsequent auto-saves of the playlist. Also, the user may not be aware of the consequences (markers being stripped) of overwriting their playlist.
The text was updated successfully, but these errors were encountered:
gkertai
changed the title
Bug: playlist markers get deleted if video file is moved
Bug: playlist markers get deleted if video file goes offline
Apr 13, 2021
Steps to reproduce:
What is the expected behavior?
The playlist should retain markers and other user data for the offline file, so it can be accessed when the video is online again.
What happens instead?
The playlist gets auto-saved without prompting the user upon closing Screen, and all user data is removed for the offline file. Only a skeleton with
{ "type" : "media", "sourceURL" : "…", "sourceRelativePath" : "…" }
remains in the JSON.Related issues
The text was updated successfully, but these errors were encountered: