Closed epsicola closed 5 years ago
We can’t shorten the tick. That part is controlled from plex. See https://github.com/Hellowlol/bw_plex/issues/24
Glad you liked it! Tried using the dockerfile?
Thanks for the response! I did end up installing the dependencies through docker since I kept getting weird errors. Once the docker process completed, I was able to run "bw_plex watch" :)
As for the post that you linked, what did you mean by: Possible solutions: add a the "task" to a queue that check over and over if its the correct time and it it is add it to the process pool.
Is that something that is easy to do?
It wouldn’t be to hard. Basically we check if the start will happen before the next tick. If it does we will manually fire the jump before we reach the tick.
Oh ok, so it's not something I can do.
I’ll get this done eventually:)
I have added a simple way to fool the progress. Can you try to edit no_wait_tick (in the config) to like 5 or seven and see if this helps
Hello, first off, loving this project. Took me 4 hours to get it running but it's pretty sweet now that it is.
I was hoping there could be an option to shorten the time between websocket ticks. Right now, it's every 10 seconds but some theme songs are like 20 seconds long so you sometimes have to sit through half of it before it gets skipped.
Any help with this would be greatly appreciated.