To My Brother Mark Clarkstone!,
The info you requested...
http://i.imgur.com/P5GKQai.png
Looks like very similar stats to me just different "weights", "BER", "Uncorrected"...
Also I am hardlined with CAT 7 Shielded STP from the RPi 3 to the Router and I have Kodi on a Amazon Fire Stick Gen 1, so I can only get it wirelessly. Once again IPTV Simple Client works fine, just not the HTSP Client that comes packaged with Kodi. I am on 5Ghz so I don't know if that's dicking with it...
#######################################################################################
To My Brother Robert Cameron!,
Copy that, I'm trying to do what you said but remember I am on a Raspberry Pi 3 with the .hts server. Therefore I think I can only use 4.2.3-33~ga255d8283 with no errors... From the screenshot below it doesn't look like I can transcode at all...
http://i.imgur.com/qgRbe53.png
http://i.imgur.com/PVuEbd7.png
#######################################################################################
To My Brother K Shea!,
I'm on 17.4 Kodi and I'm using 4.2.3-33~ga255d8283 on the Raspberry Pi 3 hooked into a ASUS RT-1900. PVR IPTV Simple Client works great but the TVHeadEnd HTSP Client is tripping balls. Is it because you are using a different version of the server software on something besides a Raspberry Pi 3 that you can get the stream profile to work? I am pulling in ATSC-T for the data and I do know that is MPEG-2. I did not purchase the MPEG-2 license for the RPi 3 but I think this is something else as PVR IPTV Simple Client is working just fine as it is using the "pass" method. (See above log for differences.) Something seems to be dicking with the TVHeadEnd HTSP Client. How did you get yours to work flawlessly?
########################################################################################
Help Brothers!!!