Tvheadend

UPDATE 11/04/2016
I have since rebuilt the TVHeadend RPi1 and have compiled TVHeadend from source. It is now at version 4.1-1851~g71e8b00. Whilst the picture looks much sharper for HD channels and the wizard is brilliant, I am still experiencing some issues with the HD channels. Earlier today I had the audio drop out again. So I decided to turn on debugging to file and trace logging as well. This time however the audio did not disappear instead the whole stream froze. Kodi was able to stop the stream using the stop button (I have had cases in the past where this could not be achieved and I had to restart the Pi device running Kodi).

The log is unfortunately quite large (152MB) but does sip down to ~20MB. What is the best method to upload this for someone to have a look at please?

Thanks in advance.

Original Post
Hopefully someone can help with this one - I posted it over on the Kodi forums but it is looking like it might be a TVHeadend issue. I am using TVHeadend as a backend for my Live TV. I have one RPi1 providing this service. The TV signal is fed to the Pi using a HDHomeRun device (should be evident from the logs provided). This RPi1 is running OpenELEC 6.0.3 and the tvheadend addon service from the unofficial repository (build according to the TVHeadend config page is 4.0.8 ~ OpenELEC Tvh-addon v6.0.4)

I use the pvr.hts addon on RPi2 devices around the house to be able to watch TV. I have noticed that on occasion, whilst watching Freeview HD channels, that audio seems to drop. I've managed to capture a log of this scenario and am just wondering if this is the fault of the backend, a problem with pvr.hts or maybe even a problem with decoding the streams.

I currently use Milhouse Kodi build #0406 and an in anticipation of this happening again I turned on debugging (including the video component - well I hope I did as I did it from the advancedsettings.xml so as not to get the overlay text on screen).

Kodi Log: http://sprunge.us/aBiD
TVHeadend Log: http://sprunge.us/AASY

The loss of audio seemed to happen at around 15:35:20 but I have provided full logs just in case there is a cumulative problem that may have caused it.

Any help would be much appreciated.

Thanks in advance.