Posts by elliottmc

    Hi all,

    I've been running a RPi4 with three XBox TV tuners for quite a few years. Ive upgraded to a Pi5 and when I plug in two tuners it seems reasonably okay. As soon as I plug the third tuner in, it doesn't boot properly, doesn't connect to the network, etc. It doesn't better whether I plug the third tuner into the USB socket on the Pi, or if I plug all three into a UBS3 hub (so all on a USB3 socket).

    Has anyone else had a similar problem? I'm starting to think I will need to run one system (RPi4) as the TV server, and the RPi5 as the client!

    To give a bit more information about the problem, I have just enabled debug logging, and rebooted after plugging in the third tuner. I'm running LE21 RC (latest nightly build) although the stable build doesn't do better. The remote control (flirc adapter) now doesn't work, and it isn't connected to the network (it shows in my modem settings as connected but "This device either does not support or is not configured for IPv4 addressing."), so I'm going to have trouble getting the log files.

    This may help, although I don't understand the timeline. This was a freshly installed system this morning, so Feb 27 logging may indicate problems with the date and time.

    https://paste.libreelec.tv/normal-raven.log

    Best wishes,

    Mark

    Thanks. So I've switched from wired to WIFI and the problems have gone away, although there is some buffering on live TV which is not ideal.

    It does look like the powerline stuff is a bit flaky and drops the connection, but then the RPi5 doesn't recover it very well. It's a bit of a niche setup, so it probably won't affect too many people.

    What I find when it happens is there is no IP address showing in settings. Sometimes LibreElec then seems to hang completely (no response to the UI - obviously without the network I can't ping it.

    It would be better if it did recover the network gracefully, but I don't know whether that is possible.

    Hi,

    I'm struggling to get a log that shows anything (yet) but I've recently upgraded from RPi4 to RPi5, and I can't seem to get everything stable.

    I'm using ethernet with powerline networking. I think the issue is with the powerline, although other devices connected handle it better.

    Basically, LibreElec drops the IP address, and never recovers it. That's a problem because the RPi is running TVHeadEnd to serve the rest of my house, as well as recording TV to my NAS.

    Currently I've switched to WIFI, and it all seems more stable, which would again point to the powerline as the underlying cause. But it would be good if the RPi could gracefully recover the IP address rather than not, or sometimes hanging.

    Has anyone else seen similar issues? I'm using using an LE12 recent nightly build.

    Best wishes,

    Mark

    Environment: Dell Optiplex i5-6500, LibreELEC-Generic.x86_64-12.0-nightly-20230923-86f2494.img,Hauppauge WinTV-dual HD - Dual tuner, TVHeadend 4.3, Rumster Forest mast

    One of my newsfeeds mentioned a program I'd like to record. Its on BBC 3. I have BBC 3 on my Panasonic TV, and I can find it using SichboPVR on a Windows PC but I can't find it on Kodi/TVHeadend. I do have the 522MHz (which is where the BBC channels are) mux set up but no sign of it. I also have a number of timers set up so don't want to wipe everything and start again. Any suggestions / help?

    It does look like it is supposed to be on 522MHz. I'm guessing you've tried rescanning?

    Have you checked the other muxes, in case it is on one of those?

    Yeah, it's a pain if you don't spot this, and only record the first half of the film!

    Even more strange, what I find is that if I set both parts to record, the first part records for the full duration of the film (including the second part!) and the second recording is just the second half.

    It's only slightly irritating, as I just delete the second recording, but it does feel like a bug.

    Thanks for this. I saw this but didn't really understand if this was the problem I was seeing, and what to change to show the LE11 test builds list in 'updates'.

    I too have been having network shares on SMB issues but priority for me has been to get the network up and running (openvpn / wireguard)

    Do you mean trouble accessing the shares on the Pi from a computer, or accessing SMB shares on a computer from the Pi.

    I can ssh into the Pi from the PC, so I know there is no fundamental network problem. If I need to I can probably reboot the PC with Ubuntu and copy the update across from there.

    I have 'show custom channels' enabled, and I have previously put 'https://test.libreelec.tv' in for the URL, but I no-longer get any LE11 test builds. Am I missing some change?

    Thanks in advance!

    Edit: As a follow-up, I have a 'main' system running LE10, and I can access this from my Windows PC with \\192.168.1.xxx, and browse the shares. I have a test system with LE11 test builds. SMB is enabled. But when I try to access it from the Windows PC, I get 'The network path was not found'. I am using the IP address reported by LE11 and also by my router, so it can't be this. This is why I need to use the LE11 test build channel.

    do you mean:

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

    in

    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.

    Hi,

    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,


    Mark

    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.

    Hi,

    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,

    Mark

    Hi,

    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,

    Mark

    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 - https://paste.kodi.tv/bufusefami

    Any suggestions please.

    Log has

    Code
    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.