Posts by elliottmc

    do you mean:

    Settings => Interface => Skin => "-configure skins" => Enable category widgets


    Settings => PVR & Live TV are some more settings regarding recording, etc

    I am afraid none of those settings make a difference, and also not something I've needed to do before.

    It looks like there has been a change, deliberate or not.


    I've been trying the LE11 nightly builds for a while. Everything is great, apart from one small niggle with the TVH plugin.

    In LE10 and earlier, at the top of the screen I get the current/next recordings showing. I don't get this in LE11 builds. Is this intentional?

    Take care,


    I have Windows-compatible filenames: set and it works for an actual programme name, unfortunately a folder name can still contain banned characters (eg : as in NEW: Ipcress File) which makes it awkward to transfer to Windows. The only way I've found so far is to SSH in and rename the folder, copy it and then rename back.

    Is there a switch in TVHeadend that I've missed?

    In the TVHeadEnd web interface,

    Configuration->Recording->Digital Video Recorder Profiles

    In the group for 'Filename/Tagging Settings' there is 'Use Windows-compatible filenames'. The setting mentioned by Mario77 is a couple above this.


    I am seeing regular crashes with live TV and 10.0.2. It tends to be after seeking/pausing, and I get a lot of green artefacts on screen, and then it will reboot.

    It's not a full LibreElec reboot, as if there is a TVHeadEnd recording running, it doesn't get messed up.

    Been using LibreElec 10.0.1 with TVHeadEnd for a long time without any issues.

    Logs attached.

    Should I just update by 'main' system to LE11 nightlies?

    Best wishes,



    Just a short note, and apologies if this isn't the best forum section for it.

    In LE10 (and earlier) there has always been a section at the top of the TV home screen where the current (if any) and next scheduled recording is shown. I have tried a few recent LE11 builds, and this is not shown. I am using the LE11 build on RPi4, connecting to TVH 4.3-1979 running on a different RPi4.

    Not sure if this change is deliberate. I guess I got used to seeing what will record next shown clearly, so it feels like a regression to not show this.

    Best wishes,


    And it's not resolved, again.

    I foolishly tried to perform the difficult task of watching the TV and it's not working again. I changed absolutely nothing.
    Here's the log -

    Any suggestions please.

    Log has

    2022-01-16 12:14:13.414 T:974      INFO <general>: AddOnLog: pvr.hts: starting PVR client
    2022-01-16 12:14:13.419 T:995     ERROR <general>: AddOnLog: pvr.hts: Command authenticate failed: Access denied

    You need to enter your credentials in the TVHeadend kodi plugin for the client to connect to the server (even if they are running on the same machine.

    Yes but I need the specific Nightly build in order to use Kodi Matrix/Nexus.

    Some of the addons I use are only on those platforms.

    Perhaps if you tell us which addons, there may be someone who can help you.

    I notice you refer to 'private addons' and internet videos in your post above. I wouldn't want to jump to conclusions, but are we talking piracy addons?

    I switched my tuner to sundtek skytv 8 but with no improvement.

    After some hours of debugging with sundtek support I was told that rpi (graphics driver) is locking system when playback is started. That's why usb is blocked, dvb buffer runs dry and some data of livetv gets lost.

    Could this be improved somehow?

    Ah, now that makes sense as to why it's only playback on the Pi that is acting as TV server that causes the issue.

    I've got to admit, bearing in mind the low cost, I was seriously considering at one point buying another Pi to use as client, so that the server is never doing any playback.

    BUT, for me, it seemed that the only time I had significant data errors was if I tried to play the recording that is running. If I start live TV on a different tuner, or play back some other video, it didn't cause it. Is this consistent with the explanation?

    Is recording to network an option for you?

    Also, I checked the thread I posted when I was having issues, and I now remember that changing the TV signal booster was a significant factor.

    I can do some testing with HD channels another day, but I've got a recording running at the moment that I don't want to mess up!

    Today I tried to boot from usb ssd, I still get continuity counter errors in tvh if I playback an ongoing recording.

    Are you recording to this SSD?

    I saw this behaviour, but I haven't had time to look into it properly.

    I've just done a very quick test with an SD TV channel. I started recording, and then started playing the recording. No errors within about a minute.

    I record to a NAS which is connected to my raspberry pi 4 via a wired network.

    Also, I was doing the playback on a different system to the one on which TVH is running.

    I THINK when I saw these problems previously, that I was recording to the microSD card.

    If your TV tuner is USB, and your SSD is USB, could it be that recording from one USB device to another AND playing the file back from USB is simply too much? Sure, it shouldn't reach the theoretical bandwidth, but you never know.

    I guess it would be useful to know which scenarios cause the problem and which do not.

    Okay, I think I have progress.

    I created folders on my NAS for timeshift and recordings. Figured it wouldn't hurt to use that for all disk bashing. Obviously I had to mount them in LibreElec.

    At the same time, I dropped down to a single tuner plugged directly into the aerial, cutting out the signal booster. This seemed to work fine, so I dug out my previous signal booster and switched back to that.

    Touch wood, I haven't had any data errors.

    Of course, I don't know which of these things has had the biggest impact. I'm inclined to suggest the signal booster, although I was getting good signal reported.

    Thanks for pointing out this thread. I'd missed it.

    So, it seems (initial testing) that this only happens if the playback is on the same raspberry pi. If it is playing back on another client on the network, it seems fine. I pushed the limit on this recording one HD and one SD channel simultaneously (two different muxes so two different tuners). Playing these in-progress recordings on a Windows PC over the network was fine.

    Of course, with the Pi, it's a question of whether the act of playing the in-progress recording is the problem, or perhaps the USB remote interferes with the USB tuner. Yesterday, I watched an in-progress recording most of the way through without a problem, and the recording only had problems at the end, which MIGHT have been when I hit the stop button and navigated out o f TV using the remote. This link does bear more investigation.

    More data points would definitely be useful.

    For me, I'm more than happy to put Raspberry Pi OS on one Pi to use as the TV server, and then have another one for the Kodi box. What I don't want to do is spend lots on different TV tuners, remotes, storage, and then find there wasn't anything I could have done.

    Okay, so I'm struggling.

    I am still having some issues with 9.2.6, but it doesn't seem as bad as 10b1.

    It seems that when I play a recording back while it's still running, I get a lot more data errors. This happened this evening, but I didn't notice while it was running, so maybe it's always happened. Having checked the actual recording file, there was a massive amount of garbage after the actual programme, which may have coincided with when I stopped the playback.

    If something records in the middle of the night, no data errors.

    So, is the RPi4 just not up to playing back a recording while it's running? Is the problem that the MicroSD card isn't fast enough (SanDisk class 10)? Could it be something stupid like birds landing on the aerial?

    Next up is to plug a second Pi4 in for playback, and just have LE9.2.6 on the 'server'.

    Any more ideas for debugging this?

    Seems to be happening on LE9.2.6 and LE10b1, but definitely worse on LE10b1. Happening on multiple TV tuners. Aerial hasn't changed. Happens with two different microSD cards.