Configure a layout with the sum of all leds installed on all hardware instances

undeporaki · 3. März 2022

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?

pclin · 4. März 2022

You only need the LED layout for each instance, the way you can create the layout I posted to you.

Delete the blacklisted LED's before you save.

I had already written that Hyperion reads the number of LEDs from WLED.

regards pclin

undeporaki · 4. März 2022

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

pclin · 6. März 2022

For 864 LEDs in a row, your grabber should now have a resolution of at least widht 864 x height XXX for an optimal result.

With the 1200 LEDs or 2880 LEDs that you wanted to have, that would be 1200x XXX or 2880 x XXX for the grabber, otherwise several LEDs would always have the same color.

regards pclin

undeporaki · 7. März 2022

Yes, I already have this into account so I will have a switch+capture interface allowing 4k resolution. For me is no needed HDR10 (LED modules not really support it) so It will runs with a standard 4k capture interface.

Thanks by your appointment!

pclin · 7. März 2022

Resolution over 720 not work with RPI very well.

Latency and CPU overload!

regards pclin

undeporaki · 7. März 2022

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

pclin · 7. März 2022

Check with top or htop.

regards pclin

undeporaki · 7. März 2022

It outputs between 23% to 38% load cpu. Capture device conguration is:

For sure if I reduce capture resolution cpu reduces, but I guess it would be fine.

Best regards,

undeporaki

pclin · 7. März 2022

These are amazing values, which grabber are you using?

Can you please post the results of

usb-devices

v4l2-ctl --all

v4l2-ctl --list-formats-ext

regards pclin

undeporaki · 7. März 2022

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

pclin · 7. März 2022

Thanks!

A 'normal' grabber with MACROSILICON chip, most users at 1920x1080 have significant delays and full CPU utilization.

gruß pclin

undeporaki · 8. März 2022

I am using latests Hyperbian image, maybe it has any improvements (changed usb dtb or similar to have more throughput...)

best regards,

undeporaki

pclin · 8. März 2022

That can't actually be due to the Hyperbian image, the RPI SoC would have to deliver more performance for that.

With my Amlogic S922X - 53,000 DMIPS box, this is possible with similar values.

regards pclin

Jetzt mitmachen!