Beiträge von undeporaki

    Tested your setup for 2 wled instances 360 leds/each, running smoothly. I guess I missed the part to put an "input position". Seems that this setting tells layout to start Led0 on the top/right corner and then all leds go in order.


    Thanks by your help pclin, one more time! I would have to invite you a beer!


    Best regards,

    undeporaki

    Hello!


    I need to install ambilight on 3 of 4 sides of a screen. I would try to set 2 wled instances, each controlling 360 leds. Total led count would be 720. Now, I am trying to configure layout for both instances but the problem is assign leds from 1 to 360 to one wled and from 361 to 720 to another because classic layout doesn´t allow to change individual led numbers, so up. Here a capture from my desired setup:






    what I have now is: (a complete mess)

    TOP: (left to right) led0 to led 270

    LEFT SIDE (bottom to top) 540 to 720

    BOTTOM ( right to left) 271 to 539



    I would try to setup manually a custom layout from file and see...


    Best regards,

    undeporaki

    Hello pclin.


    device is this:



    output from commands are:

    usb-devices


    T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1

    D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1

    P: Vendor=1d6b ProdID=0002 Rev=05.10

    S: Manufacturer=Linux 5.10.63-v7l+ xhci-hcd

    S: Product=xHCI Host Controller

    S: SerialNumber=0000:01:00.0

    C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA

    I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub


    T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 4

    D: Ver= 2.10 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1

    P: Vendor=2109 ProdID=3431 Rev=04.21

    S: Product=USB2.0 Hub

    C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA

    I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub


    T: Bus=01 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#= 4 Spd=480 MxCh= 0

    D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1

    P: Vendor=534d ProdID=2109 Rev=21.00

    S: Manufacturer=MACROSILICON

    S: Product=USB Video

    C: #Ifs= 5 Cfg#= 1 Atr=80 MxPwr=500mA

    I: If#=0x0 Alt= 0 #EPs= 0 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo

    I: If#=0x1 Alt= 2 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

    I: If#=0x2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio

    I: If#=0x3 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio

    I: If#=0x4 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid


    T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 4

    D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1

    P: Vendor=1d6b ProdID=0003 Rev=05.10

    S: Manufacturer=Linux 5.10.63-v7l+ xhci-hcd

    S: Product=xHCI Host Controller

    S: SerialNumber=0000:01:00.0

    C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA

    I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

    pi@HyperBian:~ $ v4l2-ctl --all

    Driver Info:

    Driver name : uvcvideo

    Card type : USB Video: USB Video

    Bus info : usb-0000:01:00.0-1.2

    Driver version : 5.10.63

    Capabilities : 0x84a00001

    Video Capture

    Metadata Capture

    Streaming

    Extended Pix Format

    Device Capabilities

    Device Caps : 0x04200001

    Video Capture

    Streaming

    Extended Pix Format

    Media Driver Info:

    Driver name : uvcvideo

    Model : USB Video: USB Video

    Serial :

    Bus info : usb-0000:01:00.0-1.2

    Media version : 5.10.63

    Hardware revision: 0x00002100 (8448)

    Driver version : 5.10.63

    Interface Info:

    ID : 0x03000002

    Type : V4L Video

    Entity Info:

    ID : 0x00000001 (1)

    Name : USB Video: USB Video

    Function : V4L2 I/O

    Flags : default

    Pad 0x01000007 : 0: Sink

    Link 0x0200000d: from remote pad 0x100000a of entity 'Processing 2': Data, Enabled, Immutable

    Priority: 2

    Video input : 0 (Camera 1: ok)

    Format Video Capture:

    Width/Height : 1920/1080

    Pixel Format : 'MJPG' (Motion-JPEG)

    Field : None

    Bytes per Line : 0

    Size Image : 4147200

    Colorspace : sRGB

    Transfer Function : Rec. 709

    YCbCr/HSV Encoding: ITU-R 601

    Quantization : Default (maps to Full Range)

    Flags :

    Crop Capability Video Capture:

    Bounds : Left 0, Top 0, Width 1920, Height 1080

    Default : Left 0, Top 0, Width 1920, Height 1080

    Pixel Aspect: 1/1

    Selection Video Capture: crop_default, Left 0, Top 0, Width 1920, Height 1080, Flags:

    Selection Video Capture: crop_bounds, Left 0, Top 0, Width 1920, Height 1080, Flags:

    Streaming Parameters Video Capture:

    Capabilities : timeperframe

    Frames per second: 25.000 (25/1)

    Read buffers : 0

    brightness 0x00980900 (int) : min=-128 max=127 step=1 default=-11 value=-11

    contrast 0x00980901 (int) : min=0 max=255 step=1 default=148 value=148

    saturation 0x00980902 (int) : min=0 max=255 step=1 default=180 value=180

    hue 0x00980903 (int) : min=-128 max=127 step=1 default=0 value=0

    pi@HyperBian:~ $ v4l2-ctl --list-formats-ext

    ioctl: VIDIOC_ENUM_FMT

    Type: Video Capture


    [0]: 'MJPG' (Motion-JPEG, compressed)

    Size: Discrete 1920x1080

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1600x1200

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1360x768

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1280x1024

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1280x960

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1280x720

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1024x768

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 800x600

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 720x576

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 720x480

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 640x480

    Interval: Discrete 0.017s (60.000 fps)

    Interval: Discrete 0.020s (50.000 fps)

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    [1]: 'YUYV' (YUYV 4:2:2)

    Size: Discrete 1920x1080

    Interval: Discrete 0.200s (5.000 fps)

    Size: Discrete 1600x1200

    Interval: Discrete 0.200s (5.000 fps)

    Size: Discrete 1360x768

    Interval: Discrete 0.125s (8.000 fps)

    Size: Discrete 1280x1024

    Interval: Discrete 0.125s (8.000 fps)

    Size: Discrete 1280x960

    Interval: Discrete 0.125s (8.000 fps)

    Size: Discrete 1280x720

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 1024x768

    Interval: Discrete 0.100s (10.000 fps)

    Size: Discrete 800x600

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Interval: Discrete 0.200s (5.000 fps)

    Size: Discrete 720x576

    Interval: Discrete 0.040s (25.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Interval: Discrete 0.200s (5.000 fps)

    Size: Discrete 720x480

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Interval: Discrete 0.200s (5.000 fps)

    Size: Discrete 640x480

    Interval: Discrete 0.033s (30.000 fps)

    Interval: Discrete 0.050s (20.000 fps)

    Interval: Discrete 0.100s (10.000 fps)

    Interval: Discrete 0.200s (5.000 fps)




    Best regards,

    undeporaki

    I fully tested with 1080p and for my first aproach of 900 leds it is working ok, not too much overhead. Also, take into account that it is a very long strip and it is not needed to have a lot of accuracy regarding match leds/resolution. Also, it will be mounted so far from people eyes so it would be difficult to distinguish if one led strip is matching led video or not.


    Regarding latency, as I am using rpi as a AP all bandwith is for wleds. No internet or other services are running.


    Best regards,

    undeporaki

    Hello Lord-Grey.


    Finally, I understood about led count and lyout management. I have a simple mind so I would prefer to have a "total led count" on an unique layout panel and assign there the leds used bay any interface... but it is ok, no need to make an effort to change that.


    Regarding network configuration, I have just configure my raspberry running hyperion as an AP so no problems with IPs as I can control all devices on the AP network.


    ummm, you said we can use hostnames, but I do not why hyperion doesn´t find wled devices if I do not put the IP. I will search the forum about.


    Thanks!

    Solved! thanks for your support pclin.


    I did not understand the step of "remove" blacklisted leds". Is not only config blacklisted leds but it is needed to remove those leds from text json array to let there only the led count for wled interface. This allow to save in the correct way.


    I will resume for other people who needs setup in a similar way:


    1) Set any number of leds interface. Every will have installed physical led count.

    2) go to LED Output for first instance. Set led count in Classic layout.

    3) blackilist no needed leds

    4) in text area, remove blacklisted leds. Update+Save. Saving show succesfull.

    5) repeat from 2) with other instances.


    PD: Is not a very intuitive way to do, ahahaha...but it works. ^^^^


    Best regards,

    undeporaki

    Hello! I am doing a setup as related on this post (I started with the hardware setup, ahhaha): Options for a huge LED screen (>20meters led strip)

    . Thanks to pclin by your help!


    Now, I am stucked configuring the layout for each instance, and here I have this problem. Some kind of trick has to be done to send each group of led to every hardware interface because It is impossible (at least for me) to set a layout with more leds than the leds of one instance.


    I only have one hdmi input and I want to split upper side in many hardware instances (all with wled). I am doing a test case with only 2 interfaces, 30 leds each. I want that layout uses the sum of them, 60 leds on the upper side of the video frame. But, here is the problem, layout configuration only wants 30 leds, not the total installed leds.


    pclin told me about using text configuration + blacklist leds but no way to save configuration, copy&paste text layouts, but no luck. I saw many threads about saving layout (only save button, not touch preview button...) but no work at all.



    BTW, I am using latest release, 2.0.12


    Is there any way to tell hyperion about total installed leds and split them to every instance?

    Hello again, no luck yet. I set every instance with each layout file and set blacklist too for every instance but the problem is that do not allow to save. So, when I enter again to any instance, all data of the layout file seems overwritten and limited to each 432 leds...


    If I press save button, it shows an error pop-up and if not, no changes applied.


    Do you know if there is a way to force this setup (writing config file through a terminal or so on)?




    I am using latest hyperbian image on a rpi4, maybe latests version has a bug here?

    Version2.0.12
    Build(HEAD detached at 2.0.12) (GitHub-dc6aa4d/df14958-1637501177)
    Build dateNov 21 2021 17:25:12

    Hello! I have tested a few things using ESP32 and WLED firmware. Best work for me was using "wled" as hardware controller, I managed 432 leds with on esp32 and using "udpe131" seems to act as an artner node and limit to 170 leds/universe. With "wled" no problems to control these number of leds. Speed and latency are good enough for my application.


    Now, I have problems setting up 2 instances of 2 ESP32 wled controllers. Maybe I misunderstand how pclin explained it because I will try to setup an layout screen for 864 leds, in order to set 432 leds each wled controller.... but it shows an error an doesn´t allow to do it.


    Maybe it is on another part of configuration panel, I must looking for.


    Best regards,

    undeporaki

    Thanks by your reply, pclin. Tomorrow I will test your proposal, I have a few esp32 here and some led strips to start testing setup and speed.


    Although, I am worried about many ESP on same network related to IP changed on reboot (if dhcp) and so on. If IPs changes all image to leds would be wrong. I would need to modify WLED fw somehow (static IPs, unique identity...) and even hyperion to know about ID and no about IPs. Let me think about...


    Best regards,

    undeporaki

    Hello guys, I am new to this forum and I start asking about a "strange" setup. The goal is to provide external ambilight to a led screen with about 20 meters lenght. We are talking about 20x60=1200 ws2812b leds as I only need ambilight on the upper side of the screen. This would be the minimum acceptable but I want to drive more leds using led strips of 72 or even get 144led/m to perform a very powerful impact to the audience (144x20: 2880 leds)


    I am doing some testing with different methods provided by hyperion (artnet, pwm gpio...) but it seems some kind of limit on maximum led count. For example, using artnet I cannot see how to setup many different universes (needed to manage too much leds) so it is not a way to do it.


    I think this problem would be the same using an usb-dmx interface, no way to setup many of them?



    Ideas are welcome!


    Best regards.