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
{{ message }}
This repository has been archived by the owner on Jun 14, 2019. It is now read-only.
This is the other issue I've noticed, and I'm sure this one isn't my mistake! 馃憖
If, say, I clumsily click two files one after the other without stopping the first one first, I can then control the second file, but none of the keybindings do anything to stop the original file. I have to ssh into my Pi, pkill omxplayer, then reboot. Is there any way to automatically force the original file to stop playing?
The text was updated successfully, but these errors were encountered:
Normally the script does kill all existing omxplayer instances whenever you play a new file. Maybe, if you do this multiple times when the other processes aren't done yet, it could be possible to create a mess. But this should be fixed when you wait a few seconds and that click again on the video you want to play.
It should kill all omxplayers and start fine with the new one.
This is the other issue I've noticed, and I'm sure this one isn't my mistake! 馃憖
If, say, I clumsily click two files one after the other without stopping the first one first, I can then control the second file, but none of the keybindings do anything to stop the original file. I have to ssh into my Pi, pkill omxplayer, then reboot. Is there any way to automatically force the original file to stop playing?
The text was updated successfully, but these errors were encountered: