Posts by davieboy

    oops my bad, yeah im with your thoughts. ignore my last post


    Ideally you want to login to your router/modem and reserve an ip for your most used network devices - thats good practise to do so that if it did ever reboot it always gets assigned the same ip and your stuff just works. Nowadays most routers will do this at the click of a button rather than going down the static ip route and assigning it all manually


    try and find a login and password and login to your router though and see if you can see what IP WLED is using and go from there


    typing this command should show you what hyperion is currently running as

    Code
    ps aux | grep hyperion


    im on LE so you can see mine is running as root - look after the 1st number


    403 root 5h16 /storage/hyperion/bin/hyperiond --userdata /storage/hyperion/


    but as you mentioned it shouldn't affect you as you are not driving the leds directly, but at least you will know what user its currently running under and going by recent posts is should not be root and instead be pi user, then you can just re-enable auto startup of hyperion

    going by your command you may be facing this problem



    :thumbup:

    byrdman heads just exploded with all the information. Look into WLED if you feel the need once you get this setup running


    I reckon you must of been close, you worked your way along.

    with all the advice and conspiracy around that signal cable could you not just dangle the pi up and over that hook instead of down and made that wire really short (same for led ground to pi) - just for testing purposes - you will make Mike72 smile and you can always solder it back together again afterwards.


    As if the data wire is short and you are getting good Supply and Ground to the LEDS surely it can only be config / settings or dead leds from when it got hot.


    the2812b should run without any shifters or they should at least light up providing there on the right pins maybe practise that terminal thing and try these - they might not work but i hope basic stuff like that is the same on mac

    Code
    ssh pi@your-pi-ip

    you may need to accept a ssh key if its the first time you have connected to the pi and put in the pi users password, once you get in try this one

    Code
    cat /boot/config.txt


    if it works copy all those lines and paste them straight into code blocks in the forum just as a refresher and to see if putty slipped in a few bad lines


    Good Luck :thumbup:

    maybe check the current that your LEDS are actually drawing as it may be maxing out the supply or the supply just may not be up to the job - think thats why other prefer the non brick style ones as they can be a tad unstable :thumbup:

    putty is only a tool for connecting to things - this should be a bread and butter tool for anyone that doesn't have a terminal in order to run commands on a remote machine (ie a Pi).

    hope that wasn't an April fools joke Michael Rochelle:D


    you wouldn't happen to know the location to system audio would you, heres an example of a path to the pi ttyso

    Code
    --device=/dev/ttyS0:/dev/ttyS0 \


    is there an equivalent path to access the system audio?



    Paulchen-Panther - you wouldn't know a way of setting up a named pipe to grab the system audio and pipe it to a fifo file off the top of your head would you?

    think Lighting-guy77 may have cracked it or wladi^^


    Might be worthwhile running this command before you do the post on adding the udev rule

    Code
    ps ax | grep hyperion

    if it shows you something like this


    Code
    LibreELEC:~ # ps ax | grep hyperion
    21081 root     17h10 /storage/hyperion/bin/hyperiond --userdata /storage/hyperion/
    28998 root      0:00 grep hyperion


    that shows mine is running as root, if yours shows pi instead of root, then pay attention near the end of the post :thumbup:


    if your not too comfortable in the terminal just use the Copy button at the end of each codeblock - as sometimes its easy to missout vital . or other things you may not think is relevant or added in by mistake


    some terminals require you to manually go to edit menu then paste


    Good Luck


    that should have been in the post then along with the delay part :thumbup:


    usually you would post what hardware you are using like pi version, operating system, LED type (ws2181b etc), what grabber it happens on - capture card or internal grabber


    the more info you can provide the more others can help you.


    start with what james2brite mentioned and lower the resolution on the device your using if that doesn't work post some info on your setup

    sorry mate i sidestepped once english was out the way :D


    genuinely gutted for you tho man as your putting in the effort.


    Looking at it from a diagnostic point of view I would be tempted to gather all the components and put them in a pile on the floor and start testing them.


    If i was in your shoes i would

    Start with the very basics - the Pi - install Etcher and burn a freshly downloaded v9 of libreelec and enable ssh during setup on screen

    use Paulchen-Panther tutorial and install Hyperion - do not install or do anything else except reboot after the libreelec tutorial


    You should be able to wire up the data line of the LED directly to the pi - just for testing purposes use default GPIO 18 (pin 12) make sure you are using the correct pin depending on your version of the Pi GPIO, you can then go to http://your-pi-ip-here:8090 then into

    Led Instances -> LED Output then in the LED Controller change that to RPI PWM - ws281x, set your led count and the GPIO pin that you used and save settings, You may need to go into LED Layout and define the led layout


    In theory you should then be able to use Hyperion webui at http://your-pi-ip-here:8090/#remote and toggle the LEDS on and off and set a solid colour in the Colors/Effects section - They may not all light up but you should be able to tell if the LEDS are actually working.


    Once you have a working Hyperion and LEDS, then you can introduce the Adriuno and go from there to see what works and what doesn't - as my concerns are is the clone thing compatible? will it work? have you flashed the other Adruino correctly?


    but yeah id like to see LEDS lighting up to rule all that out then go from there as what if those clone things are killing your LEDS, without going back to the basics and ruling things out its all a big time consuming guessing game

    sorry Manny i will fully support you when you provide some decent information to when the fault occurs, with it being a delay have you used the forum search at the top to see if anyone else has suffered from the delay?


    The fact that you replied to me and still didnt add some information that will allow others to help you makes me wonder if this is a serious post

    I vote you send it to TPmodding


    All out everything you have tried and if you are still using the OLD AMBIBOX chinese thing, is it not safe to assume it just doenst work? and could possibly be more hassle than its worth? especially when you can get tons of other adruino like clones for as low as $3 and this could of been resolved and let you enjoy your Hyperion setup months ago :/

    db engine quite easy to setup, if you already have netdata installed and have sufficient space on SD card and some spare ram its just a case of uncommenting a few lines in your netdata.conf


    Code
    memory mode = dbengine
    page cache size = 32


    use your current running setup to work out the next value based on what you decide here

    https://learn.netdata.cloud/do…e-needed-to-store-metrics


    then uncomment this line to your netdata.conf and change the value to the one you calculated

    Code
    dbengine multihost disk space = 1277


    The above should allow 3 months of logging, hopefully if it works and it will or should use 1277MB (just over 1gb) of storage space and consume ~200mb of ram while doing so


    ------------------------------------------------------------------


    If you dont have netdata installed and want to see your own stats you can easily install it


    If libreelec just install Docker from the official kodi addons and paste the code below

    if distro based os just follow the instructions at official docker docs for your distro https://docs.docker.com/engine/install/ once you select the distro and CPU architecture its a copy an paste of a few commands


    then a simple copy an paste the code below into the terminal then hit enter, docker pulls netdata in and sets it all up for you


    code below is good to go on LE but distro you should change the paths /storage/dockers to suit the rest should be ok



    Once its done its stuff run 1 more

    Code
    docker start netdata


    you should now be able to go to http://your-pi-ip-address:19999 and see your stats being collected :thumbup:

    With recent events and 5 terminals open i thought id run a quick check on it all, system settings reporting over 110 days total uptime with 26 days system uptime due to power shutdown.


    with netdata being installed a while ago i thought id have the 4 month of stats and hoped to possibly see the video card failing but unfortunately i didn't enable db logging back then so only 30 days was possible X( but would of been cool to see


    System Recap: Pi4 switched on 24/7 running Libre-Elec 9.2.6 - Main Network media player - Hyperion using Internal Grabber @1080 - PiHole filters all home network traffic.


    Overall its been running buttery smooth - video capture card issue aside that was just more annoying than anything else, everything ticked over as expected, Hyperion just as stable as ever and never any need to do anything apart from toggle the desired capture device on or off when card was failing.


    Since upgrade to Alpha10 everything looks normal and functioning as expected except better ^^ time will tell though


    Media play is heavily used but specs seem above board, cpu avg of 40% utilization, avg load of 1.5 and runs at around 2gb ram, its hardly breaking a sweat so shouldn't need to worry about any cooling issues.


    nothing sticks out really except that entropy levels were getting a tad high, with it running pihole and LE using 4.19 kernal i investigated increasing it but with 3413 avail and maxing out at times @ 3200 there's not much that can be done without building a custom Libreelec - would be easier to install haveged if it was a distro but as its not plus it is not constantly maxing out i will leave it as it is.


    Sd card still has plenty of space and no signs of any bottlenecking so Netdata DB will be going ahead ^^ few screenshots of graphs attached


    LE 10 is making good progress to and hopefully there will be a stable version of that out soon - Hopefully be some nice eye candy changes to the UI :/

    james2brite excluding the fact you are hijacking Mr.Shakes thread im really struggling to grasp why you are so hell bent on reducing your costs as low as you can possibly go when your scrimping on the wrong components, not only is the 3a slower but it only has 1 usb port. Yet you have went all out and are praising your capture card to the nines and in an ideal world youd want to be running that on usb3 to achieve the best possible results - USB3 is something that the pi3b also lacks despite it having a blue port they share the bus speed across the rest of the ports/ethernet


    If you are planning to include this as a component to your high end projectors would you not want peace of mind that when its all up and running there is no bottlenecks instead of asking a low powered computer to run the Hyperion webserver that can be CPU hungry at times, plus deal with video content up to 4k and produce the SPI or PWM signals to the LEDS


    Maybe its time to listen to some of the advice you have already been given or do some research on the numerous posts that are in the forum already and workout a gameplan that suits what your trying to acheive.