I doubt this may help at all, but I started a thread a short while ago about interlace issues. But in the evidence gathering I did, I found that ffmpeg/PMS can miss-identify DVR files; in that it can think they’re Progressive when they should be Interlaced This can the cause problems on how the files/streams are transmitted to your client devices.
I’m not really any the wiser, and I’d be remiss in pointing out that the “vertical lines” issue you’re having doesn’t seem to be traditional “de-interlace” issues; so the issue here (in this thread) could have nothing to do with what I posted!
Anywo, I just want to share, in-case other find it useful
I removed the solution, but I’m unsure if that’s sufficient for “re-opening” this issue.
As I previously posted, the issue has been corrected based on my current configuration. I probably won’t be much help with troubleshooting or discussing this issue moving forward, but let me know if you need me to try something.
@ChuckPa just as a side note… Do you remember the “game show” images/clips I posted in the other thread? Other thread
The smearing in the images I posted were grabbed as a “side note” when PMS was correctly transcoding i to p, but I noted that it was still smearing? I bet this is a similar thing? Which is where the idea of “doubling” the Hz/fps come in, as it could help fix/mask any interlaced artifacts showing up in the wrong frame. Especially if for some reason the order of the fields ends up being out of sync with the actual frame creation. Just a thought.
Thank you for pointing that out @thechad6, and for your patience here. This prompted me to re-read this thread. I had a question earlier about whether this was in public or not, but never heard back from anyone, so I was left to assume this was still an issue that was originally found in beta and had made its way to RTM.
I made the jump into 1.31.3 just now and can happily state that it no longer seems to occur on our server. So this appears fixed for us, too.
Onto the next fire.
(Also, thank you @ChuckPa for your assistance but I am no longer in need of any )
I just closed out the other major issue I had been facing for nearly 2 years now, and that too appears to be fixed in 1.31.x. I wanted to take the opportunity here to thank @ChuckPa and the team there for all your efforts in fixing things over there, and for putting time into improving the quality of your product. It really means a lot to those of us who have Lifetime Memberships and want to get our money’s worth.
You should be proud of the product Plex has become. Outside of these issues (which now appear addressed ), it is really really good these days.
Much appreciation and gratitude to everyone on the team there.