Beiträge von andrewj88


    Okay, I will install that version of hyperion.


    Keep in mind, I'm not exactly familiar with linux and I'm not exactly a programmer, but I will do what I can, I'll report back if I hit a wall or get somewhere.

    Excuse the formatting, I was using the default cmd in win10.



    It seems its in a codec that Hyperion (or V4L2) doesn't like


    Log for hyperion



    Solutions? Or is this device is just not gonna go?

    Interested myself if this thing will strip hdr properly, waiting for the report. DIVA will work without issues i guess, but the price.


    Okay. So I got it the other day and I don't think it works. But its probably my pi not the device itself (I do not have a pi4 - which has USB3).


    Here's the error
    ssh in: Feb 02 03:49:02 ProjHikari2 systemd[1]: Started Hyperion Systemd service.
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: Hyperion Ambilight Deamon (393)
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: Version : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: Build Time: Aug 25 2019 10:39:29
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: HYPERION INFO: ColorTransform 'default' => [0; 91]
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: HYPERION INFO: ColorCorrection 'default' => [0; 91]
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: HYPERION INFO: ColorAdjustment 'default' => [0; 91]
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: LEDDEVICE INFO: configuration:
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: {
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: "colorOrder" : "bgr",
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: "name" : "HIKARI2",
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: "output" : "/dev/spidev0.0",
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: "rate" : 1000000,
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: "type" : "apa102"
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: }
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: INFO: Creating linear smoothing
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=33;settlingTime_ms=150;updateDelay=0
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    ssh in: Feb 02 03:49:02 ProjHikari2 hyperiond[393]: EFFECTENGINE INFO: Initializing Python interpreter
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: INFO: Hyperion started and initialised
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: INFO: Boot sequence 'Rainbow swirl' EFFECTENGINE INFO: run effect Rainbow swirl on channel 0
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: BLACKBORDER INFO: threshold set to 0.1 (26)
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: BLACKBORDER INFO: mode:default
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: started
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: INFO: Json server created and started on port 19444
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: INFO: Proto server created and started on port 19445
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in: Feb 02 03:49:03 ProjHikari2 hyperiond[393]: what(): VIDIOC_S_STD ERROR 25, Inappropriate ioctl for device
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Main process exited, code=killed, status=6/ABRT
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Failed with result 'signal'.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Service RestartSec=100ms expired, scheduling restart.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Scheduled restart job, restart counter is at 9.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: Stopped Hyperion Systemd service.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Start request repeated too quickly.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: hyperion.service: Failed with result 'signal'.
    ssh in: Feb 02 03:49:03 ProjHikari2 systemd[1]: Failed to start Hyperion Systemd service.


    Diva is unable to strip Dolby vision for Hyperion purposes
    Only lldv from ATV
    It is possible could change with software update


    Yeeah, I learned that one the hard way. :(

    Interested myself if this thing will strip hdr properly, waiting for the report. DIVA will work without issues i guess, but the price.


    I will try without DIVA and report back. I'd be very interested in seeing how it handles 24P sources. I haven't found a good HDMI2AV box that'll handle it right and sometimes that affects the lights. (I get a squished picture on the input)


    I just bought this, and I plan to experiment.


    I also bought an HDFury DIVA so I can finally use dolby vision with my hue sync box.


    Will report back.

    So I got my hyperion setup working after a week of frustration and buying another capture dongle, but I've been having issues with the grabber, especially with getting video from my HTPC.


    Here's the issue from the HTPC: https://i.imgur.com/YjeKZJb.png


    But yet on my Roku its fine: https://i.imgur.com/wPirqXQ.png


    I've tried searching for solutions, but I've heard from many sources that the HDMI2AV does not work well with 24P sources (which is the HTPC, which I tried to disable 24p, but couldn't find the option and is apparently a windows bug), is there any solutions? Like a converter, or another HDMI2AV? I should add that both sources are just 1080p and is coming from a 5.1 AV reciever (ONKYO HT-R397)