You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any way to force v4l2 to a specific resolution? When testing my hdmi input via a tv i get the correct resolution of either 1280x720 (16:9) and once it is plugged into the card it goes to 720/576 (4:6).
I have tried to use v4l2-ctl -d 4 --set-fmt-video=width=1280,height=720,pixelformat=YUYV but this does not change anything.
Format Video Capture:
Width/Height : 720/576
Pixel Format : 'YUYV' (YUYV 4:2:2)
Field : Interlaced
Bytes per Line : 1440
Size Image : 829440
Colorspace : Rec. 709
Transfer Function : Default (maps to Rec. 709)
YCbCr/HSV Encoding: Default (maps to Rec. 709)
Quantization : Default (maps to Limited Range)
Flags :
The text was updated successfully, but these errors were encountered:
Hi. The v4l2 driver HDMI input format detection is not affected by set video format. The current detection tries to match the HDMI raster to a format supported by the internal video bus. If the raster or frequency of the input signal are not close it can get it wrong. What are you using for a source? There first 2 HDMI inputs of the KonaHDMI use different hardware than the second 2 inputs so if the first 2 input do not detect the signal correctly try the other inputs.
The source is a STB via component to hdmi. (HDCP was giving me grief going straight from hdmi to hdmi)
Plugged into a tv the resolution gets set correctly.
I have tried Port 1 and Port3 and both return the same resolution.
Is there a way to hardcode what resolution it uses?
Is there any way to force v4l2 to a specific resolution? When testing my hdmi input via a tv i get the correct resolution of either 1280x720 (16:9) and once it is plugged into the card it goes to 720/576 (4:6).
I have tried to use
v4l2-ctl -d 4 --set-fmt-video=width=1280,height=720,pixelformat=YUYV
but this does not change anything.The text was updated successfully, but these errors were encountered: