Posts by zehner

Quote from erythros

Why would you blank out $PROJECT_CFLAGS?

In my personal build, I replaced

TARGET_CPU="x86-64"
with
TARGET_CPU="silvermont"

and

PROJECT_CFLAGS="-mmmx -msse -msse2 -mfpmath=sse"
with
PROJECT_CFLAGS="-mmovbe -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -mpopcnt -maes -mpclmul -mrdrnd -mfpmath=sse"

So far all addons function. In fact I have noticed slightly lower memory usage, roughly 20-23% on average. However, I should state that I did not perform riguorus double-blind tests.

Oddly enough, before I implemented these changes Chromium produced choppy output from NetFlix videos. After the custom changes, Chromium produced better output. There is still a degree of dropped frames, but only during highly dynamic scenes (fast action on high quality videos). Which makes me wonder about recompiling Chromium with the same customizations...

Display More

I know this thread is very old, but for completeness and because this page is the first search result for "libreelec silvermont" on google

TARGET_CPU="silvermont" already enables MMX, SSE and so on

x86-options.html

mfpmath=sse is default for X86-64 and higher

i386-and-x86_002d64-options.html

So piotrasd tip should be the best option for compiling for silvermonts or are there other reasons why redundant PROJECT_CFLAGS should be set?

And where is the best place to set -O2 or -O3 flag for LibreELEC? PROJECT_CFLAGS?

I've never used TVHeadend, but you can use MediaTomb (miniDLNA has never worked for me) to share your tuners via DLNA/UPNP. You should be able to create your muxes in TVHeadend with the m3u file from your box.

MediaTomb can transcode, but I've never used transcoding, because my box lacks this feature.

A different approach could be to use OpenWebIf and port forwarding, but be careful if you make your box visible to the internet

Thanks vpeter, but pastebin would be using a sledgehammer to crack a nut.

There is only one command in my file
[code=php]
wget powerstate?newstate=0
[/php]
This command sends a standby to my pvr. I will try a few params, curl instead of wget, ip instead of url and check the return value, perhaps that gives me a clue whats wrong when using a timer

Thanks for the feedback and thanks vpeter for the shutdown_with_net service in general. I have no clue about systemd, so your work was a lifesaver for me

You are right, the script is also executed with shutdown timer. I have integrated some logging and can see the script is executed. The script has no dynamic parts and its the same script, so I have no clue why it's working if called by button and not working if called by timer. At least now I know that everything works in LibreELEC and I have to search on server side

Thanks

Hello

I use LibreELEC 8.0.1 with the vu+ pvr client. Most of the time I want to shutdown the pvr server (a linux box in another room), when I shutdown LibreELEC. This works with the approach from thread-107-post-1367.html#pid1367

If I shut down LibreELEC with the menu entry in the log out menu (or the mapped key on my remote), the shutdown_with_net.sh script is executed and everything works as expected. But if I try to shutdown with a timer (e.g. set the timer to 5 min), the script is not called.
The regular shutdown.sh approach also does not work, because I have to execute the script before the network of LibreELEC is disconnected and shutdown.sh is called after the network is disconnected. The same applies to the KODI Callback addon, if I execute a regular shutdown, everything works as expected, but if I try a shutdown timer, the script is not called.

Does someone here have a working solution to call a script when LibreELEC shuts down by timer or is this a problem in KODI, that shutdown by timer and shutdown by menu entry don't call the same events

Thanks
zehner