Posts by postproducer

    In defence, I raised this issue out of interest. I did not ask for help in restoring my system since I had already done that by replacing the SSD with a new hard drive. I asked for comments from any user who had installed libreelec on an SSD. It has always been obvious that, in my case, the hang is a speed issue. On logs, I said as a result of the reuse of the SSD no logs were available, but that did not stop demands for logs. I have previously replaced the main hard drive with an SSD on my similar general purpose pc running Manjaro with no problems. I did not expect a series of angry and unjustified comments. Nobody was under any obligation to respond.

    Ref frakkin64: "Where are all these people?" Try a web search on PVR manager is starting up 0%. Also nowhere do I suggest that this problem affects everyone so do not see what your "it works fine" for you had got to do has got to do with it.

    Ref Petediscrete: brand name of PC? It does not have one, I assemble my own computers as I said in post 3. The media centre dates from 2017, uses an Asus motherboard with an Intel core i3-7100 cpu. The tuner cards are DVB Sky T9580 and the configuration may well be unique. Nevertheless it has been running Tvheadend and libreelec until the main Western digital hard drive died without any problems.

    Ref chewitt: Many thanks for the code. As I said in post 1, this, as you say, looks like a race condition. Currently I have libreelec back on a hard drive so the manager start up problem is not occurring. Noted that on restarting the computer, the event log shows "Kodi successfully started", followed by " Server does not repond properly TVheadend HTST Client (127.0.0.1)" six seconds later followed by connection established after a further 15 seconds. This looks like to same mechanism as the problem. I assume the with the much faster SSD, the timing difference is too much for the software to handle so your delay looks promising? I may have to come back to on implementing the code,

    I have no issues with tvheadend & kodi & libreelec, so it's probably something unique about your setup.

    Just me and the many folk who have reported this problem since 2015!

    I’d say if you were a little clearer on your physical hardware setup and how you have your setup configured you might get a more positive response, otherwise you’ll get the stock response , please supply logs. It may well be that it is not even an LE issue.

    I am not sure what additional information I can give further to post #3. The media computer is a pc with generic libreelec as a standard installation now on a 1T hard drive. The pvr add on is TVHeadend. It has a keyboard and monitor and is on my LAN. It has two receiver cards. It stores the recordings on the hard drive or a second storage drive as set by the recording instruction. The recording can be viewed at the pc but is more convenient to access the storage drives remotely using smb file sharing. I do not use any of Kodi's sorting features but remotely access the file manager. No logs exit since the SSD has been reformatted as storage.

    If I use the SSD for the main drive I get the "pvr manager" problem, with a hard drive as now, all works as it has for many years.

    Although the same problem has been widely reported since 2015 in numerous systems nobody seems to know who's issue it is!!!


    Nightly builds are here: https://test.libreelec.tv and the images are quite stable to use (whatever you're using at the moment isn't working either, so we're unlikely to make anything worse). I'm asking for logs for two reasons: a) we don't know what hardware you have and pastekodi content will reveal that, b) if there are problems where things don't start, there are normally useful contents in debug logs that hint to the problem. The info you've shared so far isn't enough to diagnose the issue.

    Thanks for the link. In fact having changed back to a hard drive, my media system works perfectly as before so I am reluctant to interfere with it. As I said, it is an enigma why a bug reported over around eight years by so many people remains unresolved.

    Athough I happy to help solve the pvr manager is starting problem in principle, my need is to have a media centre I can trust. My understanding is that nightly builds do not meet this requirement even if I knew how to obtain them. Also my SSD is redeployed as storage. I seems to me, that the problem occurs after the starting message is issued and before the % counter is updated. In which part of the software does this occur and how is that the same problem is found in pvrs that do not use kodi, libreelec or tvheadend?

    This is a very odd fault. Web search shows the the same problem is reported on at least twelve forums covering a wide variety of pvrs and operating systems, including windows, Linux variants and firestick, dating from 2015 to date. The problem is always the same and no solution found. The question is, what is the common link between all these disparate systems. In my case, the media pc using a hard drive installed with no problem while the otherwise identical computer with an SSD as the main drive would not. It would be nice to know.

    For PVR I use tvheadend. Lebreelec is the most recent generic series 10 version. Skin changed to quartz with no art. The unattended media computer is a home brew with an Asus motherboard, 3TB storage and two TV cards. This programmed remotely from a tablet accessing TVhe directly. The recordings can be accessed via the LAN from any local tablet or phone using VLC. The two tvs have rpi3 units also running libreelec with quartz skin. These are used to access the file manager in the recording computer. This way I can organise the file structure to suit myself.

    Hard drive failure caused a need for a new main drive. Elected to use an SSD. Install was going OK until the system stuck on "PVR MANAGER etc". Tried clean Install of most of the available issues of libreelec generic. Same results. New plan, used the storage hard drive for the installation and the SSD for storage. Installation worked perfectly with no problems. The SSD and the HD are identical except for speed. This suggests that this long standing and often reported problem is a timing issue. Looking though previous reports, the hang has occurred on a wide variety of systems , produced miles of log files but no solutions. Note that as I have reused my SSD, no log files are available. I would be interested to hear of any successful installs on SSDs and any special procedures needed for success.

    Re problem file: as any MPEG2 file from any source gave the same result, I didn't think this was necessary. But only on one computer as I have discovered.

    Re log file: noted.

    Re one core: I had noticed that but had not made a connection. Probably the result of a misguided attempt at fanless cooling a while ago. Anyway, a new CPU should fix the problem or maybe I should save up for an upgrade!

    And finally: thanks to the developers for a truly great piece of software and to all who took an interest in this threat.

    More research. I have two computers, one is Intel i5 660 clarkdale running on Asus P7H57D-V and the other an Intel i5 2500 sandy bridge running on Asus P8Z68-V LX. The former is LibreELEC and the second Ubuntu. I prepared a mint drive with a new install of 8.0.1. In the Clarkdale machine, the results as before. moved the drive to the Sandy bridge machine, mpeg files played correctly. So the problem appears to come down to LibreELEC 8.0.1 needs some feature available on the "newer" machine only. I would be interested to know what this could be.

    Any final thoughts?.

    kodi.log pasted to pastebin.com as "Postproducer Kodi.log". This does include the successful playing of an HD file at 13:13:09.652 and a failed play of an SD file at 13:14:05.226. I have yet to understand Pastebin. The paste is there as a public paste but I do not know how to see it when accessing the site without logging in. I hope you all do!

    Thanks.

    Aside from not using paste, (sorry!), that is what I did in the previous post. I restarted the machine, waited for TV headend, played an HD file, successful, played two SD files, failed, rebooted, called up kodi.log. The reboot was intended to ensure the log was saved to temp. Advice?

    Thanks.

    kodi.log

    Kodi log attached.

    This appears to cover only the setup sequence. No record I can see of the one successful play of a HD file and the two failed attempts at SD files. Is this the log requested? There are several error warnings in the log, are these significant? No mpeg sample uploaded since any such file however and whenever recorded, gives the same results listed previously.

    Thanks.

    Thanks. What is the preferred method of including the kodi.log?

    With regard to the files, no mpeg2 file will show video on my libreelec generic machine. The screen shows the control bar and a still thumbnail only.The same files, accessed via my local network by two raspberry pi 3s running Libreelec, two tablets, a phone and my ubuntu computer ALL play correctly. The generic machine plays HD recordings so it seems that the problem is with the mpeg2 codec. This libreelec install was a fresh download few days ago. This installation has no unapproved additions!


    Licences are only required on the RPi boxes as it is a RPi-hardware specific thing. On Intel machines the CPU is powerful enough to do MPEG software decoding.

    Did you check whether the licences on the RPis have actually been accepted and are working?

    Yes the two RPis work correctly, and play any video file called up from the back end on the Intel machine via my local network. But the TV headend front end on the same Intel machine as the back end gives audio only on local mpeg2 files. HD files play video correctly. It appears that the mpeg2 decoder is missing or not enabled. Reloading the software did not help. What to do Now?

    Thanks.