1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Hyperion/HyperCon V1.03.0 Released

Discussion in 'Official Announcements' started by Brindosch, 11 June 2016.

Thread Status:
Not open for further replies.
  1. Brindosch

    Brindosch Administrator Administrator

    Messages:
    592
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Hyperion V1.03.0
    This is one of biggest realeses for a long time. New features and bug fixes are waiting!

    Warning ALL SYSTEMS (exception: OpenELEC, LibreELEC, RasPlex) : Hyperion change the installation and config dir!
    All configs move now to /etc/hyperion/xyz.json

    Hyperion is now located at /usr/share/hyperion

    The installation script will modify all necessary files to keep a smooth transition.
    In case you use external scripts you need to adjust the paths to the new location!
    In case you created a second service for the Hyperion forwarder you need to adjust these also (have a look at the modified service file for help) or use the new forwarder start implementation (see changelog)

    • New: Raspberry Pi: drive PWM leds now via SPI GPIO
    • New: hyperion-x11 now with XRender support which fixes all known issues
    • New: Minimum luminance as "backlight" in dark scenes
    • New: crop functionality for dispmanx
    • New: Device: UDP now with protocol 3 which is a TPM2.net support (LED matrix)
    • New: Device: udpraw (new-imp) as the first step of a refactoring of UDP to QT
    • New: UDP multicast listener
    • New: Start multiple Hyperion instances with one service file - just append the path and config name to the current one (systemd example: ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json /etc/hyperion/hyperion.bulb_left.config.json)
    • New: x86x64: hyperion-x11 now with kodi check
    • New: KodiCheck has now a option for "pause" state. Works with pictures, audio and video.
    • New: current version number via json
    • Fixed: Philips Hue flickering(blue) when switchOffOnBlack is set true
    • Fixed: KodiCheck picture modus detection
    • Fixed: power of two resolution for framegrabber (dispmanx)
    • Fixed: If you assign less APA102 leds as the current stripe has, - next 2 leds are set to a bright white
    • Improvement: Enabled color smoothing no longer flood led devices with data
    • Improvement: Effect: full color mood blobs now with random colors
    • Improvement: Changed color transform/adjustment order (it may be possible that you need to recalibrate your colors)
    • Improvement: Better color adjustment: linear grey increase and grey now independet from colors
    • Changed: JSON and PROTO server start is now forced, even when disabled at config
    Misc
    • Now it is possible to create debian packages
    • Removed after install/update: /opt/hyperion/ this directory is no longer used
    • Hyperion log improvements (loaded effects and no longer kodi debug spam)
    • some script optimizations
    • code cleanup

    HyperCon V1.03.1
    • New: name field at the led device section (as config identifier)
    • New: luminance for backlight in dark scenes (color calibration)
    • New: Kodicheck now with option for grabbing at player "pause" state
    • Changed: ssh target dir for configs now at /etc/hyperion/
    New phrases for translation:
    • hardware.device.namelabel
    • process.transform.MinimumLuminanceLabel
    • process.transform.MinimumLuminanceLabeltooltip
    • external.kodi.pauselabel
    • external.kodi.pausetooltip

    Removed phrases for translation:
    • external.effect.booteffectlist.UDP_listener
    • external.server.jsonenabled
    • external.server.protoenabled

    Thank you to all developers for this great new features and fixes!
     
    Last edited: 11 June 2016
    • Like Like x 6
    • Thank you Thank you x 1
  2. epicfail83

    epicfail83 New Member

    Messages:
    19
    Hardware:
    RPi2
    Hab grad das Update gemacht...leider kann ich jetzt meine zweite Config nicht mehr laden. Die normale hyperion.config.json startet....die hyperion.config.hdmi.json startet nicht mehr.

    Ich starte die beiden über meine Harmony mit lirc per sh....

    Für meine HDMI Config:
    #!/bin/sh
    sudo service hyperion stop
    sudo service hyperion_hdmi start

    Für meine TV Config:
    #!/bin/sh
    sudo service hyperion_hdmi stop
    sudo service hyperion start
     
  3. Brindosch

    Brindosch Administrator Administrator

    Messages:
    592
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Du musst den config Pfad des service ( hyperion_hdmi) noch editieren.
     
  4. epicfail83

    epicfail83 New Member

    Messages:
    19
    Hardware:
    RPi2
    Hä?

    Die TV Config kann ich doch auch noch per Harmony starten....sorry hab mit Linux eher wenig Erfahrungen...bin froh dass das alles bis jetzt lief :D

    Kannst du mir nen weiteren Hinweis geben...?
     
  5. Brindosch

    Brindosch Administrator Administrator

    Messages:
    592
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Du hast für diesen Befehl etwas erstellt um den überhaupt ausführen zu können
    Code:
    sudo service hyperion_hdmi start
    In dieser Datei (in diesem service) stimmt der Pfad zur .json nicht mehr und bleibt daher dunkel.

    Folgendes funktioniert noch
    Code:
    sudo service hyperion start
    weil das script es automatisch umgestellt hat. Ich gehen davon aus bei dir läuft OSMC. Du findest die beiden Dateien unter /etc/systemd/system/
     
  6. epicfail83

    epicfail83 New Member

    Messages:
    19
    Hardware:
    RPi2
    Muss morgen nochmal schaun....ich hab Raspbian im Einsatz. Bei mir liegen die beiden sh Dateien unter /home/pi

    Wenn ich die hdmi.sh ausführe gehen die Leds aus aber es scheint als würde die Config nicht geladen.
     
  7. epicfail83

    epicfail83 New Member

    Messages:
    19
    Hardware:
    RPi2
  8. Mommi

    Mommi Nur hohe Spannung ist gute Spannung

    Messages:
    2
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino
    Guten Abend zusammen,
    kam ja echt ein großen update heraus.

    was hat es den mit "Raspberry Pi: drive PWM leds now via SPI GPIO" auf sich?

    Ist das eine PWM für Standart LED Stripes?

    grüße Mommi
     
  9. TPmodding

    TPmodding Administrator Staff Member Administrator

    Messages:
    609
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino
    Man brauch nicht mehr einen PWM Pin zu nutzen sondern kann den Data-Pin benutzen vom SPI, der gibt die Signale so raus das es die PWM-Leds verstehen
     
  10. Mommi

    Mommi Nur hohe Spannung ist gute Spannung

    Messages:
    2
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino
    Ah ok,
    Habe eben ein Projekt vor, Dass ich mit Hyperion ein Standart LED-Stripe ansteuere. Möchte das es hinter meiner Couch genauso wie das TV Bild leuchtet.
    Dachte dabei an den Pi-blaster.
    Möchte dazu den Raspberry Zero verwenden.
    Mal gucken wie ich es mache.
     
  11. kiryl

    kiryl New Member

    Messages:
    2
    Hardware:
    RPi2, RPi3, +Arduino
    Hi guys, I use currently ws2812b leds with PWM ws281x drive actually with no bigger issues.
    So taking that into consideration should I be interested in new drive SPI?

    Is it somehow better? Which pin should I use?

    Cheers and congratulations for a good job guys :)
     
  12. TPmodding

    TPmodding Administrator Staff Member Administrator

    Messages:
    609
    Hardware:
    RPi1/Zero, RPi2, RPi3, +Arduino
    @Mommi @kiryl
    Could you guys start a own thread please? It is better/easier to help one person in a own thread instead of discussing in an general thread, thanks!
     
  13. AEtHeLsYn

    AEtHeLsYn New Member Developer

    Messages:
    28
    Hardware:
    RPi1/Zero, RPi2, RPi3
    And please keep german talk at international talk. I don't bother at all, but it's a bit weird :)
     
    • Agree Agree x 1
  14. Brindosch

    Brindosch Administrator Administrator

    Messages:
    592
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    /closed
    but i am glad that people like it! Just open a new thread if you have questions or want to talk about xy at the general discussion section (english) or for your language at the specific language section.
     
Thread Status:
Not open for further replies.