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
moq-gst moqsrc: fixed 1 s consumer latency and frames lost at the first frame of a GOP #7326
The latency budget of moq_mux::container::Consumer is hard-coded to 1 s and cannot be changed through an element property, caps or environment. Anyone using moqsrc with a publisher that has a different delivery latency, or a network that occasionally delays groups, cannot choose the trade-off between delay and tolerance. Consumer::set_latency exists (rs/moq-mux/src/container/consumer.rs:582) but moqsrc does not expose it.
Proposal: a latency property (ms) on moqsrc, default 1000 so the current behaviour does not change.
2. Frames lost at the first frame of a GOP
Observation: with H.264 1080p50 video, 4 streams in parallel, a lossless local network and a 600 s run, moqsrc skips between 1 and 26 frames per stream roughly every 10 minutes; the gap always starts at the first frame (keyframe) of a GOP. Raising the consumer budget to 10 s makes the same run lose no frames (0 gaps).
Suspicion: under load, a group that arrives beyond the budget is skipped (consumer.rs:360 and :372, rule max_timestamp - next_start >= latency) exactly when its first frame is the oldest one available, and the rest of the group, now without its keyframe, cannot be decoded.
Questions:
Is skipping a group for exceeding the budget intended even when it is the only group in flight and about to complete?
Can the current group be kept when its first frame has already been partially delivered?
A reproduction (script and per-stream gap count) is available if useful.
#7084 - feat(gst): moqsrc takes a max-delay [open]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Oct 30, 2026
🔗 Related PRs
#7084 - feat(gst): moqsrc takes a max-delay [open]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
davidegiudice commentedon Oct 30, 2026
Thanks, this is covered by #7084 (moqsrc
max-delayproperty), so closing this one as a duplicate.