From 8c2ce16f93be0fc1362ab74846b46c9818da14be Mon Sep 17 00:00:00 2001 From: Stefano Sabatini Date: Sun, 22 Jul 2012 11:28:57 +0200 Subject: doc/filter_design: fix a few typos --- doc/filter_design.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/filter_design.txt') diff --git a/doc/filter_design.txt b/doc/filter_design.txt index 4157fd1959..9e3eb3df6c 100644 --- a/doc/filter_design.txt +++ b/doc/filter_design.txt @@ -12,7 +12,7 @@ Format negotiation ================== The query_formats method should set, for each input and each output links, - the list supported formats. + the list of supported formats. For video links, that means pixel format. For audio links, that means channel layout, and sample format (the sample packing is implied by the @@ -26,7 +26,7 @@ Format negotiation references to the list are updated. That means that if a filter requires that its input and output have the - same format amongst a supported list, all it have to do is use a reference + same format amongst a supported list, all it has to do is use a reference to the same list of formats. @@ -70,7 +70,7 @@ Frame scheduling request_frame method or the application. If a filter has several inputs, the filter must be ready for frames - arriving randomly on any input. Therefore, any filter with several input + arriving randomly on any input. Therefore, any filter with several inputs will most likely require some kind of queuing mechanism. It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced. @@ -85,7 +85,7 @@ Frame scheduling For a filter, if there are queued frames already ready, one of these frames should be pushed. If not, the filter should request a frame on - one of its input, repeatedly until at least one frame has been pushed. + one of its inputs, repeatedly until at least one frame has been pushed. Return values: if request_frame could produce a frame, it should return 0; -- cgit v1.2.3