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
{{ message }}
Repository navigation
camera: C920 defaults to 2560×1472 at 2 FPS instead of 1080p/30 #21
Monologue 0.3.1 automatically selects the largest advertised C920 format, which on this camera is raw YUYV 2560×1472 at 2 FPS. This produces an unusably choppy recording even though the same camera supports 1920×1080 MJPEG at 30 FPS. There is no UI control to select a different camera format.
Environment
Monologue: 0.3.1-1 (Arch Linux package)
OS: Arch Linux, kernel 7.2.11-arch1-1
Camera: Logitech HD Pro Webcam C920 on USB 2.0 (480M), /dev/video4
Capture stack: Qt Multimedia / FFmpeg and PipeWire
Reproduction
Connect a Logitech C920.
Open Monologue and select HD Pro Webcam C920.
Record a short clip using the default automatic camera-format selection.
Monologue should select a practical recording format, for example the C920's 1920×1080 MJPEG at 30 FPS, rather than prioritising resolution alone. Ideally the UI would also allow selecting a camera format.
Actual behavior
Monologue records at 2 FPS. Its log also shows failed hardware-encoder format conversion for the raw source:
The selection appears to come from media::bestFormat() in src/mediautils.cpp: it compares image area before frame rate, so the largest supported format wins unconditionally. The C920's advertised modes include:
YUYV 2560×1472: 2 FPS
MJPEG 1920×1080: 30 FPS
A heuristic that prefers formats able to reach the target frame rate (30 FPS), then reasonable resolution/compressed pixel formats, would avoid this regression.
Same here with a second C920, which advertises a different largest mode (2304×1536 rather than 2560×1472), so this isn't tied to one firmware revision. For me the live preview is already choppy, before recording anything.
The integrated camera on the same machine (Chicony 04f2:b5ab) is fine, because its largest size (1280×720) also has an MJPG 30 fps mode.
Possible fix in media::bestFormat(): first drop formats whose maxFps can't reach a minimum usable rate (say 24 fps, or targetFps(...) < 24). Only fall back to the current area-first ranking if nothing passes, e.g.:
constauto usable = [](const Format &f) { return f.maxFps >= 24; };
constbool anyUsable = std::any_of(formats.begin(), formats.end(), usable);
// in the loop:if (anyUsable && !usable(f)) continue;
On the C920 this picks a 1920×1080 @ 30 mode: MJPG, or the camera's H.264 mode if Qt exposes that one and it sorts first. That would be worth a pixel-format tiebreak preferring MJPG. Cameras whose largest mode is already 30 fps are unaffected, and low-fps-only devices keep today's behaviour. A format/resolution picker in the UI would still be nice, but this default alone would fix it.
Confirming on a third C920 (046d:08e5, max mode 2560×1472 YUYV at 2 fps).
I built Monologue locally with a 15 fps floor plus fallback, the same approach as #19 (and #18, which uses the same floor with a slightly different fallback), and tested it on the camera. Both test suites pass. Monologue now picks MJPEG 1920×1080 @ 30 and records smoothly. My duplicate issue #23 is closed in favour of this one.
At that mode the C920 occasionally sends incomplete frames, which show up in recordings as garbage frames. That's a separate problem, filed as #24, with a driver workaround.
Fixed by #19: camera modes slower than 15 fps are skipped when a smoother one exists, so the C920 now records MJPEG 1920×1080 at 30 fps instead of the 2 fps still size. The garbled-frame problem some of you saw with MJPEG is tracked in #24.
Activity
smarkson commentedon Nov 6, 2026
Same here with a second C920, which advertises a different largest mode (2304×1536 rather than 2560×1472), so this isn't tied to one firmware revision. For me the live preview is already choppy, before recording anything.
Environment
/dev/video2Largest modes the camera advertises (
v4l2-ctl --list-formats-ext)Measured throughput (
ffmpeg -f v4l2 -input_format <fmt> -video_size <size> -framerate 30 -i /dev/video2 -t 4 -f null -)The integrated camera on the same machine (Chicony 04f2:b5ab) is fine, because its largest size (1280×720) also has an MJPG 30 fps mode.
Possible fix in
media::bestFormat(): first drop formats whosemaxFpscan't reach a minimum usable rate (say 24 fps, ortargetFps(...) < 24). Only fall back to the current area-first ranking if nothing passes, e.g.:On the C920 this picks a 1920×1080 @ 30 mode: MJPG, or the camera's H.264 mode if Qt exposes that one and it sorts first. That would be worth a pixel-format tiebreak preferring MJPG. Cameras whose largest mode is already 30 fps are unaffected, and low-fps-only devices keep today's behaviour. A format/resolution picker in the UI would still be nice, but this default alone would fix it.
RemyDuijkeren commentedon Nov 7, 2026
Confirming on a third C920 (046d:08e5, max mode 2560×1472 YUYV at 2 fps).
I built Monologue locally with a 15 fps floor plus fallback, the same approach as #19 (and #18, which uses the same floor with a slightly different fallback), and tested it on the camera. Both test suites pass. Monologue now picks MJPEG 1920×1080 @ 30 and records smoothly. My duplicate issue #23 is closed in favour of this one.
At that mode the C920 occasionally sends incomplete frames, which show up in recordings as garbage frames. That's a separate problem, filed as #24, with a driver workaround.
dhh commentedon Nov 12, 2026
Fixed by #19: camera modes slower than 15 fps are skipped when a smoother one exists, so the C920 now records MJPEG 1920×1080 at 30 fps instead of the 2 fps still size. The garbled-frame problem some of you saw with MJPEG is tracked in #24.