Posts by micha53

    Settings often are hard to understand. Like alredy mentionend by 350D.

    Often they look like made for experts, but they should be understandable for everybody.

    Example Platform Capture Explanation (german version):

    Option Erklärungmy remarks
    Typ Art der Plattform Aufnahme; Standard ist 'auto'  auto isn't selectable, what do mean the selectable options, where to use which?
    Breite Verkleinere Bild auf dieser Breite, da das Rohmaterial viel Leistung benötigen würde.
    little error making misunderstanding the text content
    Verkleinere Bild auf dieser Höhe, da das Rohmaterial viel Leistung benötigen würde.
    dito, and how do both points interact with the last one (Bildverkleinerung Faktor)??
    Entferne links /rechts/oben/unten
    Anzahl der Pixel auf der linken/rechten/oberen/unteren Seite die vom Bild entfernt werden. 
    why should I do this? What follows from doing this.
    Bildverkleinerung Faktor
    Bildverkleinerung (Faktor) ausgehend von der ursprünglichen Größe. 1 für die unveränderte/ursprüngliche Größe. 
    compare with "Breite" and "Höhe" above

    What is, what makes smoothing?

    ...will continue, in accordance as I crowle trough the settings....

    hmm, habe ich früher im Berufsleben immer sehr ausführlich gemacht, je idiotensicherer, desto weniger Rückfragen kommen.

    Stehe hier aber gerade mal mit den Zehenspitzen in der Materie, die ich beschreiben müßte. Ich stand heute schon mal vor der (unvollständigen) Seite, die die WS2801 leds beschreibt, hatte aber zuviel Respekt davor, eine fork aufzumachen, alles Neuland für mich mit github, auch wenn ich da einen account habe, der entstand auch mehr aus Versehen... Aber mit etwas Unterstützung bringe ich mich auch gern ein.

    Im übrigen habe ich jetzt mein Projekt auf 2 rpis verteilt, beide über LAN gekoppelt und alles zum Laufen gebracht, nur hyperion hakelt noch, aber das gehört in einen anderen Thread. Mache ich demnächst.

    Hi Bub,

    no, I even didn't know anything about Wemos D1 mini. My intention was to join all 3 parts at one raspi. But I am familiar with the ESP8266. Maybe I can use such a solution instead of one raspi...

    Actually, I use 2 Rpi's, one rpi3b+ with the rpi TV HAT as DVB-T2 receiver, and a rpi4b running kodi and Hyperion.NG, both connected with an ethernet cable to share the tv signal between both.

    Hallo Paulchen-Panther,

    ist es möglich, das Skript auch für die Nutzung unter Raspberrypi OS zu erweitern?

    Oder gibt es zu viele Unterschiede zwischen der Installation unter Raspberrypi OS und LibreElec.

    Ich komme mit der Anleitung hier (rpiOS) nicht zurecht. Ich möchte kein Hyperbian neu aufsetzen, sondern mein konfiguriertes System um Hyperion-NG erweitern.

    Ein Versuch mit

    sudo apt install /home/pi/Downloads/Hyperion-2.0.0-alpha.9-Linux-armv7l.tar.gz in Analogie zum Befehl bei Debian schlägt fehl.


    my intention is to build a small DVB-TV-Receiver based on a RaspberryPi with an integrated Ambilight, resulting in a small and smart device.

    To realize that I added a

    Raspi TV HAT extention, driven by TVHeadend,

    installed Kodi and

    installed Hyperion.

    My 1st trial based on a rpi3b+, but this device was too poor, alone driving kodi together with the TV HAT utilized the system between 80 – 90% and adding the Hyperion application caused the whole system to crash.

    So I decided to test the Raspi4. This device has a hardware decoder for the H264 Video signal and as a result the device driving kodi together with the TV HAT utilized the system between only 10 – 20%, seemed to be a good base for my intention.

    The next problem was that Hyperion was not available for Raspi4, only up to Raspi3, so I decided to switch to Hyperion.NG.

    Here came the next problem: To use both the TV HAT and Hyperion it is necessary to change the SPI port of Hyperion away from SPI0. At the TV HAT SPI0 is hardwired and SPI0 cannot be used by Hyperion unless disturbing TVHeadend.

    At the old Hyperion I found a workaround to switch the SPI port to 1 but with Hyperion.NG I first had no possibility. Actually we had release Hyperion 2.0.0-alpha.9 without the possibility to change the SPI-port away from 0. But there was a pull request for changing the SPI port away from SPI0 and it was realized already. Waiting for the next release I contacted the Hyperion developer team and got a lot of help – thanks here again to Lord Grey – to use this feature before the next release. The next release will have this possibility included and everything will get much easier.

    So, finally I got all 3 parts together working, but I am not satisfied with the result. There are some effects disturbing the system:

    1. Looking TV with the ambilight causes flickering effects at the ambilight. This is annoying. I do not have this effect if I look a video from the Harddisk, connected by USB3. So this flickering is related to the use of TVHeadend. Looks like shown here in the mp4 file.

    2. Another effect is that kodi behaves strange while looking TV with the ambilight. As long Hyperion.NG is active and I do any action with the remote control (of my TV, connected via CEC), kodi crashes for an indefinite time and brings a black screen. Then the screen comes back for some seconds and gets black again. This repeats again and again. That is the 2nd effect disturbing my intention.

    If I try to use kodi’s system information feature while looking TV together with Hyperion the whole system crashes. A trial while looking a video as long as the TVHeadend server is active also does not work, brings most time a black screen, only short sequences where I can see a processor load of less than 10%. Picture CPU-Auslastung 1.png in the same location like the video above.

    I write this thread here with 2 intentions:

    1st, to share my experience to everybody with the same idea.

    2nd, maybe somebody finds my intention interesting and has ideas to improve the rpi’s behavior.

    I could imagine that it may be possible to share the 3 applications to dedicated processor cores so they can’t influence each other. But I am not as familiar with the rpi system and do not know if this is possible.

    So, if somebody would like to join this thread with a good idea for an improvement, I welcome him/her.

    Hallo, ich versuche gerade dasselbe auf meinem Raspi 3B und habe das gleiche Problem. Wenn es nicht unbedingt .ng sein muß: Ich versuche gerade die Anleitung hier mit dem alten Hyperion.
    Mit welchem OS arbeitest du? Ich habe aktuell Raspbian Buster.

    Actually SPI0 is used by Raspi-based ambilight solutions with Hyperion. But there are more SPI interfaces available.
    The RaspberryPi TV HAT hardware for receiving DVB-T2 TV is using SPI0 with CS0. Using this Interface with CS1 for the ambilight reduces the bandwidth for the TV and for the Ambilight. Probably it won't work together.
    An older thread speaks about the possibility to change the SPI-Interface to SPI1, but this is a workaround made by hand and I do not know if this possibility still is supported by the actual version of Hyperion. I am trying this actually without success.

    I think it would be good that Hyperion supports more SPI-Interfaces and that HyperCon supports this interfaces in its hardware device selection possibilities, too.

    I do not know anything about your configuration, maybe it is helpful you explain it (OS, LED type, used LED interface, KODI or other software at your system...).
    If you use the SPI-Interface, you can try to increase the SPI-speed, but then be aware of the cable length and quality.

    my TV has no Video output, but I have a Raspi 3B+ with Raspbian stretch and Kodi as media centre. Now I want to install an ambilight and use the Raspi with a TV HAT to use it as TV receiver.
    But I do not know if the Raspi 3B+ has the power to to this all simulaneously. Does somebody has any experience with such a configuration?