Try the Sabaat version on Github.
Its separately installable, called Windows screen grabber for Hyperion
Try the Sabaat version on Github.
Its separately installable, called Windows screen grabber for Hyperion
Which audio extractor?
From Ali express i look up yhe type (sold out, item not available anymore >>> it's something like the Feintech audio extractor
Yes everything is CEC switched.
so Nvidia shield is operating TV and Receiver, also TV is Operating receiver
CEC Is very strong 💪
note: I only did this because of my 1080p receiver, with 4k receiver I am going to do it way differently
Onkyo TX-NR1007 has HDMI 1.3a and cannot do ARC and certainly not eARC.
I know thats why i connected the audio extractor to HDMI port 2 on the tv (E-arc )
Also only works when connected to HDMI Out of the receiver
Why a Loop Out Grabber?
A normal grabber directly to HDMI Out 2 from the receiver
I am not using the LOOP feature, its connected ro HDMI port 1 out of the receiver.
This is the only way I could connect the 4k tv to my 2009 Onkyo 1080p and still have Hyperion.NG on al 6 channes.
So believe me it works
the Xolorspace would not be necessary.
I started with that one and a analog grabber so i sticked with it and increase the Installation
Do you think that this will work?
it could, but maybe you interfere with HDCP and such, that really can be a bitch to sort out.
this signals : CEC/HDCP/ARC or E-arc >> what do you want to do with those?
HDCP you can't avoid, so you need a good route from splitter and switch.
i show you my schematics how i made it on a Onkyo Receiver 1080P >> and it works with HDCP/CEC and E-Arc
its the last image uploaded
Here's the screenshot:
PClin is right on the money,
there is your problem, buy a coffee black 2.0 RULLZ LOOP device without the audio jack option.
or try this,
you can try to login as expert in Hyperion and then alter the encoding format but thats a stretch..
It's working but still doesn't register all the colours correctly
strange, seems hardware to me
are you sure RGB (BGR) is set correctly? did you use the wizard for colours?
and did you power the ledstrip from both sides? > it means from beginning and end of ledstrip
connect:
GND to GND
+5volts to +5volts
Red = Blue and when I do pink it is blue.
i think RBG setting is off, use the wizard please
and then the spots..
What kind of type of spots they are?
I mean for what type you want to change them into HUE?
so i need the Philips hub for getting it to work?
the bulbs are controlable with the app and Alexa but Hyperion needs the HUE Philips HUB to controll the lights, in addition you can use the HUE app to but the moment Hyperion takes over you can't use the app at that moment ( you will see the sliders going up and down)
Thx für the answers, so i think these are the right obes:
you have HUE starter kits that have the HUB and bulbs in one package.
you can decide what you want to use, you have types as GU10 spots but also normal E14 and E27 bulbs in HUE
Controller settings
Hardware LED Count - 150 >>> put to 300
RGB byte order - GBR
Refresh time - 10000 ms >>>> put to 1000
SPI path /dev/spider0.0
Baudrate - 6000000 >>>> put to 5900000
White LED algorithm - White off
then:
above 255 leds you have to extend the SPI bus,
you probably reached maximum of packets SPI can send,
you need to ad spidev.bufsiz=1024000 to cmdline.txt,
example:
Code
Code
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=5728b712-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait loglevel=3 consoleblank=0 plymouth.enable=0 spidev.bufsiz=1024000
cmdline.txt is a file on the SD card, boot section > spacebar is needed at last line like example otherwise Raspi can not boot anymore
it have to be at the end of the line, then reboot
then check in terminal (SSH) if size has altered, therefor copy paste the big text..
pi@Hyperbian:~ $ cat /sys/module/spidev/parameters/bufsiz
result have to be 1024000 in next line after reboot
this should activate the SPI controller fully
I see already what's the problem mate
your problem is hardware, you haven't connected the 2 PSU together and made a common ground.
connect the GND pin ( better is 2 of them) together and attach it to the V- terminal of the Meanwell PSU
goodluck!
to give you a idea how you also can do it >>> this setup is only 1 PSU
If you have the HUB, in Hyperion you can implement the lights that are programmed in it.
Every HUE light is a led in Hyperion in led layout.
If you still have questions then shoot
Spots HUE type I used is GU10, thats a normal 230~v lamp
Or is there a better solution?
you can use the Hyperion screen grabber from Sabaat on windeos PC>>> then you can grab the monitors separate and send them trough the LAN to the PI
then for each monitor you create a instance and using a diffrent Hyperion server port
so
instance 1: PROTO BUFFER port 19445 (default port)
instance 2: PROTO BUFFER port 19446
for this setup you need a windows PC and LAN
goodluck!
Take a look at my topics (under my name) to see how I made a ledframe for 65” tv
hey,
It means that you have to ZOOM in until you see only the TV screen, you can only do that with cctv cameras. I did a test with those and needed a 11mm lens on a standard color cctv camera with 3,5 mtr distance. The results after tweaking were mediocre at best.
So you have to put the USB camera as close to the TV screen as possible, then look at the grabbed area in Hyperion.NG You should see only the screen to make BBD work.
Screen has to be in center of the grabbed area. Means that BBD only works when image is same as grabbed area
The ledcontrollers with build in hardware that runs the protocol to the LED-lights.
for the Meross bulbs, can't find anything that states the used protocol or that these bulbs are runned by a HUB.
hyperion can't run the bulbs if not runned by a HUB period.
Even if they are using a HUB then there's no Apple Homekitt or something similar in the ledcontroller section of Hyperion.
set hyperion as Level Expert then you have all the options
Go to upper right of WebUI, change level from standard to expert