Beiträge von peter

  • Unable to initialize ws281x library.

    Hi again, I recompiled hyperion with the cmake from CompileHowto.txt and set ws2812spi, connectied gpio to orange pi MOSI.
    Communication with LEDs is working but:
    - i see that generated colors from v4l2 grabber are delayed (and not smooth, looks like as cpu speed issue)
    - when there is no signal (I mean black screen on usb video grabber), some leds stay white
    - initial "rainbow swirl fast" effect just flashes for a while and after that hyperion goes to v4l2 grabber processing.
    - when I stop hyperiond, first LED stays white or green
    - but remote static color/effect change is working properly



    Why this happens? When I run it or RPi with pwm, everything works properly.


    /I tried to post it to the https://hyperion-project.org/t…ion-device-type.82/page-3 but it is Locked/

  • Unable to initialize ws281x library.

    @penfold42 thank you. So any advice please which cmake command should I use to compile hyperion? And after that, how to define ws2812b with spi in hyperion config?


    I assume, used gpio pins stay the same as on rpi (one gnd, one for data).


    P.S. when I used all three cmake commands as I described at the top, compilation finished but I was unable to make it working even if I paste spidev0.0 to config file. It raised "Unable to initialize ws281x" error.

  • Unable to initialize ws281x library.

    Hello, I am trying to compile hyperion on orangepi lite with Armbian, according to
    https://github.com/hyperion-pr…b/master/CompileHowto.txt for ws2812b LEDs 3pin (in hyperion config "type" : "ws281x", "colorOrder" : "grb").


    I tried these cmakes:

    Code
    cmake -DENABLE_DISPMANX=OFF -DENABLE_SPIDEV=OFF -DENABLE_X11=ON -DCMAKE_BUILD_TYPE=Release -Wno-dev ..
cmake -DENABLE_DISPMANX=OFF -DENABLE_SPIDEV=ON ..
cmake -DENABLE_DISPMANX=OFF -DENABLE_SPIDEV=ON -DENABLE_WS281XPWM=ON ..


    but none of them worked after, I mean compilation finished successful, but when I run sudo /usr/bin/hyperiond /home/pi/hyperion.config.json it raises Unable to initialize ws281x library. When I added -DENABLE_WS281XPWM=ON it raises:
    whiteAlgorithm ::
    Unable to initialize ws281x library.
    terminate called after throwing an instance of 'int'

    Any idea please?

  • OrangePi or BananaPi w/ Arduino (adalight)?

    Friends, does somebody have a steps how to compile hyperion for orangepi please? I would like to try it. I saw there are some specific libraries for rpi (during hyperion compilation) but I have no idea how to customize it for orange. I 'd like to compile it directly on OPi (without arduino). Any idea please?

  • Hyperiond crashes

    yes please, here is lsusb:

    Code
    Bus 001 Device 004: ID 05e1:0408 Syntek Semiconductor Co., Ltd STK1160 Video Capture Device
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  • Hyperiond crashes

    I think the whole problem is because of starting and stopping v4l2grabber each time you switch back from live to static/effect mode. The better would be to have v4l2grabber live mode always started, and when we choose static/effect color then just to tell to v4l2grabber part to not send data to LEDs (because of color/effect higher priority). This would probably solve this issue, because hyperiond should not need to reinitiate v4l2grabber again and again (v4l2grabber could be always initiated but just effects/static color will have just higher priority).

  • Hyperiond crashes

    I started hyperiond manually.
    Then I tried to go to static color and the back to live mode several times until this:
    V4L2GRABBER ERROR: Frame too small: 705796 != 829440
    V4L2GRABBER ERROR: Frame too small: 725796 != 829440
    ... a lot of these lines ...
    V4L2GRABBER ERROR: Frame too small: 745796 != 829440
    V4L2GRABBER ERROR: Frame too small: 715796 != 829440
    V4L2GRABBER INFO: stopped (here I tried to go to static color again and then back to live mode)
    V4L2GRABBER INFO: started (v4l2 grabber should be started, but when I go back to live mode, all LEDs are off with no color)
    V4L2GRABBER INFO: stopped (and suddenly this happens and hyperiond definitelly crashed)
    terminate called after throwing an instance of 'std:runtime_error'
    what(): VIDIOC_STREAMON ERROR 12, Cannot allocate memory


    Then when I try to start hyperiond manually again, It did not start and I see it stops initiating of hyperiond on line:
    terminate called after throwing an instance of 'std::runtime_error'
    what(): VIDIOC_STREAMON ERROR 12, Cannot allocate memory

  • Hyperiond crashes

    Zitat von TPmodding

    https://hyperion-project.org/wiki/Hyperion-Log did you try with this method?


    Yes, I did.


    I hoped for more detailed log but ssh returned (se below) the same log as I can find in system logs in /var/log :(
    In ssh log there is just information about trying of restart hyperiond service, but no information why it terminated.

  • Hyperiond crashes

    Hyperiond service is crashing when I switch between static color (colors) and other modes (effects, live view, etc). I must reboot my RPi.


    Please, where hyperiond stores logs?
    I would like to try to find the reason of crashes by myself, too. Thanks

  • sometime LEDs pulsate

    Zitat von Brindosch

    Greetings,
    this looks strange. It is possible that your av converter output that pulse. Hyperion just outputs what it gets.


    Greetings Brindosch, thanks for your answer.
    Yes, it is really really strange. I will give you as much information as I have.


    - I tested AV converter and it outputs nice image. (so this AV converter is not causing it)


    What I found out:
    When I run

    Code
    hyperion-remote -c red
hyperion-remote -x
hyperion-remote -c green
hyperion-remote -x      it starts pulsating in some parts of my LED strip (video included).


    Sometimes it needs more -c and -x cycles to start pulsating. When hyperion service is running and it starts pulsating, I just run "sudo shutdown -r now" (hyperion service is terminated properly) and after reboot everything works ok (no pulsating anymore until I repeat -c and -x cycles).
    BUT if leds start pulsating and hyperion crashes at the same time (this happens always when I run approx. 7 times -c and -x cycle) my leds continues pulsating even hyperion service is not running anymore (because of hyperion crash). When I reboot my Pi with "sudo shutdown -r now" pulsating continues over the whole reboot time and after initial rainbow reboot effect it pulsates again (I think because hyperion service was not terminated properly so it did not reset leds before reboot //because hyperion service crashed//). In this case I need to unplug power and after power replug it works again normally.


    I think there is problem (somewhere) in hyperion service during controlling leds.


    Videos:
    - pulsating - https://sendvid.com/mftmpitw
    - good colors - https://sendvid.com/0036q9x4
    Hyperion config json: http://www.filedropper.com/201715hyperionconfig
    Logs from /var/logs (after start and after hyperiond crash): http://www.filedropper.com/varlogs


    P.S. I found out, that sometimes command "hyperion-remote -x" goes back to live mode without led pulsating and sometimes it causes pulsating. Command "hyperion-remote -c red" (or any other color) never generates pulsating.
    It looks like it has something to do with v4l2 grabber settings: width, height, framedecimation, sizedecimation, cropping.

  • sometime LEDs pulsate

    Hello, sometimes, when I turn on my Rpi with hyperion and hdmi2av, LEDs pulsate. Sometimes it happens when I set static color and the switch back to live mode. And sometimes when I restart my Pi.
    Any idea what is causing this please?


    videos:
    https://sendvid.com/yiesjc6u
    https://sendvid.com/g4zfw7qh
    <iframe width="560" height="315" src="//sendvid.com/embed/g4zfw7qh" frameborder="0" allowfullscreen></iframe>
    <iframe width="560" height="315" src="//sendvid.com/embed/yiesjc6u" frameborder="0" allowfullscreen></iframe>

  • hyperion service failed to start

    Zitat von peter

    I am thinking of "modprobe -r <module name>" and "modprobe <module name>" to reload it. I listed modules with lsmod and there is several modules where stk1160 is in field "used by". Which specific module should I reload please? Or should I reload all modules where stk1160 is written?



    I tried this when "VIDIOC_STREAMON ERROR 12, Cannot allocate memory" happened but then it did not help. Maybe I try to apply it right after hyperion starts (or I try to apply it as a permanent to /etc/modprobe.d/stk1160.conf).


    I tried both mentioned things but none of them worked :/