Recording failed. Please check your tuner or antenna

[Hserver1]

Log files: Plex Media Server Logs_2019-01-08_23-01-28.zip (3.6 MB)
Thanks for the help this is frustrating at least I know of a workaround.

Update I attempted to record two things at once while watching something to see if it failed a third time just to try and figure out why and it worked fine. Tried doing it again and once again it worked so those two times of failed recordings while playing back a file could have been a fluke.

Update 2 tried enabling commercial removal again and testing with two recordings and it seemed to work fine so I’ll be trying it on my regularly recorded shows tomorrow hopefully it goes smoothly. I’ll be monitoring it closely to see if I have to intervene and start it recording again.

[Chalky1982]

funny enough i am trying the same 2mrw with some recordings while i am at work.
the dvr setting keeps throwing it off so am just trying it just enabled an see where i go… would love to know how you get on with ur attempt…

[sa2000]

@nickewi

I still had issues. Recording failures for “Blue Bloods” and “Dateline NBC”. See Logs. The shows were on at 9 PM CST. Not sure when failures occurred.

@nickewi

Recordings are still failing at around 50% of the time. I have 2 HDHomerun tuners, the Quattro and the Extend. Each have their own antenna.

There are no other programs accessing the tuners other than PLEX.

I just recorded several shows. the first block were fine and the last two ended a few minutes before the shows end time. Both saying “Recording failed. Please check your tuner or antenna.”

I am using Windows 10, Version 1.14.1.5488. My two HDHomeruns were exclusive with PLEX

@nickewi

I changed to beta Version 1.15.0.550 and I am still getting failures. See attached logs for DVR of "Happy Together "

Thanks for all the logs. Your issue is the one giving the following errors and seen from a number of windows users - see Recording failed. Please check your tuner or antenna - #68 by sa2000

Jan 07, 2019 10:56:01.203 [15216] ERROR - [Transcoder] [stream_segment,ssegment @ 03ea6e80] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/d2e76fff-d44a-4955-8bfd-8593dabffca0/002cb25a-4671-479e-b793-e898010eb3b3/seglist'
Jan 07, 2019 10:56:01.203 [5836] ERROR - [Transcoder] [stream_segment,ssegment @ 04b8a7c0] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/99dc0851-9785-4800-adbd-c7787665265e/e1d279a8-2bb1-4d2b-9d06-2a404a4fb77c/seglist'
Jan 07, 2019 10:56:01.211 [20040] ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
Jan 07, 2019 10:56:01.211 [16284] ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
Jan 07, 2019 10:56:01.219 [3168] DEBUG - Jobs: 'D:\Program Files (x86)\PlexTranscoder.exe' exit code for process 18828 is 1 (failure)
Jan 07, 2019 10:56:01.227 [12408] DEBUG - Jobs: 'D:\Program Files (x86)\PlexTranscoder.exe' exit code for process 17312 is 1 (failure)

and

Jan 07, 2019 19:42:45.587 [7672] ERROR - [Transcoder] [stream_segment,ssegment @ 03c61740] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/47b23b36-6aa5-4c1e-a160-8e94d60d1866/7a22fb3e-352c-468c-b536-37f11f0685ba/seglist?X-Plex-Http-Pipeline=infinite'
Jan 07, 2019 19:42:45.595 [5920] ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
Jan 07, 2019 19:42:45.606 [15028] DEBUG - Jobs: 'D:\Program Files (x86)\Plex Transcoder.exe' exit code for process 2480 is 1 (failure)

As mentioned earlier, last time we had these errors was after a windows update which microsoft rectified by a further update 6 days later in July 2018. It is possible similar issue again. This has been passed to our develoopment to get a better understanding of the error and to see if it is possible to avoid

[sa2000]

@Hserver1

Log files: Plex Media Server Logs_2019-01-08_23-01-28.zip (3.6 MB)
Thanks for the help this is frustrating at least I know of a workaround.

Update I attempted to record two things at once while watching something to see if it failed a third time just to try and figure out why and it worked fine. Tried doing it again and once again it worked so those two times of failed recordings while playing back a file could have been a fluke.

Update 2 tried enabling commercial removal again and testing with two recordings and it seemed to work fine so I’ll be trying it on my regularly recorded shows tomorrow hopefully it goes smoothly. I’ll be monitoring it closely to see if I have to intervene and start it recording again.

I am seeing a different issue in these logs. The original problem was that we appeared to be using one tuner at a time where the count of available tuners for the HDHR5-2US ended up as 1 instead of 2. Whereas in these logs we do show available tuners reaching 2.

The problem I am seeing in the new logs is the HDHR5-2US rejecting requests to tune a channel with a 500+ error code. Was the tuner in use by another application ?

These were the times of the fails

Jan 08, 2019 21:05:59.643 [0x7f33f1bfe700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.1: Server returned 5XX Server Error reply

Jan 08, 2019 22:00:00.792 [0x7f33eafff700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v8.1: Server returned 5XX Server Error reply

Jan 08, 2019 23:00:06.160 [0x7f33e13f5700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.1: Server returned 5XX Server Error reply

Jan 08, 2019 23:00:11.977 [0x7f33e3bfa700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.1: Server returned 5XX Server Error reply

Jan 08, 2019 23:00:44.060 [0x7f33e63ff700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.1: Server returned 5XX Server Error reply

[sa2000]

Would like to go back to the original problem -

The problem showing in the logs from the 4th January was that the HDHR5-2US DVR was showing as only having one tuner available. That was the state we were at the beginning of the log files and with an incorrect count to start with, we were maintaining an incorrect count of tuners.

So we need to actually capture logs that cover the time from launch of PMS and doing first recording or livetv and then into the period when it goes wrong and the available tuners get set to 1 instead of 2.

Will probably need to increase the number of log files ot a high number eg 40
See LogNumFiles preference - https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/

I need some logs from 1.14.1.5488 when two simultaneous recordings on different channels fail one of the two recordings (when the tuner is not used by any other application)

See this note about DVRs

Note : When connecting a tuner device to your Plex Media Server, the server expects that it will have exclusive access to the tuner. That means that if you use other programs or devices to access the tuner, you may experience unexpected behavior such as tuning problems or failed recordings.

https://support.plex.tv/articles/225877427-supported-dvr-tuners-and-antennas/

[sa2000]

@d23wilson

first time i got 2 recordings at same time completed successfully, on latest plex version.

i stopped the library scans (“automatically” and “periodically”).

not that i know what i am doing, but i did an export of logs and found that the recordings last failed at same time as library activity…so thought i would stop that activity in settings, and set 2 recordings for the same period (last night), and for the first time i have success completions for BOTH.

maybe try this and see if that is the issue with everyone else?

could you get me logs that would cover period from launch of Plex Media Server up to the time when one of two simultanuous recordings fail - you will need to increase the number of log files
See LogNumFiles preference - https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/

We get the number of tuners from http://ip-of-dvr/discover.json

[Hserver1]

To answer the first question about the 500 error no there was no one using it at the time except for plex. As for the logs I increased them to 40 in the preferences file. I will try later tonight or tomorrow to turn back on file scanning so I can recreate the issue. I am attaching the log from the tuner so you can see plex has had complete control of the tuner. The only time those logs show a different system accessing it was right when it was first setup I was testing it but since then nothing else but plex has used it. HDHomeRunLog.txt (23.7 KB)

[Hserver1]

Logs from a failed recording with two different channels Plex Media Server Logs_2019-01-09_22-38-06.zip (3.4 MB)

[jsneron]

The same error occurred again (see attached logs) and it is not obvious to me that the tuner, the antenna or its connection is the problem. I was running latest version ( 1.14.1.5488) of PMS on my Win10 PC.
Plex Media Server Logs_2019-01-12_13-17-19.zip (2.9 MB)
Plex Media Server Logs_2019-01-12_14-25-03.zip (2.7 MB)

[nickewi]

TPLEX says it is something with the Windows 10 Operating System update from some time in October November (If you are on Windows 10 that is).

I am not sure about that. I switched back to Version 1.13.8.5395 and I no longer het this error, but my HDHomerun Extend gets many of these “There was a transcoder error”. I disconnected my Extend and used only my HDHomerun Quatro and it is only getting occasional “There was a transcoder error”.

My point is that I am not getting “Recording failed. Please check your tuner or antenna”

So for me do I go back to 1.14.1.5488 and get most recordings fail due to “Recording failed. Please check your tuner or antenna” or do I stay back on 1.13.8.5395 and get occasional “There was a transcoder error”.

I am most likely staying on older version until they fix the issues on the newer version

[ben-page]

@nickewi

I switched back to Version 1.13.8.5395 and I no longer het this error, but my HDHomerun Extend gets many of these “There was a transcoder error”.

Yes I tried the same thing. I suspect that the two error messages are actually the same, they just changed the error text. When I reverted, I still got just as many failed recordings, they just failed with a different error message. Logs looked like the same error.

@nickewi

TPLEX says it is something with the Windows 10 Operating System update from some time in October November (If you are on Windows 10 that is).

How do you know this? Is it in another forum?

[nickewi]

PLEX employee has stated that in this forum I believe, plus in message.

https://forums.plex.tv/t/recording-failed-please-check-your-tuner-or-antenna/337072/149?u=nickewi

[ben-page]

@nickewi

PLEX employee has stated that in this forum I believe, plus in message.

Oh right - nah I think that was in reference to an update in July. There were subsequent updates that fixed the issue caused by the original update.

[Tberg74]

I’m having the same issues with PMS (latest version) running on CENTOS 7 VM. Live TV and recording will periodically not work and I have to restart the VM to fix it. Probably once a day I’ll have to reboot it.

[nickewi]

That was from July, but he was PLEX is thinking there is another issue with some updates.

[sa2000]

@Hserver1

To answer the first question about the 500 error no there was no one using it at the time except for plex. As for the logs I increased them to 40 in the preferences file. I will try later tonight or tomorrow to turn back on file scanning so I can recreate the issue. I am attaching the log from the tuner so you can see plex has had complete control of the tuner. The only time those logs show a different system accessing it was right when it was first setup I was testing it but since then nothing else but plex has used it.

@Hserver1

Logs from a failed recording with two different channels

Last time I looked into error 50x from HD Homerun was back in 2017 and the developer guide from the HD Homerun gave details of when such response codes are retuned. I will paste here the info I had back then

HD Homerun HTTP Errors

• If the virtual channel number is not known the tuner will return “404 Not Found”.
• If the request cannot be completed at this time (for example all tuners are in use) the tuner will return “503 Service Unavailable”.
• If the program cannot be not found in the stream within 5 seconds or the program cannot be authorized within 5 seconds the tuner will return “503 Service Unavailable”.
• If the program requires content-protection not requested by the client the tuner will return “503 Service Unavailable” after 5 seconds. This error code may change in the future to return a more relevant error code

Now the logs do show that the 5xx responses which were probably the 503 code were being returned 5 seconds after the tune request. This fits in with their spec as you can see above

Jan 09, 2019 08:00:00.790 [0x7f33e33f9700] DEBUG - DVR:Segmenter: Creating a new recorder for http://192.168.1.207:5004/auto/v12.2.
Jan 09, 2019 22:30:05.814 [0x7f33e1bf6700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.2: Server returned 5XX Server Error reply

Jan 09, 2019 22:32:05.651 [0x7f33e2bf8700] DEBUG - DVR:Segmenter: Creating a new recorder for http://192.168.1.207:5004/auto/v12.2.
Jan 09, 2019 22:32:10.701 [0x7f33eafff700] ERROR - [Transcoder] http://192.168.1.207:5004/auto/v12.2: Server returned 5XX Server Error reply````

I would suggest you raise this with Silicondust

In this case both were channel 12.2

[sa2000]

@jsneron

The same error occurred again (see attached logs) and it is not obvious to me that the tuner, the antenna or its connection is the problem. I was running latest version ( 1.14.1.5488) of PMS on my Win10 PC.

Appears you have run out of space in the transcoder temp directory area

Jan 12, 2019 12:31:19.204 [20136] WARN - Low disk space: 0B source file, 111.01GB capacity, 0B available on "C:\Users\JS\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-4d21843b-102a-45a7-aca9-3e49a5a71519"

This can be relocated
see advanced settings
https://support.plex.tv/articles/200250347-transcoder/

[sa2000]

@nickewi

TPLEX says it is something with the Windows 10 Operating System update from some time in October November (If you are on Windows 10 that is).

The only error that was stated that it could be a windows update issue is the one appearing in logs as
ERROR - [Transcoder] [stream_segment,ssegment @ 03ea6e80] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/xxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxx/seglist'
with
ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error

As mentioned this happened back in July 2018 and Microsoft rectified the issue 6 days later with an update on the 16th July 2018. The problem went away - but recent;y it started again and i said that may be Microsoft released a windows update causing this.

We do have diagnostics with our development team to look into the issue from Plex end and understand why it is arising

[sa2000]

@Chalky1982

Thanks for the response i have sort of done what you asked as i noticed that channel 74 was a jewellery making channel so decided to disable the channel completely from with in plex. so only did channel 76 below is the zip for it which contains two ts files an a couple of pics as when i started the 1st curl i noticed that the guide was updating, the 2nd is with the server doing nothing which the pics included will show also.

I am able to record two programs at once now with the server not updating the library’s at all except for the recordings but when trying to record with all four tuners it fails on two of them though. have included most recent logs too just in case ya need or want to view.

If you need anything else let me know and thanks for the help so f

Thanks for the .ts capture files. Having them checked by the development team. But they are invalid files and do not play when i tried with different players.

[Chalky1982]

Thanks for response. Yeah I have the same when trying to play… Why is it showing a channel if it has no vid but has nearly 100% receiver rate… Will have another play with it in next couple of days, as been trying to sort advert/commercial part as they seem a bit too aggressive so keep playing seeing what option best for recordings, an then editing out commercials manually…