diff options
| author | Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> | 2012-04-30 09:58:09 +0100 |
|---|---|---|
| committer | Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> | 2012-04-30 09:58:09 +0100 |
| commit | 477636479cc0171a3a3fad4a5c17ac47e39cd7e6 (patch) | |
| tree | 895758d14524469c15c8bce7e6ec261eb119cc64 /docs/design/part-seeking.txt | |
| parent | e75f68ea57e7a6691749b4f12120391628cfb8d8 (diff) | |
event: add new seek snap flags
They can be used to select snapping behavior (to previous, next, or
nearest location, where relevant) when seeking.
The seeking implementation (eg, demuxer) may currently ignore some
or all of these flags.
Diffstat (limited to 'docs/design/part-seeking.txt')
| -rw-r--r-- | docs/design/part-seeking.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/design/part-seeking.txt b/docs/design/part-seeking.txt index 38bb33cc58..ee97acf91d 100644 --- a/docs/design/part-seeking.txt +++ b/docs/design/part-seeking.txt @@ -174,6 +174,12 @@ implemented demuxer/parser-side, e.g. make demuxers/parsers ignore the KEY_UNIT flag if the position adjustment would be larger than 1/10th of the duration or somesuch. +Flags can be used to influence snapping direction for those cases where it +matters. SNAP_BEFORE will select the preceding position to the seek target, +and SNAP_AFTER will select the following one. If both flags are set, the +nearest one to the seek target will be used. If none of these flags are set, +the seeking implemention is free to select whichever it wants. + Summary: - if the KEY_UNIT flag is *not* specified, the demuxer/parser should |