New HDHomerun Extend Live TV Stops Playing

[lcasadonte 3]

I will say this about the beta - if you notice in the pic below it recognizes the hdhomerun but in the pic in my previous post it was un-named.

[Guest asrequested]

Is it working better?

[lcasadonte 3]

I haven't done the recording scenario yet but it does seem to play better so far.  No cutouts.  Emby doing the transcoding.  Pixelization in signal drops as you would expect.

[Guest asrequested]

I can recommend these signal amplifiers

 

http://www.pctstore.com/Amplifier_s/26.htm

 

https://www.amazon.com/Bi-Directional-Amplifier-Splitter-Booster-Passive/dp/B001BMKNZI

[lcasadonte 3]

Still trying to diagnose things (whether i have a defective unit or not) and I noticed this in the hdhomerun log coming from emby: 

 

20160827-15:17:47 Tuner: tuner0 tuning 4.1 WBZ-DT (8vsb:569MHz-1)
20160827-15:17:52 HTTP: rejecting request from 198.202.xxx.xxx - no video data

 

what does this mean?

[lcasadonte 3]

Thanks Doofus.  My antenna comes pre-amplified and I'm trying to figure out if I can do anything else with that.

[lcasadonte 3]

I think this is the log snippet from emby at that time:

2016-08-27 15:16:59.2023 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:02.2515 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:02.2515 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:05.2927 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:05.2927 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:08.3319 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:08.3319 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:11.3620 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:11.3620 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:14.4122 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:14.4122 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 9ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:17.4324 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:17.4384 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:20.4725 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:20.4725 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:23.5127 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:23.5127 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:25.9279 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml. UserAgent: UPnP/1.02016-08-27 15:17:25.9279 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 3ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml2016-08-27 15:17:25.9279 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml. UserAgent: UPnP/1.02016-08-27 15:17:25.9279 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml2016-08-27 15:17:25.9279 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml. UserAgent: UPnP/1.02016-08-27 15:17:25.9399 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml2016-08-27 15:17:26.4439 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml. UserAgent: UPnP/1.02016-08-27 15:17:26.4439 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 3ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml2016-08-27 15:17:26.4439 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml. UserAgent: UPnP/1.02016-08-27 15:17:26.4439 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml2016-08-27 15:17:26.4559 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml. UserAgent: UPnP/1.02016-08-27 15:17:26.4559 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 0ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml2016-08-27 15:17:26.5419 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:26.5489 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:29.5831 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:29.5831 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:32.6122 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:32.6192 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:35.6634 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:35.6634 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:38.7126 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:38.7186 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:41.7428 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:41.7428 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:44.8129 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:44.8209 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 8ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:47.8431 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:47.8431 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:50.8733 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:50.8733 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 6ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:53.9255 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:53.9325 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:17:55.9426 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml. UserAgent: UPnP/1.02016-08-27 15:17:55.9426 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 2ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml2016-08-27 15:17:55.9426 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml. UserAgent: UPnP/1.02016-08-27 15:17:55.9426 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml2016-08-27 15:17:55.9426 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml. UserAgent: UPnP/1.02016-08-27 15:17:55.9426 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 0ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml2016-08-27 15:17:56.4576 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml. UserAgent: UPnP/1.02016-08-27 15:17:56.4576 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 3ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/description.xml2016-08-27 15:17:56.4576 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml. UserAgent: UPnP/1.02016-08-27 15:17:56.4576 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/contentdirectory/contentdirectory.xml2016-08-27 15:17:56.4696 Info HttpServer: HTTP GET http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml. UserAgent: UPnP/1.02016-08-27 15:17:56.4696 Info HttpServer: HTTP Response 200 to 198.202.xxx.xxx. Time: 1ms. http://198.202.xxx.xxx:8096/dlna/b727a87aed23c8f256742e2a657cf570/connectionmanager/connectionmanager.xml2016-08-27 15:17:56.9966 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)2016-08-27 15:17:57.0036 Info HttpServer: HTTP Response 204 to 198.202.xxx.xxx. Time: 7ms. http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress2016-08-27 15:18:00.0428 Info HttpServer: HTTP POST http://198.202.xxx.xxx:8096/emby/Sessions/Playing/Progress. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTS Build/LVY48F)

Edited August 28, 2016 by lcasadonte

[Guest asrequested]

Well, it looks like it tunes to a signal, creates a data stream, but whatever reason it gets kicked out of the network, and it keeps trying. My networking knowledge isn't great, so I'll defer to Luke and ebr on that. I'm still thinking there could be something wrong with the unit. I've got an HDHR prime, and it's pretty much plug'n'play (once Comcast is taken care of)

[lcasadonte 3]

Well its a brand new unit (about a week old commercially available) and I'm trying to narrow things down.  I got the unit because of the dlna support.  So I'm going to try to play the same channels over dlna to the tv through the video app on the tv.  If the tv can process the signal better or worse it may help narrow some things down.  I'm also going to look at adding the amplifier to the signal itself but I have a 30db amp in the antenna so that may not work.  Stuff happens when the signal strength is over 90% and when I try to play the same channel through the tv it plays fine.  But that uses the tv tuner.  So at least with the dlna it will stay the same tuner.  I also have a prime and do not have any problems with it.  In its current mode the hdhomerun is not transcoding so that is eliminated as an issue in general terms.  Its either the signal/tuner or conversion to h264 if its the hdhomerun at this point.  I only have a small amount of time to request the exchange so I'll keep at it.  Any and all insight provided is appreciated.

[Luke 37096]

On the emby side of things we do need to add automatic re-connection to make the process more resilient to this. That won't stop it from happening in the first place though, it will just make the recovery a little more graceful.

[lcasadonte 3]

okay did a little more research on the hdhome run side and this is their guidance on ota antenna strength and I easily exceed these with signals in the mid 80s and up in the 90s for the channels I am trying to watch:

 

Use the

Digital Antenna:
Check that the signal strength is above 60% minimum (75% recommended).
Check that the signal quality is above 50% minimum.
Check that the symbol quality is 100%.
 

Oh BTW I also found this:

HDHomeRun software to determine Signal Strength and Signal Quality
Windows users: Open HDHomeRun Config (GUI). Click on one of the tuner icons to
select the tuner.
Other OS: Use the command: (Fill in the correct Device ID and tuner number)
hdhomerun_config <device id> get /tuner<n>/status

Signal strength will be reported as ss, Signal Quality will be reported as snq.

[Luke 37096]

Right the issue is the signal strength at the exact time of the problem, as this is something that can fluctuate due to a number of external factors.

[lcasadonte 3]

On this note I am noticing a problem with signal quality in a few more scenarios I've tried.  Am wondering if I have a cable or splitter issue.  Strength on this channel is 90% but signal quality is 50%.

Edited August 28, 2016 by lcasadonte

[Guest asrequested]

On this note I am noticing a problem with signal quality in a few more scenarios I've tried.  Am wondering if I have a cable or splitter issue.  Strength on this channel is 90% but signal quality is 50%.

Not to get too technical here, but look at what bandwidth your antenna uses. If it's above 1GHz, you'll need RG6 cable, and any splitters/connectors (if you joint cables and are using the higher frequency, they should be blue not white) you use will also need to support that frequency range. If it's below 1GHz, check and possibly remake the connectors. Also check how many db you lose on any splitters. Is your signal amplifier at the antenna or near your HDHR? Preferably, it would be better by the tuner, as you won't lose further signal. I used to work for DIsh, and had to deal with similar issues.

[lcasadonte 3]

Thanks Doofus.  I'll check.  I was having trouble finding my exact antenna manual for some reason and am having a physical issue preventing me from getting at the splitter to swap it direct and do that measurement.  Hopefully will feel better tomorrow and can do it.  My amplifier is a 30db in the antenna itself.  If i put a variable attenuator in amd played with that do you think that might cancel out the problem enough?  Im in a marine environment and I have been suspecting the connectors.  Is there any way to narrow it down?

 

For instance I'm thinking of using a portable antenna and just see what measurements i can get off that and what the signal quality is.

Edited August 28, 2016 by lcasadonte

[Guest asrequested]

Thanks Doofus.  I'll check.  I was having trouble finding my exact antenna manual for some reason and am having a physical issue preventing me from getting at the splitter to swap it direct and do that measurement.  Hopefully will feel better tomorrow and can do it.  My amplifier is a 30db in the antenna itself.  If i put a variable attenuator in amd played with that do you think that might cancel out the problem enough?  Im in a marine environment and I have been suspecting the connectors.  Is there any way to narrow it down?

 

For instance I'm thinking of using a portable antenna and just see what measurements i can get off that and what the signal quality is.

 

Try using water tight fittings with the rubber seals.

 

https://www.amazon.com/EX6WSPLUS-SignalTight%E2%84%A2-Universal-compression-integrated/dp/B00BNFK2XG/ref=sr_1_11?ie=UTF8&qid=1472427385&sr=8-11&keywords=ppc+connectors

 

Stripping tool

 

https://www.amazon.com/Ideal-45-605-Preppro-Coaxial-Stripper/dp/B008KOZYWC/ref=sr_1_20?ie=UTF8&qid=1472427975&sr=8-20&keywords=coax+stripping+tool

Edited August 28, 2016 by Doofus

[lcasadonte 3]

Ok just a side note.  Been away for a couple days.  When I play streams locally (no emby through hdview but using vlc), they play fine, no disconnects.  I saw another post but had trouble finding it with a similar issue.  They were not having a signal quality issue apparently.  I do see my signal quality go up using the hdhomerun gui exe and monitoring in real time (and down a lot because I am in a boat and the boat moves).  When it dips low my theory is emby disconnects the stream (this is where the reconnect logic would really come in handy as the hdviewer setup will not drop the signal - only pixelate).  I also get the metallic snaps and pops with transcoding but that is not an emby issue (ffmpeg would be my guess).  Transcoding seems to be effected by the variations in quality.  I'm going to get someone in to check my connections to see if I can make an improvement but it would be really nice not to disconnect in the scenario where there is a dip in signal quality but not enough for the tv tuner or hdview software to disconnect.  Should I put in a feature request?  Thanks for all your help.  Also posting to share just in case someone else has my issue.

[Luke 37096]

We are going to be adding this feature soon, yes.

[lcasadonte 3]

Thanks,