New Release! starting a thread for my test of it, anyone else with my config to say if they see this too.
Server Version#:1.15.1.707
Player Version#:roku-preview ver
I’ve noticed with this new beta, and the immediate previous one that was also 1.15 that my Hauppauge QuadHD tuning to certain channels has glitches, it looks like loss of signal type artifacts, significant and ugly enough to cringe. I uninstalled this and went back to 1.14.1.5488 and the problem went away. Happened more often with certain channels, with SNR of 28-32 which is pretty much perfect. CPU i5 quad core usage around 30-40%, pretty much the same as before so I don’t think it’s overloaded with the newer PMS version to cause it. Seems more like the interaction of PMS with the Hauppauge card changed and its for the worse. Also kind of strange that it is only with some channels more than others. I’m in the Milwaukee market. So I reverted again like with the other recent version back to the 1.14 build and have zero screen artifact issues.
Obviously 1.15 is beta, but I want to report this so it is known so it doesn’t go to full release without the knowledge out there.
upgrade finished around 12:27, started playing ABC 12.1 (entertainment tonight) right away at 12:27
stopped playing around 12:29, had problems half a dozen times, recorded with iphone.
downloaded logs(removed my logs since they were retrieved)
still image from video i recorded where motion had artifact, have none of this on 1.14 ever, every 10-20 seconds most of the time on 1.15 on this channel.
I can confirm that I experienced the same problem with the beta version 1.15.707. I’m running Plex Media Server on a i5-8500 and using a Hauppauge WinTV-quadHD tuner card. The motion artifacts appear only with HD channels, and they persist when recording to DVR or watching the channel “live”. Most of the HD channels I receive have an SNR of 29-31.
When I uninstalled the beta version and reinstalled 1.14.1.5488, the pixelation/motion artifacts disappeared.
thanks for the logs from 1.15.1.707 and 1.14.1.5488
Looked at the logs - we are logging many more ffmpeg errors in 1.15.1.707 than what is in 1.14.1.5488. I discussed this with the development team and to progress they need some specific diagnostics - capturing a sample from the channel stream and also getting a zip of all the transcode segments created during watching livetv on the channel.
I will try and give sufficient detail of what needs to be done to simplify the task.
First I suggest upgrading to 1.15.1.710 which has a new version of the transcoder.
Second is to confirm that the issue remains as before and if it is still there, then to follow the steps below to capture the specific diagnostics needed
running Plex Media Server with debug logging as before
Whilst watching livetv on channel 12.1, to establish at what times relative to the start or actual times when the pixelation arises
After a few of these pixelations, and before stopping watching livetv on this channel, copy out the transcoder sessions segments to an area outside that sessions directory. So copy D:\Plexdata\Transcode\Transcode\Sessions\ to another directory and zipping the copy. This should have 2 transcode session directories - one for the capture from the channel and one for the livetv streaming to the roku
stop the livetv session and make sure it no longer shows in the Now Playing Plex web screen
The next is to capture a stream for a few minutes from the channel using curl. The number of minutes to capture depends on how frequent the pixelation occurs and how soon it appears and what time gap between instances. Suggest capturing 5 to 10 minutes assuming it was happenng alot within a 5-10 minute period
Download curl windows binary from curl - Download
Then in command line window, cd to the directory where you have the curl.exe binary and run the following
This should start capturing the stream from the channel and writing to .ts file channel-12.1_Cap-1.15.1.710.ts
Break-in on it after 5 minutes or so
Then exit Plex media Server and uninstall it and install 1.14.1.5488 and repeat the above sequence - and naming the capture file as channel-12.1_Cap-1.14.1.5488.ts
Zip all the captured files for each version
zipped Logs
zip of all the Transcoder sessions directories
curl capture ts file
and upload to dropbox or similar service and share a link and any info on when the pixelations occured
I am sorry that it is quite involved but hopefully easy to follow the steps
Let me have some logs for livetv for a specific channel that has this issue and i will provide the steps to get similar diagnostics to what I requested from @jmfolcik
I do not believe it is a general issue with HD channels. I have tried to reproduce the problem with a Hauppauge tuner and I did not get any pixelation.
Guys, I have the same issue, 1.15 is completely unusable, it glitches every 2 seconds as others of said, but I also get glitches with 1.14.1.5488, they just aren’t as frequent, it might be every 5 minutes or so, and the glitches exist in the actual recording, because I still see them when watching the .ts file in VLC.
My setup is;
Core i5 3570
Nvidia GTX750
Hauppage HVR-2255
I see the glitches on both HD and SD channels.
SA2000 I collected all this and followed your instructions to the letter, I will try and PM you the onedrive url once it is all uploaded. The latest 1.15 still has the problem. I didn’t need to test very long with it, multiple in the first couple seconds and another few shortly after. During Jimmy Kimmel Live. My notes on when:
all the time right away, like 3 or 4 in the first couple seconds,
then smooth for a bit (seconds) then saw one when jimmy was talking with the twitter screenshot in front of him
I previewed the .ts file from curl and it looks like its interlaced video, but I didn’t notice the problem in the curl copy from 1.15.1.710 I did the entire process twice.
I just want to add on that moving back to 1.14.1.5488 helped me as well. This has been a problem for me for about a year: recorded Ota HD videos (SD vids are fine) freeze every few minutes. At first I thought it was a signal problem, because I had moved to a new house when the problem started happening. But I recently checked the signal on my tuner and it was over 80%. I saw this thread and reverted back To 1.14.1.5488 and the freezing is gone for the most part. Wish Inhad tried this a year ago.
