Posts by HyperLEDs

    Check the live feed from the grabber (upper right corner). Try to setup resolution and refresh rate manually. After grabber is disconnected it's necessarily to reboot system to work again.


    Good call.


    The grabber displays a vertical bar pattern when there's no signal detected, hence the RGB pattern.


    I got it to work with a standard 4K signal, although with a delay that I need to figure out how to fix - I can't set the frames per second to anything above 5.


    The bigger problem is that it doesn't look like I can pass a 4K HDR signal to the grabber (it just displays the bar pattern), and https://www.amazon.com/gp/product/B07VP37KMB?tag=hyperioforum-21 cannot down-convert an HDR signal to a standard signal without completely washing the image out. Any thoughts on how to make this setup work with HDR?

    @HyperLEDs as you have MJPG device maybe you can my fork as it's intended to improve performance for that type of encoding (MJPG):
    https://github.com/awawa-dev/hyperion.ng/releases


    It contains patches released after Alpha7, Raspbian Buster is recommended. Or you can compile current version of Hyperion to test: beside performance (and one related bug in live preview) I haven't meet any issues.
    But beware there's one problem in Hyperion.NG that can affect you: https://github.com/hyperion-project/hyperion.ng/issues/908 (I dont have that dual type of yuyv/mjpg grabber to check it)


    Made some good progress - Hyperion.NG is now installed and correctly controlling the LEDs. The video grabber is correctly detected. However, when I select the video grabber as the source, I just see an RGB pattern on the LEDs on the top and bottom of my TV - this pattern occurs whether I have something connected to the grabber or not.

    @HyperLEDs as you have MJPG device maybe you can my fork as it's intended to improve performance for that type of encoding (MJPG):
    https://github.com/awawa-dev/hyperion.ng/releases


    It contains patches released after Alpha7, Raspbian Buster is recommended. Or you can compile current version of Hyperion to test: beside performance (and one related bug in live preview) I haven't meet any issues.
    But beware there's one problem in Hyperion.NG that can affect you: https://github.com/hyperion-project/hyperion.ng/issues/908 (I dont have that dual type of yuyv/mjpg grabber to check it)


    Many thanks - I'll try to build from Master and see what happens.

    @HyperLEDs it's seems it's rather software problem from old Hyperion (operation not permited for that device) because linux drivers is perfectly OK. Trouble with MJPG device was the main and only reason I've migrated to Hyperion.NG. But the store is still pending as I improve it's performance.


    For the old hyperion and that device causes you VIDIOC_S_INPUT ERROR 22 could try add --pixel-format YUYV to command line


    Thanks for your help. the additional argument didn't work.


    I tried installing Hyperion.NG a few weeks ago, but I ran into so many issues just trying to get it to install properly (e.g. processes not running as root when they should be, DMA channel problems, random colors being shown on the strip as a result of a known bug in alpha v7). If you have a simple recommendation for getting a version of Hyperion.NG installed that works, I could try that to see if the grabber works.

    I tried dev/video0 and input 1 and I now get a different error:


    Code
    2>/dev/null ; hyperion-v4l2 --device /dev/video0 --video-standard NTSC --input 1 --width -1 --height -1 --crop-left 0 --crop-right 0 --crop-top 0 --crop-bottom 0 --size-decimator 1 --frame-decimator 2 --red-threshold 0.0 --green-threshold 0.0 --blue-threshold 0.0 --screenshot
    ssh in:     hyperion-v4l2:
    ssh in:         version   : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
    ssh in:         build time: Aug 25 2019 10:39:29
    ssh out:     VIDIOC_S_INPUT ERROR 22, Invalid argument
    sftp getFile(./screenshot.png, java.awt.Image)

    Well, the first registered device is MJPG, it doesnt work with old Hyperion and the new version has some performance isssue but it should work somehow. Try second instance of video device ...it's seems it's yuyv.



    Same error - I've read that the "VIDIOC_S_INPUT ERROR 25, Inappropriate ioctl for device" indicates an incompatible chipset, is that not true?


    Code
    2>/dev/null ; hyperion-v4l2 --device /dev/video1 --video-standard NTSC --input 0 --width -1 --height -1 --crop-left 0 --crop-right 0 --crop-top 0 --crop-bottom 0 --size-decimator 1 --frame-decimator 2 --red-threshold 0.0 --green-threshold 0.0 --blue-threshold 0.0 --screenshot
    ssh in:     hyperion-v4l2:
    ssh in:         version   : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
    ssh in:         build time: Aug 25 2019 10:39:29
    ssh out:     VIDIOC_S_INPUT ERROR 25, Inappropriate ioctl for device
    sftp getFile(./screenshot.png, java.awt.Image)

    @HyperLEDs dmesg looks good and v4l2 capture device is active ...and what are symptoms that the grabbers doesn't work? Hyperion.NG doesn't detect it and there is no info on the www usb grabber configuration page? or the black screen from the grabber or something else maybe?


    I'm using Hyperion, not NG. When I try to grab a screenshot from HyperCon, I get "No picture found check ssh traffic. Stop Hyperion before you take a screenshot!"


    And the logs show:


    Code
    2>/dev/null ; hyperion-v4l2 --device /dev/video0 --video-standard NTSC --input 0 --width -1 --height -1 --crop-left 0 --crop-right 0 --crop-top 0 --crop-bottom 0 --size-decimator 1 --frame-decimator 2 --red-threshold 0.0 --green-threshold 0.0 --blue-threshold 0.0 --screenshot
    ssh in:     hyperion-v4l2:
    ssh in:         version   : V1.03.5 (GitHub-66bef6b/fb413cd-1566231780
    ssh in:         build time: Aug 25 2019 10:39:29
    ssh out:     VIDIOC_S_STD ERROR 25, Inappropriate ioctl for device
    sftp getFile(./screenshot.png, java.awt.Image)

    @HyperLEDs Paste full dmesg & v4l2-ctl --list-formats. This grabber should work.


    dmesg



    v4l2-ctl --list-formats



    v4l2-ctl --all


    Yes here, I use it at the moment:
    € 7,50 18%OFF | Rullz 4K carte de Capture vidéo USB 3.0 2.0 HDMI vidéo Grabber boîte d'enregistrement pour PS4 jeu DVD caméscope caméra enregistrement en direct Streaming
    https://a.aliexpress.com/_BVDUG8


    The black one.


    But I see you already tried it and it doesn't work for you, so maybe your problem is not the grabber...


    I think it's the grabber:


    lsusb


    Code
    osmc@osmc:~$ lsusb
    Bus 001 Device 010: ID 2341:0043 Arduino SA Uno R3 (CDC ACM)
    Bus 001 Device 009: ID 534d:2109
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    dmesg


    Code
    [448030.747419] usb 1-1.3: USB disconnect, device number 7
    [448107.547422] usb 1-1.4: USB disconnect, device number 8
    [448113.728623] usb 1-1.3: new high-speed USB device number 9 using dwc_otg
    [448113.861923] usb 1-1.3: New USB device found, idVendor=534d, idProduct=2109, bcdDevice=21.00
    [448113.861940] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [448113.861950] usb 1-1.3: Product: USB Video
    [448113.861960] usb 1-1.3: Manufacturer: MACROSILICON
    [448113.862987] uvcvideo: Found UVC 1.00 device USB Video (534d:2109)
    [448113.864335] uvcvideo 1-1.3:1.0: Entity type for entity Processing 2 was not initialized!
    [448113.864351] uvcvideo 1-1.3:1.0: Entity type for entity Camera 1 was not initialized!


    v4l2-ctl --all



    sudo lshw


    Code
    *-usb:1
                 description: Video
                 product: USB Video
                 vendor: MACROSILICON
                 physical id: 3
                 bus info: usb@1:1.3
                 version: 21.00
                 capabilities: usb-2.00
                 configuration: driver=usbhid maxpower=500mA speed=480Mbit/s

    work very well... I don't know what was sent to you or what quality


    Same here.
    I've got that one and it works.
    Bought it there, the black one:
    € 7,50 18%OFF | Rullz 4K carte de Capture vidéo USB 3.0 2.0 HDMI vidéo Grabber boîte d'enregistrement pour PS4 jeu DVD caméscope caméra enregistrement en direct Streaming
    https://a.aliexpress.com/_BVDUG8


    The unit I received looks identical. Can you please run and paste the results of the following commands. This is what I get:


    lsusb


    Code
    osmc@osmc:~$ lsusb
    Bus 001 Device 010: ID 2341:0043 Arduino SA Uno R3 (CDC ACM)
    Bus 001 Device 009: ID 534d:2109
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    dmesg


    Code
    [448030.747419] usb 1-1.3: USB disconnect, device number 7
    [448107.547422] usb 1-1.4: USB disconnect, device number 8
    [448113.728623] usb 1-1.3: new high-speed USB device number 9 using dwc_otg
    [448113.861923] usb 1-1.3: New USB device found, idVendor=534d, idProduct=2109, bcdDevice=21.00
    [448113.861940] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [448113.861950] usb 1-1.3: Product: USB Video
    [448113.861960] usb 1-1.3: Manufacturer: MACROSILICON
    [448113.862987] uvcvideo: Found UVC 1.00 device USB Video (534d:2109)
    [448113.864335] uvcvideo 1-1.3:1.0: Entity type for entity Processing 2 was not initialized!
    [448113.864351] uvcvideo 1-1.3:1.0: Entity type for entity Camera 1 was not initialized!


    v4l2-ctl --all



    sudo lshw


    Code
    *-usb:1
                 description: Video
                 product: USB Video
                 vendor: MACROSILICON
                 physical id: 3
                 bus info: usb@1:1.3
                 version: 21.00
                 capabilities: usb-2.00
                 configuration: driver=usbhid maxpower=500mA speed=480Mbit/s

    I've gone through 3 video grabbers - all of them falsely advertised as containing a compatible chipset. The only thing preventing me from using Hyperion at the moment is a working video grabber.


    Are there any working UTVF007 chipset grabbers available for sale anywhere?

    You buy type A, B, C or D


    This grabber doesn't work - I ordered what everyone here suggested, waited a month to receive it, only to see it's the wrong chipset.


    I've gone through three grabbers now without any luck - the most difficult part about using hyperion seems to be finding a grabber that actually works. I'm out of ideas. Anyone know of a confirmed grabber with a compatible chipset?


    Here are the details for the 4th grabber on the right (D) from the link above:


    *-usb:1
    description: Video
    product: USB Video
    vendor: MACROSILICON
    physical id: 3
    bus info: usb@1:1.3
    version: 21.00
    capabilities: usb-2.00
    configuration: driver=usbhid maxpower=500mA speed=480Mbit/s