Live TV plays but fails

[speechles 1917]

I too am experiencing this issue with roku. Latest emby beta. Was working fine for me not too long ago. Live tv will start fine, then stop after two seconds. I thought perhaps this was linked to the roku system update on june 5th?

 

Identical channel plays fine on fire stick 4k / emby theatre on windows 10.

 

Are you on Roku firmware 9.1? I just got that update yesterday and can test out LiveTV again for issues. My LiveTV is all done over the HD Homerun but I have a few IPTV sources with the IPTV plugin I can try too. All "used to work" and if they still don't I can see WTF is making it go goofy. Let me check into this. LiveTV issues are always a priority. Stay tuned.

Edited June 7, 2019 by speechles

[Polyzp_emby 3]

Update : Tried playing identical channel on my roku 2xd. Works flawlessly. Channel in question is CNN. (Also tried a few others with same result)

 

Original system I was trying on was my roku ultra 4640x.

 

Both my rokus have identical emby beta versions. Both on identical emby server. Both have 9.1 firmware, albeit different revisions (despite the fact they are both updated to the latest firmware)

 

Roku 2xd is on 9.1 OS - 4111-02

Works!!

Seen here : https://streamable.com/58g0r

 

Roku 4640x ultra is on 9.1 OS 4111-29

Fails!!(never recovers)

Seen here : https://streamable.com/0lp24

Edited June 8, 2019 by Polyzp_emby

[Luke 36999]

Update : Tried playing identical channel on my roku 2xd. Works flawlessly. Channel in question is CNN. (Also tried a few others with same result)

 

Original system I was trying on was my roku ultra 4640x.

 

Both my rokus have identical emby beta versions. Both on identical emby server. Both have 9.1 firmware, albeit different revisions (despite the fact they are both updated to the latest firmware)

 

Roku 2xd is on 9.1 OS - 4111-02

Works!!

Seen here : https://streamable.com/58g0r

 

Roku 4640x ultra is on 9.1 OS 4111-29

Fails!!(never recovers)

Seen here : https://streamable.com/0lp24

 

Thanks for the info. Can we look at the Emby Server and ffmpeg logs for both attempts? Thanks !

[Polyzp_emby 3]

Hey Luke,

 

I sent you detailed logs via pm, with the tests redone (and reshot via video as well).

 

Thank you again!

[Polyzp_emby 3]

Any update on the issue? 

 

Thanks Luke

Edited June 11, 2019 by Polyzp_emby

[Luke 36999]

it looks like you have different quality settings and audio settings between the two Roku devices. I don't see any obvious source of the problem, but you could try changing the options on the one that is failing to match the other one.

[Polyzp_emby 3]

I have set the setting to be the same (60mbps) as on the roku 2xd. I still get the exact same result, 1 second of play, then a fail. I sent the log over again via PM. Live TV + Emby is essentially "broken" with use on the ultra 4640 until this is fixed. (non live tv, such as movies, work perfectly well still however)

 

Thanks again for looking into this

Edited June 13, 2019 by Polyzp_emby

[greenlava 2]

I have this same issue on a Roku Premier+ and a TCL RokuTV.  my ffmpeg logs seem to indicate a quit command was received:

------------

[...]
elapsed=00:21:59.85 frame=38158 fps= 29 q=-1.0 size= 1592326kB time=00:22:03.74 bitrate=9854.1kbits/s throttle=off speed= 1x
[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587.m3u8.tmp' for writing
SegmentComplete=video:0 Index=440 Start=1320.529422 End=1323.449000 Duration=2.919578 offset_pts=0 start_pts=1320529422 Frames=78 filename=hls/b9df3373098849bbaffd979fd9720587/b9df3373098849bbaffd979fd9720587440.ts
[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587441.ts.tmp' for writing
elapsed=00:22:00.35 frame=38167 fps= 29 q=-1.0 size= 1592570kB time=00:22:04.11 bitrate=9852.9kbits/s throttle=off speed= 1x
elapsed=00:22:00.94 frame=38184 fps= 29 q=-1.0 size= 1593343kB time=00:22:04.83 bitrate=9852.3kbits/s throttle=off speed= 1x
elapsed=00:22:01.49 frame=38195 fps= 29 q=-1.0 size= 1593724kB time=00:22:05.28 bitrate=9851.3kbits/s throttle=off speed= 1x


[q] command received. Exiting.

[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587.m3u8.tmp' for writing
SegmentComplete=video:0 Index=441 Start=1323.449000 End=1325.584467 Duration=2.135467 offset_pts=0 start_pts=1323449000 Frames=50 filename=hls/b9df3373098849bbaffd979fd9720587/b9df3373098849bbaffd979fd9720587441.ts
elapsed=00:22:01.72 frame=38199 fps= 29 q=-1.0 Lsize= 1593838kB time=00:22:05.45 bitrate=9850.8kbits/s throttle=off speed= 1x
video:1531740kB audio:62098kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
T=0.594s
Local Time: 21:42:38

 

I'd also be happy to help debug and troubleshoot any way I can

 

Emby Server on windows10 4.2.0.15beta on an i7 with 16gb of ram, spinny HDD

latest Emby stable on updated Roku

HDHomerun Prime

RokuTV wired network, Roku Premier+ wifi

setting to 1080p/25mbps  doesn't seem to help much.

 

it's been happening for the last month or so at least, but I don't watch a ton of liveTV so I can't tell you definitively if it happened prior.

[Luke 36999]

I have this same issue on a Roku Premier+ and a TCL RokuTV.  my ffmpeg logs seem to indicate a quit command was received:

------------

[...]

elapsed=00:21:59.85 frame=38158 fps= 29 q=-1.0 size= 1592326kB time=00:22:03.74 bitrate=9854.1kbits/s throttle=off speed= 1x

[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587.m3u8.tmp' for writing

SegmentComplete=video:0 Index=440 Start=1320.529422 End=1323.449000 Duration=2.919578 offset_pts=0 start_pts=1320529422 Frames=78 filename=hls/b9df3373098849bbaffd979fd9720587/b9df3373098849bbaffd979fd9720587440.ts

[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587441.ts.tmp' for writing

elapsed=00:22:00.35 frame=38167 fps= 29 q=-1.0 size= 1592570kB time=00:22:04.11 bitrate=9852.9kbits/s throttle=off speed= 1x

elapsed=00:22:00.94 frame=38184 fps= 29 q=-1.0 size= 1593343kB time=00:22:04.83 bitrate=9852.3kbits/s throttle=off speed= 1x

elapsed=00:22:01.49 frame=38195 fps= 29 q=-1.0 size= 1593724kB time=00:22:05.28 bitrate=9851.3kbits/s throttle=off speed= 1x

 

 

[q] command received. Exiting.

 

[segment @ 000001beef251040] Opening 'C:\Users\HTPC\AppData\Roaming\Emby-Server\transcoding-temp\b9df3373098849bbaffd979fd9720587.m3u8.tmp' for writing

SegmentComplete=video:0 Index=441 Start=1323.449000 End=1325.584467 Duration=2.135467 offset_pts=0 start_pts=1323449000 Frames=50 filename=hls/b9df3373098849bbaffd979fd9720587/b9df3373098849bbaffd979fd9720587441.ts

elapsed=00:22:01.72 frame=38199 fps= 29 q=-1.0 Lsize= 1593838kB time=00:22:05.45 bitrate=9850.8kbits/s throttle=off speed= 1x

video:1531740kB audio:62098kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%

T=0.594s

Local Time: 21:42:38

 

I'd also be happy to help debug and troubleshoot any way I can

 

Emby Server on windows10 4.2.0.15beta on an i7 with 16gb of ram, spinny HDD

latest Emby stable on updated Roku

HDHomerun Prime

RokuTV wired network, Roku Premier+ wifi

setting to 1080p/25mbps  doesn't seem to help much.

 

it's been happening for the last month or so at least, but I don't watch a ton of liveTV so I can't tell you definitively if it happened prior.

 

Hi there @@greenlava, please attach the information requested in how to report a media playback issue. thanks.

[mhaider60 3]

Is beta 3.0.168 meant to fix the issue I reported? If so, the problem still exists. 3.0.169 wasn't available on my Roku's, they're both on Roku OS 9

[mhaider60 3]

Is there some magic trick I need to do to get the Roku beta installed past 3.0.168? I'm hoping the latest beta fixes the problem I initially started this forum thread for.

[speechles 1917]

We are up to 0.170 in versioning for our development on Roku. We constantly move forward.

 

There may be a hold-up on releases as we are trying to get this ready for the store at the same time. We cannot make mistakes or bugs or make things worse on the store version. It must be as close to perfect as humanly possible. This is where we need you guys(..and girls!) to find problems in the Beta builds. This is also why most of the things you see added in the last few days have been merely to address issues not pushing new features quite yet.

 

@@ebr Will you be pushing a new beta for Roku today? Curious if our LiveTV fixes alleviate the issues for users. 

 

@@mhaider60 Thank you for all the help spotting issues. We do take these seriously. These will be addressed. It is a busy time with school being out and children. Family usually have vacations and family time during this period. @@ebr is no different. This may slow down releases during this time but it does not mean your problems have any less value for us. Please bear with us. We do appreciate your posts and your feedback. We do our best with the time we have. Thanks for the help.

Edited June 19, 2019 by speechles

[ebr 14902]

170 went out yesterday.

 

@@mhaider60 what firmware is your device running?

[speechles 1917]

170 went out yesterday.

 

Really? I just updated my Roku ultra it says all up to date.

 

Emby Beta and press *. Version 3.0 • build 168

Emby and press *. Version 3.0 • build 155

 

If you choose "update software" on your Roku then nav over to Emby Beta on your homescreen over to the published Beta app and press * do you see the same thing?

Edited June 19, 2019 by speechles

[ebr 14902]

Interesting.   Neither version with the manifest modification have delivered...  I upped the min FW version to 8.0 for them and now they aren't going out.

[mhaider60 3]

170 went out yesterday.

 

@@mhaider60 what firmware is your device running?

Both of my Roku's are on FW 9.  I'm seeing the same as @@speechles mentioned in #39

[mhaider60 3]

@@mhaider60 Thank you for all the help spotting issues. We do take these seriously. These will be addressed. It is a busy time with school being out and children. Family usually have vacations and family time during this period. @@ebr is no different. This may slow down releases during this time but it does not mean your problems have any less value for us. Please bear with us. We do appreciate your posts and your feedback. We do our best with the time we have. Thanks for the help.

 

I understand completely, there is life beyond work.  It's refreshing to actually get a response from you and your team when a question is posted in the forums, that's something your competition is completely lacking in. Thank you for your efforts!

[speechles 1917]

I understand completely, there is life beyond work.  It's refreshing to actually get a response from you and your team when a question is posted in the forums, that's something your competition is completely lacking in. Thank you for your efforts!

 

That is unfortunately how they treat their userbase. They are moving to becoming monetized by commercial endeavors. They have a 10 million dollar loan against them they must repay or give up certain control of their company. Maybe this is that loss of control of their company. They are now being forced to tie into other services to gain a repayment schedule to repay the debt. I do know that much. They gave up control of their company when they decided to take stock offerings for control of their board. So now they have a board of directors that controls their direction and they want remuneration. So not only do you have employees, and etc, but you have loans and stock that must be remunerated. It is harder for them on the forums to have any control. It is rare their developers want to post for fear of bad mouths going off on them and just fanning those flames.

 

Here we are always up front. I try to keep everybody in the loop if they ask. I will flood you with more information than you would hope to get elsewhere. I do this on purpose to make that difference. We actually care about you as the person you are. We are human. We reach out to users having issues and actively work with them to resolve issues. The difference isn't just that. We are more in tune with what our usebase wants. You want your media your way. We understand that. It is our goal to go there. No brakes. I am outspoken on my desire to make the Roku app better. The Blue Neon Night app was my love for Emby expressed in app form. Now we work together to achieve that same goal. 

 

We will always respond to posts and keep it real. No lies. The last honest media server.

 

@@Luke and @@ebr are tireless in their dedication. They bleed Emby green. I am happy to work with them.

Edited June 19, 2019 by speechles

[mhaider60 3]

Thought I'd let you know I still can't update the Roku beta past 3.0.168. I probably need to be more patient. 

[ebr 14902]

Thought I'd let you know I still can't update the Roku beta past 3.0.168. I probably need to be more patient. 

 

No, there is some sort of problem but, unfortunately, Roku support will not help us with it because this is an uncertified channel :|

[justpushplay 6]

I too have this issue but mostly because my liveTV signal is just horrible. I will dig into the problem.

 

 

 

My OTA signal suffers greatly from multipath, and the HD Homerun Quatro is far better than my Tivo Roamio OTA at dealing with it. However sometimes Emby gets pissed off and pulls the car over until things settle down:-) I can hardly blame Emby, mine is really a worst case scenario.

[mhaider60 3]

I received the 172 beta on my Roku Premiere + but the live TV issue is still there. Was this latest beta supposed to address this issue or is it still in the works? 

[Luke 36999]

Apologies for the delay. We are still looking into this, thanks.

[speechles 1917]

I received the 172 beta on my Roku Premiere + but the live TV issue is still there. Was this latest beta supposed to address this issue or is it still in the works? 

 

I think we finally hit the nail on the head what was causing your issue. We solved 2 other issues unrelated to this one but totally related to LiveTV. Your problem is the third and we just solved that one a few moments ago. We should have all the LiveTV issues finally cleaned up. After the next Beta we can readdress any issues still there at that time. Pretty sure this last fix solves that problem.

 

Reference: Fix #498: [LIVE TV] *Fix stuck video player* Timeout = DNR

[mhaider60 3]

I think we finally hit the nail on the head what was causing your issue. We solved 2 other issues unrelated to this one but totally related to LiveTV. Your problem is the third and we just solved that one a few moments ago. We should have all the LiveTV issues finally cleaned up. After the next Beta we can readdress any issues still there at that time. Pretty sure this last fix solves that problem.

 

Reference: Fix #498: [LIVE TV] *Fix stuck video player* Timeout = DNR

 That's great news! I can't wait to try it