Whatever issue was going on…has stopped. Recordings are occurring again. I’m considering this closed.
Regarding the failures that are associated with the following Transcoder Errors Log entries
ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
We have now discovered that these specific transcoder failures may arise due to Malwarebytes Premium blocking some localhost Plex Transcoder requests.
A Support Article has now been published for this problem
The specific errors this relates to is this error together with other errors
ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
coupled by
Examples
ERROR - [Transcoder] [stream_segment,ssegment @ xxxxxxx] Failed to open segment list 'http://127.0.0.1:32400/video/:/transcode/session/xxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxx/seglist
ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
ERROR - [Transcoder] Error writing trailer of media-%05d.ts: Invalid argument
or
ERROR - [Transcoder] [dash @ 028ef3c0] Unable to open http://127.0.0.1:32400/video/:/transcode/session/xxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxx/manifest for writing
ERROR - [Transcoder] av_interleaved_write_frame(): Unknown error
The support article is
Windows: Transcoder failures during playback, live TV, or DVR recording
That Malwarebytes would impede Plex is interesting. Other external applications could be accidentally doing the same thing.
Over the last month my Plex recording issues have been…random. Recordings would mostly work, but some would fail. Then all my recordings would work for several days, then some would fail again.
Not sure how to track that down, and Plex staff can’t be used to track down issues that may affect Plex but are not due to Plex.
Some “Plex Health” set of indicators may help: a dashboard quickly showing whether or not Plex can reach out and communicate with servers that it needs to; identifying issues like MalwareBytes or potentially issues like my hardware firewall may be blocking access to certain Plex-related servers because it doesn’t know what they are, it just sees a lot of questionable communication between them.
My recording issues being “random”, they do seem to be on one channel. I found this error in Plex:
“DVR:NewSchedule: We require the airing to be on channel 655 and it was on 1110, skipping”
1110 is the same station as 655.
It may be the same station but it is a different channel.
I understand this would arise if you selected “Limit the receording to channel 655”. When the channel restriction is specified, Plex Media Server does not look for the station on other channels.
Still getting the error (repeatedly). Plex Version 1.15.6.1079
Logs attached. (Turned on logging. Exited Plex Server. Restarted Plex Server and error occurred so it should be a small log you would look through).
Error around 6:05pm
Let me know if you need anything else.
Plex Media Server Logs_2019-05-21_18-09-21.zip (4.8 MB)
I am getting this error as well. It has been happening for a couple months now and is getting frustrating. I am using an HDHomeRun Cable tuner.
Log output
May 21, 2019 17:58:26.316 [4196] DEBUG - TranscodeSession: timed out waiting to find duration for live session
May 21, 2019 17:58:26.316 [4196] ERROR - Failed to start session.
May 21, 2019 17:58:26.316 [4196] DEBUG - Streaming Resource: Terminated session 0x4264520:3b26aed0-1f39-44cc-8662-aed38b771b1b with reason Recording failed. Please check your tuner or antenna.
May 21, 2019 17:58:26.316 [4196] ERROR - DVR:Recorder: Unable to create transcode session or session failed to start.
May 21, 2019 17:58:26.316 [2008] DEBUG - Killing job.
May 21, 2019 17:58:26.332 [2008] DEBUG - Job was already killed, not killing again.
May 21, 2019 17:58:26.332 [2008] DEBUG - Stopping transcode session 3b26aed0-1f39-44cc-8662-aed38b771b1b
May 21, 2019 17:58:26.332 [4196] DEBUG - Job was already killed, not killing again.
May 21, 2019 17:58:26.332 [1992] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\Plex Transcoder.exe' exit code for process 1616 is -1059143458 (intentional termination)
May 21, 2019 17:58:26.332 [4196] ERROR - DVR:Recorder: Error 16 (Recording failed. Please check your tuner or antenna.) starting the record, shutting things down.
May 21, 2019 17:58:26.332 [4196] DEBUG - MediaRecorderVirtual: setting stop time to 2019-05-21 17:58:26
May 21, 2019 17:58:26.332 [3440] DEBUG - Cleaning directory for session 3b26aed0-1f39-44cc-8662-aed38b771b1b (E:\PLEXCACHE\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-3b26aed0-1f39-44cc-8662-aed38b771b1b)
May 21, 2019 17:58:26.332 [4196] DEBUG - DVR:Recorder: Asked to stop recording 'Show - E101 - Episode 101' on channel 655.
May 21, 2019 17:58:26.332 [4196] DEBUG - DVR:Grabber: Freed a tuner on device://tv.plex.grabbers.hdhomerun/13277460 (now 3 available)
May 21, 2019 17:58:26.332 [4196] ERROR - DVR:Recorder: Error 16 (Recording failed. Please check your tuner or antenna.) starting the record, shutting things down.
May 21, 2019 17:58:26.332 [4196] DEBUG - MediaRecorderVirtual: setting stop time to 2019-05-21 17:58:26
May 21, 2019 17:58:26.332 [4196] DEBUG - DVR:Grabber: Operation for 'Show - E101 - Episode 101' on channel 655 completed with status error (Recording failed. Please check your tuner or antenna.)
May 21, 2019 17:58:26.332 [4196] DEBUG - Activity: Ended activity 785b1ce2-0cfc-46fb-96e9-0d2ec56dbbb6.
May 21, 2019 17:58:26.332 [4196] ERROR - DVR:Grabber: Starting media grab failed.
What were you recording? What station? What channel?
Thanks for the logs. It shows a 25 second timeout on starting to tune channel 655 for a recording at 18:08.
Appears to be the problem I started looking into here
A fix has been produced and initial testing has been positive for some channels that were timing out before. We are waiting for further diagnostics from one of the users
1 Like
I was going to mention that your server is crashing in the intel hardware transcoding dll mfx_mft_h264ve_32.dll
In the past this arose if the server is run as scheduled task or as a service or started in an RDP session. Lately have been seeing this crash when that is not the case - may be an update to intel driver issue
Appears to be similar to the timeout I just mentioned in my post Recording failed. Please check your tuner or antenna - #256 by sa2000
Thank you, sa2000.
Regarding timeouts on tuning I would like to extend the trial of development build 1.15.8.1156-729c84fdf to you as well to confirm the fix
But feel free to try the new beta 1.15.8.1163 first and if it makes a difference, do let me know - preferably with logs from the current version in use - failing to tune and the 1.15.8.1163 succeeding. I do not expect the beta to make a difference - but since @workit247 says it did here, i suggest you try it as well
If problem remains, let me know if you wish to try the development build and I will send you the windows binary for 1.15.8.1156-729c84fdf to try
1 Like
Could I possibly get this build for an unraid docker? I am still getting the same error where it says could not tune channel. and my logs show this:
VERBOSE - WebSocket: processed 1 frame(s)
May 30, 2019 08:21:08.590 [0x151caebc4700] DEBUG - HTTP requesting GET http://192.168.1.9:80/discover.json
May 30, 2019 08:21:08.590 [0x151caebc4700] DEBUG - HTTP 200 response from GET http://192.168.1.9:80/discover.json
May 30, 2019 08:21:08.591 [0x151caebc4700] DEBUG - HTTP requesting GET http://192.168.1.9:80/lineup_status.json
May 30, 2019 08:21:08.591 [0x151caebc4700] DEBUG - HTTP 200 response from GET http://192.168.1.9:80/lineup_status.json
May 30, 2019 08:21:08.604 [0x151caebc4700] DEBUG - Activity: updated activity ccb432e7-d7c9-4ff6-bd07-cfbb1444c408 - completed 8% - Recording
May 30, 2019 08:21:09.502 [0x151cae7c2700] DEBUG - TranscodeSession: timed out waiting to find duration for live session
May 30, 2019 08:21:09.502 [0x151cae7c2700] ERROR - Failed to start session.
May 30, 2019 08:21:09.502 [0x151cae7c2700] DEBUG - Streaming Resource: Terminated session 0x151c84628ca0:1960c744-56ef-46e4-b7a8-c4d78dfbdb31 with reason Recording failed. Please check your tuner or antenna.
May 30, 2019 08:21:09.502 [0x151cae7c2700] ERROR - DVR:Recorder: Unable to create transcode session or session failed to start.
May 30, 2019 08:21:09.502 [0x151cae7c2700] DEBUG - Killing job.
May 30, 2019 08:21:09.502 [0x151cae7c2700] DEBUG - Signalling job ID 1079 with 9
May 30, 2019 08:21:09.502 [0x151cae7c2700] ERROR - DVR:Recorder: Error 16 (Recording failed. Please check your tuner or antenna.) starting the record, shutting things down.
May 30, 2019 08:21:09.502 [0x151cae7c2700] DEBUG - DVR:Grabber: Cleaning up rolling grab for channel 744.
It’s like plex is either taking forever to get the stream going, or there is a timeout that hits before the stream can start properly.
Upgraded to 1.15.8.1163 last night.
Odd…morning show didn’t record on problem channel, but afternoon/evening shows did record on problem channel. Will need more time monitoring and will let you know.
If tomorrow morning fails I will upload logs.
I am trying to see how to get a docker internal development build out.
On 1.15.8.1163, morning show on problem channel recorded.
Just worked out how to do that for docker. Sent you a private message with info on getting 1.15.8.1156-729c84fdf
Today, all shows on the problem channel recorded properly.
Now morning show on problem channel did not record. I thought the problem was solved so I turned off logging over the weekend. I am turning it back on again…
