Jump to content
FordGT90Concept

ANSWERED Live TV not working as of 3.0.6070.0 & 20160630atest2

Recommended Posts

FordGT90Concept

As per the recommendation on another thread, I upgraded the firmware from 2015something to 20160630atest2 (not seeing how to downgrade it).  This fixed the problem on Emby Theater's ability to DirectPlay but it completely decimated Android and Android TV support.  It should be noted that I upgraded Emby Server from 3.0.6060.0 to 3.0.6070.0 at the same time.  I attached the server log.  The Leelbox MXQ Pro device it is sending it to does require transcoding done on the server.

 

-Android TV (attached) gives an error and stops transcoding on the server almost immediately.

-Android maybe only shows one frame that was transcoding and it locks up while the server continues to transcode oblivious that it is falling on deaf ears.

-Emby Theater does DirectPlay with no issues.

leelbox.zip

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
ebr

So this is not specific to Android TV?

 

What was the error?

Share this post


Link to post
Share on other sites
FordGT90Concept

The most recent test, it didn't give an error, it just sat there spinning.  Before that, it gave a "Failed to load stream" or something like that.  I seem to recall another error when attempting to start but can't recall it.

 

Here's the order of events:
​1) Updated HDHomeRun CONNECT firmware.

2) Updated Emby Server from 6060->6070

3) Tried Emby Theater on my machine: works great (no transcoding)

4) Tried Emby for Android: shows one frame (maybe) and it acts like it locked up.  Server keeps transcoding.

5) Tried Emby for Android TV: last night it worked albeit with questionable performance but this morning, it does not; the stream is failing to start.  Server transcode stops.

 

I've tried restarting Emby server as well as restarting and reconfiguring the HDHomeRun.

 

It was working fine before #1 and #2 on Android/Android TV.

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
ebr

So it is both Android Mobile and Android TV and the thing they have in common is that they are both transcoding the stream, correct?

Share this post


Link to post
Share on other sites
FordGT90Concept

Yes, which the HDHomeRun firmware apparently changed (or 6070, but more likely the firmware).

 

 

Edit: I should note that both Android apps have problems but I don't know if they're the exact same problem.  Again, neither had problems prior to step #1 and #2.

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
FordGT90Concept

I tried HDHomeRun - BETA app from the Google Play and it works but it is choppy (needs transcoding) and audio doesn't work (not sure what that is about).  It appears to be something in Emby Server doesn't play nice with the latest beta version of HDHomeRun firmware.

Share this post


Link to post
Share on other sites
Doonga

I'm using that version of the firmware and it's working just fine. Works smoothly with the hdhomerun grey app as well as Emby. I'm on 6070 and have been using a Shield as well as in chrome on a computer.

 

Have you tried restarting the hdhomerun? You may also want to check to see if you're having bandwidth issues on your network. Especially if direct playing over wireless.

Share this post


Link to post
Share on other sites
FordGT90Concept

Yeah, I've power cycled and reconfigured the HDHomeRun.  Was this on Emby for Android or Emby for Android TV?  It seems to only be transcoding that has issues.

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
Doonga

I've used it on both. I have a Pixel C tablet that I use Emby for Android on and then the Shields where I use Emby for Android TV.

Share this post


Link to post
Share on other sites
FordGT90Concept

I did notice one thing that's different.  In Emby Server Live TV, it used to show the HDHomeRun twice: <ip address> and http://<ip address>.  Because of that, it also showed up down below four times (twice for each tuner).  Now it is down to just <ip address> and two tuners.  The Android transcoding for me hasn't worked since that changed.

 

 

Edit: I tried running Emby for Android TV again.  I attached the logs.  After trying to tune to the Rio Olymics on NBC, it just sits there spinning with no error message on the Leelbox.  This is what stands out in the log:

2016-08-21 10:37:36.8754 Info HttpClient: Checking for cache file C:\Users\Lee\AppData\Roaming\Emby-Server\cache\httpclient\e1b68e771e3163dd9f1de1570ab4aaf3
2016-08-21 10:37:36.8754 Error ServiceStackHost: Error occured while Processing Request: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
*** Error Report ***
Version: 3.0.6070.0
Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
Operating system: Microsoft Windows NT 6.2.9200.0
Processor count: 8
64-Bit OS: True
64-Bit Process: True
Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
System.IO.IOException
    at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at SocketHttpListener.Net.ResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)
    at SocketHttpListener.Net.ResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)
    at ServiceStack.Formats.HtmlFormat.SerializeToStream(IRequest req, Object response, IResponse res)
    at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse(IResponse httpRes, IRequest httpReq, String contentType, String operationName, String errorMessage, Exception ex, Int32 statusCode)
    at ServiceStack.ServiceStackHost.HandleUncaughtException(IRequest httpReq, IResponse httpRes, String operationName, Exception ex)
    at ServiceStack.HostContext.RaiseAndHandleUncaughtException(IRequest httpReq, IResponse httpRes, String operationName, Exception ex)
    at ServiceStack.HttpResponseExtensionsInternal.HandleResponseWriteException(Exception originalEx, IRequest request, IResponse response, String defaultContentType)
    at ServiceStack.HttpResponseExtensionsInternal.<WriteToResponse>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__13.MoveNext()
InnerException: System.Net.Sockets.SocketException
An established connection was aborted by the software in your host machine
    at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
    at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

2016-08-21 10:37:36.8754 Info HttpServer: HTTP Response 500 to 192.168.0.39. Time: 5923ms (slow). http://192.168.0.128:8096/emby/videos/11d3df69f3899432b6eeb3a221a549bd/stream.mkv?DeviceId=2ef0757d8dca917d&MediaSourceId=a10a46f18b984289b8c3c7674d54b57cnative&VideoCodec=h264&AudioCodec=ac3,aac,mp3&AudioStreamIndex=-1&VideoBitrate=17802950&AudioBitrate=448000&MaxAudioChannels=6&Level=51&Profile=high&PlaySessionId=99acafb105064f238fde66bcbdff3c31&CopyTimestamps=true&ForceLiveStream=false
2016-08-21 10:37:38.0004 Info HttpServer: HTTP POST http://192.168.0.128:8096/emby/Sessions/Playing/Stopped. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; MXQ Pro Build/LMY47V)
2016-08-21 10:37:38.0004 Info App: Stopping ffmpeg process with q command for C:\Users\Lee\AppData\Roaming\Emby-Server\transcoding-temp\f30a98dc251a1271c663594285dccbb6.mkv
2016-08-21 10:37:38.3911 Error ServiceStackHost: Error occured while Processing Request: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
*** Error Report ***
Version: 3.0.6070.0
Command line: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
Operating system: Microsoft Windows NT 6.2.9200.0
Processor count: 8
64-Bit OS: True
64-Bit Process: True
Program data path: C:\Users\Lee\AppData\Roaming\Emby-Server
Application Path: C:\Users\Lee\AppData\Roaming\Emby-Server\system\MediaBrowser.ServerApplication.exe
Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
System.IO.IOException
    at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at SocketHttpListener.Net.ResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count)
    at SocketHttpListener.Net.ResponseStream.Write(Byte[] buffer, Int32 offset, Int32 count)
    at ServiceStack.Formats.HtmlFormat.SerializeToStream(IRequest req, Object response, IResponse res)
    at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse(IResponse httpRes, IRequest httpReq, String contentType, String operationName, String errorMessage, Exception ex, Int32 statusCode)
    at ServiceStack.ServiceStackHost.HandleUncaughtException(IRequest httpReq, IResponse httpRes, String operationName, Exception ex)
    at ServiceStack.HostContext.RaiseAndHandleUncaughtException(IRequest httpReq, IResponse httpRes, String operationName, Exception ex)
    at ServiceStack.HttpResponseExtensionsInternal.HandleResponseWriteException(Exception originalEx, IRequest request, IResponse response, String defaultContentType)
    at ServiceStack.HttpResponseExtensionsInternal.<WriteToResponse>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
    at ServiceStack.Host.RestHandler.<ProcessRequestAsync>d__13.MoveNext()
InnerException: System.Net.Sockets.SocketException
An established connection was aborted by the software in your host machine
    at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
    at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

androidtv.zip

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
Doonga

I'm on Linux so there's some difference here. Do you have anti virus or something running on there that might think the connection is malicious and is killing it? That error sounds like something is aborting the connection in an unexpected manner.

Edited by Doonga

Share this post


Link to post
Share on other sites
FordGT90Concept

Nothing has changed except Emby Server version and HDHomeRun firmware.  The network is the same, no other software has changed on the server, I haven't touched the router config, and I haven't changed the Leelbox config.

 

Edit: What is the "host machine" in this context?  Emby Server or the HDHomeRun?

 

Edit: I have two Leelboxes.

 

Older Leelbox:

Emby for Android TV: worked before; works now

Emby for Android: worked before; video works, audio does not

 

Newer Leelbox:
​Emby for Android TV: not tested; does not work (no error)

Emby for Android: worked before; video shows one frame then the whole thing locks up

 

In truth, Android version would be my preference because Android TV version lacks basic functionality (like deleting a recording).  Since upgrading the Firmware and Emby Server, Android version doesn't work for either of them.

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
Luke

In Live TV setup I would check the ip addresses of your tuners and verify that they're correct.

Share this post


Link to post
Share on other sites
ebr

I tried HDHomeRun - BETA app from the Google Play and it works but it is choppy (needs transcoding) and audio doesn't work (not sure what that is about).  It appears to be something in Emby Server doesn't play nice with the latest beta version of HDHomeRun firmware.

 

If the HDHR app itself is also experiencing problems perhaps it is something outside of Emby...

Share this post


Link to post
Share on other sites
FordGT90Concept

The "Newer Leelbox" above, I factory reset.  Now Emby for Android TV works great on both Leelboxes but Emby for Android is broke on both: the moment the stream starts, they lock up (completely, not just the app).  I would prefer to use Emby for Android on these boxes because of better mouse support and easier navigation.

 

I verified the hardware/software in both Leelboxes is identical.

 

 

Side note: The logo on Emby for Android TV and Emby for Android is identical.  It would be nice if there was a "TV" on the Emby for Android TV to tell the two apart when both are installed.

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
Luke

have you looked at your hd homerun control panel at things like signal strength? signal drops can cause failures. i know you just did a factory reset and therefore you're associating the differences with that, but it could also be volatility of the tuner that is creating the inconsistency.

Share this post


Link to post
Share on other sites
FordGT90Concept

Extremely doubtful:
Tuner 0 Status
Virtual Channel: none
Frequency: 635.000 MHz
Program Number: 1

Modulation Lock: 8vsb
Signal Strength: 100%
Signal Quality: 98%
Symbol Quality: 100%

Streaming Rate: 9.896 Mbps
Resource Lock: 192.168.0.187

Share this post


Link to post
Share on other sites
FordGT90Concept

Long story short: for no apparent reason, video is now working on both boxes but they aren't playing audio.  In the Android TV app, I have to enable downmixing to hear it.  Does the Android app have a similar setting?  I checked under Playback settings and didn't see anything.

 

 

I attached the log (basically starting playback on both devices).  I have no idea why it didn't work before and now it does.  I literally didn't change anything and certainly if I did change anything, it wouldn't have effected both boxes.  This is baffling.  I have one theory and that is related to the resolution of the recording.  I'll be able to verify in a few hours.

test.zip

Share this post


Link to post
Share on other sites
Luke

There is no transcoding happening so it appears the apps are going straight to the tuner, which is good. That eliminates Emby Server as being related to the issues. So if that is the case, I think there might be some volatility with the tuner, despite your objections. It's also possible that available resources on the playback device are a factor, but less likely.

Share this post


Link to post
Share on other sites
FordGT90Concept

The main reason for upgrading the firmware was to prevent transcoding where DirectPlay would work.

 

If you look at the first logs I uploaded (leelbox.zip) Emby Server was clearly trying to transcode.  I don't know what happened between then and now but clearly it has switched to DirectPlay (which should have worked immediately after the firmware change).

 

So it appears everything on that front is now working correctly.  The problem now is that the Leelboxes can't handle the AC3/AAC (whichever it is) audio stream.  If Android TV down mixing is any indicator, the Leelbox can't handle the 5.1 audio stream.  Android TV fixes that by transcoding the audio stream.  Is there any way I can make Android Mobile do the same?

Share this post


Link to post
Share on other sites
Luke

Why do you think it's clearly trying to transcode? If it is then I apologize but I cannot see it. Please make sure to follow the log posting guidelines in the link I gave you, which include attaching complete log files as well as any generated ffmpeg logs. Thanks!

Share this post


Link to post
Share on other sites
FordGT90Concept

I meant in the first ZIP I attached to the thread.  It created the transcode file and one of the last lines in the server log is that transcoding was terminated.  This is in the rear-view now though.  I don't think I could reproduce it if I tried.  Basically what happened is:
​1. Updated HDHomeRun firmware.

2. Updated Emby Server to 3.0.6070.0

3. Noticed neither Leelboxes worked anymore.

4. Noticed one Leelbox worked using Android TV.

5. Factory reset the other Leelbox so it would also work using Android TV (had to turn on downmixing too).

6. Neither Leelbox worked using Android Mobile.

7. Both Leelboxes worked using Android Mobile.

 

The only explaination I have is that Emby Server on steps #2-6 (perhaps except #5) was trying to transcode when it shouldn't.  I have no idea why it changed its mind over time.  I suppose it could have been HDHomeRun as well.  I don't know but I do know I can't point to anything I did that caused the changes except #1, #2, and #5.

 

Testing...

Android Mobile, not transcoding, no audio

Android TV, not transcoding, locks up

 

FFS!  Now it reversed!  WTF is going on!?!  I attached the logs.

 

I thought no audio on Android Mobile was the only problem (it still is a problem) but that clearly is not the case.  Something else is causing it to be unreliable.

 

 

Edit: I'm going to contact Silicon Dust for instructions how to downgrade firmware.

problems.zip

Edited by FordGT90Concept

Share this post


Link to post
Share on other sites
Luke

Ok since you upgraded the firmware i assumed the first zip was no longer relevant. i will look at the new one.

Share this post


Link to post
Share on other sites
FordGT90Concept

It is relevent.  I upgraded the firmware prior to creating this thread.  That said, I have no idea what is going on.  All I know right now is that the problems are consistent across both Leelboxes.

 

 

Edit: Here's the log off the HDHomeRun:

19700101-00:00:02 System: reset reason = power on
19700101-00:00:08 System: network link 100f
19700101-00:00:09 System: ip address obtained: 192.168.0.59 / 255.255.255.0
20160820-14:21:59 System: time changed from Thu Jan  1 00:00:24 1970 to Sat Aug 20 14:21:59 2016
20160820-14:25:14 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160820-14:25:14 Tuner: tuner0 streaming http to 192.168.0.128:64299
20160820-14:31:40 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160820-14:31:41 Tuner: tuner0 streaming http to 192.168.0.187:51275
20160820-15:50:58 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160820-15:50:58 Tuner: tuner0 streaming http to 192.168.0.128:50607
20160821-13:11:49 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-13:11:49 Tuner: tuner0 streaming http to 192.168.0.39:42941
20160821-15:37:31 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-15:37:31 Tuner: tuner0 streaming http to 192.168.0.128:57394
20160821-18:13:08 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:13:08 Tuner: tuner0 streaming http to 192.168.0.128:61656
20160821-18:15:28 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:15:28 Tuner: tuner0 streaming http to 192.168.0.76:58023
20160821-18:16:57 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:16:57 Tuner: tuner0 streaming http to 192.168.0.128:61678
20160821-18:17:49 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:17:49 Tuner: tuner0 streaming http to 192.168.0.76:58036
20160821-18:22:48 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:22:48 Tuner: tuner0 streaming http to 192.168.0.128:61951
20160821-18:25:35 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:25:35 Tuner: tuner0 streaming http to 192.168.0.128:61971
20160821-18:33:59 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:33:59 Tuner: tuner0 streaming http to 192.168.0.31:39159
20160821-18:36:19 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:36:19 Tuner: tuner0 streaming http to 192.168.0.128:62258
20160821-18:36:25 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:36:25 Tuner: tuner0 streaming http to 192.168.0.128:62259
20160821-18:36:32 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-18:36:32 Tuner: tuner0 streaming http to 192.168.0.128:62260
20160821-19:29:47 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-19:29:47 Tuner: tuner0 streaming http to 192.168.0.31:56301
20160821-19:31:32 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-19:31:32 Tuner: tuner0 streaming http to 192.168.0.31:56302
20160821-19:37:16 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-19:37:16 Tuner: tuner0 streaming http to 192.168.0.31:56334
20160821-19:41:14 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-19:41:14 Tuner: tuner0 streaming http to 192.168.0.31:40213
20160821-19:52:08 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-19:52:08 Tuner: tuner0 streaming http to 192.168.0.128:64396
20160821-22:02:31 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-22:02:32 Tuner: tuner0 streaming http to 192.168.0.187:60178
20160821-22:22:58 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-22:22:59 Tuner: tuner0 streaming http to 192.168.0.215:37502
20160821-22:24:34 Tuner: tuner1 tuning 9.1 KCAU-TV (8vsb:189MHz-3)
20160821-22:24:34 Tuner: tuner1 streaming http to 192.168.0.31:40232
20160821-23:00:18 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160821-23:00:18 Tuner: tuner0 streaming http to 192.168.0.128:53458
20160822-00:00:18 Tuner: tuner0 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160822-00:00:18 Tuner: tuner0 streaming http to 192.168.0.128:55279
20160822-00:28:58 Tuner: tuner1 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160822-00:28:58 Tuner: tuner1 streaming http to 192.168.0.215:37519
20160822-00:30:40 Tuner: tuner1 tuning 4.1 KTIVNBC (8vsb:635MHz-1)
20160822-00:30:40 Tuner: tuner1 streaming http to 192.168.0.128:56206
20160822-00:30:48 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:30:50 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:30:52 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:30:55 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:31:46 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:31:47 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:31:49 Tuner: tuner1 tuning 14.1 KMEG-DT (8vsb:623MHz-3)
20160822-00:31:49 Tuner: tuner1 streaming http to 192.168.0.128:56222
20160822-00:31:55 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:31:56 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:31:58 HTTP: rejecting request from 192.168.0.128 - all tuners in use
20160822-00:32:01 HTTP: rejecting request from 192.168.0.128 - all tuners in use

128 = server

215 = leelbox (android-25c2ce3)

76 = not sure...IP changed

31 = not sure...IP changed

87 = my computer

Edited by FordGT90Concept

Share this post


Link to post
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...