UTV007 - Could not find any capture device settings #421

Carko · 2022-11-19T12:14:21Z

Carko
Nov 19, 2022

Hi!

I'm having trouble with HyperHDR getting video from my basic usbtv007 grabber (HDMI to USB version) on my RPi 3 B. This happens in the latest (beta) version, but happened on the previous versions as well.

HyperHDR reports:

2022-11-19T09:50:46.322Z [V4L2:USBTV (VIDEO0)] (V4L2Grabber.cpp:402) Device has 'brightness' control => min: 0, max: 1023, default: 448
2022-11-19T09:50:46.322Z [V4L2:USBTV (VIDEO0)] (V4L2Grabber.cpp:408) Device has 'contrast' control => min: 0, max: 1023, default: 464
2022-11-19T09:50:46.323Z [V4L2:USBTV (VIDEO0)] (V4L2Grabber.cpp:414) Device has 'saturation' control => min: 0, max: 1023, default: 512
2022-11-19T09:50:46.323Z [V4L2:USBTV (VIDEO0)] (V4L2Grabber.cpp:420) Device has 'hue' control => min: -3583, max: 3583, default: 0
2022-11-19T09:50:46.324Z [V4L2:USBTV (VIDEO0)] (V4L2Grabber.cpp:212) Searching for usbtv (video0) 0 x 0 @ 0 fps, input: -1 (NO_CHANGE)
2022-11-19T09:50:46.324Z [V4L2:USBTV (VIDEO0)] Could not find any capture device settings

However, V4l2 output seems just fine to me:

pi@hyperhdr:/tmp $ v4l2-ctl --device /dev/video0 --all
Driver Info:
        Driver name      : usbtv
        Card type        : usbtv
        Bus info         : usb-3f980000.usb-1.5
        Driver version   : 5.15.61
        Capabilities     : 0x85200001
                Video Capture
                Read/Write
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x05200001
                Video Capture
                Read/Write
                Streaming
                Extended Pix Format
Priority: 2
Video input : 0 (Composite: ok)
Video Standard = 0x0000f900
        PAL-M/60
        NTSC-M/M-JP/443/M-KR
Format Video Capture:
        Width/Height      : 720/480
        Pixel Format      : 'YUYV' (YUYV 4:2:2)
        Field             : Interlaced
        Bytes per Line    : 1440
        Size Image        : 691200
        Colorspace        : SMPTE 170M
        Transfer Function : Default (maps to Rec. 709)
        YCbCr/HSV Encoding: Default (maps to ITU-R 601)
        Quantization      : Default (maps to Limited Range)
        Flags             :
Streaming Parameters Video Capture:
        Frames per second: 29.970 (30000/1001)
        Read buffers     : 2

User Controls

                     brightness 0x00980900 (int)    : min=0 max=1023 step=1 default=448 value=448 flags=slider
                       contrast 0x00980901 (int)    : min=0 max=1023 step=1 default=464 value=464 flags=slider
                     saturation 0x00980902 (int)    : min=0 max=1023 step=1 default=512 value=512 flags=slider
                            hue 0x00980903 (int)    : min=-3583 max=3583 step=1 default=0 value=0 flags=slider
                      sharpness 0x0098091b (int)    : min=0 max=255 step=1 default=96 value=96 flags=slider

I was thinking there was something wrong with the grabber, but it works normally on a desktop computer.

Power supply and power cable are not an issue. The grabber is connected directly to the RPI 3 USB ports (no extension cables).

I'm also able to capture frames from it on the same RPI with another app:

pi@hyperhdr:/tmp $ yavta -F /dev/video0 --capture=10
Device /dev/video0 opened.
Device `usbtv' on `usb-3f980000.usb-1.5' (driver 'usbtv') supports video, capture, without mplanes.
Video format: YUYV (56595559) 720x480 (stride 1440) field interlaced buffer size 691200
8 buffers requested.
length: 691200 offset: 0 timestamp type/source: mono/EoF
Buffer 0/0 mapped at address 0x7f920e7000.
length: 691200 offset: 692224 timestamp type/source: mono/EoF
Buffer 1/0 mapped at address 0x7f9203e000.
length: 691200 offset: 1384448 timestamp type/source: mono/EoF
Buffer 2/0 mapped at address 0x7f91f95000.
length: 691200 offset: 2076672 timestamp type/source: mono/EoF
Buffer 3/0 mapped at address 0x7f91eec000.
length: 691200 offset: 2768896 timestamp type/source: mono/EoF
Buffer 4/0 mapped at address 0x7f91e43000.
length: 691200 offset: 3461120 timestamp type/source: mono/EoF
Buffer 5/0 mapped at address 0x7f91d9a000.
length: 691200 offset: 4153344 timestamp type/source: mono/EoF
Buffer 6/0 mapped at address 0x7f91cf1000.
length: 691200 offset: 4845568 timestamp type/source: mono/EoF
Buffer 7/0 mapped at address 0x7f91c48000.
0 (0) [-] interlaced 0 691200 B 5254.546789 5254.546866 15.218 fps ts mono/EoF
1 (1) [-] interlaced 1 691200 B 5254.739766 5254.739906 5.182 fps ts mono/EoF
2 (2) [-] interlaced 2 691200 B 5254.779769 5254.791976 24.998 fps ts mono/EoF
3 (3) [-] interlaced 3 691200 B 5254.819759 5254.843601 25.006 fps ts mono/EoF
4 (4) [-] interlaced 4 691200 B 5254.859749 5256.301972 25.006 fps ts mono/EoF
5 (5) [-] interlaced 5 691200 B 5254.899745 5256.353108 25.003 fps ts mono/EoF
6 (6) [-] interlaced 6 691200 B 5254.987939 5256.403868 11.339 fps ts mono/EoF
7 (7) [-] interlaced 7 691200 B 5255.027919 5256.462011 25.013 fps ts mono/EoF
8 (0) [-] interlaced 8 691200 B 5255.112027 5256.515600 11.889 fps ts mono/EoF
9 (1) [-] interlaced 9 691200 B 5255.172025 5256.569657 16.667 fps ts mono/EoF
Captured 10 frames in 2.088578 seconds (4.787945 fps, 3309427.664405 B/s).
8 buffers released.

There are no errors in dmesg.

Any idea what could be wrong?

Thanks!

Answered by awawa-dev

Nov 20, 2022

utv007 support was restored for Linux:
#423

Installers (when the build is finished):
https://github.com/awawa-dev/HyperHDR/actions/runs/3509132610

View full answer

awawa-dev · 2022-11-19T12:38:29Z

awawa-dev
Nov 19, 2022
Maintainer

Hi
From that small fragment of code, seems it cannot detect video modes, not sure if it's related to analog switches (input => pal/ntsc) that were removed long time ago. This grabber was superseded by real digital MS2109 USB2.0 grabber with tag price under $10. I wrote about it 2 years ago so there are new alternative USB models too but nothing has changed on the UTV007 https://www.hyperhdr.eu/2020/11/hyperhdr-prepare-for-building-buying_12.html

0 replies

awawa-dev · 2022-11-19T14:16:40Z

awawa-dev
Nov 19, 2022
Maintainer

I dug my old UTV007 out of the abyss of hell and tested it. If you type v4l2-ctl --list-formats-ext you won't see any available video mode:

and you should see something like that:

So probably it's not a HyperHDR problem.

0 replies

HyperFann · 2022-11-19T16:31:44Z

HyperFann
Nov 19, 2022

I have the same problem, I guess that i'll stick with Hyperion.ng until I buy another USB grabber.

I just want to share that I get this with HyperionNG to :

But it works...

0 replies

awawa-dev · 2022-11-19T16:42:09Z

awawa-dev
Nov 19, 2022
Maintainer

Don't remember exactly my old days using UTV007, but if it works for you (despite v4l2-ctl --list-formats-ext returns nothing) in Hyperion then maybe this device does not report supported resolutions, but still may accept some arbitrary resolutions fixed without any hints by the program or the user. All modern devices report supported resolutions and HyperHDR does not allow you to set something that has not been reported as allowed by the driver as it will not work on new models and will only confuse the user.

0 replies

awawa-dev · 2022-11-20T18:14:05Z

awawa-dev
Nov 20, 2022
Maintainer

utv007 support was restored for Linux:
#423

Installers (when the build is finished):
https://github.com/awawa-dev/HyperHDR/actions/runs/3509132610

0 replies

Uh oh!

UTV007 - Could not find any capture device settings #421

Uh oh!

Uh oh!

Carko Nov 19, 2022

Replies: 5 comments

Uh oh!

Uh oh!

awawa-dev Nov 19, 2022 Maintainer

Uh oh!

awawa-dev Nov 19, 2022 Maintainer

Uh oh!

Uh oh!

HyperFann Nov 19, 2022

Uh oh!

Uh oh!

awawa-dev Nov 19, 2022 Maintainer

Uh oh!

awawa-dev Nov 20, 2022 Maintainer

Carko
Nov 19, 2022

awawa-dev
Nov 19, 2022
Maintainer

awawa-dev
Nov 19, 2022
Maintainer

HyperFann
Nov 19, 2022

awawa-dev
Nov 19, 2022
Maintainer

awawa-dev
Nov 20, 2022
Maintainer