just trying to get a baseline here i.e. tuner hooked up and running, has signal, etc. my initial setup had a really weak signal and wasn’t tuning (HDHomeRun Connect Duo).
Im pretty sure this is all about timeouts because that was one of the changes in the version I mention in the title.
Other observations is that it does take a few seconds to tune each time. About 16sec for an SD channel and nearly 20sec for HD, but it always works.
How long does it take HD Homerun?
Agree on the timeout
upgraded early to the latest version, after approx 16 seconds it times out an gives a please check antennae error
I can tune to channel manually after this error and everything is perfect, Plex is taking too long to lock the signal and erroring
ok. I just setup plex a couple weeks ago and then updated to the release this week already too, so I’ve always been on a 1.14 build. when mine works, it’s roughly that I haven’t timed it. My biggest issue is mine doesn’t tune in on AppleTV, it seems like it finally times out after 2 mins or so. it seems to work the best when I’m remote and pull it up, it seems to stream ok, but don’t really have any controls other than Pause for a few mins (FF & Rewind do not really work).
is this set in an XML file by chance?
Just updated my Plex (Windows 10 with WinTV DualHD) from 1.13.7.5369 to 1.14.0.5470 and ran into the same issue - could no longer watch live TV on any Plex clients or the web interface. Rolling back has fixed it for now. If I can help with anything to help fix this bug please message me, but I see others have already given logs so will otherwise wait for the fix in upcoming version.
Thank you. Very good logs.
There were 5 tune attempts for channels 1, 2, 109, 202 and 101
For the first 3, the tuner took over 10 seconds to send any packet when the channel was being tuned,. Although a timeout was increased from 5 seconds to 15, there was still another timeout of 10 seconds that seems to have triggered here. (Need to establish why this did not show up when the 15 second timeout fix was tested by users who had the timeout issues)
I will refer this now to the development team to look into increasing this second timeout.
I mentioned 5 tunes:
The 4th tune for channel 202 completed within 3 seconds and was successful.
The 5th tune for channel 101 - although we did receive a packet within good time (5 seconds) - the packets were corrupt - leading to transcoder logging errors as it was processing them
20194 Nov 30, 2018 11:09:40.795 [14244] ERROR - [Transcoder] [h264 @ 00c62f40] non-existing PPS 0 referenced
20195 Nov 30, 2018 11:09:40.798 [11552] ERROR - [Transcoder] [h264 @ 00c62f40] decode_slice_header error
20196 Nov 30, 2018 11:09:40.800 [5084] ERROR - [Transcoder] [h264 @ 00c62f40] no frame!
20197 Nov 30, 2018 11:09:40.906 [14688] ERROR - [Transcoder] [h264 @ 00c62f40] mmco: unref short failure
20198 Nov 30, 2018 11:09:41.154 [15160] ERROR - [Transcoder] [h264 @ 00c62f40] mmco: unref short failure
Normally issues like this are down to signal / quality issues. Perhaps you could run some WinTV tools for testing signal strength / quality for the various channels
Can you check my log please to see if its the same issue
I tried to record most haunted at 16:00 (which i think timed out) and the recording aborted
A couple of minutes after this i manually tuned to the channel in the web app and the picture was perfect
Thanks
log removed
There is more than just the Plex Media Server.log for DVR related investigations
I need zipped logs please so I can see how the tuner was dealing with the tune request
See
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Thanks for info
I have reverted back to previous a previous version as i need my recordings to work, so unable to provide more lgs
It’s about time Plex did some beta testing on these releases before issuing them
Good job i am only on monthly Plex Pass, as i am about to abondon this, it’s just problems after problems, never known released software have such show stopping bugs before
Total disgrace how this is a paid feature
Can we just get the links to download the version that works till Plex figures out the problem and fixes it? It seems I need 1.13.7.5369 or earlier (I’m running QNAP 32bit “_x86.qpkg”).
It’s taking Plex months to fix this, so it seems reasonable to request the link to be downgraded, being paid users and all…
Yeah, paid features should work, right? Maybe we’re asking too much? They don’t even provide links to previous versions, so I can’t even downgrade to get it working.
I totally agree! Up till they added Tidal (Overpriced music library) Plex was working great across all my devices, but since they added it, on the latest version of the server, I along with my remote users are having continued issues with live TV even with PMP on Linux now showing Playback Error!
@sa2000 knows what I run, and he’s had my logs from November but still had no reply to what is causing the transcoding to drop like it does.
Things need fixing before adding new useless features to the server side. I run 3 WinTV DuoHD tuners, on Ubuntu 18.04LTS and the PC is an i5-3330k with 8Gb RAM and Nvidia GTX750ti GPU which handles transcoding of multiple movies quite nicely, I’m not having drops on my movies or TV shows that are stored on my hard drives, 15Tb and counting, it’s just the live TV side that falls.
More testing needs to be done before issuing out updates to the server, and I was thinking of purchasing the 12 months subscription to Plex, but at this rate, not a chance!
To me, it seems that Plex Devs are leaving the “Gurus” to take the flack that they’re causing and this isn’t on! Stop hiding Devs and come and look at the issues that have mounted by you not fixing them before adding useless features like Web Shows and Online Music streaming…
Dave
If you need links to download 1.13.8.5395 or 1.13.7.5369 for Ubuntu 64 bit here you go:
If you need the 32-bit version, change the extension from amd64.deb to i386.deb
This was an unexpected regression. The timeout issue was fixed in 1.13.9.5456 after extensive user participation in testing with timeout increased from 5 seconds to 15 seconds. Unfortunately there was a release in the pipeline that went out as 1.14.0.5465 that introduced a 10 second timeout. This was not spotted until logs were examined here DVR & Live TV Completely broken in 1.13.8.5395 with WinTV dualHD and probably others - #27 by sa2000
As long as you and Plex are aware that 1.14.0.xxxx is totally non-functional for live TV playback on an Ethernet device. Also, 1.13.7.xxxx and 1.13.8.xxxx work, but not 100%. A few channels (about 25%) refuse to play, even after rebooting Plex server.
I think there’s more to it than just a timeout. Why is it taking 15 seconds? When using the HDHomeRun app, channel changes take from 3.5 to 4.4 seconds. Why do certain channels refuse to play?
The timeout issues I mentioned have been seen to mainly arise on USB tuners - it may be a different issue that is affecting the tuning in your case
Are there any logs of your tune failures ?
@sa2000 Ah, so you say it’s fixed yet users like myself and @teckel are still having these issues where channels don’t work, and the transcoder just falls flat on it’s face and Dev’s just keep adding features that seem easier to add then to fix the important issues first?
I agree that it’s definitely far more than just timeout that is the issue, especially when VLC in Linux loads up the channels in a few seconds and not 15! Sloppy developing is one of the answers I think??? but hey we’re just the users that spot these issues and when we let Plex Guru’s know we get fobbed off with something totally different.
Will there be any update to fix anymore TV/DVR issues? or are we just going to have to either plod on with a broken system where TV is concerned or are we finally going to get a more useful side of Plex fixed?
I’ve attached the logs of one such issue I’m currently having on both internal network and external where after X amount of time I get a playback error or my users do…
.Plex Media Server Logs_2018-12-02_10-09-46.zip (4.0 MB)
Plex Media Server Logs_2018-12-02_18-32-28.zip (4.5 MB)
Hopefully these logs will help???
Dave
Not aware of any fobbing
The main issues that have been reported as affecting tuning:
- this timeout regression that came in 1.14.0.5465
- reports of tuners that are not operational (eg no antenna) affecting tuning on live tuners
- reports of deleted tuners interfering with tuning on live tuners
Each case will be investigated through logs and information on what the problem is and at what time it arose
I am aware that logs have been provided before but so far nothing conclusive and would need more examples of issues
Well, save me going through them… I’ve added my logs from today for you to check through… and none of my users or I are using a Browser…
Dave
