Open GeorgeIoak opened 5 years ago
Getting closer...
I modified the PP server to listen on port 6454 and that got me to this message so at least it's actually receiving data it just doesn't like the format,
Expecting multiple of {1 + (rgb)*128} = 385, but got 526 bytes (leftover: 141) Expecting multiple of {1 + (rgb)*128} = 385, but got 526 bytes (leftover: 141) Expecting multiple of {1 + (rgb)*128} = 385, but got 526 bytes (leftover: 141)
Hello, good morning. Please I want you to help me to write an stream file for video-viewer. Eg: mickeyminnie.stream
You just need to follow the instructions on this page. You just run the led-viewer app with the output switch (-Oanimation-out.stream)
Hi @GeorgeIoak, Did you figure out how to send a sequence from xlights to pixel-push? I'm basically at the same spot that you described in your last comment. Any suggestions?
Sorry, I honestly can't remember where I left off after all this time.
Thanks for the reply @GeorgeIoak. No worries. I learned about Falcon Pi Player (FPP) and that met most of my needs. Between using FPP with xLights and video-viewer, for live video, in @hzeller /rpi-rgb-led-matrix, I'm all set.
Before I saw your Pixel Pusher repo I used your matrix repo and successfully played GIFs on my setup of 4 panels using the following:
./led-image-viewer -C --led-rows=64 --led-cols=64 --led-gpio-mapping=adafruit-hat-pwm --led-show-refresh --led-chain=4 -l100 --led-pixel-mapper=U-mapper --led-rgb-sequence=BGR --led-slowdown-gpio=0 --led-pwm-lsb-nanoseconds=50 /share/mickeyminnie.stream
Now I'm trying the following in the PP directory:
./pixel-push -C --led-rows=64 --led-cols=64 --led-gpio-mapping=adafruit-hat-pwm --led-show-refresh --led-chain=4 -l100 --led-pixel-mapper=U-mapper --led-rgb-sequence=BGR --led-slowdown-gpio=0 --led-pwm-lsb-nanoseconds=50 -i wlan0 -a 1,1
Using Wireshark I can see that Xlights is sending data to the Pi running PP
When I start PP I get the following:
102.2Hzwlan0: IP: 192.168.10.121; 100.0H:27:eb:02:99:31 Display: 128x128 (128 pixels each on 128 strips) Accepting max 3 strips per packet (with UDP packet limit 1460). discovery packet size: 202 101.4HzPress <RETURN> to shut down (supply -d option to run as daemon) Starting PixelPusher discovery beacon broadcasting to port 7331 Listening for pixels pushed to port 5078
With XLights you can just tell it the IP address and Universe s that's what I've done but you can also specify the "network" and "subnet" but I haven't done that (those options are only available if you choose to set those up. I'm not quite sure what it's expecting so I configured just the IP address and universe.I can't post yet on the XLights forum so I thought I'd start here. I'm not sure how the port information is selected but it appears from the Wireshark capture that XLights is sending to port 6454 and PP is listening to port 5078 so I'm hoping that's the issue but I don't see an option in either software package on how to choose the port to use so maybe that's something automatically selected behind the scenes?
Hopefully you can help shed some light on this for me!