Posts by Da Flex

Quote from shedrock

This is not an addon issue. If it were, then it would not be working on a windows setup.

The programming of the functions are very different on Windows and Linux. Under the hood it's really something else.

Quote

Are you using LE? If so, does your Cast show up while watching a TV episode and pressing Info on your keyboard, or remote?

Yes, but I only have DAZN and German TV streams. Not sure whether TVDB scraper works with it, but I'll do the test.

PS: If you know a free and legal streaming add-on, which we can both test, let me know.

Looks like we have not solution, because we can only guess what the add-on does.

Find the developer of the add-on, and ask. Maybe milhouse knows him, and can make it happen.

shedrock :

Do you use a custom skin or fanart? I'm asking because I read "fanart" lines at your log.

If yes, use the default skin and disable fanart. Sometimes GUI entries are invisible, because graphics is missing for a custom GUI config.

Quote from mattlach

I never noticed this before, but apparently the Asus H81M-K motherboard in my HTPC does not have an HDMI port for the on board GPU, only DVI and VGA, and without it I can't get sound in my setup.

It's not part of the DVI standard, but many motherboards support sound over DVI. Check the EFI settings whether you have it.

If yes, then maybe a DVI <-> HDMI adapter will do the trick. The Haswell platform is popular and has good Linux support - worth to try it.

I was just trying it on my RPi 3B+.

After upgrading to 9.1.5x from the 9.2 branch, the ISA 2.4.2 update is available.

Sadly, DAZN won't run any streams on that configuration.

So I downgraded to 9.0.2 again, and fortunately ISA 2.4.2 will not downgrade with it.

Buffering issues are still there.

I'm one of those match-3-players, too. Currently I'm playing "Wonka's World of Candy" on Android.

Amazon Appstore (Fire TV) and Google Play (Shield TV) have "Candy Crush" and "Wonka".

Kodi runs on both devices.

No, you need an app store for that.

Hint: The Nvidia Shield TV has Android with Play Store, too. There are rumors about a 2019 version coming soon.

Quote

Code

(prefer) mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced

Then despite of your thread title, 1080i is detected.

The unusual point, compared to other users, is that you have a coloring issue. Have you already tried a different HDMI cable? If you buy a new one, look for the "HDMI High Speed" or "HDMI High Speed Premium" standard.

We have several threads where users want to force a display mode, which is not detected by LE. To my knowledge, there is no way.

Hopefully the crash log will help devs to fix it. I had several safe mode issues with LE 9.1.0.x on RPi 3B+.

I think it's the best choice to use the LE 9.0 branch for all RPi lower than version 4.

PS: Ich weiss nicht, welche add-ons Du schon installiert hast. Für die verwendete Python-GPIO-Bibliothek braucht man das add-on "Raspberry Pi Tools".

Evtl. kann es sein, dass autostart.sh und/oder volume_regulator.py mit chmod +x <Dateiname> ausführbar gemacht werden müssen.

Du kannst autostart.sh testen, indem Du es direkt vom SSH-Terminal mit /storage/.config/autostart.sh aufrufst.

Quote from CvH

der Befehl für Volume +- ist

kodi-send --action="VolumeUp"

kodi-send --action="VolumeDown"

Das macht es einfacher. Dann fällt die umständliche Abfrage der bisherigen Lautstärke weg.

Der Code müsste dann so aussehen (mit extra Button-Definition des Reglers zum Stumm schalten):

#!/usr/local/bin/python3
    
import RPi.GPIO as GPIO
from KY040 import KY040
import os
import time
 
# Lautstärke ändern, wenn der ky-040 gedreht wird
def rotaryChange(direction):
    if direction == 1:
        os.system("kodi-send --action='VolumeUp'")
    else:
        os.system("kodi-send --action='VolumeDown'")
        
# Funktion ausführen, wenn der ky-040 gedrückt wird        
def switchPressed():
      os.system("kodi-send --action='Mute'")
 
 
if __name__ == "__main__":
 
    CLOCKPIN = 5
    DATAPIN = 6
    SWITCHPIN = 13
   
    
    GPIO.setmode(GPIO.BCM)
    
    ky040 = KY040(CLOCKPIN, DATAPIN, SWITCHPIN, rotaryChange, switchPressed)
 
    ky040.start()
 
    try:
        while True:
            time.sleep(0.05)
    finally:
        ky040.stop()
        GPIO.cleanup()

Installation:

- Ordner für das Python-Script anlegen: mkdir /storage/scripts

- Script-Datei erstellen: > /storage/scripts/volume_regulator.py

- Code einfügen und speichern

- Python-Bibliothek KY040.py aus dem Start-Posting in den gleichen Ordner kopieren

- Script beim Start von LE ausführen, dazu Inhalt von /storage/.config/autostart.sh wie folgt:

#!/bin/sh

python /storage/scripts/volume_regulator.py

Quote from Blackbeard

Wie ist das mit Zeile 9-11 ?

Das Kommando zum Setzen der Lautstärke erwartet eine Angabe in Prozent (relevant für Code-Zeilen 18 und 20).

Beispiel: Lautstärke auf 80% mit Bildschirm-Ausgabe zur visuellen Bestätigung (Option "true"):

kodi-send --action='SetVolume(80, true)'

Es muss also vorher die bereits eingestellte Lautstärke in Prozent ermittelt werden. Das geht per JSON-Anfrage:

curl  -H "Content-Type: application/json"  -d "{\"jsonrpc\": \"2.0\", \"method\": \"Application.GetProperties\", \"params\" : { \"properties\" : [ \"volume\", \"muted\" ] }, \"id\" : 1 }" http://libre-elec:8080/jsonrpc

Ergebnis der JSON-Anfrage:

{"id":1,"jsonrpc":"2.0","result":{"muted":false,"volume":80}}

Problem: Das Ergebnis muss noch geparsed werden, um nur die Zahl 80 (%) zu bekommen.

Verwende also statt Zeile 9-11 das genannte Kommando, und eine Regular Expression, mit der Du vom JSON-Ergebnis zum Prozentwert konvertierst. Dann den Step-Wert vom Regler addieren oder subtrahieren. Das Ergebnis wie gezeigt per kodi-send übergeben.

Probiere die Kommandos im SSH-Terminal aus, bevor Du sie in Dein Python-Script übernimmst.

Quote from Blackbeard

Hallo Da Flex,

ich denke, ich habe DvH verstanden.

Nein, Du hast weder CvH noch mich verstanden. amixer geht genauso wenig wie sudo unter LE.

Mach' es so, wie CvH geschrieben hat, also per os.system und kodi-send. amixer geht nicht.

Looks like the LE server was offline:

2019-09-14 19:21:59.191 T:140409242113792   ERROR: ## LibreELEC Addon ## oe::load_url(http://releases.libreelec.tv/releases.json) ## ERROR: (URLError(error(110, 'Connection timed out'),))
2019-09-14 19:21:59.191 T:140409242113792   ERROR: Traceback (most recent call last):
                                              File "/var/lib/jenkins/LE/build2/workspace/Generic/build.LibreELEC-Generic.x86_64-9.0.2/LibreELEC-settings-37e206b712a46213522a567a408382f5f082502a/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/oe.py", line 270, in load_url
                                              File "/usr/lib/python2.7/urllib2.py", line 154, in urlopen
                                              File "/usr/lib/python2.7/urllib2.py", line 429, in open
                                              File "/usr/lib/python2.7/urllib2.py", line 447, in _open
                                              File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
                                              File "/usr/lib/python2.7/urllib2.py", line 1228, in http_open
                                              File "/usr/lib/python2.7/urllib2.py", line 1198, in do_open
                                            URLError: <urlopen error [Errno 110] Connection timed out>

You can switch add-on updates to manual as a workaround.

I assume you want to attach it to a running LE machine.

LE can handle different file systems. They will be auto-detected and auto-mounted by LE.

If you have an external HDD, and occasionally want to attach it to a Windows PC, too, format as NTFS.

If it's for LE only, format as EXT4.

Use a bootable USB stick with an OS specialized for device checking. Your HTPC can probably boot from stick.

GParted LIve can check and repair partitions. Especially it can leave bad blocks out when reformatting a partition.

Be sure to make an LE backup before you try to repair anything.