Runaway Playback Protection
Posted 20 December 2018 - 03:51 PM
I set this up on a Roku Premiere+ 9 hours and 17 minutes ago and it's still playing the same channel.
The temp transcode file is over 10 GB already and of course still growing.
Is this going to be fixed in the next release?
Edited by cayars, 20 December 2018 - 04:31 PM.
Posted 20 December 2018 - 06:47 PM
I had something that would prompt the user after 5 hours and kill the stream if no reply. But @ebr said that wasn't how he wanted it to work. We will have something for this soon. Please bear with us. It is a known issue at this point and we will get it solved. Thanks.
Edited by speechles, 20 December 2018 - 06:47 PM.
- Sammy likes this
Posted 28 May 2019 - 11:08 AM
Hi. Yes, the next public release will address this.
Any update on this?
Still having issues with runaway playback of Live TV.
Server Version 126.96.36.199
Remote connection of Roku Stable V3.0.155 (4/10/2019)
HDHomerun Model HDHR45-4US
Guide data is active, accurate and visible.
Runaway Playback prompt set to YES
Remote Stream started at 9:00 pm. Timer set on television (Sony) to turn off after 60 minutes (Sleep timer).
Checked at 6:00 am and the stream was still active.
With all of the Data Caps imposed by ISP's, this is becoming a very necessary feature. A single stream with bandwidth limiting set, it still pulling an average of a gig per hour. Cox is imposing a 33 gig per day limit, so a few streams could become a problem on both ends if unchecked.
Side note - Tried to set an access time for the user from 5:00 am to 11:00 pm. This did not stop the playback as well. Was unable to restart server (due to active playback) once the schedule was established, so not sure if that needs to be done before it goes into effect. It has been restarted now, and will check again this evening.
Second Side Note - The "Stop" (Square Box) on the Active Devices located on the server dashboard did not stop the stream as well. First time trying this feature, but did not work.
Edited by Scott D, 28 May 2019 - 11:52 AM.
Posted 28 May 2019 - 11:30 AM
@ebr Check pull request #138 on Roku Github. It's long since closed but it gives a reference that we were here before.
Last comment on it Dec 16, 2018. Was anything ever completed on this? I think this was missed and we need to address this still. My method to address was insufficient or too aggressive. How should we handle this? In a way that doesn't require more text that has to be translated. In other words without a setting.. lol
Edited by speechles, 28 May 2019 - 11:33 AM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users