I have Plex DVR running on Nvidia Shield TV. I have two HD Homerun Connects linked to plex. If I try and record two tv programmes simultaneously the second programme the grey Nvidia Shield notification appears at the bottom of the screen saying that the recording failed.
If I then go into scheduling the recording still shows failed ‘for unknown reason’ but if I cancel the other recording the failed recording immediately starts to work.
I have tried recording these files to different locations, to the internal drive, to a nas drive but the same thing happens each time.
As I have two HD Homerun Connects I should be able to, in theory, record up to 4 programmes as once. I am based in the UK but as far as I can see this shouldn’t have an effect.
I don’t have the Shield, but I do have 3 HDHomeRun Extend units. I have just recently setup Plex on an Ubuntu 16.04 dedicated workstation and today I had 3 recordings set for 10pm. Two other recordings were in progress and ending when the two new ones started. One of the new recordings started as soon as one of the other in progress recordings finished. The second recording failed with the same unknown error message. The third recording never attempted to start at all.
I rebooted the 2nd HDHomeRun Extend and attempted to manually start recording 3, but no dice. I then ran a channel scan on the DVR within the Plex software even though everything looked just fine in the existing channel lineup. After that finished, I deleted the recurring recording entry and went back to the list of programs and again created a recurring daily recording job for the 10pm news. This time the 3rd recording started and is continuing to run.
I also had installed the new update today. The failure occurred both before and after the Plex software update. All 3 HDHomeRun boxes have the latest August 2017 Firmware installed.
Server is a HP Z420 which sports an E5-1650 2.3Ghz Xeon processor with a Passmark score of over 11,500+, so server speed should not be an issue. Also, I’m running the OS on a 250GB SSD and recording tv programs on a WD RED 2TB HD, and everything is being recorded in native format, so no real load on the server during recording from looking at CPU Usage and all 6 Core Temperatures.
I will have to monitor this one closely.
Also, I need to find a way to get Plex to report successful and unsuccessful recording results as soon as the job fails or completes. A Text message or email would work nicely as well as a reviewable Log File to see what happened.
I’ve been battling the same issue since cutting the cord in June. It’s been over two months of frustrating problem solving and equipment upgrades and I still don’t have a reliable DVR for the impending Fall Season.
I’m running another test right now to capture some server logs to send to the devs. I’m afraid they’re too busy working on more versions of the PMS (Fire TV…) than addressing the issues on the ones already out there.
Similar suffering here. Plex DVR, Synology NAS & HDHomeRun Quattro. I can view simultaneous channels, I can set simultaneous recordings, the recoding schedule displays them and, at the appointed time the guide show them as ‘recording’ but the ‘activity’ monitor only shows the first one recording.
Post-recording the failed programmes vanish from the recording schedule and the priority menu displays ‘no upcoming airings’. There are no failure messages displayed.
Looking at the Plex logs I can see that Plex and HomeRun set an individual tuner for each recording but I cannot find anything in the logs that explains why only 1 tuner was actually used and the others discarded.
I did wonder if it was a Synology issue but from previous comments I see this also impacts other more powerful servers.
If there is anything particular I should be looking for in the logs I will explore further.
