-
Notifications
You must be signed in to change notification settings - Fork 3
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
mpv driver failed to load due to timeout position -1 #12
Comments
Do you sync changes to the folder with pi presents' playing. If not the playlist can get modified while a video is playing. See manual for details. |
Thank you for the details. I will change the setting to sync and see how we get on |
Would you be able to make a list of steps for me to follow as I changed the mode from async to sync in pp_livelistfetcher.py and still getting the same error. I have a live-tracks-dir1 set to the folder that is being updated every 2 mintures. It say in the manual you need to set live-tracks-dir2 but what to? |
Set live-tracks-dir-2 to a directory that PP is going to play the files from. (not the cache directory) Set the cache-dir to the directory that you own update program puts the files into when it sees that the .lock file in that directory is not present It's possible that the lack of synchronisation was not the only reason for the failure. If you play the track in a mediashow rather than a liveshow and it still fails you probably have a problem with the video file. |
Thank you for getting back to me. I have made the edits you listed. I see I have to add the .lock file in the folder to which my script adds files for the system to copy them to the working directory. I am going to let the system run for some time and see what happens. I will post my results soon |
Hi, I keep getting this error mpv driver failed to load due to timeout position -1. After one cycle. I have all the recommended setting set and the lastest from github.
It is a liveshow that looks at a folder that updates every 2 minutes.
Can you help
The text was updated successfully, but these errors were encountered: