DVR Recording - Streaming Pile of Goo!

@tsheley said:
I can confirm going to version 1.6 on my QNAP fixes the problem.

Update from my end, 1.6 yes, does seem to have correct this problem for me (sort-of…) While it does occur less, I am occasionally getting a new error (but ends the same) “Recording Aborted” now?

The brief time I spent on 1.5.7 I didn’t experience any issues so I am downgrading yet again to 1.5.7 public to see if recording become stable again.

Anyone know what file I have to edit to stop update nag for good? Every time I visit home it tells me to upgrade. It’s very annoying!!!

@cantenna said:

Anyone know what file I have to edit to stop update nag for good? Every time I visit home it tells me to upgrade. It’s very annoying!!!

I was also getting really annoyed by this message (well…not so much the message itself…it was knowing that I ‘could’ do an update, but I really couldn’t because if I did my DVR would get all messed up again). But then I clicked on the “skip this version” option and it went away (for now).

Since the 1.7.x version came out, I see quite a few forum posts that all seem to revolve around the same kinds of problems with the DVR (recordings stuck, aborted, corrupted, etc.) In my own case, dropping down to 1.6.x fixed my issues, but staying with an older versions is probably going to create new problems in the long run. For example, if IMDB changes it’s structure and therefor Plex server needs an update to be able to pull metadata, I’ll lose that ability. Same for TV guide data, music metadata, etc. They’ve got that news service that they purchased a while back…I’m sure whatever they do with that will require a server update. The longer I go without an update, the more that kind of thing is going to become an issue.

@Agent_Cooper

With regard to “in the long run” problems around updating, the solution is to update to each new version when it’s released and test it. It’s fine to roll it back if there are major show stoppers, but don’t rely on a beta feature so much that you can’t test new versions when they come out.

And for whoever is interested, I did notice one interesting thing in some of my explorations around the TS file remuxing issue. In version 1.7.5 when the DVR records it is recording the RAW .ts stream into a temporary folder using thousands of 1 second .ts files. Then it must rebuild those into the MKV or whatever the final container is used. I would imagine this keeps the entire single file from being corrupt.

However, I found one frozen recording which seemed to match up to one of these temporary folders and it was obvious that some of the files were missing. It wasn’t a few in the middle it was like the last 10 minutes or so. I would think that even if the antenna stream had a glitch and the DVR failed to write a couple minutes, it should at least pick up with the next “clean” minute. It seem weird that the entire end of the show would be missing in the recordings.

@kamererhouse

instead of me testing each new release… how about plex tests it BEFORE it releases it…

Mind-Blown

The term “beta” indicates we are beta testing it. Our job to look for these issues however i do wish they had a github like tracking where we could see progress. Frustrating to not know if issues have even been seen by devs.

@dragonmel - So you are saying you’d rather wait another couple years to use the DVR feature instead of seeing it early as a BETA feature?

I’m sure Plex does test this stuff BEFORE releasing it, but when you have thousands of variables out in the world, it’s almost impossible for them to test for everything before hand. Currently Plex releases the server for a dozen platforms and over a dozen client players running on different hardware using codecs designed for each device. To thoroughly test every feature on every platform in every environmental situation would require a couple hundred man hours every time they changed something.

Personally I like having access to the feature early. So it’s a win for Plex and a win for me.

@kamererhouse

I am pretty sure DVR left beta and is now in public release… if not mainstream pass release…

and this is another issue here in pass… the users that PAY to use the product are most often using the least stable code…

and lets not beat around the bush… most plexpass features operate flakey at best and some really not at all for enough people that there are frequent and recurring threads to that effect…

and even public only releases… plex has been known to break things… last year they released some clients on ios and tvos that could not even talk to the current PMS because they implemented security features before the server pushed and for serveral weeks were dead in the water… and more recently the trasncoder is going nuts, peoples external access is going down because internally to the software on windows servers I think its setting the port to 0 after some uptime… they didnt catch THAT before release, the release of the linux 1.7.5 I think didnt have complete librarys and failed install for lots of folks… I can go on…

plex and its quality control of lack theroff is notorious…

the only reason they have thousands of variables is that they choose to MARKET it that way… if they cant handle it… than support only the hardware that you have enough competent coders to write for…

but stop charging poeple for stuff that doest work…

IF it was ALL FREE than yeah… I have and in the past have not had a problem being a guinne pig… but I am a paying customer … as are you and unless I am SPECIFICALLY given the option to BETA something I would rather what they release as a product that they advertise has these features … they actually WORK… again… unless I download a special beta…

my 2 cents…

It’s still called “DVR (beta)” in the server settings. So…

@kamererhouse

just because plex are too lazy to properly admin the board doesnt mean its still in beta…

I can read… how about you…

https://www.plex.tv/blog/well-do-it-live/

plex announced its pass release as a full feature back on june 1st

@dragonmel - I didn’t really mention the board did I. It’s still labeled as “DVR (Beta)” inside the server settings. That means the feature is still considered beta.

@kamererhouse

quote plex…

Remember, Plex Live TV and DVR is a Plex Pass only feature, and is immediately available for Plex Pass users. You can find out more info about Plex Live TV and DVR here as well.

when you call something a feature for paying pass customers to me that is no longer a beta but a paid feature… but again this is plexes entire problem… they treat their entire paying Pass customers as one giant testing pool… and they overstate the ‘features’ and ‘capabiiites’ of plex on a reguluar basis to sell pass subscriptions…

I am done with this discussion… sorry…

I just upgraded to 1.8.0.4109. Let’s see what happens in regards to this issue.

keep us posted, anymore testers willing try it out :slight_smile:

Same issue here on 1.8.0.4109. In fact I hadn’t had the 100% hang issue before until now.

I’m on the 1.8.0.4109 update and I’ve had one program record so far without hanging.

This hang problem seem pretty weird. Last week on 1.7.5, I had about 6 shows spanning two days showing hung up and displaying like they were all still recording. Every single new show would hang. I finally decided to restart the NAS that Plex is running on and haven’t had another hang since. I upgraded to 1.8.0 this morning. We’ll see what happens after a few more days.

If anyone encounters this hang issue on 1.8.0.4109, can they please provide some logs?

1.8 seems to have fixed the issues I had with recording,

With this new version of 1.8x, everything seems to be working…that never happened with 1.7x. Thank you (so far) Plex developers!

I do have transcoding off on the HDHomerun tuners…I think I’m going to try to see what happens with it back on…

@“Dean Junk” said:
1.8 seems to have fixed the issues I had with recording,

I spoke too soon. Checked my recordings after work today and it shows 5 of them still at 100% all on one tuner. 3 Transcode processes are still running on Ubuntu. Back to 1.6.1…

I have had great success with the newer 1.8.0.4109 version on a Windows system…everything seems to be working well these past few days.