Jump to content


Photo
3.0.6070.0

Live TV not working as of 3.0.6070.0 & 20160630atest2

20160630atest2 HDHomeRun Connect Live TV

Best Answer CBers , 04 September 2016 - 03:15 PM

Have a link to the September 2 beta? All I'm seeing is stuff from 2015.


https://www.silicond...p?f=119&t=20613 Go to the full post


  • Please log in to reply
36 replies to this topic

#21 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 21 August 2016 - 07:57 PM

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?



#22 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142115 posts
  • Local time: 06:40 AM

Posted 21 August 2016 - 08:04 PM

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!



#23 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 21 August 2016 - 08:38 PM

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.

Attached Files


Edited by FordGT90Concept, 21 August 2016 - 08:43 PM.


#24 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142115 posts
  • Local time: 06:40 AM

Posted 21 August 2016 - 08:46 PM

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



#25 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 21 August 2016 - 08:54 PM

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, 21 August 2016 - 09:08 PM.


#26 Doonga OFFLINE  

Doonga

    Advanced Member

  • Members
  • 145 posts
  • Local time: 07:40 AM
  • LocationConnecticut

Posted 21 August 2016 - 09:06 PM

I know that this probably isn't part of the issue, but just for reference. There's an Android app called hdhomerun signal meter. It'll show you the signal strength and signal to noise ratio live as it changes. It's come in handy a few times.

Good luck getting to the bottom of this issue!

Edited by Doonga, 21 August 2016 - 09:07 PM.


#27 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 22 August 2016 - 09:38 AM

I did not expect this...

Firmware can not be rolled back. We've discovered a decode/playback issue specifically with devices running Amlogic CPUs. We've purchased a couple of devices and will running tests this week.

Can't roll back firmware and the Leelboxes do have Amlogic S905 chips...

Edited by FordGT90Concept, 22 August 2016 - 09:39 AM.


#28 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48060 posts
  • Local time: 06:40 AM

Posted 22 August 2016 - 10:11 AM

So it is a problem with the HDHR after all?



#29 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 22 August 2016 - 11:22 AM

Appears so. I'll update on this thread when they get new firmware pushed out.

Edited by FordGT90Concept, 22 August 2016 - 11:23 AM.


#30 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142115 posts
  • Local time: 06:40 AM

Posted 22 August 2016 - 01:38 PM

Thanks for reporting back.



#31 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 01 September 2016 - 02:26 AM

Just so you know, I did an Emby install at my sister's with the new HDHomeRun EXTEND (has 2016 firmware) and an Amlogic Leelbox playback on it is very broken be it Live TV or a recording of previous Live TV. Other devices work fine. I can understand the issues with Live TV but playing back recorded TV is bewildering because that should no longer involve the HDHomeRun's broken firmware.


That said, no news of a firmware update yet.

Edited by FordGT90Concept, 01 September 2016 - 02:59 AM.


#32 earthtorob OFFLINE  

earthtorob

    Advanced Member

  • Members
  • 130 posts
  • Local time: 12:40 PM

Posted 02 September 2016 - 07:05 PM

This sounds similar to an issue I have been having.    For instance, I recorded the Ravens game last night and I also watched it live.  The picture on my living room set was flawless 1080i.  But when I looked at the recording the next day I had a lot of reception issues that I'm sure the encoder struggled with.  The cable run from my antenna is about 3 feet before it hits my Amp.  From the Amp my cable run is about 25 feet to my Tv and about 5 feet to my HDHomerun.  So I shouldn't be getting any kind of issue with a weak signal unless my HDHomerun has a really bad splitter.

 

Could it be that this gentlemans issue is a bad HDHomerun?



#33 earthtorob OFFLINE  

earthtorob

    Advanced Member

  • Members
  • 130 posts
  • Local time: 12:40 PM

Posted 02 September 2016 - 07:07 PM

That will teach me to read the whole thread before I post.   :(



#34 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15049 posts
  • Local time: 11:40 AM
  • LocationKent, England.

Posted 03 September 2016 - 03:38 AM

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


You can't downgrade the firmware - see a similar question/answer here.

The latest version of firmware, announced today, is 20160902beta3.

Also, you can post a question on the SD forums, including the model and serial number and SD can check out your HDHomeRun from their end.

#35 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 04 September 2016 - 03:12 PM

Have a link to the September 2 beta? All I'm seeing is stuff from 2015.

#36 CBers OFFLINE  

CBers

    Advanced Member

  • Moderators
  • 15049 posts
  • Local time: 11:40 AM
  • LocationKent, England.

Posted 04 September 2016 - 03:15 PM   Best Answer

Have a link to the September 2 beta? All I'm seeing is stuff from 2015.


https://www.silicond...p?f=119&t=20613
  • FordGT90Concept likes this

#37 FordGT90Concept OFFLINE  

FordGT90Concept

    Advanced Member

  • Members
  • 662 posts
  • Local time: 05:40 AM

Posted 04 September 2016 - 06:36 PM

Thanks, installed it, Emby for Android TV appears to be working great now but Emby for Android does not on the Amlogic boxes. To clarify: Emby for Android no longer appears to crash (improvement) but the framerate is like 0.01 fps and there is no audio.

Edit: The other Amlogic running Emby for Android played the video fine but the audio was a nasty pulse sound.

Edit: All testing on Emby for Android TV on both Amlogic Leelboxes worked great.

Edited by FordGT90Concept, 04 September 2016 - 06:50 PM.






Also tagged with one or more of these keywords: 3.0.6070.0, 20160630atest2, HDHomeRun, Connect, Live TV

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users