summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorOlivier Crete <tester at tester.ca>2009-04-14 18:16:37 +0200
committerWim Taymans <wim.taymans@collabora.co.uk>2009-04-14 18:21:45 +0200
commitc628641880d9b0a1c7dacd2be8e67ecd47754d4e (patch)
tree900715785013b302cbc3e87ea353e050e0589823 /docs
parentd0c36826278182b3bd986e6efafd65434127e26b (diff)
theoraenc: implement upstream keyframe force
Implement handling of upstream keyframe forcing. Update the design documents too. Fixes #578656
Diffstat (limited to 'docs')
-rw-r--r--docs/design/draft-keyframe-force.txt17
1 files changed, 16 insertions, 1 deletions
diff --git a/docs/design/draft-keyframe-force.txt b/docs/design/draft-keyframe-force.txt
index d315e8dd..c1d408a0 100644
--- a/docs/design/draft-keyframe-force.txt
+++ b/docs/design/draft-keyframe-force.txt
@@ -48,7 +48,7 @@ Implementation:
triggered the event.
(G_TYPE_UINT64)"stream-time" : the stream position that triggered the
event.
- (G_TYPE_UINT64)"running_time" : the running time of the stream when the
+ (G_TYPE_UINT64)"running-time" : the running time of the stream when the
event was triggered.
.... : optional other data fields.
@@ -70,3 +70,18 @@ Implementation:
3) The application receives the GstForceKeyUnit on a sink padprobe of the sink
and reconfigures the sink to make it perform new actions after receiving
the next buffer.
+
+
+Upstream
+--------
+
+When using RTP packets can get lost or receivers can be added at any time,
+they may request a new key frame.
+
+An downstream element sends an upstream "GstForceKeyUnit" event up the
+pipeline.
+
+When an element produces some kind of key unit in output, but has
+no such concept in its input (like an encoder that takes raw frames),
+it consumes the event (doesn't pass it upstream), and instead sends
+a downstream GstForceKeyUnit event and a new keyframe.