If anyone can provide logs showing where the recording fails when it should use the second device, I’d love to see them. @lvmickey I see you’ve posted logs, but without knowing when things are supposed to have not worked, it’s difficult to track them down.
Here are the logs of the first Tuner. We should be able to merry up the time stamps some how. It appears that all the requests are going to the first Tuner and being rejected and messing with them causes them to switch to another Tuner. This is one of the streams that didn’t encode video 20170810-03:20:10 Tuner: tuner2 tuning 584 Fox Sports 2 HD (auto:261MHz-1239) but did audio.
19700101-00:00:00 System: reset reason = firmware upgrade
19700101-00:00:01 CableCARD: M-CARD inserted
19700101-00:00:03 System: network link 1000f
19700101-00:00:04 System: ip address obtained: 10.9.9.8 / 255.255.255.0
19700101-00:00:05 CableCARD: Motorola card (0000:0625)
19700101-00:00:05 CableCARD: authentication status: authentication in progress
19700101-00:00:05 CableCARD: authentication status: authentication success, validation success
20170809-15:56:59 CableCARD: time changed from Thu Jan 01 00:00:52 1970 to Wed Aug 09 15:56:59 2017
20170810-03:20:04 Tuner: tuner0 tuning 596 BeIN Sport HD (auto:651MHz-1197)
20170810-03:20:04 Tuner: tuner0 streaming http to 10.9.9.11:44096
20170810-03:20:05 CableCARD: tuner0 596 BeIN Sport HD (auto:651MHz-1197) access = subscribed
20170810-03:20:07 Tuner: tuner1 tuning 732 FXM HD (auto:69MHz-1282)
20170810-03:20:08 Tuner: tuner1 streaming http to 10.9.9.11:44420
20170810-03:20:08 CableCARD: tuner1 732 FXM HD (auto:69MHz-1282) access = subscribed
20170810-03:20:10 Tuner: tuner2 tuning 584 Fox Sports 2 HD (auto:261MHz-1239)
20170810-03:20:11 Tuner: tuner2 streaming http to 10.9.9.11:44824
20170810-03:20:11 CableCARD: tuner2 584 Fox Sports 2 HD (auto:261MHz-1239) access = subscribed
20170810-03:20:14 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:20:17 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:20:17 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:30:01 Tuner: tuner0 http stream ended (remote closed)
20170810-03:43:07 Tuner: tuner2 http stream ended (remote closed)
20170810-03:43:13 Tuner: tuner1 http stream ended (remote closed)
20170810-03:53:29 Tuner: tuner0 tuning 596 BeIN Sport HD (auto:651MHz-1197)
20170810-03:53:30 Tuner: tuner0 streaming http to 10.9.9.11:54064
20170810-03:53:30 CableCARD: tuner0 596 BeIN Sport HD (auto:651MHz-1197) access = subscribed
20170810-03:53:32 Tuner: tuner1 tuning 732 FXM HD (auto:69MHz-1282)
20170810-03:53:33 Tuner: tuner1 streaming http to 10.9.9.11:54634
20170810-03:53:33 CableCARD: tuner1 732 FXM HD (auto:69MHz-1282) access = subscribed
20170810-03:53:35 Tuner: tuner2 tuning 584 Fox Sports 2 HD (auto:261MHz-1239)
20170810-03:53:36 Tuner: tuner2 streaming http to 10.9.9.11:54810
20170810-03:53:36 CableCARD: tuner2 584 Fox Sports 2 HD (auto:261MHz-1239) access = subscribed
20170810-03:53:39 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:53:41 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:53:44 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:53:44 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:53:53 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:53:53 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:55:26 Tuner: tuner0 http stream ended (remote closed)
20170810-03:55:38 Tuner: tuner2 http stream ended (remote closed)
20170810-03:55:44 Tuner: tuner1 http stream ended (remote closed)
@DaveBinM The times stamps of when unknown errors occurred should match up with. Not sure the difference of Plex and HDHRs timestamps. I added the Videoless timestamp above. I am in Washington DC if that helps, I think that HDHR is in UTC and DC is -5 UTC at the moment.
20170810-03:20:14 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:20:17 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:20:17 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:22:52 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
20170810-03:23:11 HTTP: rejecting request from 10.9.9.11 - all tuners in use
@lvmickey said:
@srjinatl Did you do a uninstall and reinstall or did you do an upgrade?@BRBMan Did you reboot when you uninstalled and reinstalled? I know it sounds someone old school but I have noticed with Plex that rebooting while uninstalled seems to help.
I did an upgrade.
@johnm_ColaSC I agree with your assessment that there is an issue with the tuner selection logic.
@DaveBinM Here you go. See times in my previous post above.
@lvmickey It’s the PMS logs which are important, not the HDHR ones.
@johnm_ColaSC I’ll have a look at those logs now, and see what I can find.
@DaveBinM I understand that the PMS logs are important. I was trying to find a way to give you a time stamp to look for in the PMS logs. I requested to record shows already in progress so the plex logs should be near the time the error occurred within the tuner log. I’m not certain on the time zone the HDHRs put them self into. I guess it is fome form of UTC. I will try to look through the PMS logs tomorrow to try to see an error.
@lvmickey said:
@srjinatl Did you do a uninstall and reinstall or did you do an upgrade?@BRBMan Did you reboot when you uninstalled and reinstalled? I know it sounds someone old school but I have noticed with Plex that rebooting while uninstalled seems to help.
yes I did
@DaveBinM said:
If anyone can provide logs showing where the recording fails when it should use the second device, I’d love to see them. @lvmickey I see you’ve posted logs, but without knowing when things are supposed to have not worked, it’s difficult to track them down.
I provided just that in the post above on August 8th.
@DaveBinM I show the same error as @johnm_ColaSC below in the plex log. The IP is for my second recorder not my first.
Aug 09, 2017 23:45:54.118 [0x7fe1667f7700] DEBUG - DVR:Segmenter: Creating a new recorder for http://10.9.9.9:5004/auto/v596.
Aug 09, 2017 23:46:11.697 [0x7fe16a7ff700] DEBUG - DVR:Segmenter: Creating a new recorder for http://10.9.9.9:5004/auto/v734.
I have no clue why it isn’t pulling video now, though.
@DaveBinM I am going to guess this is the error associated with the Video not working correctly.
Aug 09, 2017 23:45:55.101 [0x7fe1777ff700] ERROR - [Transcoder] [h264 @ 0x196ae80] SPS unavailable in decode_picture_timing
Aug 09, 2017 23:45:55.102 [0x7fe17e7fe700] ERROR - [Transcoder] [h264 @ 0x196ae80] non-existing PPS 1 referenced
Aug 09, 2017 23:45:55.102 [0x7fe191bff700] ERROR - [Transcoder] [h264 @ 0x196ae80] SPS unavailable in decode_picture_timing
Aug 09, 2017 23:45:55.103 [0x7fe1797fd700] ERROR - [Transcoder] [h264 @ 0x196ae80] non-existing PPS 1 referenced
Aug 09, 2017 23:45:55.103 [0x7fe175bff700] ERROR - [Transcoder] [h264 @ 0x196ae80] decode_slice_header error
Aug 09, 2017 23:45:55.104 [0x7fe179ffe700] ERROR - [Transcoder] [h264 @ 0x196ae80] no frame!
@lvmickey I think those are unrelated to this issue.
Maybe this will help . . . here are the logs that I generated when trying to duplicate the issue
I said earlier . . .
I have logs at each of the points - I’ve only attached the final set of logs but can provide the earlier ones if needed
Kicked off the first 6 - created logs
Cancelled the first 3 - created logs
Cancelled the final 3 - created logs
I just attached all 3 - so in the first one you should see me try to record 6 shows and 3 fail - I then downloaded the logs. I then cancelled the the first 3 and downloaded the logs and then cancelled the final 3 and downloaded the logs (which I attached earlier)
Go Ninja Go!!! 
I too am only able to use 1 of my HD Homerun devices. I have Connects, HDHR4-2US. Things have worked fine until the last two 1.7 updates. Tried updating to version 1.8.0.4109 and no joy, I still have the same issue. Plex will only use 1 of the Connect devices. I am using Ubuntu 16.04.
I too have this issue, and posted it at https://forums.plex.tv/discussion/282019/bug-ver-1-8x-only-one-hdconnect-tuner-works-additional-recordings-dont-run-on-2nd-hdconnect-unit
Below is an example and logs. I triggered four recordings…two work, but the remaining two do not take advantage of the idle tuner. This is with current firmware for the two HDConnect HomeRun tuners version 20170810beta1
I don’t know if this will be helpful, but I noticed that Plex starts 2 transcoding sessions when it starts recording the first show (as detected by clicking on the > icon in the menu bar). It indicates that I have 4 transcoding sessions active when I record two shows at the same time (both successfully recorded). It’s only when I try to record additional shows that I get the “Unknown Error” message (I used to be able to record 4 shows using my two HDHomeRun Extend devices, each with two tuners). Interestingly, if I just “watch” a show using the HDHomeRun Channel (laptop) or LiveTV (iOS), only a single transcoding session is started.
Could this help with the diagnosis of the problem?
I’m running the latest Plex Server (lifetime PlexPass) on a dual core Mac mini; two HDHomeRun Extend devices with the latest Firmware.
Just to add to this…I looked at the logs of my tuners.
The firmware was updated at the same time, so at Fri Aug 11 18:50:38 2017 they were both “in sync”
Looking at the first log set, it appears Plex did “ask” for tuner data when I triggered the four simultaneous recordings, but was rejected by physical HDHomerun one, as both its internal tuners were busy.
My uneducated guess is when the tuner rejects the request by Plex, Plex does not roll over to subsequent tuners…instead, it just tried hitting the same tuner again several times
HDHomeRun CONNECT
System Log
19700101-00:00:02 System: reset reason = firmware upgrade
19700101-00:00:09 System: network link 100f
19700101-00:00:10 System: ip address obtained: 192.168.1.128 / 255.255.255.0
20170811-18:50:38 System: time changed from Thu Jan 1 00:00:25 1970 to Fri Aug 11 18:50:38 2017
20170811-21:59:01 Tuner: tuner0 tuning 32.6 COMET (8vsb:563MHz-6)
20170811-21:59:01 Tuner: tuner0 streaming http to 192.168.1.188:51188
20170811-22:32:34 Tuner: tuner1 tuning 2.1 WSB-HD (8vsb:623MHz-1)
20170811-22:32:34 Tuner: tuner1 streaming http to 192.168.1.188:49809
20170811-22:32:36 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:41 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:41 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:45 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:45 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:57 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:32:57 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:33:23 HTTP: rejecting request from 192.168.1.188 - all tuners in use
20170811-22:33:31 Tuner: tuner1 http stream ended (remote closed)
20170812-00:00:01 Tuner: tuner0 http stream ended (remote closed)
Second log entry from second physical tuner
System Log
19700101-00:00:02 System: reset reason = firmware upgrade
19700101-00:00:09 System: network link 100f
19700101-00:00:10 System: ip address obtained: 192.168.1.206 / 255.255.255.0
20170811-18:50:51 System: time changed from Thu Jan 1 00:00:25 1970 to Fri Aug 11 18:50:51 2017
20170812-15:59:00 Tuner: tuner0 tuning 8.3 KNOWLED (8vsb:183MHz-3)
20170812-15:59:00 Tuner: tuner0 streaming http to 192.168.1.188:51482
20170812-16:55:05 Tuner: tuner0 http stream ended (remote closed)
20170813-01:58:59 Tuner: tuner0 tuning 32.9 CHARGE (8vsb:563MHz-9)
20170813-01:58:59 Tuner: tuner0 streaming http to 192.168.1.188:51553
20170813-04:59:59 Tuner: tuner0 http stream ended (remote closed)
20170813-12:59:59 Tuner: tuner0 tuning 5.1 WAGA-HD (8vsb:551MHz-3)
20170813-12:59:59 Tuner: tuner0 streaming http to 192.168.1.188:60471
20170813-14:00:00 Tuner: tuner0 http stream ended (remote closed)
@EABenton Not yet, I’m afraid. I have some information which I’m slowly working through, and trying to reconcile, but I’m still trying to put the pieces together.
