This problem of not rolling over to additional configured Plex tuners continues even in the latest version 1.8.1.4139
I updated my post at https://forums.plex.tv/discussion/282019/bug-ver-1-8x-only-one-hdconnect-tuner-works-additional-recordings-dont-run-on-2nd-hdconnect-unit#latest
…with log files for both the tuners and Plex.
Hoping this will get fixed soon…
@“rbkirk.Plex” The log files for the tuners aren’t really that useful for this. It’s more PMS logs. I think I have sufficient information to work through for the time being, but please be patient and bear with me. 
Thanks for the reply!
@“rbkirk.Plex”
Agreed - I just tried the latest on my secondary server and the issues persisted.
I just re-connected an older Mac server running Plex Server 1.4.2.3400. When I start recordings with this older Plex Server software, Plex DOES NOT START ANY TRANSCODING SESSIONS. (The HDHomeRun Extend devices are both set up for Highest Quality transcoding). However, when I use my regular Mac Server running the latest Plex Server (the same home network, same HDHomeRun tuners, etc.), PLEX SERVER SAYS I’M STARTING TWO TRANSCODING SESSIONS FOR EACH RECORDING I MAKE. It apparently shouldn’t be starting any transcoding sessions (the HDHomeRun devices should be doing the transcoding). Also, with the old PlexServer software, I can record four shows simultaneously, no problem. As I mentioned above, I can only record two at a time with the latest Plex Server software. I THEN COMPLETELY REMOVED AND THEN INSTALLED THE LATEST PLEX SERVER FROM SCRATCH ON MY SECONDARY MAC COMPUTER, BUT THIS DIDN’T SOLVE THE PROBLEM… NOW BOTH COMPUTERS GIVE THE SAME RESULTS: TWO TRANSCODING SESSIONS PER RECORDING, and only two shows max recording at a time.
Plex transcodes all recordings starting with the 1.7.0 release in anticipation of Live TV. So your old version not starting transcodes with recording was the normal behavior up through the 1.6.1 release.
@DaveBinM if you need use to search of anything specific in any of our logs, I think most of on here are willing to help with any data processing you might need.
@lvmickey Thanks. I think I have enough to go on now, but I’ll certainly pipe up if I need more
@John_ColaSC Thanks!
I updated my HDHomeRun Connects to firmware version 20170815 to see if it was possible that a firmware update would fix this issue…
Unfortunately, it did not. The problem persists, and in the exact same manner as before.
I posted logs and details to https://forums.plex.tv/discussion/282019/bug-ver-1-8x-only-one-hdconnect-tuner-works-additional-recordings-dont-run-on-2nd-hdconnect-unit#latest
@“rbkirk.Plex”
I think you can take a break on updating everything . . . . as @johnm_ColaSC has said repeatedly across the forums that they have identified the issue with his help and it has been passed along to the Plex Engineers thanks to the help of a Plex Ninja - guessing that was @DaveBinM
and I’d like to Thank both of them for the hard work to identify it!
Thanks from me too! Absolutely love the software, but looking forward to getting all my HDHRs working again!
this is still not working in the latest 1.8.2
Disappointing it still isn’t fixed in 1.8.2. Will Plex support multiple HDHomeRun devices in the future, or is this a phased out feature?
Never mind my last post… I see from above posts that Plex Engineers are still working on it…
We’re a little over 3 weeks from the start of the new fall season . . . let’s hope this gets resolved before then . . .
Any chance we can get an update on how close they are to a fix?
Thanks!
@EABenton I am right there with you.
Just uninstalled 1.8.2 and installed 1.8.3. Started 4 recordings and all 4 worked for me, both of my Connects were able to be utilized.
@johnm_ColaSC: I just upgraded to 1.8.3 using the feature in the Plex program and I still have the recording problem. Can you tell me exactly the procedure you used to uninstall and install? I’ll give it a try. Thanks! Mike
Ignore that previous post. First 4 worked, next set of recordings Plex was back to thinking one connect was recording when the other was actually being used.
Sounds like what happened when I installed 1.8.1 :/.
