The set looks good to me as well.
lu
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
This allows callers with avio write callbacks to get the bytestream
positions that correspond to keyframes, suitable for live streaming.
In the simplest form, a caller could expect that a header is written
to the bytestream during the avformat_write_header, and the data
output to the avio context
On Sat, 14 May 2016, Luca Barbato wrote:
On 14/05/16 20:32, Martin Storsjö wrote:
.
What I try to mean is "sync point" == keyframe, "parse point" == any
packet boundary, opaque == anything/random/unknown (e.g. if a packet is
cut into multiple write callbacks due to a too small IO buffer, or
On 14/05/16 20:32, Martin Storsjö wrote:
>> .
>
> What I try to mean is "sync point" == keyframe, "parse point" == any
> packet boundary, opaque == anything/random/unknown (e.g. if a packet is
> cut into multiple write callbacks due to a too small IO buffer, or if
> the muxer doesn't mark
On Sat, 14 May 2016, Anton Khirnov wrote:
Quoting Martin Storsjö (2016-05-09 13:34:26)
This allows callers with avio write callbacks to get the bytestream
positions that correspond to keyframes, suitable for live streaming.
In the simplest form, a caller could expect that a header is written
Quoting Martin Storsjö (2016-05-09 13:34:26)
> This allows callers with avio write callbacks to get the bytestream
> positions that correspond to keyframes, suitable for live streaming.
>
> In the simplest form, a caller could expect that a header is written
> to the bytestream during the
On 09/05/16 13:34, Martin Storsjö wrote:
> Better suggestions on the data type names are welcome.
Sounds quite ok, sync_point vs parse_point might enjoy more information
I guess.
lu
___
libav-devel mailing list
libav-devel@libav.org
This allows callers with avio write callbacks to get the bytestream
positions that correspond to keyframes, suitable for live streaming.
In the simplest form, a caller could expect that a header is written
to the bytestream during the avformat_write_header, and the data
output to the avio context
