Hi everyone,
I am testing the RunCam WiFiLink 1/2 (SSC338Q + IMX415) and trying to achieve 720p@120fps streaming via wfb-ng using the H.264 codec.
The sensor configuration seems to read 120fps properly (and it records 120fps to the SD card), but the live stream received on the ground station is strictly hard-locked at 60fps. Even after completely disabling the sub-stream (video1: enabled: false), reducing the resolution to test, and optimizing majestic.yaml, it won't push past 60fps on H.264.
However, when I switch the codec to H.265, 720p@120fps works perfectly fine.
Is this a hardwired hardware limitation inside the SigmaStar SSC338Q's H.264 encoder block itself? Or is there a firmware/driver level FPS cap (like in the binary ISP driver) that we can tweak or modify in the kernel/builder?
Any advice or insights on how to bypass this limitation for H.264 would be highly appreciated. Thank you!
Hi everyone,
I am testing the RunCam WiFiLink 1/2 (SSC338Q + IMX415) and trying to achieve 720p@120fps streaming via wfb-ng using the H.264 codec.
The sensor configuration seems to read 120fps properly (and it records 120fps to the SD card), but the live stream received on the ground station is strictly hard-locked at 60fps. Even after completely disabling the sub-stream (video1: enabled: false), reducing the resolution to test, and optimizing majestic.yaml, it won't push past 60fps on H.264.
However, when I switch the codec to H.265, 720p@120fps works perfectly fine.
Is this a hardwired hardware limitation inside the SigmaStar SSC338Q's H.264 encoder block itself? Or is there a firmware/driver level FPS cap (like in the binary ISP driver) that we can tweak or modify in the kernel/builder?
Any advice or insights on how to bypass this limitation for H.264 would be highly appreciated. Thank you!