Jump to content

Live TV Malformed Data


mattisam

Recommended Posts

mattisam

We have been having issues with live tv on the roku only. It works fine on our android phone, but ends up with the malformed data error at random times. Sometimes five minutes, sometimes after an hour of viewing. We run into this issues on all of our Roku units, including a couple of Roku Ultra/Premire, two different models of Roku sticks, and even my older model 3 Roku.
I have also tried the Emby Beta app for Roku. Emby version 3.4.0.0 but also had the issue with previous versions.

 

Part of the emby log when it died at around 19:00.

2018-05-07 18:59:54.396 Info HttpServer: HTTP POST http://10.2.7.9:8096/emby/Sessions/Playing/Progress. UserAgent: Roku/DVP-8.1 (468.01E04090A)2018-05-07 18:59:54.398 Info HttpServer: HTTP Response 204 to 10.6.154.227. Time: 3ms. http://10.2.7.9:8096/emby/Sessions/Playing/Progress 2018-05-07 19:00:04.406 Info HttpServer: HTTP POST http://10.2.7.9:8096/emby/Sessions/Playing/Progress. UserAgent: Roku/DVP-8.1 (468.01E04090A)2018-05-07 19:00:04.409 Info HttpServer: HTTP Response 204 to 10.6.154.227. Time: 3ms. http://10.2.7.9:8096/emby/Sessions/Playing/Progress 2018-05-07 19:00:14.417 Info HttpServer: HTTP POST http://10.2.7.9:8096/emby/Sessions/Playing/Progress. UserAgent: Roku/DVP-8.1 (468.01E04090A)2018-05-07 19:00:14.420 Info HttpServer: HTTP Response 204 to 10.6.154.227. Time: 3ms. http://10.2.7.9:8096/emby/Sessions/Playing/Progress 2018-05-07 19:00:26.690 Info HttpServer: HTTP POST http://10.2.7.9:8096/emby/Sessions/Playing/Stopped. UserAgent: Roku/DVP-8.1 (468.01E04090A)2018-05-07 19:00:26.692 Info SessionManager: Playback stopped reported by app Roku SG 3.0.78 playing ID HD. Stopped at 1565000 ms2018-05-07 19:00:26.692 Info MediaSourceManager: Closing live stream 09efa0d56b934a82adec00a87b837fb0_0d756050aec84d6689b67283cfc33305_e43dd8f5cba90f91f0222fcd4de7717e with provider LiveTvMediaSourceProvider2018-05-07 19:00:26.692 Info App: Closing live stream from Emby, stream Id: 0d756050aec84d6689b67283cfc33305_e43dd8f5cba90f91f0222fcd4de7717e2018-05-07 19:00:26.692 Info App: Live stream 0d756050aec84d6689b67283cfc33305_e43dd8f5cba90f91f0222fcd4de7717e consumer count is now 02018-05-07 19:00:26.692 Info App: Closing live stream 0d756050aec84d6689b67283cfc33305_e43dd8f5cba90f91f0222fcd4de7717e2018-05-07 19:00:26.692 Info App: Closing SharedHttpStream2018-05-07 19:00:26.692 Info App: Live stream 0d756050aec84d6689b67283cfc33305_e43dd8f5cba90f91f0222fcd4de7717e closed successfully2018-05-07 19:00:26.692 Info PlaybackReporting: Playback stop tracker found, processing stop : dad88fec-6a63-5422-8f9e-ecbd5d543596-faea9cb5e51d43c9946abffb614d0d4f-49a5edcd6662b570dceab9523e8b1e052018-05-07 19:00:26.692 Info PlaybackReporting: PlaybackTracker : Adding Stop Event : 5/7/18 7:00:26 PM2018-05-07 19:00:26.692 Info PlaybackReporting: Saving playback tracking activity in DB

post-267958-0-03245500-1525744074_thumb.jpg

Link to comment
Share on other sites

Hi there, can you please attach the complete emby server and ffmpeg log (if there was one). Thanks !

Link to comment
Share on other sites

mattisam

Here is the emby logs. Nothing in transcode as it was direct streaming. I will add that it does not matter what iptv provider I am using, it still happens. I have tried three. The Roku in this example is hard wired, but still does it on the roku sticks that are wireless.

EmbyLog.txt

TranscodeLog.txt

Link to comment
Share on other sites

We are direct streaming from your iptv url.

 

We will see what @@ebr thinks but it looks to me like the Roku video player doesn't like the stream for whatever reason and we're going to have to do a full transcode in order to correct it.

Link to comment
Share on other sites

mattisam

The server it is on is a dual processor Xeon with 72 gigs of memory. So transcoding a live stream is fine. Is there a way to force it to transcode to try and see how it does?

Link to comment
Share on other sites

Currently the only way is to drop the in app quality setting on the Roku to something lower than that of the source stream.

Link to comment
Share on other sites

mattisam

Making it transcode worked, but pretty crazy to have to do that. Did anyone have any suggestions?

Link to comment
Share on other sites

It's something specific to the stream that the Roku video player doesn't like. 

 

Perhaps @@ebr can look at this so that we can detect this situation and automatically switch to transcoding.

Link to comment
Share on other sites

First, please send a log from the app from when this occurs.  You'll need to enable the debug options, then restart the app, then right after the problem, go to the home screen and send the log.

 

But also, do you have anything in your network setup that may be messing with the traffic?  It just seems odd that only you would be seeing this and across multiple sources.

Link to comment
Share on other sites

mattisam

It is strange. I used to use Plex, and I fired it up and it worked fine, same source iptv. As far as network, it is all Ubiquiti based and hardware that is less than one year. Internet is cable, 1 gig down. Other streaming apps such as netflix and idgo works fine in full high def. I will send the logs from the roku unit.

Edited by mattisam
Link to comment
Share on other sites

mattisam

The Plex might be transcoding, I have not looked. However I turned on debugging, video set to auto so no transcode, and it errored out after a few minutes. However, I cant find any tile or menu option to send the log as per the directions?

Link to comment
Share on other sites

If i understand correctly, if we had been transcoding from the beginning and it had just worked, you never would have had an issue, right?

Link to comment
Share on other sites

If i understand correctly, if we had been transcoding from the beginning and it had just worked, you never would have had an issue, right?

 

The app understands how to direct play and fallback to transcoding, aka remuxing. This should be improved upon. The next part is if that remuxing (direct stream copy) errors is to fully transcode.

 

To fully transcode just take the video stream bitrate and subtract 1 from it and have the app use this as the new max video bitrate, then have the app update its capabilities profile to the server to make it aware. This will now automatically fallback to full transcoding without stream copy. All without the user having to do much except watch the app go through the workflow of fallbacks. Seems pretty simple to do... blue neon does this...

 

The only time this solution wouldn't work is when the roku video player gets stuck on the retreiving bar. It may hang at 99% and just stick there, forever until the user presses the back button. You obviously can't automatically fallback from remux to full transcoding in this case as it breaks the work flow. The only way to resolve this is to have the user set the max bitrate manually below the video bitrate...

Edited by speechles
Link to comment
Share on other sites

@@speechles the issue is that sometimes the roku player fails in a way that can't be caught.

 

It can _always_ be caught. The event is the video player node closed. In this case, fallback/re-spawn. But..

 

...sometimes the video player goes into "No video" showing or green screen. When direct stream copy something that should be fully transcoded.

 

...sometimes you can "direct play" something and the pre-video "retreiving/loading" bar will grow to a certain % and just hang. This could be at the 15%, 33% or 99% point... The user must intervene and press back.

 

It is in these cases, the user may have to manually set the max bitrate under the video bitrate. The issue comes in that, you can't just select "VideoBitrate-1" as an option, where the app will smartly choose the video bitrate for each item played as its current bitrate -1 as to force a full transcode. This is akin to using blue neon with "force transcode w/o stream copy" and every time it plays video the app reports to the server its max video bitrate is 1 below the videos bitrate. This is smart. Your max loss in bitrate is 1. There is nothing smaller. This can't get any better.

 

Require the user to do less on the roku is more intuitive. So add the ability to fallback to full transcode in the auto-fallback-logic-workflow, and also add a bitrate option called "videobitrate-1" or similar so its a one stop shop for users to do this with the minimal amount of bitrate loss. Hopefully you see this issue is really just in picking a bitrate (1mb/1.5mb/2mb/2.5mb/etc), and how it will now cause severe quality loss possibly because it cant possibly be as close as videobitrate-1.

 

A smarter app is a better app.

Edited by speechles
Link to comment
Share on other sites

This app just doesn't have the same level of intelligence of some of the others when it comes to re-trying playback when there are errors (yet).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...