Notifications after fast-forward and rewind

[computerprep 148]

So I use push notifications to stay apprised of my server's approximate load... to know how many videos are being streamed and such.

 

Lately I've been getting a massive number of notifications from the same users/devices playing a title several dozen times over the course of a few seconds or minutes. I finally hit my own Roku out (I usually stream through Android TV) svc I've realized the issue.

 

When Roku or Apple TV devices fast forward or skip to another spot within a video they've already started streaming, it initiates another "started playing" notification.

 

This notification is unnecessary and just earlier today resulted in exactly 52 identical notifications over a 30 minute timespan. This happened from a user with a Apple TV. I just replicated it on a Roku with seven notifications in 20 seconds by fast forwarding to find where I left off.

 

Not sure if this happens on any other devices, but I can't recreate it on Android Mobile, Web, or Android TV.

[speechles 2055]

For the roku (official app), you need to make these changes:

 

https://github.com/MediaBrowser/Emby.Roku/pull/144

 

And then... Replace this line below:

 

https://github.com/MediaBrowser/Emby.Roku/blob/master/source/VideoPlayer.brs#L340

 

With this line:

 

if m.lastposition = 0 then m.ReportPlayback("start")

 

(The lastposition is kept to tell the player how many seconds it has been playing. It isnt a resume point, or used for anything else. I am using this as a way to tell when a stream is freshly started or just fast forwarded. This makes it only send a start when lastposition is 0 and the stream was just started.)

 

Now the double stops are gone, as well as the starts everytime you change position. The blueneon roku app already has had these changes made long ago.

 

For the roku (beta app) I dont believe it has this issue. At least I couldnt replicate it in my short testing.

Edited January 20, 2017 by speechles

[computerprep 148]

It's too late here to read any of that to comprehend it... Just adding that the problem didn't occur when pausing and resuming, just skipping forward and backward.

 

I'll try to look at some code after some sleep

[computerprep 148]

Update: this problem is fixed in the latest Roku beta preview. Can't speak for Apple TV.