hey guy. just bounce back to version 2.016.
i had the same behaviors after i "upgraded" to 2.1.1
after the bounce back to 2.016 everything was back to normal, i made a topic about it
hey guy. just bounce back to version 2.016.
i had the same behaviors after i "upgraded" to 2.1.1
after the bounce back to 2.016 everything was back to normal, i made a topic about it
my advice is, roll back to the 2.016 version.
I have the same setup as you and after the update from 2.016 to 2.1.1 I had problems with Hyperion.NG restarting every 5 minutes.
I also have pi 3b and APA102 ledcontroller in use.
did you connect common GND to psu/ledstrip and module?
60l/mtr pointed to a white wall from the TV should be sufficient.
make sure you use a powerfull psu, from Meanwell.
and inject the DC power at least at begin/middle/end at the ledstrip, to have nice whites on your 83" TV 📺
after updating Hyperion 2.016 to 2.1.1 Hyperbian distro on Raspi 3b it suddenly stops after approx 5 min and restarts all the time.
Before the update occured i never had any problems with the old distro
So i did a "downgrade" back to 2.016
now that behaviour stopped, after this problem is resolved i go back to latest version 2.1.1
maybe its something for dev's to dive into
i didn't make any backup of the Json or altered the Json config, just install over the old version.
hello,
just upgraded from 2.016 to 2.1.1 Hyperbian distro without any hassle on a Raspi 3b with
Hyperion-2.1.1-Linux-armv7l.deb package.
so problem probably lies in your updating packets/drivers for the Raspi.
i ain't a Linux expert whatsoever, but i know that you can update the library (did it myself) with Putty SSH really easy.
after that everything worked fine.
i had also problems with HDMI driver on the raspi, with updating library everyting worked (years ago already)
update: after updating Hyperion 2.1.1 it suddenly stops after approx 5 min and restarts all the time.
So i did a "downgrade" back to 2.016
now that behaviour stopped, after this problem is resolved i go back to latest version 2.1.1
but i didn't have any issues with the USB grabber not working.
hello.
You changed the router, after that is doesn't work anymore >> so problem is probably caused bij LAN problems.
check IP adres of your TV / Wled and make them static BIND > in router bind MAC to DHCP IP adres.
Make sure after that you can reach Wled esp32 with the app from Aiircookie >> SWLED on Github
as last, in Wled app, go to settings and delete Mdns adres in the IP section of the esp32 ( you don't need that)
also set FPS to 25 frames in Wled
Use the wizard for Wled again in Hyperion
give Hyperion the "server" a new IP adres and BIND it as step 1
Open the android grabber and connect.
if not, then open router settings and make sure port 19445 PROTO is "open" to/from hyperion IP server
if everything is okay it should work.
now i am facing the same problem to be solved. I want to capture the frame in the Smart TV system, but I don't find any efficient way. I tried hyperion-andriod-grabber mentioned before, but It can't work for my TV.
directly grabbing on tv depends on verndor/brand. Mostly doesn't work, only hypertizen i think atm
I was talking about a Android mediaplayer device, on that you can install Play store apps from 3th parties, that you connect with HDMI to the TV
thatswhy i said it MOSTLY will not work. In some cases (depends on setup and AVR) it will
there's always the exemption that will prove a point.
btw, I am really curious what will happen over time with the HDCP 2.1 protocol because you are using different HDMI ports to split.
let's see.
ambilight ftw 🙌
EDID and HDCP trough a receiver can be a nightmare.
hope with you it ain't 🙌
Which HDMI 2.1 grabber could I use? Should I use a 2.1 HDMI Splitter with an EDID Emulator and some sorts of downscaling?
I'm kinda at a loss.
my man.
splitting a source with a receiver mostly doesn't work. you need a EDID and HDCP capable splitter/scaler for that, if it ain't working
just order a Xolorspace 61121 for instance and connect main HDMI output from receiver at input splitter/scaler.
then split 4K to tv and 1080p to the Raspi
grabbed image in HA works but, it's a standstill image so unusable.
fwi with my settings it is and played around with HA and hyperion,
so you see image but really big delay or freeze frame.
count them with your fingers/eyes. then write the numbers down and use a new instance.
i had the same problem, blacklisted leds in 2.016 build you can't unlist and stay off.
only possibility for me was to count them and program them into a new instance after rebooting.
goodluck!
the "lag" can be caused by LAN. Make sure the streaming port 19444 (or other) is open on TCP/UDP and not being intervened by your router
use a new instance and remove the old one, that did it when is was diddling with blacklist
ik like to hear more how you achieved this result with LVDS. No more DRM problems with this method?
i am intrigued
Any more ideas to my request? Up to now I just get a dot as answer. What ever that means.
Best regards
i wrote something and removed it, wasnt good info... because you cant delete a post i put a dot.
hope that clarifies it.
first time it took me 2 weeks to get Hypercon to work with the Raspi, so yes we all been there.
what does the debug log say? Put it here or wit pastebin