I see what you mean. I watched the Cache/Transcode/Sessions folder and when a recording started it created two folders there. One stayed empty but the other filled up with small .ts files created at a rate of about one file per second. 3,552 files for the one hour recording. When the recording finished and PMS moved the recording from the .grab folder it also deleted those two folders it created. Not sure why I have two transcode processes per recording running, but other than thrashing the disk by creating all those small files and eating up an extra 4% cpu (2% per transcode process) per recording I donāt see it causing any problems.
I check the forums every now and then to see if these issues have been resolved. And while I get the sense that fewer people are experiencing them, I am still seeing people post similar problems. How about the folks involved in this thread? Has the 1.8.x release helped? Iām still sitting at 1.6 but hopeful Iāll be able to updated eventually.
For me the issues are unchanged with 1.8. I use a HDHR Expand with latest beta firmware. My issues are: On specific channels in Germany no recording is possible (transcoded error apparently), while other channels show no issues. My PMS runs on a Synology DS415+ with DSM 6.1.3 in 64bit. When a recoding on the problematic channel is running, all seems to be fine at first, but the recording cannot be saved. No difference here between 1.7 and 1.8. When watching live issues seem to be specific to the content broadcasted. Some programs play fine, others wonāt play.
I get the same problems with PMS 1.8 using an HDHR Connect on the Nvidia Shield in the UK.
I suspect the problem is that 1.8 is highly intolerant of any transmission gaps, corruptions or other hiccups. PMS 1.6 had no problems at all - but then it was just capturing the stream and dumping it as a .ts file.
Iāve reverted to 1.6 until I have confidence that theyāve resolved these problems.
@Agent_Cooper,
I tried every release they have made available and 1.8 still doesnāt work properly for me on Synology nas that has been working fine up to release 1.6.1 after that recordings seem to take hours beyond their recording time and either donāt complete properly or never show up in your target directory. I have had several tv shows that run for about 1 of air time continue to increase in size for several hours but never actually complete, in Version 1.6.1 they show up about a minute after the recording ends and everything is perfect, I assume the later releases do this āchunkedā recording that others have mentioned where there lots of tiny chunks of the recording that gets merged back into single recording, but for me they never seem to finish building the master recording and continue to cause problems . I have had to downgrade back to 1.6.1 for consistent recordings. Not sure what they changed in the recording engine but as of 1.8.x it still isnāt normal.
Iām on beta firmware for hdhomerun connect and i am no longer having these issues in 1.8ā¦donāt know what solved the issueā¦but 1.8 definitely has been better with keeping the file in .ts instead of remuxing in mkv. I do reencode in real time to h264 but i still donāt know what was causing the initial problem
I have the same experience as @mcrommert with HDHomeRun Prime and beta firmware. Itās running on nvidia shield and Iām in the US.
Live TV tends to tune channels faster too.
Hope it helps narrow down the issue!
@mcrommert @abarbaccia - what exact HDHR firmware version are you running?
@DavidAndAndrea said:
@mcrommert @abarbaccia - what exact HDHR firmware version are you running?
The beta2 that they currently offerā¦donāt know the rest of the string though
Same here
There is a beta3 firmware out now but I canāt seem to get it to install. It keeps saying there is some sort of network error and I donāt have a strong reason to debug or upgrade until the stable (non-beta) version comes out because this is working for now.
Things have improved dramatically using Plex 1.8.0.4109 on a Windows system. The recordings are good. The PC it is running on has pretty good specs, Xeon processor, 16GB of RAM and an SSD.
The tuners are two HDHomeRun Connects running 20170808beta2 firmware. One problemā¦the Plex server does not use the second physical HDHomeRun connect if the first one and its two tuners are busy. I have that posted as a bug.
I would certainly recommend updating to 1.8x
Question for you guys talking about the firmware for HDHomeRunPrime and other HDHomeRun boxes, if its a firmware problem would would it work fine with plex 1.6.1 with no video recording problems yet 1.7-1.8 plex dvr seems to suck monkey balls when recording? Is it because plex records differently in later release? I would think it gets the same feed from hdHomeRun units? I have updated to Beta3 on hdhomrun boxes and will test out 1.8 again on Synology Nas units and report back but last test run i had recordings ābuildā for hours past the time of the show and other recordings that were junk. Strange part is I have a QNAP with 1.8 and that recorded some test shows fine, but still take longer to show up in filesystem then 1.6 versions, looks like building ts files is still being done differently then 1.6 and lower then before. Its like its still remuxing or maybe the recordings are chunked like others have reported and the āmergeā is just extremely slow.
In anycase I will try 1.8 with beta3 HDHomerunProms again and let you all know if it makes a difference.
Resultsā¦
Recordings still taking hours to ābuildā after show has aired under 1.8, and 1.6.1 completes within minutes of airing.
Turners are still locked way after show has aired causing other recordings to fail due to tuner being locked. Regressed back to stable 1.6.1 with no issues in 1.6.1 version, Beta 3 firmware no effect on 1.8.
FYI on the SD HDHomeRunPrime Firmware versionsā¦ it doesnāt activate in the HDHomerun Setup app anymore , it shows in the browser portion of hdhomerun there is a option under āsystem Statusā Firmware upgrade that shows now, it used to do updates in the setup software
Following up here.
I have started to experience similar issues mentioned by @skraemertx above. Also here http://forums.plex.tv/discussion/283156/status-of-100-complete-recording-bug#latest
My transcode temp directory has filled up with >500gb of files likely that are āstuckā recordings. I will likely keep 1.8 for now, just stop using the DVR while it is sorted (Live TV working fine).
@abarbaccia said:
I will likely keep 1.8 for now, just stop using the DVR while it is sorted (Live TV working fine).
I have been on 1.8.1 for the past week and have experienced absolutely no 100% recording issues. I was having these issues in the 1.7.X-1.8.0 releases. BTW, I almost never use LIve TV.
@rodgerzeisler thanks for the heads up. I upgraded to 1.8.1 recently and havenāt experienced any of these issues so far. Iāll post back if that changes.
@abarbaccia ,
keep us posted, I have been testing new 1.8.1 on another nas unit but that one isnāt used that much for dvr recording and I havenāt even gone down the live tv route yetā¦ want stable recording first before i even attempt that stuff.
So far second nas is working fine its a Qnap NAS, and for whatever reason it doesnāt seem to ever show problems with recording and they show up quickly and finish, my Main NAS Synology which is active alot seems to be where I see the problems with hung recordings and ābuildsā of ts files taking hours past the end of show time, that I have to revert to stable version of 1.6.1. Others have reported similar issues on different platforms I wonder if its something to do with processors or memory issue??
What is your Config, maybe we have something similar in processor,memory or platform that could help the Plex guys find issue.
Iām having some success with 1.8.1 but a recording just failed. Any thoughts:
Aug 17, 2017 20:30:05.165 [19759] DEBUG - Request: [192.168.1.130:47100 (Subnet)] GET /:/timeline?bandwidth=6938&bufferedTime=420&containerKey=%2FplayQueues%2F78&duration=2512010&guid=com.plexapp.agents.thetvdb%3A%2F%2F247808%2F7%2F6%3Flang%3Den&key=%2Flibrary%2Fmetadata%2F2041&machineIdentifier=d8793166988cd8f6a74e18b775f871de3ebd28c5&playQueueItemID=402&ratingKey=2041&state=playing&time=1519285&token=xxxxxxxxxxxxxxxxxxxx (6 live) TLS GZIP Signed-in Token (abarbaccia)
Aug 17, 2017 20:30:05.166 [19759] DEBUG - Client [8f64587ec8a41fd3-com-plexapp-android] reporting timeline state playing, progress of 1519285/2512010ms for guid=com.plexapp.agents.thetvdb://247808/7/6?lang=en, ratingKey=2041 url=, key=/library/metadata/2041, containerKey=/playQueues/78, metadataId=2041
Aug 17, 2017 20:30:05.176 [19759] DEBUG - Play progress on 2041 'Home to Roost' - got played 1519285 ms by account 1!
Aug 17, 2017 20:30:05.195 [19759] DEBUG - [Now] User is abarbaccia (ID: 1)
Aug 17, 2017 20:30:05.196 [19759] DEBUG - [Now] Device is Android (SHIELD Android TV).
Aug 17, 2017 20:30:05.197 [19759] DEBUG - [Now] Profile is Android
Aug 17, 2017 20:30:05.197 [19759] DEBUG - [Now] Updated play state for /library/metadata/2041.
Aug 17, 2017 20:30:05.198 [19759] DEBUG - Statistics: (8f64587ec8a41fd3-com-plexapp-android) Reporting active playback in state 0 of type 4 (scrobble: 0) for account 1
Aug 17, 2017 20:30:05.204 [3094] DEBUG - Completed: [192.168.1.130:47100] 200 GET /:/timeline?bandwidth=6938&bufferedTime=420&containerKey=%2FplayQueues%2F78&duration=2512010&guid=com.plexapp.agents.thetvdb%3A%2F%2F247808%2F7%2F6%3Flang%3Den&key=%2Flibrary%2Fmetadata%2F2041&machineIdentifier=d8793166988cd8f6a74e18b775f871de3ebd28c5&playQueueItemID=402&ratingKey=2041&state=playing&time=1519285&token=xxxxxxxxxxxxxxxxxxxx (6 live) TLS GZIP 39ms 491 bytes (pipelined: 94)
Aug 17, 2017 20:30:07.166 [19759] ERROR - [Transcoder] [tcp @ 0x201d832380] Connection to tcp://192.168.1.156:5004 failed: No route to host
Aug 17, 2017 20:30:07.169 [19760] ERROR - [Transcoder] http://192.168.1.156:5004/auto/v699: No route to host
Aug 17, 2017 20:30:07.182 [3099] ERROR - JobManager: child process returned: 1 (Operation not permitted)
Aug 17, 2017 20:30:07.182 [3099] DEBUG - Jobs: '/data/user/0/com.plexapp.mediaserver.smb/Resources/Plex Transcoder' exit code for process 20328 is 1
Aug 17, 2017 20:30:07.182 [19825] DEBUG - Using default transcode duration of 120 minutes
Aug 17, 2017 20:30:07.182 [19825] DEBUG - Started session successfully: bcabfd5b-7d28-4d02-8ec9-2dd7b982493b
Aug 17, 2017 20:30:07.183 [19825] DEBUG - DVR:Recorder: It took 2.9 sec to start the session for http://192.168.1.156:5004/auto/v699
Aug 17, 2017 20:30:07.184 [19825] ERROR - Unable to find title for item of type 5
Aug 17, 2017 20:30:07.184 [19825] DEBUG - MDE: analyzing media item -1
Aug 17, 2017 20:30:07.184 [19825] ERROR - MDE: video has neither a video stream nor an audio stream
Aug 17, 2017 20:30:07.184 [19825] DEBUG - MDE: ignoring media item -1
Aug 17, 2017 20:30:07.184 [19825] ERROR - MDE: no compatible media decisions are available
Aug 17, 2017 20:30:07.184 [19825] ERROR - DVR:Recorder: Unable to compute media decision.
Aug 17, 2017 20:30:07.185 [19825] ERROR - DVR:Recorder: Error 14 (An unknown error occurred) starting the record, shutting things down.
Aug 17, 2017 20:30:07.185 [19825] DEBUG - DVR:Recorder: Asked to stop recording 'Home Alone (1990)'.
Aug 17, 2017 20:30:07.185 [19825] DEBUG - DVR:Recorder: Stopping transcode session.
Aug 17, 2017 20:30:07.185 [19825] DEBUG - Killing job.
Aug 17, 2017 20:30:07.185 [19825] DEBUG - Signalling job ID 20328 with 9
Aug 17, 2017 20:30:07.185 [19825] DEBUG - Job was already killed, not killing again.
Aug 17, 2017 20:30:07.185 [19825] DEBUG - Stopping transcode session bcabfd5b-7d28-4d02-8ec9-2dd7b982493b
Aug 17, 2017 20:30:07.185 [19825] DEBUG - DVR:Grabber: Freed a tuner (now 3 available)
Aug 17, 2017 20:30:07.186 [19825] DEBUG - DVR:Grabber: Operation for Home Alone (1990) completed with status error (An unknown error occurred)
Aug 17, 2017 20:30:07.186 [19825] DEBUG - Activity: Ended activity a3c260ca-9377-41e2-8299-f67f0cd34843.
Aug 17, 2017 20:30:07.186 [19825] ERROR - DVR:Grabber: Starting media grab failed.
Aug 17, 2017 20:30:07.255 [20327] DEBUG - DVR:Recorder: Asked to stop recording 'Home Alone (1990)'.
DISREGARD ā user error.
Just realized my HDHR power cord got knocked out!
1.8.1 seems to still be working OK for me.
Recordings are nothing but garbage. Plex HELP!!
