Posts by Alucard van Blood

Alright, I did a test with the latest stable LE12 from a clean install on a fresh SD card.
As more or less expected, this is working well, i.e. no delay anymore. Sadly, this does not hint a solution to the issue with my current installation.

Next step would probably be to rebuild my setup from this clean situation, step by step and checking every time if the issue re-appears.
But honestly, I cannot be bothered to do this - I just don't have capacities for this right now.

I guess, it's one of the not-so-many addons I use, but I have no idea which one and just deactivating them without full de-installation does not seem to help.

I hope that the update to LE13 (once the stable is released one fine day) will kind of erase my issue during the process.
If not, I will consider re-building my stuff with a fresh stable LE13 to that future date.

I hoped that there might be a simple explanation with a hopefully rather simple solution that I am not able to see (happened before, trust me).

Fresh installs are somewhat troublesome for me - I always have a big share of Murphy's law and I will for sure need more than just an hour (already granted I can dig up an usable SD card here)...

To phrase it in a metaphor: I do not want to break down my whole house due to a single squeaky door before I have had a carpenter check on it.

------------------

Besides, and I mean that in the most positive way: If you think that I am wasting everybody's time with my nonsense and that I should f**k off asap, then why do you spent your time by yourself to write that answer?! Seriously? Why? Just leave me and my stupid question alone and do something else with your time that makes you happy.

And for the record: I am not requesting anything here, I am asking for help - everybody is free to pass on this thread and myself. And I am grateful for all the input that came from chewitt and Da Flex although my issue is still there. I still hope that someone might pop-up with an solution that is not called "fresh install", but even if that is the only solution - then, I can deal with it.

Cheers, AvB

Dang! Took longer than I expected until someone suggests to try "fresh install" or something like that
For the moment I do not have the time to start something from scratch, but I'll keep it in mind...

Concerning VPN:

1. I tested it with the addon _deactivated_, but that did not fix anything, thus I reactivated it.
2. I know that the latest version of the addon is over 3 years old. Maybe I should give the WireGuard addon a try...
   Does not support Proton... Any suggestions?

Nope again, that does not change anything.

Also, I played around a bit with the buffermode/buffersettings that by now have been moved to the GUI - but no effect either.

Nope, does not change anything. Unplugged the HDD and tried to play something directly from the internal file system - same issue...

Plus, as I said, this also happens when I try to stream something via Youtube.

Quote from chewitt

However there's a 75 second gap between an update scrape/scan of the USB drive and the playback event starting. Do you have Kodi configure to update the library on start? .. perhaps this is the delay you are seeing?

Yes, but this process is long over and done before I hit play the first time - so, this is not the cause of the delay.

Important: This delay always happens at the first play, absolutely no matter how long Kodi was already running.

I did another test and measured the time Kodi needed to respond: it was ~50 s (well, not 2 minutes, but still damn long)
--> https://paste.libreelec.tv/unturfed-edra.log

2026-07-10 19:47:51.744 T:1232    debug <general>: OnPlayBackStarted: CApplication::OnPlayBackStarted

I did hit play more or less precisely at 19:47:00. This means Kodi kind of did not recognize it for said ~50 s. Also, the overlay displaying RAM, CPU etc freezes during my delay, I am not fully sure if the log is even working during this.

Btw... The Log is full of thousands of this stuff... What is this?

2026-07-10 19:47:47.596 T:1268    debug <CSettingsManager>: requested setting (label533) was not found.

Sorry for the delay...

https://paste.libreelec.tv/cobwebby-niesha.log

Hope that helps.

Hi everyone.

My apologies if this was discussed elsewhere, but I can't find anything... Maybe I am just bad at putting this into the right words.

For a while now, I have this strange problem: After booting the first play takes ages to start. As I hit play, for up to two minutes Kodi does not respond at all. After this, it wakes up the HDD and finally starts playing. After this, the consecutive plays work just fine. This also happens for videos played via the Youtube addon. It seems to be a rather general issue. For me, this started fully out of the blue - I am not aware of an update or something alike that may have caused this.

I'm running LibreElec 12.2.1 on a RPi4. The RPi is connected to a rather ancient Samsung TV. Additionally, there is an HDD directly attached to the RPi via USB as storage.

Any ideas?

Yes, I did check the CEC-adpater settings in the past because I was rather sure that the issue would be solved around there, but I did not find anything useful.

In fact, the solution actually is there - but sadly it's disguised behind some bad German translation. Picture for reference: deactivating the very first entry does the trick! Roughly translated back to English this entry reads "Upon starting announce Kodi as active source". There is no word about starting or powering on the TV or whatsoever - at least not for me.

My case 2 now works as desired. Case 1 got a bit more inconvenient than I expected because now I need to scroll down a quite long list of (unconnected) sources/devices on my TV before I can use Kodi - this is btw what I thought would be done by the first option in the settings. But overall this is still an improvement. Maybe I can work around that "scrolling through sources" inconvenience, too

Hi folks.

TL;DR – When my RPi4 starts, it starts the TV as well... is there a way to prevent this?

I’m running LibreElec 12.0.1 on a RPi4. The RPi is connected to a rather ancient Samsung TV (bought in 2011-ish…). Additionally, there is an HDD directly attached to the RPi via USB as storage. Said HDD is made accessible via SMB in my local network for managing its contents. When I’m not using it, the whole set-up is shutdown – because the RPi4 has no power management to hibernate it or something similar.

There are basically two scenarios:

1. I actually want to watch something using Kodi.
2. I just want access to the HDD for file transfer etc.

For case 1 everything is fine: As soon as I power on the RPi the TV is started as well, and I’m ready to go. For case 2 it is kinda stupid because I don’t need the TV and therefore I have to re-shutdown it manually myself.

==> Is there a way to prevent the RPi from “co-starting” the TV? For case 1 this would require me to start the TV myself, but I could do this easily by simply pushing a button on my remote.

Any ideas? Much appreciated.

I am thinking about moving some stuff from a NAS to a locally attechted HDD... Would something like this work, too?

<advancedsettings>
<pathsubstitution>
 <substitute>
   <from>smb:some-IP/my-stupid-fritznas/soure</from>
   <to>/var/media/my-new-local-hdd/source/</to>
 </substitute>
</pathsubstitution>
</advancedsettings>