1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

4k HDR Capable HDMI Splitter (supposedly)

Discussion in 'Hyperion Hardware' started by sl81, 23 January 2017.

  1. joebar65

    joebar65 Member

    Messages:
    53
    Hardware:
    RPi3
  2. Andrew_xXx

    Andrew_xXx Software Developer

    Messages:
    24
    No one will guarantee that, but this is the same device
    https://www.amazon.com/HDMI2-0-Recorder-Commentary-Compatible-ezcap269/dp/B07VRBB6N8?th=1
    And on producer website
    http://www.ezcap.com/index.php/product/ezcap269gamecapturelive.html
    You can download the manual there
    It is a UVC usb driverless device with linux support, amazon page says v4l2 support, so IT SHOULD WORK.

    I could not find any confirmation if it strips the HDR data from the 1080p capture, but it is supposed to work with streaming services like twitch, but there isn't any such service with HDR support, so probably it strips HDR data, so no color issues.
     
  3. andrewj88

    andrewj88 New Member

    Messages:
    6
    Hardware:
    RPi1/Zero
    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.
     
  4. Andrew_xXx

    Andrew_xXx Software Developer

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

    andrewj88 New Member

    Messages:
    6
    Hardware:
    RPi1/Zero
    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)
     
  6. Andrew_xXx

    Andrew_xXx Software Developer

    Messages:
    24
    Well i try to eliminate any analog down the pipe and number of devices, so not worth going HDMI2AV anymore, it get quickly too advanced and those av analog boxed will die eventually so all digital setup IMO is much better, there also a lot of those 4k hdmi matrixes from china with hdr support and 1080p output, but they need checking too, digital is getting cheaper and cheaper.
     
  7. Claudio Branco

    Claudio Branco Cranco

    Messages:
    57
    Hardware:
    RPi3
    Diva is unable to strip Dolby vision for Hyperion purposes
    Only lldv from ATV
    It is possible could change with software update
     
  8. andrewj88

    andrewj88 New Member

    Messages:
    6
    Hardware:
    RPi1/Zero
    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.

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

    Andrew_xXx Software Developer

    Messages:
    24
    Im not sure if the lack of usb 3.0 would make such issue, at least on basic connection level, it maybe will not work for capturing as the bandwidth is too small but should work for diagnostics.

    First of all check if it is properly visible by the system not hyperion
    v4l2-ctl --list-devices
    And then check formats
    v4l2-ctl --list-formats-ext

    Then maybe try hyperion-v4l2 --screenshot

    The default v4l2 device should be at /dev/video0

    Post all log result here
     
    Last edited: 3 February 2020
  10. andrewj88

    andrewj88 New Member

    Messages:
    6
    Hardware:
    RPi1/Zero
    Excuse the formatting, I was using the default cmd in win10.

    Code:
    ]0;[email protected]: ~[01;[email protected][00m:[01;34m~ $[00m v4l2-ctl --list-devices
    bcm2835-codec-decode (platform:bcm2835-codec):
            /dev/video10
            /dev/video11
            /dev/video12
    
    ezcap U3 capture: ezcap U3 capt (usb-20980000.usb-1):
            /dev/video0
            /dev/video1
    
    ]0;[email protected]: ~[01;[email protected][00m:[01;34m~ $[00m v4l2-ctl --list-formats-ext
    ioctl: VIDIOC_ENUM_FMT
            Type: Video Capture
    
            [0]: 'MJPG' (Motion-JPEG, compressed)
                    Size: Discrete 1920x1080
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 640x480
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 800x600
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1024x768
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1280x720
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1280x960
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1280x1024
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1360x768
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1400x900
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1440x900
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                    Size: Discrete 1920x1080
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
                            Interval: Discrete 0.017s (60.000 fps)
                            Interval: Discrete 0.033s (30.000 fps)
    ]0;[email protected]: ~[01;[email protected][00m:[01;34m~ $[00m hyperion-v4l2 --screenshot
    hyperion-v4l2:
            version   : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
            build time: Aug 25 2019 10:39:29
    V4L2GRABBER INFO: width=1920 height=1080
    V4L2GRABBER ERROR: Only pixel formats UYVY, YUYV, and RGB32 are supported ERROR
    ]0;[email protected]: ~[01;[email protected][00m:[01;34m~ $[00m
    It seems its in a codec that Hyperion (or V4L2) doesn't like

    Log for hyperion

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

    Andrew_xXx Software Developer

    Messages:
    24
    Well it looks good, it is working with the system, its under /dev/video0 and even /dev/video1 not sure why two, but ok.
    Looks like the grabber is fine, but i can see u are not using hyperon ng, but the original and to my knowledge, only hyperion ng supports MJPG encoding.
    Thats not the first hdmi to usb3 grabber i see that uses MJPG, it is more and more popular amongst modern hdmi2usb capture devices.
    Well if its not rpi4 then it would probably not work either way, but u could try and install hyperion ng just to check diagnostics, make a screen etc.
    Or if u have system with gui u can easily run vlc visually on pi and open the device as a capture card, vlc should have no issues supporting mjpg and showing u an image from the device and allow to easily change configuration to at least check if maybe it can work in lower resolution.

    There was a similar issue on forum with ezcap and mjpg https://hyperion-project.org/threads/hdmi-grabber.3302/

    U can just tinker here and there if u want and tell what u have found.
     
  12. Paulchen-Panther

    Paulchen-Panther Active Member Developer

    Messages:
    481
    Hardware:
    RPi1/Zero, RPi3, 32/64bit, +Arduino
  13. andrewj88

    andrewj88 New Member

    Messages:
    6
    Hardware:
    RPi1/Zero
    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.
     
  14. Andrew_xXx

    Andrew_xXx Software Developer

    Messages:
    24
    @andrewj88
    Well i'm a programmer and sometimes work with linux, but i do not know all the available commands for hyperion and v4l2 exactly, so i look up forums or github if i need too.

    But look at that, seems hyperion v1 also supports mjpeg and even more, someone added opencv grabber that can take most formats, i wasn't aware of this, but i do not know if it works out of the box or need to compile install yourself, but u can try and check if u didn't install ng already, just add the entries to the config according to that link.

    But i think its not there as the install procedure downloads release from 25 08 and this was merged into master on 30 09, maybe Panther the dev can help u more.

    Still if u have that gui, vlc is the simplest way to check if it actually send some images at least, but i think the grabber just works fine.
     
    Last edited: 5 February 2020
  15. rasp

    rasp New Member

    Messages:
    1
    Hardware:
    RPi3
    I've got a copy of that ezcap 269. 4K 60 & HDR/30 works fine but rather as pass thru to the TV. For the grabber: HDR color conversion bt2020 to bt709 results in bleak colors. It's seems that they improved internal splitter in that device generation but the grabber is still the old one: 1080p.

    Works with Rpi 3 on usb2.0 just fine. Anyway it simplifies connections because we can replace now ex. VSP01201 + utv007 + 3 HDMI cables (same problem with HDR colors) with just one ezcap 269 and two HDMI cables. Works with hyperion-ng out of box, has much better picture quality than utv007, no need to crop image because screen always fits captured frame and 1080/24 is not a problem anymore. Current price is $65 on ali with coupons.

    HDR demo: HDR10-Sony-Bravia-OLED.mp4
    [​IMG] [​IMG] [​IMG]
     
    • Like Like x 1