Hello all. I am glad I found this post as I was having the same problem with unwatchable channels. I switched to the older version and everything is good again. Being new to this whole ota TV thing I sure was getting tired of climbing up my antenna tower making adjustments to my antenna thinking it was at fault. I had also switched from an old core duo machine running a linux plex server with two old single hauppauge tuners to an i5 windows 10 server running one quadhd tuner so I am not even sure if the linux and windows versions are similar. If it helps Sa2000 I can try and send you some logs or information.
Note: 1.15.8.1163 has the same artifacting issue. Reverting to 1.14.1.5488 fixes it.
Still no news?
I am sorry I have no update for you. The problem needs to be reproduced it internally and that is what the development team are waiting for.
But it seems to be hard to be reproduced… what’s the reason? you need a listing of my material? to have some clues?
I suspect that it is to do with specific channels. I already have the information concerning the tuners - which I believe is as follows
WinTV-quad HD
WinTV-HVR-955Q
What’s do you mean about specific channels?
Audio codec and video codec?
what i mean is that using the wintv tuners does not show the problem and the suspicion is that may be it only does for specific channels
I have this tuner too
Hauppauge 723x BDA ATSC/QAM Tuner
could you isolate the issue to one specific tuner - preferably the quadHD then we can concentrate on just that. So suggest you remove the other 2 and see if problem is occurring and which channels on
Already tried and occur on all OTA channel…
i will try if i have the issue on others tuner
but i will retry on the latest release
Ok well i tested again and here the result…
Tuner with no problem on the latest version…
Hauppauge 723x BDA ATSC/QAM Tuner
Tuners having issue on the latest version
WinTV-quad HD
WinTV-HVR-955Q
Problem doesn’t seem to happen with specific channels…
maybe a setting on a specific tuner?
If you want i can give you the log with the working tuner and the tuner with the issue??
Hi @sa2000
I believe that the sample streams I uploaded above ^^^ will help the dev team. Can you confirm they have them?
Comparing the working stream vs the non-working stream (same channel, same hardware, only difference is the version of the PLEX server) should enable the dev team to see what’s wrong with the non-working stream, and perhaps help them figure out what piece of new code is causing it.
Yes they do have them, and wanted to reproduce the problem
Did we ever get a curl capture from one of your channels?
No, I don’t think we did. I don’t even know what a curl capture is. Happy to do one though, if it helps track down the issue.
will have to repeat the last set - so would be curl capture, do the record on 1.14.x and again soon after on same channel on 1.15 or 1.16
best if I send you the latest alpha release for 1.16.
The curl capture would be a curl.exe command line request you send out to the tuner. The exact syntax would be worked out from looking at a debug server log that covers time of starting a tune / recording for that channel
Ok, happy to run the curl.exe test.
I’ve attached my logs, which capture me manually recording 30 seconds or so of channel 31.1 - can you let me know which part of the logs Id copy/paste into the curl.exe to perform the test & capture (with PMS 1.14.x and then 1.16.x)
