Ambilight from any video source with a Raspberry (part 3)

A couple of months ago I purchased a HummingBoard-i2eX, a raspberry-like board with a more powerful i.mx6 chip. Since OpenELEC, Geebox and Raspbmc are actively supporting this board, I decided to try to use it as my main HTPC instead of my raspberry.

The main problem were the leds (I will talk about the other one in the next paragraph), Hyperion does not support boards different from the Raspberry Pi, so instead of messing with Hyperion source code, I decided to use the raspberry to just handle the leds. The nice thing of this setup is that you can still use the OpenELEC installed on it, so you do not have to buy another board just because you want the Ambilight while playing with your console or watching video from another device.

The parts list

As usual, let us start with the part list. I assume you already have a raspberry with working leds, if not, look at part one and part two of this series to build your own.

Beware of a couple of things. With the splitter in place, the CEC stopped working, so you cannot use your TV remote to pilot Kodi (ex XBMC and used by OpenELEC 5.0 rc3). I did not think about it when I purchased the parts, but after some searches, I found there are some that declare to support it, so keep it in mind when you buy your parts. For me is no big deal, because I have the infrared port of the hummingbird (look here on how to configure it) and actually I use my tablet or phone.

The second thing is the video capture, if you do some searches, you will find that not all chipsets are supported by the Linux kernel 3.11 and the one, suggested by many, is the Fushicai chip. Unfortunately, not all EasyCap use the same chipset, so you may buy a device that will not work. I purchased two different USB video grabbers (the other one was the August VGB100) and just the EasyCap works, so be careful when you buy yours.

The HDMI splitter, the video converter and the video grabber are needed to pass the signal to the Raspberry, while the HDMI switch is necessary only if you plan to use more than one video input. In my case, I use the input from the PS4 and the Hummingboard so, if you use your raspberry with OpenELEC and not just for controlling the leds, you can skip this purchase.

Here are the photos of the pieces.

 

WP_20141220_002 WP_20141220_005
WP_20141220_009 WP_20141220_006

WP_20141220_011

Check if the system correctly sees the video grabber

The first thing to do is to be sure that the system correctly see the video grabber. To do that, connect to OpenELEC (to learn how look at part 2) and type these two commands:

lsusb
ls /dev/video*

You should see your video grabber listed (in my case the Fushicai USBTV007) and then the video0 mounted in /dev directory

UsbList

Configuring Hyperion with OpenElec

Now that we have assembled all the pieces, we need to configure Hyperion to handle the video input.
The commands that I will show here are for OpenELEC, if you are using Raspbmc, you should use different commands (this page should help).

Hyperion support the v412 grabber, so we just need to activate it in our configuration file.

Open the hyperion.config.json file and add, at the end, the following lines of code:

/// Configuration for the embedded V4L2 grabber
///  * device          : V4L2 Device to use [default="/dev/video0"]
///  * input           : V4L2 input to use [default=0]
///  * standard        : Video standard (no-change/PAL/NTSC) [default="no-change"]
///  * width                : V4L2 width to set [default=-1]
///  * height               : V4L2 height to set [default=-1]
///  * frameDecimation      : Frame decimation factor [default=2]
///  * sizeDecimation       : Size decimation factor [default=8]
///  * priority             : Hyperion priority channel [default=800]
///  * mode                 : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default="2D"]
///  * cropLeft             : Cropping from the left [default=0]
///  * cropRight            : Cropping from the right [default=0]
///  * cropTop              : Cropping from the top [default=0]
///  * cropBottom           : Cropping from the bottom [default=0]
///  * redSignalThreshold   : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]
///  * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]
///  * blueSignalThreshold  : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]
"grabber-v4l2" :
{
    "device" : "/dev/video0",
    "input" : 0,
    "standard" : "no-change",
    "width" : -1,
    "height" : -1,
    "frameDecimation" : 2,
    "sizeDecimation" : 8,
    "priority" : 800,
    "mode" : "2D",
    "cropLeft" : 0,
    "cropRight" : 0,
    "cropTop" : 0,
    "cropBottom" : 0,
    "redSignalThreshold" : 0.0,
    "greenSignalThreshold" : 0.0,
    "blueSignalThreshold" : 0.0
}

Remember to put a comma on the line preceding this piece of code as in the picture:

Hyperion-v412 config

Reboot your Pi and we are ready to face the tricky part.

Setting the correct crop size and other params

The image coming from the video grabber will surely have some black border, what we need to tell Hyperion, is how much to crop from every border. Before we start, we need to choose a video frame or an image bright enough to easily distinguish the black border from the real image.

Let us start by stopping the Hyperion service or we will not be able to take the screenshots needed for our calibration. Just type:

killall hyperiond

Before executing the next command, move to a directory that you can access with your pc client, because Hyperion will save the screenshot in the correct directory.

I choose the screenshot directory because is already shared by OpenELEC so I do not have to manually copy the files.

Once you are in your preferred directory, copy and paste this command:

LD_LIBRARY_PATH=/storage/hyperion/bin /storage/hyperion/bin/hyperion-v4l2 /storage/.config/hyperion.config.json --crop-top 0 --crop-left 0 --crop-bottom 0 --crop-right 0 --size-decimator 8 --frame-decimator 2 --screenshot

You should end up with something like in the picture below:

Hhyperion screengrab

The result will we be like this

totalcmd_screen

The sizeDecimator specify the quality of the image, higher the number less the quality and, obviously, its size. The default value is eight and is acceptable. The image size is also very small (about 9kb).

Now that we have the image, we can adjust the crop params to get a clean image. For me, the final configuration is this one:

LD_LIBRARY_PATH=/storage/hyperion/bin /storage/hyperion/bin/hyperion-v4l2 /storage/.config/hyperion.config.json --crop-top 40 --crop-left 50 --crop-bottom 0 --crop-right 30 --size-decimator 8 --frame-decimator 2 --screenshot

screenshot

The image is small, but you get the idea of the result you should obtain.

Now we just need to update the configuration file with the values discovered and reboot the raspberry.

In case you want more precision, you can lower the sizeDecimator value, but remember that it will consume more CPU. In my test using a value of four I got a 27KB image and no noticeable differences. I cannot say if the OpenELEC playback is compromised somehow, because I use it only for the leds. It would be nice to hear from yours experiments.

Here is a video of Far Cry 4 from my PS4, I can say that playing with the leds on, is somehow more immersive.

If you need it, here you can download my complete configuration file.

Android application

As a plus, you can download the android app here or here, if you want to support the developer, and you can use the led as a mood lights.

If you have changed the path in the config file, as I wrote in part 2, you should also have all the effects available.

 

  • Pingback: Ambilight with Raspberry Pi and OpenElec (part 2)()

  • Pingback: Configuring an IR remote control with OpenElec 5.0()

  • chad cole

    Do you know if this is compatible with a pi that’s B+? I can’t find any clear info anywhere.

    • It should works without problem. I recently switch to the new A model (less power consumption) and the first 26 pins are the same as the ones of the model B. So the model B+ should not have any problem too.

  • xia

    Thanks for the guide, very useful. I’m trying to configure openelec but I get a constant stream of frame too small error when trying to get the screen shot even with a video input from hdmi present. I’m wondering if it’s because I haven’t connected anything to the SPI connector as the LEDs haven’t arrived yet, could you try and see if you can still get a screenshot without anything connected to the SPI?

    • I do not think it should change anything, because the command line to take the screenshot does not use the leds (as far as I know). The error you are getting is because the software can not get enough informations from the grabber. Here is a discussion about it: https://github.com/tvdzwan/hyperion/issues/12. I will try anyway what you are asking when I get back home and let you know.

      • xia

        Thanks for the reply, I had the feeling it wasn’t the spi causing the problem. STK1160 with 256mb model bi pi, thought this setup should have worked fine.

        • HI, I confirm that everything work without the spi connected. BTW I’m using a Model A and works perfectly fine

          • xia

            I am using a USB wifi dongle, wonder if it’s hogging the bandwidth on the usb hub

  • Reddemise

    Hello there,

    I loaded your configuration and the lights made its normal turn on, but when I tried to screenshot and it froze… I connected the video grabber to my windows pc and the video easy cap works fine.

    Step up:
    power hub for the easy cap.
    raspberry pi B+
    openelec 5.0.1 (because i can recognize STK1160)
    WS2801 LED

    Freeze frame:

    V4L2 width=720 height=480
    V4L2 pixel format=UYVY
    V4L2 grabber signal threshold set to: {0,0,0}
    V4L2 grabber started

    • Hi, are you sure the video grabber has the fushicai chip? the xbmc service is turned down? Another try you can do is to connect the grabber directly to the raspberry and see if it works.

      • Reddemise

        Hi Alessandro – the chip is STK1160. OpenElec 5.0.1 claims it can support it. I bought Fushicai grabber as well and should be here tomorrow. Do you think that’s causing the issue ?

        • For what I know (and found during my searches) in the chipset that works without many troubles is the fushicai one. So I hope it will solve your problem

          • Reddemise

            Hi Alessandro – Have you ever had the chance to confirm it on B+ on OpenElec5.0.1? I know the HDMI Splitter and HDMI2AVI works since I proved functionality. The bottle neck is the EasyCap.

            I will be sure to update you tomorrow with my full setup to confirm if it works. I really apprecaite that you take time out of the day and help others set this up. Thank you!

          • Not tried on a B+, but as I wrote in another comment, I have switched to a model A and everything works perfectly. So you should not have any trouble with the B+. The first 26 pins are the same of the model B.

          • Reddemise

            Hi Alessandro, Good news the UTV007 definitely has gotten farther than STK1160. My current problem at the moment is the screen is black. I know the HDMI signals are working since im using a splitter, any thoughts?

          • Have you tried without the splitter? Still black screen?

          • Reddemise

            I got my new Fushicai grabber and i am able to finally get a screenshot!

            I did all the cropping and saved the config but i still cannot get the video to react to hyperion

            /storage/hyperion/bin/hyperiond.sh/storage/.config/h… /dev/null 2>&1 &

            but i cant get hyperiond to react to my screen… any ideas?

  • Johan

    Hi there,

    Must “mplayer” be installed on raspberry?

    I get a great screenshoot from the grabber.

    I took your hyperion file and changed the number of leds.

    But the leds are only on on bootsequence, the rainbow pattern.
    Then nothing happens.

    Any ideas?

    • If the rainbow effect start everything should works. Have you tried launching some commands from the console to see if it works? (look here for the commands http://alessandrocolla.com/ambilight-raspberry-pi-openelec-part-2/)

      • Johan

        That link is broken :/

        The leds are not responding, after the rainbow.
        Thats why I ask about the mplayer.

        Because If i can use the mplayer to show the grabbed video from the hdmi. I would be able to get the correct scheme on the leds, right?

        I read something about mplayer and show a grabbed usb material.

        But maybe i missjudged it.

        • The link is working, I do not know why the browser took also the ending parenthesis, just remove it. If the leds after the boot are not reponding, maybe for some reason the hyperion daemon closed itself. Can you check if it is runnig?

          • Johan

            What is the easiet way todo that?

            I’m a noob to raspberry 😉

            I can use the effects and set s static color with hyperion app after the rainbow startup.
            But not see the grabbed picture. Thats Very very frustating 🙁
            But i can run the screenshoot command thru putty and have a good screenshoot. However i have to run killall hyperiond to the screenshoot part.
            So i dont think that hyperion closes after the rainbow.

          • I do not know what could be then. From your description everything should work fine with the openelec image. The only way I can think of, for helping you, is to share my current installation. I can create an iso and upload it, so you can do a double check

          • Johan

            That would be Nice If you could do that 🙂

            Imorgon running out of options…

          • Reddemise

            Hi Johan – Are you using OpenElec 5.0.1? Which grabber are you using STK1160 or Fushicai?

            I am at similar step using OpenElec 5.0.1 with STK1160, but the difference is I cannot capture an image. I will get Fushicai tomorrow to report my findings.

          • Johan

            Yes, im using the openelec build that is on lightberry download page with stk1160.
            My problem in the begining was that i had no picture grabbed, like u. But that problem was solved with a powered usb hubb. I see that u already have one.
            How have u placed the hubb? It should be pi > hubb > grabber. the usb cable that is attached to the hubb are going in the pie, then a usb male,/male to the grabber.
            Have u the posibilities to test the grabber with a pc? Do that in that case.

          • Reddemise

            Originally i used Lightberry and could not get it to work (that was before powering the hub) I was fed up with it so i decided to start from scratch. I did realize Lightberry uses a “developer os” so I’m not sure what they have modified. I will go back to it with a powered hub and see if i get lucky, but it seems like i will probably run into the same issue as you. Can you share your hyperion config?

            I was able to prove functionality via windows and no issue with the grabber.

            Others have been able to get it to work with Openelec 5.0.1 + fushicai + RPI B+ I will be getting the Fushicai tomorrow and let you know if that works and then we can call it a day!

          • Johan

            That was odd, that the screenshoot freezez.
            If i were u, i should take the v4l2 part inside the json code. Paste it in after the xbmcvideocheker part.
            Then also change to PAL (If u got the input source in PAL, also change the height to 576, Because the resolution that the grabber gets is in 720×576)
            Give that a shoot.
            If the leds start flickering, change the value on the priority to 1200.

            I managed to install the newest raspbian on my rpi B+. And i got the same result, cant grabb anything for the leds. Except for a clean screenshoot. I can run the hyperion app, and set static color and effects.

            So i think it is Probably a small small part of the code that has to be changed.

            I’m ripping my hair off…

          • Hi, here is the link of my image: http://1drv.ms/1zHIu52
            I hope you can solve your issue 🙂

          • Johan

            Thanks 🙂

            Can u refresh my memory, but I have forgot how i do an Img-file from an ISO 🙂

            Then i only have to put the img to an sdcard, right? With windisk32.

            / Johan

          • it’s the image of an 8gb sdcard and you can “burn” it using win32diskimage

          • Johan

            Thanks, i’ll try that later, My 8gb card was too small 🙁 it had 1-2 mb to litle memory. So i will go and buy a 16 gb after lunch.

            But i only need to change,. Iso to img, right?

            I’m such a noob…. Haha

          • I do not think yiou should change the fil eextension. Win32diskImage should open both if I’m not mistaken

          • Johan

            Hi again,

            Problem solved, it was the width and height parameters in v4l2 section that was wrong.

            Thanks for the help 🙂

          • Reddemise

            Hi Johan, can you shed some light please? im still stuck thanks man

          • Johan

            Hi,

            Logg on with putty to your raspberry.
            You had openelec right?
            If so…
            please run:
            killall hyperiond
            and then:
            /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json (on one line)

            And please paste me the output. All things connected of course,

          • Reddemise

            Please note I have Fushicai and STK1160. result below is using Fushicai

            OpenELEC:~ # /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config

            .json

            Application build time: Jan 11 2015 16:59:41

            QCoreApplication initialised

            Selected configuration file: /storage/.config/hyperion.config.json

            ColorTransform ‘default’ => [0; 32]

            Device configuration:

            {

            “colorOrder” : “rgb”,

            “name” : “MyPi”,

            “output” : “/dev/spidev0.0”,

            “rate” : 250000,

            “type” : “ws2801”

            }

            Black border threshold set to 0.01 (3)

            Creating linear smoothing

            Created linear-smoothing(interval_ms=50;settlingTime_ms=50;updateDelay=0

            Effect loaded: Knight rider

            Effect loaded: Blue mood blobs

            Effect loaded: Cold mood blobs

            Effect loaded: Full color mood blobs

            Effect loaded: Green mood blobs

            Effect loaded: Red mood blobs

            Effect loaded: Warm mood blobs

            Effect loaded: Rainbow mood

            Effect loaded: Rainbow swirl fast

            Effect loaded: Rainbow swirl

            Effect loaded: Snake

            Effect loaded: Strobe blue

            Effect loaded: Strobe Raspbmc

            Effect loaded: Strobe white

            Initializing Python interpreter

            Hyperion created and initialised

            run effect Rainbow swirl fast on channel 0

            Boot sequence(Rainbow swirl fast) created and started

            XBMC video checker created and started

            Display opened with resolution: 1920×1080

            Frame grabber created and started

            V4L2 width=720 height=576

            V4L2 pixel format=YUYV

            V4L2 grabber signal threshold set to: {102,51,255}

            V4L2 grabber started

            V4l2 grabber created and started

            Json server created and started on port 19444

            Proto server created and started on port 19445

            BORDER SWITCH REQUIRED!!

            CURRENT BORDER TYPE: unknown=0 hor.size=0 vert.size=0

            XBMC Connection error (0)

            BORDER SWITCH REQUIRED!!

            CURRENT BORDER TYPE: unknown=0 hor.size=0 vert.size=0

            V4L2 grabber stopped

            effect finished

          • Reddemise

            updated: removed XBMC and I get:

            OpenELEC:~ # /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config

            .json

            Application build time: Jan 11 2015 16:59:41

            QCoreApplication initialised

            Selected configuration file: /storage/.config/hyperion.config.json

            ColorTransform ‘default’ => [0; 32]

            Device configuration:

            {

            “colorOrder” : “rgb”,

            “name” : “MyPi”,

            “output” : “/dev/spidev0.0”,

            “rate” : 250000,

            “type” : “ws2801”

            }

            Black border threshold set to 0.01 (3)

            Creating linear smoothing

            Created linear-smoothing(interval_ms=50;settlingTime_ms=50;updateDelay=0

            Effect loaded: Knight rider

            Effect loaded: Blue mood blobs

            Effect loaded: Cold mood blobs

            Effect loaded: Full color mood blobs

            Effect loaded: Green mood blobs

            Effect loaded: Red mood blobs

            Effect loaded: Warm mood blobs

            Effect loaded: Rainbow mood

            Effect loaded: Rainbow swirl fast

            Effect loaded: Rainbow swirl

            Effect loaded: Snake

            Effect loaded: Strobe blue

            Effect loaded: Strobe Raspbmc

            Effect loaded: Strobe white

            Initializing Python interpreter

            Hyperion created and initialised

            run effect Rainbow swirl fast on channel 0

            Boot sequence(Rainbow swirl fast) created and started

            V4L2 width=720 height=576

            V4L2 pixel format=YUYV

            V4L2 grabber signal threshold set to: {102,51,255}

            V4L2 grabber started

            V4l2 grabber created and started

            Json server created and started on port 19444

            Proto server created and started on port 19445

            BORDER SWITCH REQUIRED!!

            CURRENT BORDER TYPE: unknown=0 hor.size=11 vert.size=11

            BORDER SWITCH REQUIRED!!

            CURRENT BORDER TYPE: unknown=0 hor.size=0 vert.size=2

            V4L2 grabber stopped

            effect finished

            V4L2 grabber started

            BORDER SWITCH REQUIRED!!

            CURRENT BORDER TYPE: unknown=0 hor.size=0 vert.size=0

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

            V4L2 Grabber: Signal detected

            V4L2 Grabber: Signal lost

          • Johan

            If I were u, i should make a fresh install of the Openelec. http://img.lightberry.eu/download/OpenELEC-5.0.RPi.arm-Bplus_stk1160.zip

            I have the stk1160 version and it works now. U should give that a last try.

            did you have the kit from Lightberry?

            take the fresh installed openelec.

            Install hyperion https://github.com/tvdzwan/hyperion/wiki/Installation-on-RPi-with-OpenELEC

            After installation, restart the RPi to enable Hyperion.

            create the hyperion configfile in https://github.com/tvdzwan/hyperion/wiki/Configuration

            do the following adjustments in note++.

            *type = “lightberry” ( if u got it)

            * rate 1000000,

            then insert the v4l2 section after the xbmcchecker section, and before the json server section, like this –>

            “xbmcVideoChecker” :

            {

            “xbmcAddress” : “127.0.0.1”,

            “xbmcTcpPort” : 9090,

            “grabVideo” : true,

            “grabPictures” : true,

            “grabAudio” : true,

            “grabMenu” : false,

            “grabScreensaver” : true,

            “enable3DDetection” : true

            },

            /// Configuration for the embedded V4L2 grabber

            /// * device : V4L2 Device to use [default=”/dev/video0″]

            /// * input : V4L2 input to use [default=0]

            /// * standard : Video standard (no-change/PAL/NTSC) [default=”no-change”]

            /// * width : V4L2 width to set [default=-1]

            /// * height : V4L2 height to set [default=-1]

            /// * frameDecimation : Frame decimation factor [default=2]

            /// * sizeDecimation : Size decimation factor [default=8]

            /// * priority : Hyperion priority channel [default=800]

            /// * mode : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default=”2D”]

            /// * cropLeft : Cropping from the left [default=0]

            /// * cropRight : Cropping from the right [default=0]

            /// * cropTop : Cropping from the top [default=0]

            /// * cropBottom : Cropping from the bottom [default=0]

            /// * redSignalThreshold : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]

            /// * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]……

            /// * blueSignalThreshold : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]

            “grabber-v4l2” :

            {

            “device” : “/dev/video0”,

            “input” : 0,

            “standard” : “PAL”,

            “width” : 360,

            “height” : 288,

            “frameDecimation” : 2,

            “sizeDecimation” : 4,

            “priority” : 1200,

            “mode” : “2D”,

            “cropLeft” : 0,

            “cropRight” : 5,

            “cropTop” : 0,

            “cropBottom” : 5,

            “redSignalThreshold” : 0.2,

            “greenSignalThreshold” : 0.2,

            “blueSignalThreshold” : 0.2

            },

            Use these numbers in the v4l2 as above. (very important)

            “width” : 360,

            “height” : 288,

            “frameDecimation” : 2,

            “sizeDecimation” : 4,

            “priority” : 1200,

            save the changes.

            after the changes…

            run killall hyperiond, to make sure the hyperion is not running, when u replace the running hyperion.config,json file. othervise there can be a malefunction.

            upload the changed hyperion config file. with ex. cyberduck to the .config folder

            then run /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.config.json /dev/null 2>&1 & (in one line)

            this worked for me 🙂

            give it a shoot.

          • Reddemise
          • Johan

            yes, rpi b+.

            can u take a screenshot from Fushicai?

            try this

            killall hyperiond

            LD_LIBRARY_PATH=/storage/hyperion/bin /storage/hyperion/bin/hyperion-v4l2 -v PAL –width 360 –height 288 –screenshot (one line code)

            i bougt my things from lightberry and got support from there.

            i have probably spent 15 hours before i got it to work.

          • Reddemise

            Okay ill will try to purchase the easycap from light berry too. Are you in he US? Was it fast shipping

          • Reddemise

            Hi Johan,

            Did you buy the “HDMI Kit” or “Premium HDMI Kit”?
            Out of curiousity do you live in the US? If so, how fast was the shipping?

            I am returning both STK1160 since its not working and chalking up the Fushicai one as broken and ordered 2-3 different ones to try my luck.

          • Johan

            Hi,

            I,m living in Sweden. The delivery chain took only 20 hours from Poland to the nothern Sweden. 😉 However was my order backorderd three weeks, but that depended on the leds was out of stock. They deliver with DHL.

            I’ve got the premium Hdmi kit.
            Ok, If u live in Us you should use ntsc in v4l2 section. But that do you know already i presume 🙂

            God luck! 🙂 post the result here when u got the parts 🙂

          • Reddemise

            I am waiting on 3 other grabbers to test before I order the HDMI kit.

            Yes I know to use NTSC, but what is odd is that when I tested on my laptop with the STK1160 that wouldn’t screenshot. It didn’t matter if NTSC or PAL both worked fine with a clear image. The HDMI input was Amazon Fire TV. Is that weird?

          • Reddemise

            Hi Johan,

            I got my new Fushicai grabber and i am able to finally get a screenshot! I did all the cropping and saved the config. and then ran

            /storage/hyperion/bin/hyperiond.sh/storage/.config/hyperion.config.json /dev/null 2>&1 &

            but i cant get hyperiond to react to my screen… any ideas?

          • I’m glad you solved it! 🙂

          • Johan

            My wonders about the mplayer is related to this linkhttp://raspberry-at-home.com/video-grabber-for-raspberry-pi/

            In the end there is a couple of lines about the mplayer.

            Do you know what the lines would be for openelec? Because that must be to the raspbian build.

          • I get your point, but I never used mplayer so I can not be of any help. Have you tried looking in the wiki of hyperion on github and see if you find some hints for the STK chip? Anyway tonight I will upload my image (8gb card, 1gb zip) and post the link here. Sorry I can not be of more help

          • Johan

            You are the best 😉

            I apriciate all the help. And on a Friday night aswell

          • No problem, I will not stare at the monitor while my pc upload the file 🙂
            Get back to you tomorrow

          • Johan

            Btw do u know how to install the “mplayer”

            Forgot to write what in using,
            Using rpi!B+

  • Murc

    Many thanks for the guide, very clear!
    I am running openelec 4.2.1 and my setup works, also the effects work.
    I get a crisp and clean screenshot and cropped it accordingly, changed the cropped values at the config file. But when i reboot my pi and kodi loads, i get the rainbow swirl and blue light for some seconds. The thing is, ambilight doesnt react to my grabber input (it doesnt give any color output) even though i know it has an input and the screenshots are fine too. I changed the settings on my config file but nothing works (even the priority values).
    Maybe hyperion “sees” the openelec media centre as standard input and doesnt switch to the grabber input. Maybe you have got some ideas how to fix this? many thanks

    • Hi, it should works without problem, have you tried with openelec 5.0.1? maybe it’s the 4.2.1 that has some issues? If you wnat to try, this is my image for a 8gb sd card:
      http://1drv.ms/1zHIu52

  • Josh Long

    Any update about CEC issue with hdmi splitters? any splitter with CEC support?

  • Aki

    Any one had luck with Lightberry HDMI Premium Kit? i can’t get it to work.

    • Flo

      Same here, but i’m a noob to all of this but i followed each step exactly but i fail at setting the parameters…. hope there will be some kind of tool soon like the hyperion conig one but then for the complete settings including the v4l2 section.

  • bingston

    This is the first tutorial that I’ve gotten to work. I’m having a small problem though and was hoping for some advice. I’ve been working on this for about a month now, and it turns out there seems to be a problem with the hdmi splitter. It seems to work on its own, and the composite converter seems to work on its own as well…however when I connect the splitter to the tv and the composite converter at the same time, only a black signal is passed to the composite converter box. When I plug the source video straight into the composite converter everything is working but I obviously lose my picture to the tv so it seems to be an issue between the splitter and the converter. Any advice is greatly appreciated. This is the last step in the process and I’ll finally be able to get this working. Thanks for this tutorial!

    • From your summary I can only thing that maybe the splitter is defective. I do not know how to help you, because as far as I know you should only power it up and do nothing more.
      Have you tried to connect the splitter to another television or change the hdmi cables (maybe they are the problem)?

      • bingston

        I’m thinking it’s the splitter as well. I ordered another one and hopefully the new one will bypass hdcp. I’ve tried changing cables and anything else I could think of to troubleshoot, but nothing seemed to work. For what it’s worth, in case it can help someone else, I had the Orei HD-102. I’ve read mixed reviews about it working for some and not for others. My understanding, which may be wrong, is that they worked at one time, but no longer bypass hdcp. I wish they would have changed model numbers or something, it’s made things kind of confusing. We’ll find out in a couple days when the new one gets here.
        Thanks for the reply and thanks for posting your tutorial. As I mentioned this is the first one that I’ve been able to get to work and I can’t wait to see it in action! I’ll post the results of the new splitter once I get a chance to test it in case it can help anyone else. Thanks again!

        • Thank you, I’m glad it is of help. I will wait to hear from you then

          • bingston

            I tried another splitter and it still didn’t work. I can get the signal going to two different TV’s, but when I come out of the splitter to the composite converter all I get is a black signal. If I take my A/V receiver output into the composite converter I get a scrambled signal. I can’t figure out if the problem is with the splitter or the converter. I tried buying buying a different converter so I’ll find out if that’s the problem in a few days. I hope this works, can’t wait to see it. I thought the software would be the tough part…we finally got that working and now we’re stuck on the devices passing the signal properly, what I thought would be the easy part.

          • Koeniejj

            How did you fix the problem, was it he HDMI to AV converter?
            I have the same problem

          • bingston

            My problem ended up being the composite converter

          • bingston

            Well it turns out, I’m pretty sure it was the composite converter – Two
            splitters later and a couple new composite converters and I’m finally
            seeing something. Once I get everything working for sure I’ll update
            the devices that I used. One of the converter boxes is working great but when I turn the TV off it sends color bars to the pi so I just have a rainbow of lights behind the TV when I turn it off.
            When the TV is running, the lights are working but my colors are a little off. Could someone
            offer some insight on the easiest way to edit the hyperion config
            file? Every time I change something and send it over, the raspberry pi
            starts acting funny and I have to reload the image to get it working
            again. Thanks in advance

          • For editing the config file you use HyperCon or are you doing it by hand?

          • bingston

            I was using HyperCon and then sending the file over to the pi. I’m just not sure how to get Hyperion to read the new file. I’m not opposed to changing by hand instead of HyperCon if it’s easier. Does it update automatically or do I have to relaunch Hyperion? and if I have to restart it for it to read the new config file, could you share the command to do so? Is there any way to see live changes to the config file (that may be asking too much, but would be nice)
            Thanks for helping out!

          • Hypercon is much easier imo. Once you overwrite the config file you must restart the hyperion service by restarting your pi or more simply using this command: initctl restart hyperion

          • Hypercon is much easier imo. Once you overwrite the config file you must
            restart the hyperion service by restarting your pi or more simply using
            this command: initctl restart hyperion
            Hope it helps

          • bingston

            I think I’ve read that command before, but when I try to run it is says that “-sh: initctl: not found”.

          • Sorry, I just copied and pasted without trying it. With OpenElec you should use killall hyperiond (as stated in this blog post) and then restart it. You should find it in /hyperion/bin/hyperiond.sh

          • bingston

            “killall hyperiond” definitely works to shut it down, but I’m having trouble getting it to start back up. I see the hyperiond.sh file you mentioned, I’m just not sure what to do with it. Sorry to bug you again with this. I really appreciate you taking the time to help

          • bingston

            ok, so i tried to run the hyperiond.sh and got the following message

            QCoreApplication initialised
            Missing required configuration file. Usage:
            hyperiond [config.file]

          • As the message say you must pass the name of the config file you want it to load: something like ./hyperion/bin/hyperiond.sh /pathofyourconfig/hyperion.config.json Anyway remember that yo can just simply reboot 🙂

          • bingston

            I can’t get it to work for some reason. I had to do a reboot. I’ll play around with it some more. Thanks again for your help today!

          • bingston

            I realized why the file kept failing after I made any changes. I was forgetting to go back and add that snippet to the bottom of the hyperion.config file that activates the grabber. I’m in much better shape now.
            When I turn the TV off it sends a blue signal to the composite grabber, so when the TV goes off I get a bright blue light that never turns off. Are there any recommendations to stop that from happening?
            Thank you again for all of your help.

          • That’s because the video from the openelec on your pi kicks in and the skin is blue… I did not tried it, but if you disable the Xbox you should not see the blue light anymore

          • bingston

            I think the composite converter sends blue when it doesn’t get a signal. When everything gets turned off the converter sends blue to the pi so the lights turn blue. I just need to figure out a convenient way to turn hyperion off when I turn everything off and then turn it back on when the A/V receiver sends a signal to it.

          • bingston

            I finally got that command to work (sorry, newbie to raspberry). That’s much faster than rebooting. When I run that command hyperion starts again but then the command line seems to hang. Any ideas on that?

          • Sorry, but I will be out of town for a week and until than I can not play with my pi :/

            I guess the restart is your preferred option 🙂

  • Thomas Swanton

    I made it very far with this project. I’ve gotten the ws2801 to work with my PS4 with your tutorial and it looks awesome. I am not getting any sound though. Has anyone else had this problem?

    • The only thing I can think of is the splitter that is faulty. Sorry I can not be of more help

      • Thomas Swanton

        I switched it to the Wii U and it completely works with it. I switch back to the PS4 and I have no audio.

        • bingston

          The only thing I can think of off the top of my head is, check your PS4 settings and make sure your sound is set to HDMI out. If it works with the Wii it makes me think it could be a setting with the PS4…something to check anyway. Good luck

  • Chaves

    So far trying the same steps with a PI, but no succeed, Open elec does install and works, the rest failed 🙁

    • Are you sure your grabber has the correct chipset and is it correctly initialized? Can you grab a screenshot with success?

      • Chaves

        Well after many attempts it work. Got questions? Ping me I think I might help

    • bingston

      I had a lot of issues getting mine to work, but this is the only tutorial I’ve come across that actually worked. One thing that I kept forgetting to do – After you create the file in HyperCon, make sure you add the little snippet of code that Alessandro provides further up on this page under the section “Configuring Hyperion with Openelec”. If you make any changes in HyperCon and save a new config file, you have to go back and add that snippet for the grabber to work. I kept forgetting that step after making a new config file and without that snippet it won’t work. I’m not sure if that’s your issue, but it’s something worth checking

  • Scott Winterringer

    cut the tutorial into three separate parts or make it one piece. It feels like setting up stuff that doesn’t matter for a separate part of the tutorial. This tutorial does not explain what some things do and for which video grabber. It doesn’t explain how to properly install the image or where to see the plugin in the menu. use hyperion_ssh instead. what about other light strips like the lpd8806, baudrates, why you chose the specific frame grabber WxH and interval. Pal and NTSC settings, are different and can have subtle differences on usage for people in different countries.

  • Eric

    Hello, i have a problem! When i put : LD_LIBRARY_PATH=/storage/hyperion/bin…. in putty open elec say to me permision denied and when i use other program for shh comunication it lagged and say to me 1000 times the frame is to small, what can be happening? The graber is the fushicai! Please help me ! Thx

    • It seems that you do not login as root.
      For the “frame too small” it could be because of your usb hub (if you have one between your pi and the grabber) if you look in the commnets of this post you will find some information. There is also a discussion on the github of hyperion.

      • Eric

        oh! i dont have a usb hub but i have a USB extension cable, it can be the problem? I will try to remove of it! very very thx!

  • Yuri De Angelo

    Ciao Alessandro, scrivo in italiano perchè ho la fortuna di condividere la lingua 🙂

    Ho acquistato un raspberry pi2, ho collegato i pin 4 (+5V), 6 (ground), 19 (SD) e 21 (Clock) ai led W2801…visto che li sto provando, la striscia led usata per la prova, ha soltanto 3 led, per ridurre il più possibile l’assorbimento di corrente (ho alimentato raspberry e led tramite la microusb 5V 2A).
    Ovviamente ho installato XBMC su rapsberry pi2 e l’add-on lightberry tramite usb….ma non funziona nulla! 🙁 Puoi darmi una mano? Grazie

    • A occhio hai sbagliato i connettori. Nel Pi2 dovrebbero essere 19 e 23. Guarda questo commento: http://alessandrocolla.com/ambilight-raspberry-pi-openelec-part-1/#comment-1947377069

      • Yuri De Angelo

        Grazie mille!!! Hai ragione, è il pin 23 (clock), non il 21…oltretutto volevo anche aggiungere che nel mio setup provvisorio, visto che sono in attesa dell’arrivo dell’alimentatore con connettore jack, ho conneesso SOLAMENTE il connettore microusb 5V 2A per alimentare sia il raspberry pi2 sia un mini striscia led w2801 costituita da 4-5 led…ho misurato sui pin che sono connessi alla striscia led e ho riscontrato 5v, quindi penso dovrebbe comunque funzionare, tu che ne pensi? È fondamentale collegare raspberry al plug e NON al microusb? Non vorrei che fosse il motivo per cui non riuscissi ad eseguire la prova “rainbow” che tu citi nel tuo blog.
        A proposito, complimenti per il blog!!! Finalmente uno “smanettone” italiano ” 🙂

        • Non collegare l’alimentazione se non usando la microsub, in quanto (almeno per pi1) non è protetta. Se gli spari dentro più corrente rischi di bruciare tutto.

          I led w2801 li uso anche io e li alimento a 5v (dovresti trovare cmq le specifiche complete dove li hai comprate o su google). Con solo 2a che si dividono tra pi2 e led credo che sia insufficiente. Quando provai il pi2 con un alimentatore a 2a non si alimentava nemmeno un hd esterno e avevo dovuto usare un hub alimentato esterno. Il pi2 si succhia tutto, quindi è plausibile che non ti funzionino i led in perchè non gli arriva corrente a sufficienza. Grazie per i complimenti 🙂

    • Yuri De Angelo

      ok grazie dell’info, ora provo ad alimentarli esternamente e ti dico: in effetti ho acquistato un alimentatore 5V 10A perche avendo un 75 pollici, ho circa 160 led (30 su ciascuna verticale+ 50 sulle orizzontali)..però scusami ma non ho ben capito, se l’alimentazione microusb 2A non è sufficiente è visto che qualsiasi alimentatore in commercio da 10A è del tipo con a connessione filare con viti, come mi configuro? Cioè dove connetto l’alimentatore da 50W?
      Secondo la tua esperienza, il setup che hai postato nel tuo link può funzionare anche con raspberry pi2, ovviamente rivedendo la connessione dei pin :-)?

      • Mi sono espresso male temo. La mia configurazione attuale usa un alimentatore da 5a che ho modificato per alimentare sia il pi1 che i 50led e tutto funziona. (Nel mio post uso due alimentatori separati da 2a, ma non cambia). Le periferiche esterne le alimento con un hub esterno. Al pi1 bastano 1.6A mentre con il pi2 con 2A ho visto che va solo lui. Quindi a parità di led dovresti avere un alimentatore da 2a per il raspberry (microusb) e uno che alimenta i led (tramite connessione diretta ai led). Così tutto dovrebbe funzionarti regolarmente (cambiando i pin per il pi2 ovviamente).

  • Yuri De Angelo

    Ok grazie mille. Quindi ricapitolando, NON DEVO COLLEGARE i pin 4 (+5V) e 6 (GROUND), ma collego soltanto i pin CK (PIN23) e SD (PIN19) del Pi2 alla striscia led e i connettori l’alimentazione dei led con alimentatore esterno da 50W. Parallelamente collego la microusb per alimentare Pi2. Vorrei essere sicuro perchè se non sbaglio su molti forum ho letto che è pericoloso per il Pi o Pi2 alimentare sia i pin 4 e 6 che la microusb…

    Comunque una volta appurato il funzionamento (lo spero 🙂 ), utilizzerò questo bridge

    http://www.hackerspaceshop.com/raspberrypi-things/ambipi-tv.html#

    che però prevede l’alimentazione del Pi2 e delle strisce con un unico alimentatore con power jack da 3,5. Ora però mi hai fatto venire un dubbio, è pericoloso farlo funzionare così?

    Grazie mille!!!!

    • Colleghi il ground solo il 5v non lo colleghi al Pi. guarda le foto nel primo dei miei post.
      Per quanto riguarda il pi2 non ho molta esperienza e dovrei fare un po’ di ricerche. Ai tmepi avevo letto solo della pericolosità di alimentare il pi tramite il pin 5v. Magari con il pi2 adesso è tutto protetto (spero). Da quello che ho capito il bridge servirebbe solo come telecomando per i led. Perchè non usi il cec pulse, o nel caso tu stia usando una cosa simile a quella di questo post, un semplice ricevitore ir? i led li puoi anche controllare con android. Spero tu riesca a far andare tutto!

  • Yuri De Angelo

    Salve,
    ho appena effettuato delle prove con il setup condiviso (ossia con due alimentazioni distinte), ma il problema persiste, ossia facendo la prova “arcobaleno”, i led non si accendono…ho notato che il problema sta nel fatto che sebbene eseguo tutti i passaggi del suo blog, nella sd del raspberry, non c’è la cartella hyperion!! :-(…ma se compro il raspeberry pi, forse risolvo, mi sa dire conrtesemente quello che lei ha testato, in modo da ripertlo esattamente come da tutorial.
    Grazie

    PS
    e’ per caso questo:
    http://www.amazon.it/pi%C3%B9-recente-Raspberry-Modello-Plus/dp/B00Q8MM4PI/ref=sr_1_22?ie=UTF8&qid=1432588675&sr=8-22&keywords=raspberry+pi

    • Si ho comprato il modello A perchè lo suo solo per gestire i led. Per i video uso una board più potente del Pi/Pi2

  • Yuri De Angelo

    Installando hyperion direttamente da zip file, ora la cartella hyperion è visibile nella directory “storage”, ma quando lancio il comando tramite putty mi compare la scritta “Unable to connect to host”…che vuol dire? aiutoooo 🙁

    • una volta che hai scaricato (o copiato da zip) hyperion devi eseguire gli altri step del mio post in modo che si installi correttamente

  • Yuri De Angelo

    Grazie replay risposta, stasera resetto tutto e riprovo, se non riesco nemmeno stasera, mi comprerò il pi A tanto mi serve solo per i comandare i led. Poi le sarò sapere. Grazie ancora

  • Yuri De Angelo

    Salve,
    come le accennavo, prima di acquistare il modello pi (a proposito, il modello pi che versione? La versione “A” che lei utilizza sembra non avere la porta ethernet!!) Se è cos’ come fa a indentificare il pi in rete?), vorrei fare l’ultimo tentativo cercando di ripetere ogni step, ma per far ciò avrei bisogno
    cortesemente di alcune delucidazioni.

    Premetto che onde evitare che errori precedenti potessero compromettere
    questo mio tentativo d’installazione, vorrei fare un reset (format) della
    microsd, o mi consiglia di fare qualche altro passaggio di “pulizia” della microsd e del pi2?

    A parte il format, ricapitolando, di seguito in crolologia gli step in cui ho dei dubbi:

    1) nella sua guida non compare lo step per l’installazione di
    openelec..va installato subito, giusto? Che versione? Io, prima di seguire la
    sua guida, ho installato la 5.0.5…

    2) successivamente, conoscendo l’indirizzo IP di raspberry, in che modo
    installo Hyperion? Tramite putty ieri sera mi ha dato l’errore sull’host che le
    ho scritto 🙁

    Sarebbe uguale scaricare il file zip ed installarlo da USB? Se si, che versione
    installo?

    3) Come faccio a vedere che ho installato correttamente Hyperion?

    4) appurato che è correttamente installato, va avviato? Se si, come?

    5) installare Hyperion da zip, è un modo alternativo all’installazione che
    lei efettua con putty con la riga di comando “…-L ecc..”?

    6) appurato / installato/avviato hyperion, con “terminal”, sostituisco la riga “/opt/hyperion/effects” come da sua guida – step chiaro e non avuto problemi nel ripeterlo

    7) per fare una prova funzionale con una mini striscia da 4-5 led, devo comunque eseguire lo step di modifica del file. Jar settando hyperion per farlo lavorare coi led nella mia configurazione?

    8) Se necessario, modifico il file .jar inserendo la mia configurazione finale – step chiaro e non avuto problemi nel ripeterlo

    9) spengo il raspberry pi2

    10) connetto direttamente il positivo ed il negativo della mini striscia led ad un alimentatore esterno (prima scollegato) ed gli altri due ingressi della mini striscia ai pin del GPIO, rispettivamente, uno (ck) al pin23 e l’altro (SD) al pin19.

    11) riaccendo il raspberry pi2 ed eseguo il test “arcobaleno” tramite putty e dovrebbe andare giusto?

    Resto in attesa di un suo cortese riscontro, cosìcchè questa sera io possa rieseguire la prova d’installazione avendo sviscerato tutt i miei dubbi

    La ringrazio della sua disponibilità
    Buona giornata
    Yuri

    PS se dovesse andar male la prova di questa sera, come le accennavo, vorrei acquistare il modello identico al suo: ho trovato su ebay

    http://www.ebay.it/itm/291272723963_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

    il raspberry pi con lan che riporto in foto…è esattamente il modello che ha lei? Nella descrizione ebay, parlano di modello pi A, ma nelle speciche del sito raspberry sembra essere il modello pi B!!! boh?! 🙁

    https://www.raspberrypi.org/products/model-b/

    Comunque il venditore ebay che ho già contattato, mi ha detto che è esattamente come la foto che ho allegato…

    • Vediamo se riesco a rispondere a tutto 🙂
      Ovviamente non mi assumo responsabilità per malfuzionamenti o altro.
      La verisone A non ha la rete, collego una penna wifi usb quando mi serve (se usa un modello B ha due usb e la porta ethernet, quindi nessun problema).
      Per resettare basta sovrascrivere la SD con una iso e il gioco è fatto.

      1) Per istruzioni su come insatllare openelec guardi questo post: http://alessandrocolla.com/raspberry-pi-xbmc-powered-usb-hub-my-new-htpc-part-1/ è vecchio, quindi a differenza di allora scarichi la iso (per la versione giusta del PI) dal sito ufficiale e segua le istruzioni per installarla con win32diskimager. A quel punto se mette la scheda si dovrebbere trovare openelec installato e da configurare. Io attualemtne uso l’ultima versione e tutto funziona. La 5.0.5 mi funzionava tranquillamente
      2) installi hyperion come da mie istruzioni, se non si collega putty, vuol dire che non ha configurato correttemente la parte di rete di openelec (veramente facile dalla sezione “programmi”, ma nel caso qui http://alessandrocolla.com/raspberry-pi-xbmc-powered-usb-hub-my-new-htpc-part-2, anche se vecchio, vede come fare)
      3) come da post, se ci sono errori lo vede durante l’installazione oppure quando cerca di lanciare il comando per accendere tutte le luci rosse
      4) non serve avviarlo, fa lui
      5) suppongo di si, deve poi lanciare i comandi di installazione comunque
      7) Sarebbe meglio dirgli quanti le ci sono. In teoria dovrebbe funzionare anche con quello di default, che se non erro, ha 50 led configurati quindi di più dei suoi 4.
      11) quando riavvia se tutto è ok il test arcobaleno parte in automatico. Può modificare quale effetto eseguire all’avvio tramite il file di configurazione di hyperion

      Sepro di esserle stato d’aiuto, Rimango in attesa sapere se va o esplode tutto 😀

  • Yuri De Angelo

    Salve,

    innanzitutto grazie della imnmensa disponibilità!!! 🙂

    ovivamente stia tranquillo, qualsiasi danno è mia responsabilità, ci mancherebbe 😉

    1) avevo già installato openelec 5.0.5 esattamente come lei suggerisce (windisk per convertire l’iso e copiarlo su microsd). Inserito nella microsd, ho inserito la stessa nel raspberry pi2 e ho collegato alimentazione. Fatto ciò, su TV ho appurato che è partita l’installazione del SW e dopo max minuti è comparsa la schermata di Kodi!

    2) in realtà non ho configurato alcun indirizzo ip (forse è proprio qui il pb del mio bug), ma ho semplicemente cercato il raspberry nell’elenco degli indirizzi ip dei dispositivi connessi al mio router, ed è risultato essere 192.168.2.182. Ho poi inserito tale indirizzo ip nella casella dell’applicazione putty e avviato la stessa. Ho poi inserito id (root) e password (openelec), come indicato nel suo forum e le uniche differenze rispetto a quello riportato nella schermata screenshoot di putty del suo blog, le ho evidenziato in rosso in un’immagine che allego…pensa che possa essere un problema di rete, se così fosse non riuscirei a collegarmi con putty, nel senso che non riuscirei nemmeno ad arrivare all schermata iiniziale con richiesta di credenziali (id e password)…

    3) Ok, anche se non ho mai avuto errori, allora sicuramente c’è un problema sull’installazione perchè le luci non si accendono 🙁

    4) Ok…ma su kodi, tra le applicazoni attive, oltre a openelec, c’è “lightberry” e se volessi aprire la sua pagina di configurazione, c’è la possibilità di settare delle configurazioni 18X10, 21X10, ecc..e non so nemmeno cosa volgia dire…oppure addirittura c’è la possibilità di fare altri tipi di settaggi…comunque, come capisco, ignoro tutto! 🙂

    5) su questo punto non ho ben capito, l’installazione di hyperion avviene tramite i due passaggi con comandi su putty, giusto?

    per il download dell’app (I)

    curl -L –output install_hyperion.sh –get https://raw.githubusercontent.com/tvdzwan/hyperion/master/bin/install_hyperion.sh

    e il comando seguente per l’installazione dell’app (II)

    sh ./install_hyperion.sh

    Giusto? Se si, l’installazione tramite .zip da usb, non dovrebbe sostituire sia il punto (I) che il punto (II)?

    Mi scusi se faccio domande a cui ad alcune forse tra le righe lei ha già risposto, ma essendo un ingegnere sono un pò duro di comprendonio 🙂

    Grazie mille per la pazienza e disponibilità

    • 2) non vedo l’immagine, ma se fornisce le credenziali di login ha già raggiunto la macchina
      4) lightberry non lo consoco quindi non so che menu ed opzioni si installino e tantomeno se prendono il controllo esclusivo ed hyperion non può partire. In teoria se ha lightberry e un suo programma installato in kodi dovrebbe essere lui a gestire il tutto.

      5) Quasi. Lei copia da usb in una cartella e poi, da quella cartella, lancia l’installer che attiva il demone.

  • Yuri De Angelo

    Salve,

    ho effettuato diverse prove, ma ancora niente. Proverò ancora, avvalendomi di questa mini guida

    http://raspberry-at-home.com/raspberry-pi-2-lightberry

    Che ne pensa?

    Contemporaneamente, acquisterò anche un raspberry pi modello

    Grazie
    Yuri

    • Si direbbe più adatto visto che ha un lightberry. Mi faccia sapere come finisce. Son curioso di vedere un bel 75″ con tutti quei led 🙂

      • Yuri De Angelo

        Buongiorno sig.Alessandro,

        ho finalmente acquistato un raspberry pi1 versione B, ho installato il SW “OpenELEC-5.0.RPi.arm-Bplus_stk1160” e poi ho seguito le istruzioni del suo tutorial e finalmente sono riuscito a comandare le strisce led per dar luogo all’effetto arcobaleno, sia tramite pc (putty) si a tramite smartphone app 🙂

        L’unica cosa è solo sui colori, nel senso che quando do il comando per il rosso impostando la riga di comando come indicato nel suo tutorial, la striscia si illumina di blu :-(…in tal senso vorrei cheederle se c’entra qualcosa la configurazione della finestra “process” di hyperion: io ho lasciato quella di default anche perchè nel suo tutorial mi sembra che lei non ne parli…allega una diversa configuazione trovata su web, che però non ho provato, non vorrei combinare qualche guaio anche perchè nno ho idea di cosa siano tutti quei parametri 🙁

        A parte questo problemino con il set dei colori, per cui spero lei mi possa aiutare, proprio ieri mi è arrivato il kit all-in-one della lightberry per connettere il raspberry alla TV (https://lightberry.eu/shop/shop/hdmi-premium-kit/)

        Alla fine la mia configurazione prevederà ben 320 leds 🙂 ossia due strisce in parallelo da 5 metri ciascuna, ognuna alimentata da un proprio alimentatore (allego uno schematico dei collegamenti)

        Ora ho un dubbio, nel senso che, nel suo tutorial parte 3, lei suggerisce di aggiungere al file hyperion le righe di comando

        “grabber-v4l2” :

        {

        “device” : “/dev/video0”,

        “input” : 0,

        “standard” : “PAL”,

        “width” : 240,

        “height” : 192,

        “frameDecimation” : 2,

        “sizeDecimation” : 2,

        “priority” : 1100,

        “mode” : “2D”,

        “cropLeft” : 0,

        “cropRight” : 0,

        “cropTop” : 0,

        “cropBottom” : 0,

        “redSignalThreshold” : 0.2,

        “greenSignalThreshold” : 0.2,

        “blueSignalThreshold” : 0.2

        },

        mentre nell’user manual del prodotto all’in-one della lightberry, indicano di mettere le seugenti righe

        “grabber-v4l2” :

        {

        “device” : “/dev/video0”,

        “input” : 0,

        “standard” : “no-change”,

        “width” : -1,

        “height” : -1,

        “frameDecimation” : 2,

        “sizeDecimation” : 8,

        “priority” : 800,

        “mode” : “2D”,

        “cropLeft” : 0,

        “cropRight” : 0,

        “cropTop” : 0,

        “cropBottom” : 0,

        “redSignalThreshold” : 0.0,

        “greenSignalThreshold” : 0.0,

        “blueSignalThreshold” : 0.0

        },

        Cosa cambia tra i due? Quale mi consiglia? Poi un’altra cosa, dopo l’aggiunta delle righe di comando, nel suo tutorial lei fa diverse configuazioni con putty per la regolazione-sincronizzazione immagine e colori (mi sembra di vaer capito), mentre nell’user manual del all-in-one del lightberry, è espressamente indicato solo l’aggiunta delle righe di comando sopra mensionate e niente più…

        La ringrazio del suo supporto, se tutto va bene fra poco mi sdebiterò in parte, con un bel video con il sistemino in funzione su 75″con 320 led 🙂

        Buona giornata
        Yuri De Angelo

        • Buonasera,
          complimenti per il sistemone che sta mettendo in piedi 🙂

          Per quanto riguarda il file di configurazione che trova su uno dei miei post è semplicemente il mio. Quindi la striscia dei miei 50 ledcon specificato il chip che suo. Ad usarlo dovrebbero andare solo i primi 50 led, oppue nulla, perchè usa un chip differente.

          In merito al grabber, quello che riporto nel mio post è dato dalle mie prove con la mia scheda di acqusizione. Spiego a cosa servono i parametri principali proprio perchè uno possa configurarsi autonomamente il proprio, nulla di più. Pertanto partirei da quello che le dice il veditore. Mi aspetto che sia fatto apposta e che lei non debba fare il processo che descrivo, in quanto, “in teoria” è già tutto calibrato. Personalmente farei un ritocchino sul size e frame Decimation per ridurre o aumentare la qualità dell’immagine, e l’uso della cpu. In ogni caso ci giocherei dopo che tutto si è messo a funzionare correttamente.

          Per quanto riguarda la luce blu, non mi è mai capitato, possibile siano collegati male i led?.
          Si direbbe che RGB sia invertito in BGR, la verifica la fa velocemente lanciando il comando per il verde ed il blu.
          Se così fosse dovrebbe bastarle impostare a BGR la 4 opzione di Hypercon “RGB Byte order”

  • Alex

    Hello,

    I have a problem when i enter:

    LD_LIBRARY_PATH=/storage/hyperion/bin /storage/hyperion/bin/hyperion-v4l2 /storage/.config/hyperion.config.json –crop-top 40 –crop-left 50 –crop-bottom 0 –crop-right 30 –size-decimator 8 –frame-decimator 2 –screenshot

    V4L2 width=720 height=480
    V4L2 pixel format=UYVY
    V4L2 grabber signal threshold set to: {0,0,0}
    V4L2 grabber started

    I never have the next step:”V4L2 grabber stopped” … Have you an idea why ?

    • The first things that come to mind are:

      has the grabber a supported chipset?

      is it working (try to connect it to a pc and see)?

      is it connected via a usb hub? if yes try to connect it directly to the pi and see what happens

      • Alex

        my chipset is a “stk1160” . Is it working with ?

        Do you know a solution to make it working with stk1160 ? ? (Please say yes…)

        • For what I know the stk should be supported. Do you see it (and correctly mounted) when you execute the two commands on top of this post?

          • Alex

            Hello ,

            I change the device and buy a UTV007.

            Now when I enter this command:

            LD_LIBRARY_PATH=/storage/Hyperion/bin /storage/Hyperion/bin/hyperion-v4l2 /storage/.config/hyperion.config.json –crop-top 0 –crop-left 0 –crop-bottom 0–crop-right 0 –size-decimator 8 –frame-decimator 2 –screenshot

            I have :

            -sh: /storage/Hyperion/bin/hyperion-v4l2: not found

            HELP Me :'(

          • Have you tried to change the signal type? Instead of using “no-change”, try “PAL” or “NTSC”

          • Alex

            Thank you for your reply !!

            I bought a new HDMI 2 AV and screenshots works now !!

            But after some configuration… Still no LED light on 🙁

            Could you check my configuration ??

            “device” : “/dev/video0”,
            “input” : 0,
            “standard” : « PAL »,
            “width” : 720,
            “height” : 1280,
            “frameDecimation” : 2,
            “sizeDecimation” : 2,
            “priority” : 1100,
            “mode” : “2D”,
            “cropLeft” : 40,
            “cropRight” : 20,
            “cropTop” : 20,
            “cropBottom” : 0,
            “redSignalThreshold” : 0.5,
            “greenSignalThreshold” : 0.5,
            “blueSignalThreshold” : 1.0
            },

            Is the black side part when I take a screenshots have to be completely hide or can I leave it like this screenshot ?

            Could you advice me ??

          • You should crop the top and left parts or the leds won’t light up for that sides. That’s because hyperion will “see” black

          • Alex

            I don’t success to set the black border, even if I change the cropping in the hyperion.config file :/

          • Can you post an image of your grab along with the crop values? I will try to help

          • Alex

            // Automatically generated configuration file for ‘Hyperion daemon’
            // Generated by: HyperCon (The Hyperion deamon configuration file builder

            {
            /// Device configuration contains the following fields:
            /// * ‘name’ : The user friendly name of the device (only used for display purposes)
            /// * ‘type’ : The type of the device or leds (known types for now are ‘ws2801’, ‘ldp8806’,
            /// ‘lpd6803’, ‘sedu’, ‘adalight’, ‘lightpack’, ‘test’ and ‘none’)
            /// * ‘output’ : The output specification depends on selected device. This can for example be the
            /// device specifier, device serial number, or the output file name
            /// * ‘rate’ : The baudrate of the output to the device
            /// * ‘colorOrder’ : The order of the color bytes (‘rgb’, ‘rbg’, ‘bgr’, etc.).
            “device” :
            {
            “name” : “MyPi”,
            “type” : “ws2801”,
            “output” : “/dev/spidev0.0”,
            “rate” : 250000,
            “colorOrder” : “rgb”
            },

            /// Color manipulation configuration used to tune the output colors to specific surroundings.
            /// The configuration contains a list of color-transforms. Each transform contains the
            /// following fields:
            /// * ‘id’ : The unique identifier of the color transformation (eg ‘device_1’) /// * ‘leds’ : The indices (or index ranges) of the leds to which this color transform applies
            /// (eg ‘0-5, 9, 11, 12-17’). The indices are zero based. /// * ‘hsv’ : The manipulation in the Hue-Saturation-Value color domain with the following
            /// tuning parameters:
            /// – ‘saturationGain’ The gain adjustement of the saturation
            /// – ‘valueGain’ The gain adjustement of the value
            /// * ‘red’/’green’/’blue’ : The manipulation in the Red-Green-Blue color domain with the
            /// following tuning parameters for each channel:
            /// – ‘threshold’ The minimum required input value for the channel to be on
            /// (else zero)
            /// – ‘gamma’ The gamma-curve correction factor
            /// – ‘blacklevel’ The lowest possible value (when the channel is black)
            /// – ‘whitelevel’ The highest possible value (when the channel is white)
            ///
            /// Next to the list with color transforms there is also a smoothing option.
            /// * ‘smoothing’ : Smoothing of the colors in the time-domain with the following tuning
            /// parameters:
            /// – ‘type’ The type of smoothing algorithm (‘linear’ or ‘none’)
            /// – ‘time_ms’ The time constant for smoothing algorithm in milliseconds
            /// – ‘updateFrequency’ The update frequency of the leds in Hz
            “color” :
            {
            “transform” :
            [
            {
            “id” : “default”,
            “leds” : “*”,
            “hsv” :
            {
            “saturationGain” : 2.0000,
            “valueGain” : 1.5000
            },
            “red” :
            {
            “threshold” : 0.2000,
            “gamma” : 2.0000,
            “blacklevel” : 0.0000,
            “whitelevel” : 0.9000
            },
            “green” :
            {
            “threshold” : 0.2000,
            “gamma” : 2.0000,
            “blacklevel” : 0.0000,
            “whitelevel” : 1.0000
            },
            “blue” :
            {
            “threshold” : 0.2000,
            “gamma” : 2.0000,
            “blacklevel” : 0.0000,
            “whitelevel” : 0.5000
            }
            }
            ],
            “smoothing” :
            {
            “type” : “linear”,
            “time_ms” : 100,
            “updateFrequency” : 50.0000
            }
            },

            /// The configuration for each individual led. This contains the specification of the area
            /// averaged of an input image for each led to determine its color. Each item in the list
            /// contains the following fields:
            /// * index: The index of the led. This determines its location in the string of leds; zero
            /// being the first led.
            /// * hscan: The fractional part of the image along the horizontal used for the averaging
            /// (minimum and maximum inclusive)
            /// * vscan: The fractional part of the image along the vertical used for the averaging
            /// (minimum and maximum inclusive)
            “leds” :
            [
            {
            “index” : 0,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.9000, “maximum” : 1.0000 }
            },
            {
            “index” : 1,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.8000, “maximum” : 0.9000 }
            },
            {
            “index” : 2,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.7000, “maximum” : 0.8000 }
            },
            {
            “index” : 3,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.6000, “maximum” : 0.7000 }
            },
            {
            “index” : 4,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.5000, “maximum” : 0.6000 }
            },
            {
            “index” : 5,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.4000, “maximum” : 0.5000 }
            },
            {
            “index” : 6,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.3000, “maximum” : 0.4000 }
            },
            {
            “index” : 7,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.2000, “maximum” : 0.3000 }
            },
            {
            “index” : 8,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.1000, “maximum” : 0.2000 }
            },
            {
            “index” : 9,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0600 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.1000 }
            },
            {
            “index” : 10,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0667 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 11,
            “hscan” : { “minimum” : 0.0667, “maximum” : 0.1333 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 12,
            “hscan” : { “minimum” : 0.1333, “maximum” : 0.2000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 13,
            “hscan” : { “minimum” : 0.2000, “maximum” : 0.2667 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 14,
            “hscan” : { “minimum” : 0.2667, “maximum” : 0.3333 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 15,
            “hscan” : { “minimum” : 0.3333, “maximum” : 0.4000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 16,
            “hscan” : { “minimum” : 0.4000, “maximum” : 0.4667 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 17,
            “hscan” : { “minimum” : 0.4667, “maximum” : 0.5333 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 18,
            “hscan” : { “minimum” : 0.5333, “maximum” : 0.6000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 19,
            “hscan” : { “minimum” : 0.6000, “maximum” : 0.6667 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 20,
            “hscan” : { “minimum” : 0.6667, “maximum” : 0.7333 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 21,
            “hscan” : { “minimum” : 0.7333, “maximum” : 0.8000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 22,
            “hscan” : { “minimum” : 0.8000, “maximum” : 0.8667 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 23,
            “hscan” : { “minimum” : 0.8667, “maximum” : 0.9333 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 24,
            “hscan” : { “minimum” : 0.9333, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.0800 }
            },
            {
            “index” : 25,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.0000, “maximum” : 0.1000 }
            },
            {
            “index” : 26,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.1000, “maximum” : 0.2000 }
            },
            {
            “index” : 27,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.2000, “maximum” : 0.3000 }
            },
            {
            “index” : 28,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.3000, “maximum” : 0.4000 }
            },
            {
            “index” : 29,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.4000, “maximum” : 0.5000 }
            },
            {
            “index” : 30,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.5000, “maximum” : 0.6000 }
            },
            {
            “index” : 31,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.6000, “maximum” : 0.7000 }
            },
            {
            “index” : 32,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.7000, “maximum” : 0.8000 }
            },
            {
            “index” : 33,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.8000, “maximum” : 0.9000 }
            },
            {
            “index” : 34,
            “hscan” : { “minimum” : 0.9400, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.9000, “maximum” : 1.0000 }
            },
            {
            “index” : 35,
            “hscan” : { “minimum” : 0.9333, “maximum” : 1.0000 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 36,
            “hscan” : { “minimum” : 0.8667, “maximum” : 0.9333 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 37,
            “hscan” : { “minimum” : 0.8000, “maximum” : 0.8667 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 38,
            “hscan” : { “minimum” : 0.7333, “maximum” : 0.8000 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 39,
            “hscan” : { “minimum” : 0.6667, “maximum” : 0.7333 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 40,
            “hscan” : { “minimum” : 0.6000, “maximum” : 0.6667 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 41,
            “hscan” : { “minimum” : 0.5333, “maximum” : 0.6000 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 42,
            “hscan” : { “minimum” : 0.4667, “maximum” : 0.5333 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 43,
            “hscan” : { “minimum” : 0.4000, “maximum” : 0.4667 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 44,
            “hscan” : { “minimum” : 0.3333, “maximum” : 0.4000 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 45,
            “hscan” : { “minimum” : 0.2667, “maximum” : 0.3333 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 46,
            “hscan” : { “minimum” : 0.2000, “maximum” : 0.2667 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 47,
            “hscan” : { “minimum” : 0.1333, “maximum” : 0.2000 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 48,
            “hscan” : { “minimum” : 0.0667, “maximum” : 0.1333 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            },
            {
            “index” : 49,
            “hscan” : { “minimum” : 0.0000, “maximum” : 0.0667 },
            “vscan” : { “minimum” : 0.9200, “maximum” : 1.0000 }
            }
            ],

            /// The black border configuration, contains the following items:
            /// * enable : true if the detector should be activated
            /// * threshold : Value below which a pixel is regarded as black (value between 0.0 and 1.0)
            “blackborderdetector” :
            {
            “enable” : true,
            “threshold” : 0.01
            },

            /// The configuration of the effect engine, contains the following items:
            /// * paths : An array with absolute location(s) of directories with effects
            /// * bootsequence : The effect selected as ‘boot sequence’
            “effects” :
            {
            “paths” :
            [
            “/storage/hyperion/effects”
            ]
            },

            “bootsequence” :
            {
            “effect” : “Rainbow swirl fast”,
            “duration_ms” : 3000
            },

            /// The configuration for the frame-grabber, contains the following items:
            /// * width : The width of the grabbed frames [pixels]
            /// * height : The height of the grabbed frames [pixels]
            /// * frequency_Hz : The frequency of the frame grab [Hz]
            “framegrabber” :
            {
            “width” : 96,
            “height” : 54,
            “frequency_Hz” : 25.0
            },

            /// The configuration of the XBMC connection used to enable and disable the frame-grabber. Contains the following fields:
            /// * xbmcAddress : The IP address of the XBMC-host
            /// * xbmcTcpPort : The TCP-port of the XBMC-server
            /// * grabVideo : Flag indicating that the frame-grabber is on(true) during video playback
            /// * grabPictures : Flag indicating that the frame-grabber is on(true) during picture show
            /// * grabAudio : Flag indicating that the frame-grabber is on(true) during audio playback
            /// * grabMenu : Flag indicating that the frame-grabber is on(true) in the XBMC menu
            /// * grabScreensaver : Flag indicating that the frame-grabber is on(true) when XBMC is on screensaver
            /// * enable3DDetection : Flag indicating that the frame-grabber should switch to a 3D compatible modus if a 3D video is playing
            “xbmcVideoChecker” :
            {
            “xbmcAddress” : “192.168.0.14”,
            “xbmcTcpPort” : 9090,
            “grabVideo” : true,
            “grabPictures” : true,
            “grabAudio” : true,
            “grabMenu” : true,
            “grabScreensaver” : true,
            “enable3DDetection” : false
            },

            /// The configuration of the Json server which enables the json remote interface
            /// * port : Port at which the json server is started
            “jsonServer” :
            {
            “port” : 19444
            },

            /// The configuration of the Proto server which enables the protobuffer remote interface
            /// * port : Port at which the protobuffer server is started
            “protoServer” :
            {
            “port” : 19445
            },

            /// The configuration of the boblight server which enables the boblight remote interface
            /// * port : Port at which the boblight server is started
            “boblightServer” :
            {
            “port” : 19333
            },

            “endOfJson” : “endOfJson”,

            /// Configuration for the embedded V4L2 grabber
            /// * device : V4L2 Device to use [default=”/dev/video0″]
            /// * input : V4L2 input to use [default=0]
            /// * standard : Video standard (no-change/PAL/NTSC) [default=”no-change”]
            /// * width : V4L2 width to set [default=-1]
            /// * height : V4L2 height to set [default=-1]
            /// * frameDecimation : Frame decimation factor [default=2]
            /// * sizeDecimation : Size decimation factor [default=8]
            /// * priority : Hyperion priority channel [default=800]
            /// * mode : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default=”2D”]
            /// * cropLeft : Cropping from the left [default=0]
            /// * cropRight : Cropping from the right [default=0]
            /// * cropTop : Cropping from the top [default=0]
            /// * cropBottom : Cropping from the bottom [default=0]
            /// * redSignalThreshold : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]
            /// * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]……
            /// * blueSignalThreshold : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]
            “grabber-v4l2” :
            {
            “device” : “/dev/video0”,
            “input” : 0,
            “standard” : « no-change »,
            “width” : -1,
            “height” : -1,
            “frameDecimation” : 2,
            “sizeDecimation” : 8,
            “priority” : 800,
            “mode” : “2D”,
            “cropLeft” : 0,
            “cropRight” : 0,
            “cropTop” : 0,
            “cropBottom” : 0,
            “redSignalThreshold” : 0,
            “greenSignalThreshold” : 0,
            “blueSignalThreshold” : 0,
            },

            ____________________
            It is the same result with or without values, I think there is a problem in the config file …

          • Your crop values are all to zero. That’s why no crop is applied. As I wrote you before, adjust the crop values and you should solve the problem.
            With a couple attempts you should be able to grab the correct image.

          • Alex

            Hello ! No more change after your advice … But it works now because I have downloaded your configuration file and I rework it with y configuration.

            I’ve compare both but I don’t see any difference… It seems to be magic !!!

          • That’s strange. I will take a look at it, I’m curious. Anyway I’m glad you solved it also if you’ve used the help of some kind of dark magic 🙂

          • Alex

            Hello I enjoy my ambilight TV very well now !!
            I try to set with more accuracy my config file.

            How can I set the “size” of my screenshot because a part of the bottom is missing, and nothing change when I set the width and height…

            “OpenELEC:~/screenshots # LD_LIBRARY_PATH=/storage/hyperion/bin /storage/hyperion/bin/hyperion-v4l2 /storage/.config/hyperion.config.json hyperion-v4l2
            V4L2 width=720 height=480
            V4L2 pixel format=YUYV
            V4L2 grabber signal threshold set to: {0,0,0}
            Connecting to Hyperion: 127.0.0.1:19445
            V4L2 grabber started”

            I don’t know why the V4L2 width and height are always the same ? can I change it ?

            There are also some calculation mistakes (LED flash sometimes) do you know how can I avoid it ??

            Thank you very much for your help !!

          • AFAIK you can not. Because that is what arrive from the grabber. I too have the same problem and did not take the time to solve it yet. If you find a way, keep me in the loop please 🙂

          • Now that I though a little bit, maybe you are using the wrong video format. Have you tried to set the Video standard fo the config file to PAL or NTSC? What happens?

          • Alex

            Hello !

            After some configuration LED stop blinking ( I’ve adapated the width: 16 and height: 9) and it seems to be good .

            I tried to switch from PAL to NTSC and now it works very fine !!

            I would like to thank you for your precious helps and advices from the beginning of my many problems to now !

          • Well I am glad you solved everything 🙂

  • Thomas Swanton

    Hello Alessandro,
    I had gotten this working for the past 3 months and then all of a sudden the lights stopped working with the tv. It just displays a rainbow all the way around. After some troubleshooting I noticed that the Easycap was not being read by the Pi anymore so I ordered a new one. The one I have now is a UTV007 rather than an STK1160. The Pi sees it connected. I can get the effects to work when i test them through SSH. The app on my phone connects and I can control the lights with the colorwheel. I’m still not able to get the lights to link up with my TV. Any suggestions?

    • mmh. The easycap is mounted correctly? didi you see it when you launch the two commands “lsusb” and “ls /dev/video*? if you try to grab a screenshot it works? or you get a black image?

      lsusb
      ls /dev/video*
      lsusb
      ls /dev/video*

      • Thomas Swanton

        I figured out the rainbow color…… perhaps the HDMI2AV is defective?

        • I guess too it could be the culprit. Without it you get the screen correctly

          • Thomas Swanton

            Could I bypass the HDMI2AV device with a cable that already does that?

          • I think it should work.

          • Thomas Swanton

            Tried a direct cable and it didn’t work right. New HDMI2AV device came in and now I get this screenshot. I’m so lost.

          • Have you tried to connect the hdmi2av with something else to be sure that it works correctly? there are a lot of low quality products around :/
            Another stupid question. have you tried the switch both with pal and ntsc?

          • Thomas Swanton

            After a bunch of restarting the Pi and plugging/unplugging devices I somehow managed to get it to work again. Let’s see how long it will last.

  • Yuri De Angelo

    Salve Sig.Alessandro,

    la ringrazio della pronta risposta…mi dispiace di esser, come si dice a Roma, “un pò di coccio”, ma non ho capito i suoi consigli 🙁

    Per ciò che concerne la colorazione dei led, ho effettuato un’altra prova con un piccola striscia di led e anche in questo caso, la colorazione va un po per conto suo, nel senso che solo con il giallo e rosso ho una giusta risposta del sistema, mentre con gli altri colori, il colore che setto non è quello che visualizzo…

    Inoltre lei accennva al fatto che dovrei rivedere dei prametri sul file hyperion esattamente RGB con BGR, aiuto che vuol dire, dove trovo queste impostazioni??? 🙁

    Nel rivedere il suo tuttorial e il mio setup, ho notato che forse ho commesso un errore, in quanto io NON ho collagato il pin del ground del raspberry con quello della striscia led..questo sencondo lei può incidere nel buon funziomento?

    Per l’aggiunta del file grabber, alla mia domanda di come inserire le righe di comando sugggerite sul loro sito (che allego come scrrenshot del loro sito) per far riconoscere al raspberry il loro dispositivo, il venditore mi ha scritto questo:

    “end of json tag is:

    “endOfJson” : “endOfJson”

    🙂 It’s the last line that hyperion will parse

    Please correct your file acording to above information 🙂 You have grabber section placed after closing tag.”

    Le ho inserito ed il risultato è il file in allegato (per allegarlo ho fatto uno screenshot della parte finale del file hyperion), pensa che può andar bene?

    Grazie ancora

    Saluti
    Yuri De Angelo

    • Come le dice l’assistenza, lei mette il codice del grabber dopo la linea “endofjson…”, deve invece metterlo prima.
      Per il BGR: con hypercon, nella voce che le dicevo nel mio precedente post, lei deve specificare come hyperion deve gestire il segnale RGB (Red Green Blu).
      Se quando manda il comando di rosso ottiene blu, ho il sospetto che i suoi led necessitino dell’informazione in BGR (Blu, Green, Red). Per fare la prova lanci i comandi dei tre colori principali, così capsice come sono impostati. Poi da Hypercon specifica la sequenza corretta e crea il file di configurazione corretto.

      • Yuri De Angelo

        Salve,

        finalmente, grazie ai suoi consigli ho risolto con l’accensione dei led by Hyperion app, ora I colori rispondono correttamente ai comandi (allego una foto delle prove eseguite…vorrei anche farle vedere un video non riesco a caricarlo, come devo fare?)

        Stasera proverò a riportare i suoi consigli sul file di configurazione, aggiungendo le righe di comando per il grabber e poi le farò sapere.

        Grazie
        Buona giornata
        Yuri

        • Complimenti, mi fa piacere sia riuscito finalmente a farlo andare.
          I video non si possono caricare qui, deve caricarli su una piattaforma come youtube o vimeo ed successivamente incollare il link nel commento.

  • Yuri De Angelo

    Salve,
    ho aggiunto le righe di comando al file di configurazione e finalmente il sistema funziona!!!
    Solo che le luci emesse dai led mi sembrano un po’ tremolanti e la cosa strana è che nei momenti di scena nera, i led sembrano che simulano un arcobaleno…inoltre ho notato che entrare le strisce sul lato destro del TV in alcuni frangenti tendono al verde anche se tale colore non è presente nella scena del film riprodotto…

    Che ne pensa?

    Grazie

    • Mi fa piacere che cominci a funzionare. A freddo si direbbe un problema con l’immagine del grabber. Provi a prendere qualche screenshot e veda cosa arriva

  • Yuri De Angelo

    Cioè, cosa intende con screenshoot, devo inviare un comando dedicato tramite putty?

    Secondo lei su quali parametri devo agire per provare a risolvere?

    La mia configurazione è costituita da due strisce da 5 metri (150 led) messe in parallelo ed ognuno di queste è suddivisa in 4 parti (per ciascun lato del tv 50 led + 30 led + 50 led +30 led)

    Di seguito riporto la parte grabber

    “grabber-v4l2” :
    {
    “device” : “/dev/video0”,
    “input” : 0,
    “standard” : “PAL”,
    “width” : 720,
    “height” : 576,
    “frameDecimation” : 2,
    “sizeDecimation” : 8,
    “priority” : 1100,
    “mode” : “2D”,
    “cropLeft” : 5,
    “cropRight” : 5,
    “cropTop” : 5,
    “cropBottom” : 5,
    “redSignalThreshold” : 0.2,
    “greenSignalThreshold” : 0.2,
    “blueSignalThreshold” : 0.2
    },

    Cosa mi consiglia di fare?
    Se mi da un suo riferimento email le posso inviare i video…

    Grazie

    • con screenshot intendo il slavataggio di un’immagine che arriva dalla penna di acquisizione, come descritto proprio in questo post.

      • Yuri De Angelo

        Salve,
        ho eseguito un reset ed ora il sistema funziona anche se a dir il vero, ho notato che nelle prove eseguite successive al reset, per far riconoscere il segnale video, 2-3 volte sono stato costretto a spegnere e riaccendere il sistema hdmi-usb, nello specifico ho notato che questo va meglio se acceso dopo l’accensione del raspberry.
        Grazie del supporto
        Buona giornata

  • Yuri De Angelo

    Grazie della risposta, stasera provo a prendere uno screenshoot, ma non capisco cosa dovrei vedere nell’immagine che acquisisco? 🙁

    Devo vedere se l’immagine è sfocata ai lati? Se si, qual’è il criterio per cambiare i “drop” e che legame c’è con il “difetto” nell’immagine?

    Grazie

    • Dall’immagine vede cosa arriva ad hyperion e quindi l’eventuale verde laterale etc.
      Dipende molto dalla sua penna di acquisizione. Per modificare i parametri dell’immagine come il crop, è sempre spiegato nel post qui sopra

  • Yuri De Angelo

    Salve,
    ho provato a seguire le sue indicazioni inserendo le righe di comando per prendere degli screenshoot, ma o il seguente errore (in allegato)…ho comunque iniziato a variare alcuni parametri pian piano e dopo vari tentativi sono arrivato alla seguente configurazione:

    “grabber-v4l2” :

    {

    “device” : “/dev/video0”,

    “input” : 0,

    “standard” : “PAL”,

    “width” : 1920, (PRIMA ERA 720)

    “height” : 1080, ((PRIMA ERA 576)

    “frameDecimation” : 2,

    “sizeDecimation” : 3, (PRIMA ERA 8)

    “priority” : 1200,

    “mode” : “2D”,

    “cropLeft” : 30, (PRIMA ERA 5)

    “cropRight” : 30, (PRIMA ERA 5)

    “cropTop” : 50, (PRIMA ERA 5)

    “cropBottom” : 50, (PRIMA ERA 5)

    “redSignalThreshold” : 0.2,

    “greenSignalThreshold” : 0.2,

    “blueSignalThreshold” : 0.2

    In questa configurazione, non ho più quello strano verde sul lato destro del TV ed i colori sono abbastanza corrispondenti.

    Direi che un’ottimo risultato, ora mi documento su come poter caricare video su web e poi condivido i link per farle vedere il lavoro finito e avere un suo parere 😉

    • Le da quell’errore perchè il percorso di hyperion è diverso da quello che riporto io (deve mettere il percorso in cui ha installato il suo). In ogni caso, manualmente ha fatto lo stesso, cioè croppato l’immagine in modo da averla corretta. Mi fa piacere sia riuscito nell’impresa 🙂

  • Yuri De Angelo
  • Yuri De Angelo

    Ci sono riuscito, ho caricato 2 video su YouTube, di seguito i link

    https://m.youtube.com/watch?v=uZP4ABzm1C8&feature=youtu.be

    https://youtu.be/xsKzFKDzZW8

    • Non so se è il video o meno, ma forse ha croppato un po’ troppo l’immagine, porverei a ridurre i crop laterali. Comunque deve essere notevole l’effetto con un televisore così grande, cmplimenti per il lavoro.

      • Yuri De Angelo

        Ok, ma qual’è il criterio del crop? Io ho messo un numero corrisponde al numero di led della mia configurazione (50 per top e bottom e 30 per left edge right).
        Da cosa si è reso conto che solo i crop laterali sono troppo alti? Le chiedo per iniziare ad avere un occhio più critico e così poter calibrare il setup…

        • Il crop è il taglio dell’immagine acquisita, come spiego nel post. non ha nulla a che fare coi led.
          Segua il mio post sostituendo il percorso con quello della sua installazione di hyperion e dovrebbe riuscire a calibrare tutto millimetricamente

  • Yuri De Angelo

    Ok grazie, stasera proverò ad affinare i crop e le farò sapere

  • Yuri De Angelo

    Salve Sig.Alessandro,

    ho appena terminato i setting dei parametri crop, penso siano perfetti, può giudicare dallo screenshoot che allego. A parte l’assenza di bordi nello screenshoot, mi sono messo nella condizione che cambiando il valore di ciascuno di un so punto, l’immagine presenterà dei bordi neri in corrispondenza del relativo crop (se riduco di un numero il crop right, l’immagine nella parte dx presenterà un piccolo bordo nero e così via..)

    La configurazione finale è

    “frameDecimation” : 2,
    “sizeDecimation” : 8,

    “cropLeft” : 2,
    “cropRight” : 7,
    “cropTop” : 5,
    “cropBottom” : 3,

    Ora li led sembrano perfettamente corrispondenti all’immagine sul tv, ma ho notato che ancora che ci sono due cose strane:

    1) c’è troppo “tremolio” dei colori in molte zone

    2) in modalità stand-by del lettore multimediale (classica immagine con logo che si muove nello schermo nero) i led lampeggiano bianco-verde e non rimangono spenti come mi aspetterei visto che l’immagine è completamente nera

    Inoltre non capisco su quale/i parametro/i devo agir per ridurre/eliminare i sopra citati “problemini”, a patto che tali siano.

    Gli unici parametri che sono rimasti da settare, sono i seguenti:

    “standard” : “PAL”,
    “width” : -1,
    “height” : -1,
    “priority” : 1200,
    “redSignalThreshold” : 0.2,
    “greenSignalThreshold” : 0.2,
    “blueSignalThreshold” : 0.2

    Che mi consiglia?

    Grazie
    Yuri

    • L’unica che mi viene in mente è porvare a cambiare lo standard PAL in “no-change”

      • Yuri De Angelo

        Ho appena effettuato una prova sostituendo lo standard ma non cambia nulla 🙁
        Ma gli altri parametri, tipo

        “width” :
        “height” :
        “priority” :
        “redSignalThreshold” : “greenSignalThreshold” : “blueSignalThreshold”

        sono influenti per la giusta configurazione? A cosa servono?

        Grazie

  • Yuri De Angelo

    Salve,
    ho utilizzato per diversi giorni il sistema ma da ieri sera senza un motivo il sistema non funziona più nel senso che i led non rispondono correttamente al video del TV e la cosa ancora più strana è che in fase di accensione del raspberry, la sequenza arcobaleno non è quella consueta e il successivo step non è quello con il blu fisso. Ho provato a lanciare i comandi led by App ma anche in questo caso non ho una corrispondenza con i colori (lancio il verde ed ho il verde sul 70% del TV e sul resto un misto di colori, ecc..).
    Ho quindi provato a staccare il kit USB/hdmi e sostituire il file di configurazione mettendo quello iniziale senza grabber che inizialmente funzionava con i comandi by app ma il problema persiste.
    La cosa strana è che non ci sono state modifiche SW o HW o possibilità di fili disconnessi rispetto al giorno prima quando tutto funzionava.
    Cosa mi consiglia di fare? Reinstallo tutto da capo? Se si come devo fare? Devo cancellare la SD é reinstallare il SW OPENELEC e poi seguire il suo tutorial per reinstallare Hyperion?
    Grazie del supporto
    Buona giornata

    • Come prima prova anche io farei l’installazione da capo. Nel momento in cui sovrascrive la SD con l’immagine di openelec, azzera tutto. Magari quando tutto è pronto e funzionante, esegua un backup della sd (sempre con win32diskimage) così, se si riverifica il problema ripristina in due minuti tutto

  • Yuri De Angelo

    Ok grazie, questa sera reinstallo tutto poi le faccio sapere.
    Grazie

  • Joel Pinto

    Hello Alessandro,

    You have been my savior in this ambilight adventure and I really hope you can help me once again.
    I was following your tutorial but there seams to be a problem and I can’t figure out what’s wrong.
    I’m not using any hdmi spliter, after connecting everything I get the video grabber listed as you can see below. I then edited the hyperion.config.json file and after rebooting it seams that my leds stop working. I then enter the comand killall hyperiond and I get “killall: hyperiond: no process killed”. When trying to take a screenshot I get: “terminate called after throwing an instance of ‘std::out_of_range’
    what(): basic_string::at: __n (which is 1) >= this->size() (which is 1)
    Aborted”

    So, I think that the problem may be in the hyperion.config.json file, not sure about it, you can also see the image of it bellow and I think it’s like the one in the tutorial.

    I’m using a raspberry pi2, not sure if it makes any difference.
    Do you have any idea about what’s wrong here?

    • Joel Pinto

      In the images forget the second one because I was using a wrong command to take a screenshot.

      Now I was able to take a screenshot (image bellow) which was like nothing. After that I have disconnected the “Mini HDMI video converter to composite AV” and the result was the same!?!?!?

      So, may the problem be in the hyperion.config.json file, since I can’t stop the Hyperion service?
      Or may it be something with the Mini HDMI video converter to composite AV?

      Any idea?

      • In the screenshot of the config file it seems that your are missing a closing brace. Also try to move the line “”endOfJson” : “endOfJson” at the end and before the last closing brace (the one your are missing). With someone the endofjason not at the “end” created some strange behaviour

        • Joel Pinto

          Isn’t the closing brace the character that I have on the line 465 “}”?
          I’ll make those changes When I get home to see if it solves the problem, just need to confirm if the closing brace is this symbol “}”, I’m a newbie in this programming issues!

          • Yes

          • Joel Pinto

            Hello again,

            Thank you for your advices, I still haven’t maneged to get it to work but i think I know where the problem is!:) After testing all the parts it seams that my HDMI2AV converter is not working, I’ll have to buy another one to try again… I found on the internet several cases like mine with many people with hardware problems!

            Mean while, I thought I had my config.jonson finnaly ok, but after disconnecting all the other parts and get the sistem back to the original, the leds doesn’t work.
            Does it mean that after changing the config.jonson file leds will only work when the image is sent from the Easycap?
            I want to continue to use my Rasp as a media center as well and thought It would detect where the image is coming from and still working fine directly from the raspberry! P

  • Pawel

    Hi!
    First – great job and tutorial! I am only wondering if it’s possible to just connect video grabber to AV/s-video signal directly from TV and enjoy ambilight when watching regular TV, is it possible?

    BR,
    Pawel

    • If your TV has the video output (and not the input) I think it is be possible.

  • Apt

    Hi Alessandro,
    I have configured ambilight with Rpi 2 (xbmc) and Arduino Uno R3 with boblight. The ambilight works awesome. However can you please share the code/ file to configure boblight to accept any video source ? I want to connect my xbox 360 to the Rpi.
    Thanks in advance.

    • I never used boblight or Arduino for an ambilight project, so I can not help you. Sorry

  • Roy

    I’m getting really frustrated.
    A few days ago i wrote the config file for the hdmi input. Everything went well, but after a few hours, the leds doesn’t respond anymore.
    I reset the json file to the Original and the leds working fine in de openelec media player.
    I tried to config the file again, but when i take a screenshot, i only receive a black screen. I’ve tested the HDMI2AV converter with the same HDMI and AV cable from my laptop to beamer: works fine. Put my laptop directly into the converter en tried to make a screenshot, but only a black screen.
    Tried Pal / Ntsc and no-change but it does not make any difference.
    Made a copy of your config file: same problem.
    Any ideas?

    • I will double check that the grabber is seen correctly by the system. (the first check in the post).

      Try also to put the code of the grabber code, before the “EndOfJson”, with a friend of mine worked because of that. I can not think of other check at the moment

    • Maggie

      I’m having the same issue as you, when I take a screenshot I just get a black screen. Did you ever find a solution?

      • Roy

        Not yet, but I didn’t really tried it anymore. Busy @ work etc.
        But my next option is to put the grabber in a powered USB hub. Myabe the Raspberry can’t boot him up correctly. (grabber is seen correctly by the system, but I have to try someting)

        • Maggie

          Well I ended up buying a different HDMI2AV converter and my screenshots and lights started working

  • Steve Beeson

    Nice tutorial. I am having issues once I add an HDMI splitter to the system, it works fine without a splitter but im sure you can guess it makes watching tv difficult;). I have tried different HDMI2AVI boards and different HDMI splitters and the results are the same. The Video in gets heavy green lines and it switches back to the default PI screen background lighting.

    • The fact taht you have some green lights in the grabbed image it is ok, but they should not be too large. I suggest you to chekc Hyperion’s github, because if I am not mistaken there is a discussion on the matter.

      • Steve Beeson

        After browsing the github I see a lot of open issues with grabbers. Most of them unresolved/no longer responding.

        • Steve Beeson

          Got it working, seems to be some issues with the HDMI2AV and HDMI splitter setting the wrong resolutions. If they get set wrong I get black or green from the grabber, if I power them off and restart them and they detect the correct resolution I get good screen grabs. And for some reason I have not found any decent AV sources that work with my grabbers.

  • Jason

    Hello! Were you able to output 1080p to the TV and through the HDMI2AV adapter? If I use any resolution higher than 480p then there is no signal on the composite side of the HDMI2AV adapter.

  • Brian P.

    Great tutorial! I was bummed initially when I was follow another tutorial since my grabber was not the correct chip set. Your tutorial worked like a charm! One thing I am having, is it seems to crash when going to a black screen when I am launching a game on my PS4.

    Any ideas on what may cause this?

    Also, would it be possible to start Hyperion without kodi launching?

    Thanks!

    • Brian P.

      Fixed the crashing issue. It was a problem with the config file, but I am curious about the other question.

      • Glad you solved it. Hyperion is a stand alone service so it should will work without kodi. Honestly I never tried it

  • Alex

    Hello,

    My hyperion is working fine with 50 LEDs. On a HMDI Switch are connect:

    – my XBOC 360

    – my TV box

    – Kodi

    All is working fine without any problem, except when I want to see a movie on KODI, the raspberry crash. (I tried with Rpi & Rpi2). If I disabled the hyperion managing, I can see the movie without problem ( but I have no leds :'( )

    Do you think hyperion need to much ressources on the CPU ? or something else ? even with raspberry 2 ??

    Thanks for your help,
    Alex

    • I can not answer because I use a dedicated Raspberry A to handle the leds, but I agree to think that the movie (720p or 1080p) can require a lot of cpu, so what I would do is to try to overclock the raspberry a little and see what happens.

  • Gianluigi Accietto

    Salve,
    sono riuscito a realizzare il progetto dopo qualche tentativo. Potrebbe forse essere di interesse una piccola implementazione che ho realizzato, che mi consente di utilizzare l’ambilight per kodi, per un altro ingresso hdmi convertito in av (un internet kit della haier che mi consente di navigare in internet con il televisore) ed anche per i canali tv ordinari del digitale terrestre.
    Quasi tutti i televisori, infatti, hanno la presa scart che è bidirezionale, quindi può anche “trasmettere” il segnale interno e non solo ricevere il segnale da apparecchi esterni.
    Montando sulla presa scart un piccolo adattatore da scart a rca ho preso il solo segnale video e ho visto che collegato al grabber funzionava perfettamente; ho anche notato, poi, che se al grabber non era collegato nulla l’ambilight funzionava in base alle immagini di kodi.
    Quindi, per poter gestire il tutto, ho fatto un piccolissimo circuito con 2 switch, uno che stacca il segnale che va al grabber e mi consente quindi un on/off per kodi, un’altro che seleziona quale delle 2 uscite (tv e internet) inviare al grabber. In questo modo ho un interruttore per kodi, quando è in off si aggancia in automatico il segnale dell’altro switch (tv o internet).
    Spero possa essere di interesse.
    Grazie

    • Buongiorno,
      interessante lo switch, se ha uno schema e voglia di condividerlo, possiamo fare un post qui oppure mi giri il link al suo blog che integro volentieri nel mio post

      • Gianluigi Accietto

        Provo a tirare giù uno schema.

      • Gianluigi Accietto

        Salve,
        Provo ad inviarle 2 schemi veloci.
        Ho utilizzato interruttori / switch bipolare per staccare completamente il segnale ed evitare quindi interferenze tra i vari apparecchi.

        Buona serata

  • Pingback: URL()