design: Fix typos in docs

This commit is contained in:
ekwange 2019-08-14 14:13:08 +09:00
parent 1a046968d6
commit 9aa5afb7a5
4 changed files with 7 additions and 7 deletions

View file

@ -43,7 +43,7 @@ mode). `activate_mode(PULL)` is then responsible for starting the task
that pulls from fakesrc:src. Clearly, fakesrc needs to be notified that that pulls from fakesrc:src. Clearly, fakesrc needs to be notified that
fakesrc is about to pull on its src pad, even though the pipeline has fakesrc is about to pull on its src pad, even though the pipeline has
not yet changed fakesrcs state. For this reason, GStreamer will first not yet changed fakesrcs state. For this reason, GStreamer will first
call call `activate_mode(PULL)` on fakesink:sinks peer before calling call `activate_mode(PULL)` on fakesink:sinks peer before calling
`activate_mode(PULL)` on fakesink:sinks. `activate_mode(PULL)` on fakesink:sinks.
In short, upstream elements operating in PULL mode must be ready to In short, upstream elements operating in PULL mode must be ready to

View file

@ -96,7 +96,7 @@ operation will eventually block when the ringbuffer is filled.
When no samples arrive in time, the ringbuffer will play silence. Each When no samples arrive in time, the ringbuffer will play silence. Each
buffer that arrives will be placed into the ringbuffer at the correct buffer that arrives will be placed into the ringbuffer at the correct
times. This means that dropping samples or inserting silence is done times. This means that dropping samples or inserting silence is done
automatically and very accurate and independend of the play pointer. automatically and very accurate and independent of the play pointer.
In this mode, the ringbuffer is usually kept as full as possible. When In this mode, the ringbuffer is usually kept as full as possible. When
using a small buffer (small segsize and segtotal), the latency for audio using a small buffer (small segsize and segtotal), the latency for audio

View file

@ -63,7 +63,7 @@ This policy allows for parents to iterate their children and setting
properties on them. properties on them.
Whenever a nested lock needs to be taken on objects not involved in a Whenever a nested lock needs to be taken on objects not involved in a
parent-child relation (eg. pads), an explictic locking order has to be parent-child relation (eg. pads), an explicit locking order has to be
defined. defined.
## Path Generation ## Path Generation

View file

@ -24,16 +24,16 @@ When going to `PAUSED` and `PLAYING` a buffer should be queued in the pad.
We also make this a requirement for going to `PLAYING` since a flush event We also make this a requirement for going to `PLAYING` since a flush event
in the `PAUSED` state could unqueue the buffer again. in the `PAUSED` state could unqueue the buffer again.
The state is commited in the following conditions: The state is committed in the following conditions:
- a buffer is received on a sinkpad; - a buffer is received on a sinkpad;
- an GAP event is received on a sinkpad; - a GAP event is received on a sinkpad;
- an EOS event is received on a sinkpad. - an EOS event is received on a sinkpad.
We require the state change to be commited in EOS as well, since an EOS We require the state change to be committed in EOS as well, since an EOS
, by definition, means no buffer is going to arrive anymore. , by definition, means no buffer is going to arrive anymore.
After the state is commited, a blocking wait should be performed for the After the state is committed, a blocking wait should be performed for the
next event. Some sinks might render the preroll buffer before starting next event. Some sinks might render the preroll buffer before starting
this blocking wait. this blocking wait.