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

SOLVED Hyperion, Arduino and Wetek Core

Discussion in 'Software Support' started by Remus, 1 May 2016.

  1. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    could you post both hyperion logs with this config? one with the old hyperiond and one with my hyperiond? I really want to know what is going on now.
    This is no problem, We still had no real feedback to the wetek devices or any other amlogic device, so no idea what is working here or not.
     
    Last edited: 1 May 2016
  2. Remus

    Remus New Member

    Messages:
    12
    Hardware:
    Wetek
    The new boblightd


    The old(original) boblightd
     
    • Thank you Thank you x 1
  3. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    thank you!
    This is strange, the log says nothing about the amlogic grabber that is working for you now. hm
    You are 100% sure that the duplicated entry changed it?
     
  4. Remus

    Remus New Member

    Messages:
    12
    Hardware:
    Wetek
    I will double check! I will remove those lines and get back to you.
     
  5. Remus

    Remus New Member

    Messages:
    12
    Hardware:
    Wetek
    Nope. It doesn't work without those added lines.
     
  6. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    Yeah, great that it solves this for you, on the other hand sad that you need that strange workaround and the log indicates nothing here.
    Thank you for your help, we will note it.
     
  7. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    One question, did you tried again with LibreELEC? I am really interested, if they just pushed a RPi build.
    Thank you
     
  8. redPanther

    redPanther Moderator Developer

    Messages:
    211
    Hardware:
    RPi1/Zero, RPi2, 32/64bit, +Arduino
    I recommend to delete the framegrabber section in config when using aml grabber, because then you have 2 active screen grabbers on the same host -> can lead to unwanted effects

    the "framegrabber" stands for one of this grabbers
    - "dispmanx" (raspi/broadcom videocore)
    - osx
    - framebuffer (linux without x11)

    which one depends on how you compile hyperion.

    some "nice" config facts:

    instead of "framegrabber" you can also write "osxgrabber" when you use it on osx.
    on linux you can replace the section name "framegrabber" with "framebuffergrabber" when you intend to use the framebuffer grabber.


    BTW adding the amlgrabber section for amlogic devices is no workaround.
     
  9. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    I am not happy about the current "non-linear" grabber solutions. which are working or not, or you need to call it external (x11)
    I would prefer a clean way, but we need working grabbers for each section.

    @redPanther
    of course 2 grabbers are bad, but it was the solution?
    Hyperion don´t shown anything at the log, that 2 grabbers are started.
     
  10. redPanther

    redPanther Moderator Developer

    Messages:
    211
    Hardware:
    RPi1/Zero, RPi2, 32/64bit, +Arduino
    hyperion show this:

    ssh in: ERRROR: The dispmanx framegrabber can not be instantiated, because it has been left out from the build
    ssh in: AMLOGICGRABBER INFO: [AmlogicGrabber::AmlogicGrabber(unsigned int, unsigned int)] constructed(160x160)
    ssh in: BLACKBORDER INFO: threshold set to 0 (0)
    ssh in: BLACKBORDER INFO: mode:default
    ssh in: INFO: AMLOGIC grabber created and started

    hyperion tries to start the dispmanx grabber (because of framegrabber section) and then amlogic grabber is clearly to see in the log
     
  11. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    huh? then i missed something.
    edit: no if you use framebuffer not?
     
  12. redPanther

    redPanther Moderator Developer

    Messages:
    211
    Hardware:
    RPi1/Zero, RPi2, 32/64bit, +Arduino
    BTW clean way ... you can start every grabber as standalone version, no need for integrated one - this was one big thing in my "prio cleanup PR"
     
  13. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    clean indeed, but comfortable?
    Users (I) want to start hyperion and it should select what it needs :)
    anything other is a support request here :)
     
  14. redPanther

    redPanther Moderator Developer

    Messages:
    211
    Hardware:
    RPi1/Zero, RPi2, 32/64bit, +Arduino
    thats why we need a hyperion-launcher. that thing should take multiple configs and start multiple hyperions and the needed grabbers.

    ok one thing we can do is to kick out all other grabber sections (including v4l2) and add a "type" in the framegrabber section. This will select the framegrabber. This is the way the device section work
     
    • Agree Agree x 1
  15. Brindosch

    Brindosch Active Member

    Messages:
    678
    Hardware:
    RPi1/Zero, RPi2, RPi3, +nodeMCU/ESP8266
    a hyperion launcher,
    all options available for all grabbers? Yeah!

    sounds very good :D
    why are we waiting? :D
     
  16. redPanther

    redPanther Moderator Developer

    Messages:
    211
    Hardware:
    RPi1/Zero, RPi2, 32/64bit, +Arduino
    For my taste a python app will be the best. From there I can read json files and control the apps. communication with hyperiond's can be stablished through jsonserver. Because it's python no compilation is needed and this can be platform independend.

    If this works, we can delete lots of c++ code in hyperion :)
     
    • Like Like x 1
  17. pigbait

    pigbait New Member

    Messages:
    28
    Hardware:
    RPi1/Zero, RPi2
    sounds like a good plan :) thanks guys..